Installing a JES2 secondary subsystem

The following steps show how an installation might install a secondary subsystem. The assemblies and link edits can be accomplished by using the System Modification Program/E (SMP/E) (see SMP/E for z/OS User's Guide for a description of this technique) or by using your own JCL. Examples of assembly and link edit procedures are provided in the HASIBLD member of the JES2 distribution library.

Note that JESA (the secondary member) must be added to a IEFSSNxx member of SYS1.PARMLIB.

Create a JESA PROC, which defines the secondary JES2's parmlib as 'JESPARM'. For example:
Figure 1. Example JESA PROC
```
  //JESA      PROC   M=JESAPARM,U=3380,L=LINKLIB,N=SEC,
  //                 V=SYSRES
  //IEFPROC   EXEC   PGM=HASJES20,TIME=1440
  //STEPLIB   DD     UNIT=3380,VOL=SER=&V,DISP=SHR,
  //                 DSN=&N;.&L;
  //PROC00    DD     DSN=SYS1.PROCLIB,DISP=SHR
  //HASPPARM  DD     DSN=&SYS1;&PARMLIB;(&M),DISP=SHR,UNIT=&U ^*
  //HASPLIST  DD     DDNAME=IEFRDER
```
Note: Libraries specified in the JES2 procedure must be referenced in one of the following ways:
- Cataloged in the master catalog (or in a user catalog, provided the data set has a high-level qualifier other than SYS1)
- Specify UNIT= and VOL= on the JCL DD statement
- Managed by SMS (UNIT= and VOL= on the JCL DD statement are ignored.)
Create load modules in a separate, APF-authorized library. This library should be cataloged in the master catalog. For more information on how to perform this task, see z/OS MVS Initialization and Tuning Reference.
If the checkpoint data set(s) resides on a direct access storage device (DASD), specify them through the DSNAME= and VOLSER= subparameters on the CKPTn= parameters of the CKPTDEF initialization statement. If the checkpoint data set(s) resides on a Coupling facility structure, specify the structures through the STRNAME= subparameter on the CKPTn= parameters of the CKPTDEF initialization statement.
When the checkpoint data sets reside on DASD, they are often named SYSn.JESCKPT1 and SYSn.JESCKPT2, where 'n' represents any number from 0-9.

A checkpoint data set on a Coupling facility structure must refer to a predefined structure. For an example of the definitions necessary for JES2 checkpoints on Coupling facilities, see Placement of the checkpoint data set. For checkpoints residing on a Coupling facility structure, IBM® suggests using a name without a period, such as SYSn_J2WRKCKPT1 and SYSn_J2WRKCKPT2, to differentiate from DASD.
Allocate a spool data set, using the name SYSn.HASPACE, and place it on a particular volume (many use SECJ2, but the volume name is optional).
Specify options to the primary JES2 member when it enters initialization.
If you intend to use a functional subsystem (FSS), add or modify any cataloged procedures for functional subsystems thatrun under the secondary subsystem. Ensure that the correct version of the HASPFSSM load module is used.
The internal START command that JES2 uses to start a functional subsystem (FSS) cannot contain variable operands to specify STEPLIB information. Therefore, if multiple versions of the JES2 are maintained in separate libraries, you might need to maintain multiple versions of the FSS cataloged procedure(s) and vary the PROC= keyword of the FSS initialization statement.
Issue an 'S JESA' MVS™ command when the primary member is active.

The secondary JES2 proclib member (referred to as 'JESA' on the MVS START command) points to the JES2 initialization data set that defines the primary checkpoint data set to a Coupling facility structure and allocates the secondary checkpoint to a DASD volume. The following is an example of the initialization statements:

    CKPTDEF    CKPT1=(STR=SYS1_WRKCKPT1,INUSE=YES)
               CKPT2=(DSN=SYS1.JESCKPT2,VOL=SECJ2,INUSE=YES)
    SPOOLDEF   VOLUME=SECJ2
    CONDEF     CONCHAR=/
    .
    .
    .

To execute this procedure and obtain a listing of the initialization deck for secondary subsystem JESA on printer 00E, enter the following command:

S   JESA,UNIT=00E,