Creating the JES2 cataloged procedure

To start the JES2 component, you must provide a subsystem cataloged JCL procedure (PROC). The PROC name can be a maximum of four characters. For other naming restrictions, see z/OS MVS JCL User's Guide. Before IPL, define the PROC in the IEFSSNxx member(s) of SYS1.PARMLIB.

Instead of a distributed JES2 procedure, IBM® provides the sample member 'HASIPROC' in the SYS1.SHASSAMP data set. 'HASIPROC' is a sample JCL procedure that should be tailored, renamed, and moved to the production JCL procedure library for use as the JES2 subsystem JCL (the procedure specified on a START command to start JES2).

The basic JES2 procedure ( Figure 1) contains an EXEC statement and five data definition (DD) statements named PROC00, PROC01, HASPLIST, HASPPARM and STEPLIB. PROC00 defines a default procedure library to be used for converting the JCL of batch jobs, time-sharing logons, and system tasks. HASPLIST defines what is normally a dummy output data set, but you can modify this statement to permanently point to a specific device or data set. Also, you can use the START command facilities to generate a IEFRDER statement to override the HASPLIST statement.

The following parameters on the EXEC statement deserve mentioning:

PGM=: Specify the name of the JES2 load module. (It must reside in an authorized library.)
TIME=: Specify 'NOLIMIT' or 1440 to prevent system ABEND code 322 (CPU time limit exceeded).
REGION=: Typically, do not code this parameter (or specify REGION=0M) to prevent any virtual storage restriction on the JES2 address space.
PERFORM=: Specify a unique performance group for tracking JES2 resources through RMF™.
PARM=: Specify 'Warm,NOREQ' for the start parameters in the JES2 procedure. If necessary you can override these parameter specifications on the 'S JES2' command. See Specifying the Start Options.

Figure 1. The Basic JES2 Procedure

//JES2         PROC N=SYS1,L=SHASLNKE,
//                  M=JES2PARM,PN=SYS1,PL=PARMLIB,U=
//                  PROC00='SYS1.PROCLIB',PROC01='SYS1.PROCLIB'
//IEFPROC      EXEC PGM=HASJES20,TIME=1440,PARM=(WARM,NOREQ)
//HASPLIST  *  DD DDNAME=IEFRDER
//HASPPARM     DD UNIT=&U,DSN=&PN;.&PL(&M),DISP=SHR
//PROC00       DD DSN=&PROC00,DISP=SHR
//PROC01       DD DSN=&PROC01,DISP=SHR
//STEPLIB      DD DSN=&N;.&L,DISP=SHR

*: The MVS™ message, IEC130I HASPLIST DD STATEMENT MISSING, will be issued if this DD name is not included here.

You can change the JES2 procedure by entering updates with a TSO/E editor such as SPF or the IBM IEBUPDTE utility program. You can add DD statements to the JES2 procedure to define:

Other cataloged procedure libraries that are associated with job classes by the JOBCLASS initialization statement or by the /*JOBPARM JES2 control statement.
IBM suggests using PROCLIB statements instead of changing the JES2 PROC.

Each library should be defined by a PROCnn DD statement. For instance, to specify a special library for TSO/E logons, code PROCLIB=nn (where nn corresponds to the associated PROCnn DD statement) in the JOBCLASS(TSU) initialization statement.
One or more initialization data sets that define different conditions and types of workloads. See Figure 1 for an example of an updated JES2 procedure.

IBM suggests that you specify DDNAMEs in the format of PARMxxxx when defining installation parameter libraries in the JES2 procedure. After initialization, JES2 automatically unallocates data sets that have a DDNAME of HASPLIST, HASPPARM, or PARMxxxx. By unallocating these data sets, installations can dynamically delete the devices on which these data sets reside.