Products | Versions |
---|---|
TIBCO Object Service Broker for z/OS | - |
Not Applicable | - |
Resolution:
For OTMA to work properly, the OTMA C/I module DFSYSVC0, needs to be loaded and registered to the SVC services by an authorized address space running on the same z/OS image as the application programs that will be accessing it. If you get a SF92 abend when the OTMA enabled IMS Adapter starts, this usually means that the OTMA C/I module DFSYSVC0 has not been LOADed. This may have been caused due to faulty post-IPL procedures where an IPL has recently been done and OTMA C/I module DFSYSVC0 has, for some reason, not been loaded.
OTMA Callable Services provides a stand-alone program, DFSYSVI0, that must be run after MVS IPL to initalize the OTMA C/I. You must add an entry in the MVS program properties table (PPT) for the OTMA Callable Services initalization program. The steps for doing this are:
1. Edit the SCHEDxx member of the SYS1.PARMLIB data set.
2. Add the following entry to the SCHEDxx member:
PPT PGMNAME(DFSYSVI0)
CANCEL
KEY(7)
SWAP
NOPRIV
DSI
PASS
SYST
AFF(NONE)
NOPREF
3. Take one of the following actions to make the SCHEDxx changes effective:
Re-IPL the MVS system.
or
Issue the "MVS SET SCH=" command.
RELATED READING: For additional reading about updating the program properties table, see the IBM "MVS Initialization and Tuning Reference" manual.
A sample JCL proc 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.RESLIB
//SYSPRINT DD SYSOUT=&SOUT
//SYSUDUMP DD SYSOUT=&SOUT
Ensure that the above PROC is re-executed after every IPL. It would be helpful if this could be *automated* to run after every IPL.
Also, if currently you are overriding the IMS/TM startup options by using the command, such as:
S IMS81,PARM1='IMSID=I81E,OTMA=Y,OTMASE=N,OTMANM=IMS81S,GRNAME=I81E'
perhaps it will be better if the PROC you use to start IMS/TM, includes "OTMA=Y" as a standard feature.