Specifying cell information
This topic describes how to implement a z/OS connection to TSOM by using BMC Impact Integration for z/OS (BMC II for z/OS).
The following procedures describe how to implement the bidirectional communication between TSOM and the BMC Impact Integration for z/OS Server through a TCP/IP connection.
Before you begin
To establish a connection, you must have already installed the BMC Impact Integration for z/OS cell and console components.
Additionally, you must have the following items:
- At least one BBI-SS PAS with BMC II for z/OS
- The z/OS TCP/IP product
- At least one cell directory file, mcell.dir, configured for the BMC II for z/OS integration to which you want TSOM to communicate
To establish a connection to TSOM
After you have met the requirements listed above, you are ready to configure BMC Impact Integration for z/OS.
Configure BMC Impact Integration for z/OS by editing the sample JCL member, IIMSALC1, which allocates and initializes two files that are needed to connect BMC II for z/OS with BMC Impact Manager.Depending on your site requirements for persistency queueing and detailed trace data collection, edit sample JCL member IIMSALC2.
To configure BMC II for z/OS
- Copy hlq.BBSAMP(IIMSALC1) to hlq.UBBSAMP(IIMSALC1)
Edit IIMSALC1 according to its instructions by performing the following actions:
- Add a JOBCARD
- Replace all occurrences of ++SMP++ with the high level qualifier of the SMP/E datasets used during installation
- Replace all occurrences of ++HLQ++ with the high leve qualifier for the UBBPARM dataset.
Add cell definitions as follows:
type cellname encryptionkey ipaddress1:port ipaddress2:port
Variable
Description
type
Following are the type options:<type> = cell | gateway
cellname
TSOM cell to which you want BMC II for z/OS to connect
Use all uppercase letters. Lowercase characters are not converted to uppercase
encryptionkey
Seed encryption key
The default key value is mc. All clients must encrypt their communications by using the same key value.
ipaddress1:port
IP address or fully qualified domain name and port number of the TSOM cell to which you want BMC II for z/OS to connect (this value must be an exact match to the TGTIP value used for the cell in BBPARM member AAOGMEIZ)
ipaddress2:port
(optional) BMC II for z/OS supports High Availability (HA) TSOM cell configurations. For HA TSOM cell environments you must specify a second IP address or fully qualified domain name and port number for the backup TSOM cell.
Submit the JOB.This will create two following members:
- MVQA.BZ15B2BD.S0SC.UBBPARM(IIMDIR00) which is for the cell's connection definitions
- MVQA.BZ15B2BD.S0SC.UBBPARM(IIMLCL00) which is for localization definitions
- Copy hlq.BBSAMP(IIMSALC2) to hlq.UBBSAMP(IIMSALC2)
- Edit hlq.UBBSAMP(IIMSALC2) according to its instructions in IIMSALC2 by performing the following actions:
- Add a JOBCARD
- Replace all occurrences of ++HLQ++ with the high level qualifier of the UBBPARM dataset.
- Replace all occurrences of ++PFX++ with the high level qualifier to be used for the IIM disk queuing and trace datasets.
Replace all occurrences of ++SFX++ with member suffix used for this specific connection definition.
Replace all occurrences of ++CNC++ with a unique 1-8 character name for the connection.
This is used to create a unique dataset name for the connection's queuing and trace datasets.
- Replace all occurrences of ++UNIT++ with a valid unit type.
- Replace all occurrences of ++VOLSER++ with the target volume serial number.
- Replace all occurrences of ++NAME++ with the name of the BIIZ Integration or BMC EM / SIM cell.
Submit the JOB.This will create the following data sets and members as shown in the following table:
Data set
Description
hlq.UBBPARM(IIMCNFSFX)
Connection to cell configuration file
hlq.RECVQUE
For receiving queue
hlq.RCVQUETM
For temporary receiving queue
hlq.SENDQUE
For send queue
hlq.TRACEOUT
For trace output
Go to hlq.UBBPARM(AAOGMEIZ) and add the following definition for the cell:TGTIP=CELLNAME,TGTBIMCF=DD:BBIPARM(IIMCNFxx),optionalParameters
The variables as defined as follows:
To create persistent connection members and files
The sample member IIMSALC2 allocates and initializes two BBIPARM members and four IIM files that define each connection and that are needed if you optionally implement persistent queuing and tracing. IIMSALC2 must be run once for each connection that require persistent queuing and tracing, including the server connection and all the client.
- Copy the member hilevel.BBSAMP(IIMSALC2) to hlq.UBBSAMP(IIMSALC2).
- Edit the user sample member IIMSALC2.
- Replace all occurrences of ++HLQ++ with the high-level qualifier that you want to use for the data sets.
- Replace all occurrences of ++CNC++ with the name of the connection.
- Replace all occurrences of ++UNIT++ with a valid unit type.
- Replace all occurrences of ++VOLSER++ with the target volume serial number.
- Replace all occurrences of ++NAME++ with the name of the BMC IM cell to which you want BMC II for z/OS to connect.
- (optional) If you want to change the parameters from the default values provided in IIMSALC2, see Configuration-parameters.
Submit the JCL to create six files:hlq.connectionID.CONF is the primary configuration file for a connection.
hlq.connectionID.RECVQUE is the queue of events that have arrived from the TSOM cell. If enable receive persistence is turned on, a unique set of RECVQUE files are required for each connection.
hlq.connectionID.RCVQUETM is the temporary queue used during compacting the receive queue.
hlq.connectionID.SENDQUE is the disk queue of events that are to be sent to a TSOM cell. If persistency enabled is turned on, a unique set of SENDQUE files are required for each connection.
hlq.connectionID.RACONF is the trace configuration file for this connection. If tracing is turned on, a unique set of TRACE files are required for each connection.
hlq.connectionID.TRACEOUT is the trace output file for this connection if tracing is turned on.