360 Tivoli Business Systems Manager Version 2.1: End-to-End Business Impact Management
These exits must be stored in the IMS RESLIB or concatenated in the
STEPLIB of the IMS Control Region. At the startup of the IMS Control Region,
the messages shown in Example 11-4 on page 360 indicate a successful
installation of the IHSIAOE0 exit.
Example 11-4 Messages from IHSIAOE0
IHS370I AO Exit IHSIAOE0 initialized for IMS v7.1.0 TM/DB system IMSQ
IHS371I Successfully loaded Message Table IHSIAOEM IMSQ
2. Enable Open Transaction Manager Access (OTMA). IBM Tivoli Business
Systems Manager integration uses OTMA for issuing IMS commands from
the IBM Tivoli Business Systems Manager console. To enable OTMA, you can
specify parameters at IMS startup as shown below.
S IMS710Q,PARM1='OTMA=Y,GRNAME=WTSCPLX1'
where GRNAME represents the Sysplex group name on which IMS runs.
The OTMA command interface program DFSYSVI0 also must be run
immediately after IPL, before any address space that uses OTMA is started.
You can achieve this by running the JCL stored in DFSYINIT in the IMS library
SDFSISRC. A sample is shown in Example 11-5.
Example 11-5 DFSYINIT
//OTMAINIT JOB ,'OTMA INITIALIZATION',CLASS=A,REGION=4M
//*
//IEFPROC EXEC PGM=DFSYSVI0
//*
//STEPLIB DD DISP=SHR,DSN=IMS710Q.SDFSRESL
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
3. Configure IMS security. The NetView autotasks specific to IMS integration
(IHSIAUT0, IHSIAUT1, IHSIAUT2 and IHSIAUT3) must be defined as RACF
user IDs. These user IDs require the following access:
– Access to issue all IMS display commands through the OTMA interface
and for the EMCS interface for DBCTL regions. To enable OTMA interface
access, you can set the IMS startup parameter OTMASE=F (full security)
and tailor your security product to have access to IMS display commands.
– Access to IMSXCF.group.IHSI* RACF profile.
– Allocate temporary data sets.
– READ access to IMS data sets ACBLIB, MODBLKS, RESLIB and
PROCLIB.
– CONTROL access to recovery control (RECONxx) data sets.
– Access to run DSPURX00 (DBRC utility), which is usually protected using
the PROGRAM profile.