Example

In the following example, you start from an existing setup with the CA Endevor® SCM RAM, using the CRASTART startup method, and add the sample PDS RAM.

Definitions for the CA Endevor® SCM RAM:
  • FEL.SFELVSM2(CRA0VCAD): CRADEF definitions
  • FEL.SFELVSM2(CRA0VCAS): CRASTRS definitions
  • /etc/zexpl/crastart.endevor.conf: CRASTART configuration file
Definitions for the PDS RAM:
  • FEL.SFELVSM2(CRA0VDEF): CRADEF definitions
  • FEL.SFELVSM2(CRA0VSTR): CRASTRS definitions
  • FEL.#CUST.CRARAM1: CRARAM1 definitions
The process starts with a RAM developer gathering the data and information needed by the system programmer to complete the setup.
  1. Extract the data that is specific for the PDS RAM from the SFELVSM2 members. These members hold definitions for all sample RAMs, not just the PDS RAM.
  2. Merge this data with the CA Endevor® SCM RAM SFELVSM2 members.
  3. Create a list of PDS RAM-specific prerequisites:
    • DD CRARAM1, linked to FEL.#CUST.CRARAM1
    • TSO environment
The system programmer then uses this data to create the updated CARMA VSAM data sets and uses the prerequisite information to create a CRASTART configuration file that is capable of supporting both RAMs.
  1. Use the combined data as input for the CRA$VDEF and CRA$VSTR jobs to create the updated CARMA configuration and custom information VSAM data sets, CRADEF and CRASTRS. The CRAMSG VSAM is specific for the CARMA server, and thus identical for both RAMs.
  2. Add a CRARAM1 definition to crastart.endevor.conf: 
    CRARAM1 = FEL.#CUST.CRARAM1
  3. Verify the PROGRAM statement in crastart.endevor.conf to ensure that it is capable of providing the environment needed by both RAMs.
  4. PROGRAM=IKJEFT01 %CRANDVRA NDVRC1 PGM(CRASERV) 
  PARM(&CRAPRM1. &CRAPRM2.)
    • IKJEFT01: TSO, used to allow certain authorized calls in a non-authorized environment, and used as environment to run the CA Endevor® SCM RAM pre-allocation exec.
    • %CRANDVRA: CA Endevor® SCM RAM pre-allocation exec, located in FEL.SFELPROC, that allocates temporary user-specific working data sets.
    • NDVRC1: CA Endevor® back end, which has a built-in mechanism to execute TSO and ISPF commands.
    • PGM(CRASERV): Command to start a CARMA server, in ISPF command format.
    • PARM(&CRAPRM1. &CRAPRM2.): Parameters for CRASERV, in ISPF command format. &CRAPRM1 is the port to be used and &CRAPRM2 is the timeout value.

The CA Endevor® SCM RAM is active in an ISPF environment, which implies that the TSO environment required by the PDS RAM is also available.