Normal production jobs

HCL Workload Automation for Z submits production jobs to the internal reader, or starts started tasks, when all prerequisites are met. HCL Workload Automation for Z first attempts to find jobs in the JS file. If no job is found, it keeps searching in the following order:
  • Partitioned data set indicated by the JOBLIBRARY operation user field, if specified. If no job is found, an error message is issued.
  • Job-library-read exit (EQQUX002), if loaded. If no job is found, it searches the EQQJBLIB partitioned data set concatenation.
  • EQQJBLIB partitioned data set concatenation, if the JOBLIBRARY user field and EQQUX002 are not specified.
You can determine the authority given to a job or started task by the following ways:
  • Submitting work with the authority of the HCL Workload Automation for Z address space. The job or started task is given the same authority as the controller or tracker whose submit subtask actually submits the work. For example, work that is transmitted from the controller and then submitted by the tracker is given the authority of the tracker.
  • Using the user field name SUBJOBUSER, specified at operation level, to cause any kind of jobs to be submitted with a specified user ID. If you use this method, it is preferred over using the job-submit exit EQQUX001.

    The user field name SUBJOBUSER must always be uppercase. The user field value cannot be longer than 8 characters and cannot contain blanks: if you specify a value longer than 8 characters it is truncated; if you specify a value containing a blank, the characters after the blank are not considered.

  • Using the job-submit exit, EQQUX001. This exit is called when HCL Workload Automation for Z is about to submit work.
    • You can use the RUSER parameter of the EQQUX001 exit to cause the job or started task to be submitted with a specified user ID. The RUSER name is supported even if the job or started task is first sent to a tracker before being started.
    • In certain circumstances you might need to include a password in the JCL to propagate the authority of a particular user. You can use the job-submit exit (EQQUX001) to modify the JCL and include a password. The JCL is saved in the JCL repository (JSn) data set before the exit is called, thus avoiding the need to store JCL with specific passwords. This method prevents the password from being visible externally. For more information about the job-submit exit, see Job-submit exit (EQQUX001).