Flow of Control

When the name of a request starts with UX, TWS Automation assumes that the request is not related to a subsystem known to SA z/OS.

As before, it expects to find an OPCACMD entry within a policy object that is identified through the Job name field of the TWS operation. However, if no match is found for USER E-T pair 'OPCACMD jobname', then TWS Automation will check for USER E-T pair 'OPCACMD OPCA', and if again no match is found, TWS Automation will check for USER E-T pair 'OPCACMD subsystem'. Although user exit processing is designed to be non-subsystem related, this approach provides flexibility for users who have jobnames that do not match subsystems names but still prefer subsystem-related processing. There are however two differences compared to subsystem-related requests:

• The only keyword that is needed is OPCACMD. OPCA and OPCAPARM are ignored.The CMD attributes of the OPCACMD entry should have the following format:

  CMD=(UXxxxxxx,,'userfunc &EHKVAR1')

  For &EHKVAR1, see Parameters Passed to a User Exit.
• The policy object identified through the Job name field of the TWS operation should be a USER E-T pair (see OPCACMD).

For non-subsystem requests, TWS Automation immediately tries to issue the command specified in the OPCACMD entry. After issuing the command, the request module of TWS Automation terminates. It is up to the user function to determine whether or not the request was executed successfully. The user function should then call OPCAPOST (see OPCAPOST) with the corresponding completion code. This returns the control of the application processing to TWS. The samples contain a code template for a non-subsystem command (EVJERUX1).