Reducing JCL requirements in OMEGAMON XE for CICS on z/OS v5.3.0
RichardBurford 120000E258 Comments (2) Visits (9355)
The OMEGAMON Performance Management Suite for z/OS consists of eight OMEGAMON monitors which are packaged together. In common with the other mainframe OMEGAMON products which were made generally available on September 5th, OMEGAMON XE for CICS on z/OS v5.3.0 included new features which are focused on Enhanced 3270 UI near term history and embedded data. Both of these features will help you resolve problems in your CICS environment by ensuring that the data that you need is available quickly, even when that data is from different subsystems or relates to a problem that occurred in the recent past. More information about the OMEGAMON Performance Management Suite for z/OS can be found at www.
The code then reads the INITPARM data which was specified in the SIT to determine whether the other JCL statements should be allocated. Here is an example of the INITPARM used in one of our test systems:
If we review the parameters shown in this example, the first is the RETRY option. Introduced in OMEGAMON XE for CICS on z/OS v5.1.0, the RETRY option allows you to control the behaviour of OMEGAMON CICS when CICS/TS starts before the common interface. In this example the OMEGAMON code running in CICS will attempt to connect to the common interface every 30 seconds, a maximum of 20 times. You can specify RETRY(30) and the OMEGAMON code will attempt to establish the connection to the common interface every 30 seconds until the connection is established or you issue an OMEG CANCEL command to terminate the attempts.
All of the parameters shown in the first example are present, and you can see that the order does not matter. The extra parameter is KC2_GLOBAL=# which is the equivalent of coding KC2GLB# in the CICS JCL. If there is already a KC2GLBxx DD card this parameter is ignored.
Scenario one - modifying the OMEGAMON datasets after CICS/TS has initialized.
Because the allocations are all made dynamically you can use the OMEG REMOVE followed by an OMEG INIT (or OMEG RECYCLE) function to remove the allocated datasets. You could, for example, change the CICS LIBRARY definition to specify a new load library (or libraries), and pick up those changes dynamically. In this situation the following sequence of commands might be used:
Scenario two - modifying the XMIT or GLOBAL DD cards after OMEGAMON has initialized.
All of the INITPARM parameters can be specified with the OMEG terminal command. This means that in the event that you wanted to change the agent to which a CICS/TS region connects, you could use an OMEG REMOVE to deallocate the DD cards, followed by an OMEG INIT,parameters. For example you would change the KCPXMxx DD card like this OMEG INIT
Scenario three - connecting a CICS/TS region to a different agent or common interface using options on the START command.
Another option that this offers is the ability to use CICS/TS JCL with override parameters for the OMEGAMON DD cards. You could define multiple CICS System Initialization Tables, each with different OMEGAMON INITPARM definitions. For example, on one LPAR you might want to connect CICS/TS to an agent with an XMIT ID of 05, but on another LPAR the XMIT ID is 06. Coding two SITs, and starting the CICS/TS region on the different LPARs with the appropriate override on the start command will add the required flexibility.
Naming standards and the new code.
It should be noted that the new feature relies on installing the product using the default naming conventions. The LIBRARY definition can include as many datasets as are appropriate for your site, but the dataset names must be in the hilev.xKANMODR format. The dataset names from the LIBRARY definition are then used to dynamically allocate the RKANMOD DD, and the dataset names are built from the RKANMODR entry, so the code will attempt to allocate hilev.xKANMOD.
An example, using the RETRY option, OMEG CANCEL and OMEG INIT,LIST.
This example shows the datasets that were located, and then dynamically allocated. Note that the LIST option was specified, and shows the source of the XMIT and global DD cards.
As I mentioned earlier, the LIST option is intended as a diagnostic tool, you might use it under guidance of IBM support or when you are first implementing this new feature. It is not intended to be used on every start of OMEGAMON CICS due to the number of messages that can be issued.