Setting Up Extended Recovery for a IBM Connect:Direct/Stand-Alone Server

To configure a IBM® Connect:Direct®/Stand-alone Server to use extended recovery, follow this procedure.

  1. Specify the XCF.NAME in the initialization parameters file. The XCF.NAME is a unique 8-character string that identifies a IBM Connect:Direct/Stand-alone Server using extended recovery.

    The following example shows a IBM Connect:Direct/Stand-alone Server assigned the XCF.NAME of MNPLS.

    XCF.NAME=MNPLS
    Note: XCF group names cannot begin with the letters A through J or with the letters SYS because these are reserved by IBM.
  2. Add the following parameter to the initialization parameters file.
    EXTENDED.RECOVERY=YES
  3. Add the XRFJOB DD statement to the IBM Connect:Direct startup JCL as follows.
    //XRFJOB DD DISP=SHR,DSN=$CD.SDGAJCL(CDJOBX)

    $CD.SDGAJCL is the PDS where the active (current) IBM Connect:Direct startup JCL is located. The CDJOBX member is the standby IBM Connect:Direct startup JCL or startup command to run as a started task, which will be created later.

  4. To run as a started task, use one of the following, or skip to step 5 if you are not running as a started task.
    • To run the IBM Connect:Direct standby image as a started task on the same z/OS image as the IBM Connect:Direct active image, use the following as the first statement in the JCL.
      START=membername,parms

      In this example, START= indicates to issue a START command. When the START command is issued, the equal sign (=) is replaced with a blank, and the entire statement is passed to z/OS as a command.

      For example, if START=HOSTJCL,X is the first statement, then START HOSTJCL,X is issued to z/OS.

    • To run the IBM Connect:Direct standby image as a started task on an z/OS image in the sysplex that is not the IBM Connect:Direct active image, use the following as the first statement in the JCL.
      /*$VS,‘command'

      Where command is the command you want the Job Entry Subsystem (in this case, a JES2 environment) to send to z/OS. Because the statement does not begin with START=, IBM Connect:Direct submits the statement to JES. JES identifies the /*$VS and issues the command to z/OS rather than placing it in the job queue.

      For example, if /*$VS,‘RO CSGB,S CDICOMB' is submitted in the JCL, the

      RO CSGB,S CDICOMB command is issued rather than placed in the job queue.

  5. Copy the IBM Connect:Direct startup JCL to the CDJOBX member if you are submitting the JCL.
  6. Change the job name in CDJOBX so that it runs simultaneously with the active IBM Connect:Direct image. (Both the active IBM Connect:Direct image and the standby IBM Connect:Direct image run at the same time.)
  7. Change the XRFJOB DD statement in the standby IBM Connect:Direct startup JCL to reference the IBM Connect:Direct startup JCL or command to run as a started task, as in the following example (where CDJOB is replaced by the member name that actually has your IBM Connect:Direct JCL).
    //XRFJOB DD DISP=SHR,DSN=$CD.SDGACNTL(CDJOB)
  8. Submit the CDJOB JCL to bring up IBM Connect:Direct using extended recovery.

    After IBM Connect:Direct initializes, the JCL specified in the startup JCL initializes the standby IBM Connect:Direct system. The standby IBM Connect:Direct image partially initializes, then begins monitoring the active IBM Connect:Direct image.

    If the active IBM Connect:Direct image terminates abnormally, the standby IBM Connect:Direct image resumes initialization, becomes the active IBM Connect:Direct image, and submits the JCL in its XRFJOB DD statement. This JCL initializes the original active IBM Connect:Direct image, which now becomes the standby system.

    If the active IBM Connect:Direct image shuts down normally, the standby IBM Connect:Direct image also terminates normally.