z/OS TSO/E Customization
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF

Customizing how users submit jobs and process the output

z/OS TSO/E Customization

After you have changed the defaults for how TSO/E jobs are processed, you can use exits and RACF® resource classes to customize the way TSO/E users submit jobs and process the output. For example, you can customize JCL statements, cancel jobs or job output, or allow users to process output from jobs other than their own.

In addition to using the TSO/E SUBMIT and the TSO/E OUTPUT, STATUS and CANCEL exits to customize the way users submit jobs and process the output, you can use JES and SMF. With RACF installed, you can also use the RACF resource classes, JESSPOOL, JESJOBS, and SURROGAT.

In general, you can use JES and SMF exits to perform the same processing as the TSO/E SUBMIT, and OUTPUT, STATUS, CANCEL exit routines.

With RACF installed, you can use the RACF resource class, JESSPOOL, to protect against unauthorized spool access of the SYSOUT data sets for the TSO/E OUTPUT command, and JESJOBS to control who can submit and cancel jobs by job name. For more information about the RACF resource classes, JESSPOOL and JESJOBS, see .

With RACF installed, users can be defined to the RACF SURROGAT class. Jobs submitted by surrogate users can be cancelled and/or viewed by surrogate users without knowing the user's password. For more information about submitting a job as a surrogate user, see z/OS® Security Server RACF General User's Guide. For more information about setting up the RACF SURROGAT class, see .

This topic will help you decide which type of exit to use and explains how to use the TSO/E SUBMIT exit (IKJEFF10) and the TSO/E OUTPUT, STATUS, CANCEL exit (IKJEFF53). For information about specific JES and SMF exits you can use, see Overview of facilities for customizing TSO/E.

The type of exit you use—TSO/E, JES, or SMF—depends on:
  • Whether you want to tailor only the jobs TSO/E users submit, or all jobs, including TSO/E jobs
  • The information you must access. For example, to access the job queues, use a JES exit.
  • When in the job processing cycle you want to get control.
To customize only the jobs TSO/E users submit, use either the TSO/E SUBMIT exit or the TSO/E OUTPUT, STATUS, CANCEL exit. Those exits run in the user's address space. It is more convenient to access user-related information, such as logon information in the RACF data base, from that address space.

To customize the way all jobs and their output are processed, use JES or SMF exits. For example, you can use JES or SMF exits to tailor the processing the system does for jobs submitted via ISPF/PDF, external readers, or TSO/E users.

The JES exits run in either the JES2 or JES3 address space, or in the submitted job's address space. Use JES exits to access JES information, such as the job queues. Most SMF exits run in the submitted job's address space. To access accounting information, use an SMF exit.

To avoid using more resources than necessary, you should perform a task as early in the processing cycle as possible. For example, because the TSO/E SUBMIT exit gets control before any JES or SMF exits, it is more efficient to cancel a job using the TSO/E SUBMIT exit instead of using a JES or SMF exit. Most of the JES exits receive control before data sets and devices have been allocated. Most SMF exits receive control after data sets and devices have been allocated, and just before and during job execution.

You can use a combination of exit types to perform a task. For example, you can use the TSO/E SUBMIT exit to access information associated with a user's address space and store the information in the job's JCL as a control statement. You can then use a JES exit to process the information. You should be careful, however, that an exit does not nullify the processing another exit performed.

For more information about JES2, JES3, and SMF exits, see:

Go to the previous page Go to the next page

Copyright IBM Corporation 1990, 2014