Previous Topic: About This AppendixNext Topic: Installing CA IDMS VSAM Transparency in the CICS Environment


z/OS Installation

Steps to Follow

To install CA IDMS VSAM Transparency under z/OS, complete the following steps:

  1. Install the CA IDMS VSAM Transparency software into the CA IDMS/DB library by using integrated installation procedures. These procedures are described in CA IDMS Installation and Maintenance Guide—z/OS.
  2. Copy ESVSINIT, ESVSSBLD, and ESVSSSSM to an APF-authorized library that will be used for the CA IDMS VSAM Transparency command interface startup procedure. (If the library used in Step 1 is APF authorized, you do not have to recopy these modules.)
  3. Include an ADD PROGRAM statement for ESVSAMBE in the system definition of all DC/UCF systems to be used with CA IDMS VSAM Transparency. Specify the ADD PROGRAM statement as follows:
    ADD PROGRAM ESVSAMBE
      LANGUAGE IS ASSEMBLER
      REENTRANT
      RESIDENT.
    

    Note: As part of the normal installation process for CA IDMS VSAM Transparency, your system definition will be updated with the definition of all programs required for this product. If you need to add these definitions to another system, source module DLODEVSM in your installed library contains the definition of all the CA IDMS VSAM Transparency programs.

    More information:

    For more information on the ADD PROGRAM statement, refer to CA IDMS System Generation Guide.

  4. Make additions to the CA IDMS system for variable length records, as detailed in Appendix C, Variable-Length Record Considerations.
  5. Set up an CA IDMS VSAM Transparency command interface procedure to start up the CA IDMS VSAM Transparency system. The procedure must be a member of SYS1.PROCLIB. (z/OS) requires all subsystem startup procedures to be in SYS1.PROCLIB.)

    The name of this procedure is assumed to be ESVS in this manual. If you want to use different versions, for example one to test and one for production, then the name of the version on the PROC statement must match the name on the SUBSYS= control statement.

    Startup JCL

    To set up a startup procedure, use the JCL exactly as shown below. ESVSINIT (z/OS)

    //ESVS PROC
    //STEPESVS EXEC PGM=ESVSINIT,TIME=1440
    //STEPLIB  DD   DSN=idms.apf.loadlib,DISP=SHR,VOL=SER=nnnn,
    //              UNIT=unit
    //APFLIB   DD   DSN=idms.apf.loadlib,DISP=SHR,VOL=SER=nnnn,
    //              UNIT=unit
    

idms.apf.loadlib

Data set name of the APF-authorized CA IDMS/DB load library that includes ESVSINIT and ESVSSSSM

nnnn

Volume serial number for the APF-authorized CA IDMS/DB load library

unit

Disk type

  1. Define CA IDMS VSAM Transparency as a subsystem in z/OS. You do this by adding the subsystem name, ESVS, to member IEFSSN00 of SYS1.PARMLIB.
  2. You can define ESVS as a subsystem by executing the program ESVSSBLD with parm=(<ESVS>).. In this way, you don't need to wait for a system IPL before using VSAM/T. ESVSSBLD must be on an authorized library, where <ESVS> is the chosen subsystem name. The job does not require dd statements. If the subsystem name has not been defined in SYS1.PARMLIB subsystem name member, then this program must be executed whenever an IPL of z/OS has been done.
  3. Cycle the z/OS system to implement the definition of the CA IDMS VSAM Transparency subsystem.

    Note: It is not necessary to cycle the system if you reinstall CA IDMS VSAM Transparency.