Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Task 2.8: Configuring the Code Debug IMS User ID Intercept Installation Utility

This section describes how to use the Code Debug IMS User ID Intercept Installation Utility program, XPIMSTLR. The User ID intercept must be activated to enable User ID Support and User ID/Data Value Intercept Support to function properly.

The following people are required:

  • Code Debug TSO and Code Debug IMS Installer
  • IMS DBA.

Activation Procedure

  1. Edit the member JCLIMSLR from the SLXTINST library.
  2. Use the XTUPDATE ISPF Edit macro to customize the JCL.
  3. After the SYSIN DD *, supply the name of the IMS subsystems and dummy transaction names. If the IMS subsystem is part of a Shared Queue environment, specify the LPAR name and four-byte identifier for the Shared Queue.
  4. Submit the job. It should complete with a condition code of 0.

XPIMSTLR Functions

The four functions of XPIMSTLR are:

  • ACTIVATE - Installs or reactivates the intercept.
  • DEACTIVATE - Deactivates the intercept.
  • FORCE - Deactivates the intercept, even if it is in use.
  • MAINTENANCE - Updates the current intercept with a new copy from an authorized library.

For an explanation of any error messages issued by XPIMSTLR during the Intercept install and initialization, see the Code Debug TSO and Code Debug IMS Messages and Codes space.

The following sections explain each of the four XPIMSTLR functions.

ACTIVATE Function

This function can only be used if the intercept is not currently active. You must specify a list of IMS subsystems to intercept and the prefix and range of the dummy IMS trancodes for Code Debug’s use.

A sample PARM for the ACTIVATE function is

PARM=ACTIVATE

The IMS subsystem and trancode range is specified in the SYSIN DD. The format of the control is

XXXX/XPED9999/LLLLLLLL/SSSS

where

  • XXXX = 1- to 4-character IMS Subsystem name
  • XPED = 4-character dummy trancode prefix
  • 9999 = 4 digits of max trancode number
  • LLLLLLLL = 1- to 8-character LPAR name to which the dummy trancodes belong
  • SSSS = 4-character Shared Queue group identifier.

and LLLLLLLL and SSSS are optional segments required for IMS Shared Queue support.

For example:

IMS6/XPED0025

means Code Debug will intercept transactions on the IMS6 subsystem. The dummy trancodes for this subsystem are XPED0000 through XPED0025.

If you have a Shared Queue environment, for example:

  • LPAR 1 (LPR1):
    • IM18 is local only
    • IM19 is part of an IMSplex (IM19 and IM29)
    • IM1A is part of an IMSplex (IM1A and IM2A).
  • LPAR 2 (LPR2):
    • IM28 is local only
    • IM29 is part of an IMSplex (IM29 and IM19)
    • IM2A is part of an IMSplex (IM2A and IM1A).

control cards would resemble:

IM18/XPED0050
IM28/XPED0050
IM19/XPED0050/LPR1/#001
IM29/XPED0100/LPR2/#001
IM1A/XPED0050/LPR1/#002
IM2A/XPED0100/LPR2/#002

which means Code Debug will:

  • Intercept transactions on the IM18 subsystem. The dummy trancodes for this subsystem are XPED0000 through XPED0050.
  • Intercept transactions on the IM28 subsystem. The dummy trancodes for this subsystem are XPED0000 through XPED0050.
  • Intercept transactions on the IM19 subsystem. The dummy trancodes for this subsystem are XPED0000 through XPED0050. This subsystem is on the LPAR named LPR1 and is associated with a Shared Queue group designated by #001.
  • Intercept transactions on the IM29 subsystem. The dummy trancodes for this subsystem are XPED0051 through XPED0100. This subsystem is on the LPAR named LPR2 and is associated with a Shared Queue group designated by #001.
  • Intercept transactions on the IM1A subsystem. The dummy trancodes for this subsystem are XPED0000 through XPED0050. This subsystem is on the LPAR named LPR1 and is associated with a Shared Queue group designated by #002.
  • Intercept transactions on the IM2A subsystem. The dummy trancodes for this subsystem are XPED0051 through XPED0100. This subsystem is on the LPAR named LPR2 and is associated with a Shared Queue group designated by #002.

As shown in the previous example, the dummy transaction codes for a Shared Queue are cumulative. This means the first member of a Shared Queue group follows the standard rule (XPEDnnnn, where the initial transaction code is XPED0000 and nnnn represents the maximum transaction code), while the initial transaction code of subsequent members is one greater that the prior member’s maximum transaction code (nnnn+1).

Tip

We recommend that, where possible, the control cards used on each LPAR to activate the Code Debug IMS User ID Intercept be the same. This will eliminate potential specification errors and ease implementation and maintenance.

DEACTIVATE and FORCE Functions

The DEACTIVATE function is used to disable the Code Debug IMS User ID intercept. It will not perform its function if any Code Debug IMS debugging sessions are in progress. If you want the intercept to be disabled, regardless of the consequences, use the FORCE option.

The sample PARM for the DEACTIVATE function is

PARM=DEACTIVATE

The sample PARM for the FORCE function is

PARM=FORCE

MAINTENANCE Function

This function can only be used if the PC intercept is not active. It would normally be used when directed to do so by a PTF or by BMC Support.

The sample PARM for the MAINTENANCE function is

PARM=MAINTENANCE

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*