OTMA C/I initialization

OTMA C/I provides a stand-alone program, DFSYSVI0, that must be run to initialize the OTMA C/I after either an IPL of z/OS® or the application of maintenance to the OTMA C/I.

Note: Do not run the DFSYSVI0 program if any OTMA C/I clients are active.

If any OTMA C/I clients are active when DFSYSVI0 starts, DFSYSVI0 issues DFS3948E and DFS3950A. Running the SVC initialization when an OTMA C/I client is still active can result in XCF errors.

Active clients can be identified by issuing the z/OS command D GRS,RES=(DFSOTMA,*).

If any clients are active when the DFSYSVI0 program is run, terminate the clients and reply "RETRY" to DFS3950A to attempt to initialize the SVC again.

If the clients cannot be terminated, reply "CANCEL" to DFS3905A to stop the utility without initializing the SVC.

If the clients are orphaned and will not be used again, then reply "BYPASS" to DFS3905A to proceed with the SVC initialization. Extreme care must be taken with this option as XCF errors may result if those existing clients attempt to use OTMA C/I again.

DFSYSVI0 invokes DFSYSVC0, one of the OTMA C/I modules. DFSYSVC0 loads and registers the SVC services by an authorized address space running on the same z/OS image as the application programs accessing it. Initializing the OTMA C/I after applying maintenance to the OTMA C/I ensures that when an OTMA C/I call is executed by an OTMA C/I client, all the OTMA C/I modules in the DFSYSVC0 load module that are needed to process the call are at the same level as DFSYSVC0.

Because there is only one OTMA C/I and OTMA C/I runs in the client address space through SVC rather than in IMS, DFSYSVI0 refreshes OTMA C/I for all OTMA C/I clients in the system regardless of which IMS systems the clients connect to.

You must add an entry in the z/OS program properties table (PPT) for the OTMA Callable Interface initialization program. The steps for doing this are:

Procedure

  1. Edit the SCHEDxx member of the SYS1.PARMLIB data set.
  2. Add the following entry to the SCHEDxx member: 
    PPT PGMNAME(DFSYSVI0)   /* PROGRAM NAME = DFSYSVI0             */
             CANCEL     /* PROGRAM CAN BE CANCELED             */
             KEY(7)     /* PROTECT KEY ASSIGNED IS 7           */
             SWAP       /* PROGRAM IS SWAPPABLE                */
             NOPRIV     /* PROGRAM IS NOT PRIVILEGED           */
             DSI        /* REQUIRES DATA SET INTEGRITY         */
             PASS       /* CANNOT BYPASS PASSWORD PROTECTION   */
             SYST       /* PROGRAM IS A SYSTEM TASK            */
             AFF(NONE)  /* NO CPU AFFINITY                     */
  3. Take one of the following actions to make the SCHEDxx changes effective:
    • Re-IPL the z/OS system.

      or

    • Issue the MVS SET SCH= command.
    Related Reading: For additional reading about updating the program properties table, see z/OS MVS Initialization and Tuning Reference.
A sample JCL procedure for running DFSYSVI0 is as follows: 
//OTMAINIT PROC RGN=3000K,SOUT=A
//*
//IEFPROC  EXEC PGM=DFSYSVI0,
//              REGION=&RGN 
//* 
//STEPLIB  DD   DISP=SHR,UNIT=SYSDA, 
//              DSN=IMSVS.SDFSRESL 
//* 
//SYSPRINT DD   SYSOUT=&SOUT 
//SYSUDUMP DD   SYSOUT=&SOUT

After OTMA C/I is installed and initialized, you can use it to connect to any IMS OTMA release.