When placing a checkpoint data set on a coupling facility structure for the first time, IBM® suggests defining the JES2 checkpoint on a secondary JES2 (preferably a test system). Starting the checkpoint on a secondary JES2 ensures connectivity to the coupling facility and allows you to verify the accuracy of the coupling facility resource management (CFRM) policy definition. Then you can use the checkpoint reconfiguration dialog to forward the primary JES2 member's checkpoint data set onto the coupling facility structure. To start a JES2 member with a checkpoint data set residing on a coupling facility structure for the first time, use the following procedures:

1. Ensure that you have followed the instructions for predefining a coupling facility resource management (CFRM) policy as described in Defining JES2 structures in a CFRM policy.
2. Start a primary JES2 member as described in Starting JES2 for the first time (a cold start).

   Note the number of 4K records specified on the $HASP537.

3. Cold start a secondary JES2 member with the checkpoint defined on a coupling facility structure, using the STRNAME= subparameter instead of the DSNAME= and VOLSER= subparameters on the CKPTDEF initialization statement. Follow the directions provided in Defining a secondary JES2 member to MVS.
   Ensure that the secondary member's JES2 definitions match those of the primary JES2 member for the following initialization parameters that define the checkpoint data set:

   • SPOOLNUM= and TGSPACE=(MAX=) on the SPOOLDEF initialization statement
   • JOBNUM= on the JOBDEF initialization statement
   • JOENUM= on the OUTDEF initialization statement
   • BERTNUM= on the CKPTSPACE initialization statement.
   • NODENUM= on the NJEDEF initialization statement.
4. If problems occur when initializing the JES2 secondary, see both Correcting a structure error of size and Correcting a structure error of incorrect attributes.
5. When JES2 is fully operational (after you receive the $HASP400 message), verify that the coupling facility structure has been allocated by using the $D CKPTDEF command to display the status of all defined JES2 checkpoint data sets.
6. After you have completed testing the checkpoint on a coupling facility, bring down the secondary JES2 member and invoke the JES2 reconfiguration dialog through operator command to forward the checkpoint data set to the coupling facility.

   For complete instructions on how to use the checkpoint reconfiguration dialog, see Operator-initiated entrance into a checkpoint reconfiguration dialog.