Transaction conflict zap

When transaction ID conflicts exist between a user’s transaction ID and a MainView for CICS transaction ID, the user can change the BMC transaction ID by zapping module CMRINT2.

The following table lists the zaps that can be applied to change transaction IDs.

Zaps to change transaction ID

Tran ID

Offset

Zap for each transaction ID

BCRT

0080

NAME CMRINT2 CMRINT2VER 0080 C2C3D9E3REP 0080 xxxxxxxx

SMN2

00A4

NAME CMRINT2 CMRINT2VER 00A4 E2D4D5F2REP 00A4 xxxxxxxx

FCM1

00A8

NAME CMRINT2 CMRINT2VER 00A8 C6C3D4F1REP 00A8 xxxxxxxxx

BMCE

00AC

NAME CMRINT2 CMRINT2 VER 00AC C2D4C3C5 REP 00AC xxxxxxxx

FST2

00B0

NAME CMRINT2 CMRINT2VER 00B0 C6E2E3F2REP 00B0 xxxxxxxx

JNL2

00B4

NAME CMRINT2 CMRINT2VER 00B4 D1D5D3F2REP 00B4 xxxxxxxx

FIC2

00B8

NAME CMRINT2 CMRINT2VER 00B8 C6C9C3F2REP 00B8 xxxxxxxx

FCD2

00C0

NAME CMRINT2 CMRINT2VER 00C0 C6C3C4F2REP 00C0 xxxxxxxx

Changing the FST2 or BMCE transactions requires the following actions:

  1. The CSD definition for the transaction has to be changed and installed. Refer to BBSAMP member CSDOLTDF.

  2. If the BBI-SS PAS has static targets, restart it with a cold start; otherwise, a warm start is sufficient.

Note

While the transaction IDs may change in CICS, the original transaction IDs still appear in online Help. BBSAMP member OLTUMOD0 includes a sample USERMOD to apply the zap by using SMP/E.

Was this page helpful? Yes No Submitting... Thank you

Comments