How do you submit a process with a user ID that is different from the one within the configuration of the File Agent?
Connect:Direct Windows with File Agent
Connect:Direct z/OS on remote site
The PNODEID is used within the process, but the submitter at remote site remains the one defined within the File Agent configuration.
For transfers from Connect:Direct Windows, the submitter ID is passed in the destination id token (DUID) of the FMH72, unless a SNODEID is specified. The PNODEID is set in the OUID token. The Secure point of entry (SPOE) processing in Connect:Direct for z/OS is done against the value taken from the DUID token. So the submitter ID, rather than the PNODEID, is checked against the Connect:Direct for z/OS Auth file entry. The File Agent behaves the same.
The only way to get SPOE to check for user ID testuser, would be to specify this on the SNODEID and set the Connect:Direct for z/OS init parm: INVOKE.SPOE.ON.SNODEID = YES
that is, SNODEID=(testuser) No password is needed in the SNODEID .
Note: Setting the INVOKE.SPOE.ON.SNODEID = YES init parm will affect all incoming transfers to Connect:Direct for z/OS that use SNODEID, so this might not be an acceptable solution.
Another solution might be to create a different rule for the files that must be sent to the mainframe by user ID testuser. The process submitted for these files should contain a run task that submits a script. In the script you call direct.exe passing the user ID testuser and submit the process to copy the file to the mainframe.
Writing processes or scripts is not covered by support. However, consider the following:
1. Try to provide the process arguments as they are to the first process with the run task.
2. Within the run task of that process, you would provide the arguments to the script.
3. The script would need to get written in a way to provide the arguments to the further process.
For information about Adding a Run Task Statement, see: