Transaction entries for MainView for CICS and MainView AutoOPERATOR for CICS

The following table describes the transaction IDs used by MainView for CICS and MainView AutoOPERATOR for CICS.

Table 2 lists ZAPs that may be applied to change these IDs.

Table 1. Transaction IDs

Tran ID

Description

BMCE

is started by the CICS External Interface on behalf of a request from the BBI-SS

This transaction is not created dynamically.

BCRT

processes GET and SET requests that require CICS SPI commands to collect data and process modifications (for CICS 4.1 and later)

For CICS Transaction Server 2.x and later, it also handles, on an interval basis, the queues that control the allocation and reuse of the MainView for CICS TIE (Task Interface Element) space used by the data extractor.

For user security purposes and other monitoring exits, BCRTshould be handled like transaction JNL2.

FCD2

performs an action request that uses CICS services for completion

It is scheduled once for each request to ensure proper serialization.

FCM1

routes messages to terminals through BMS for MainView AutoOPERATOR for CICS message broadcast

FIC2

captures and records MainView for CICS statistical data

It runs once each minute.

FST2

controls the communications, the data collection and other agent functions within the CICS.

The following functions are available if the appropriate product is installed:

  • QON: starts BBI-SS communications; MainView AutoOPERATOR; MainView for CICS data collection extractor

  • QOFF: stops the MainView for CICS data collection extractor

  • SYSM ON: starts MainView AutoOPERATOR for CICS

  • SYSM OFF: stops MainView AutoOPERATOR for CICS

  • LON: starts the MainView for CICS BCRT control task (should be used only under the direction of MainView for CICS support)

  • LOFF: stops the MainView for CICS BCRT control task (should be used only under the direction of MainView for CICS support)

The following functions are available when automatic maintenance is active:

  • INIT: build and initialize the MainView for CICS agents

  • TERM: terminate and remove MainView for CICS from the CICS

  • KON: activate the MainView for CICS task kill function

  • KOFF: deactivate the MainView for CICS task kill function

  • KRLD: reload the MainView for CICS task kill function

The FST2 transaction is not created dynamically.

Note

On commands start BBI-SS communications if not already started.

JNL2

monitors the status of the BBI-SS and starts transaction FCD2 when CICS action requests are processed

JNL2 is always shown as active on the TASK display, but most of that time is spent waiting (user ECB). When JNL2 starts, it remains active because it must be present in the system at all times once communication with the BBI-SS is established. JNL2 is assigned a very high internal dispatching priority.

SMN2

allows manual starting of communications and data collection components

It also allows manual stopping of data collection (communications, however, remain active once started). It schedules FST2 (FST2 QON, FST2 QOFF) to perform a service and reports on the status of the components. Its use is required if the PLT is not used to start data collection and communications automatically.

If your site has existing transaction IDs that are the same as those used by MainView for CICS or MainView AutoOPERATOR for CICS, or your site has standards that preclude the use of these IDs, you need to change them. To change these IDs, apply the following ZAPs:

Table 2. ZAPs for transaction ID changes

Tran ID

ZAP Required if Transaction ID Is Changed

BCRT

NAME CMRINT2 CMRINT2

VER 0080 C2C3D9E3

REP 0080 xxxxxxxx

BMCE

NAME CMRINT2 CMRINT2

VER 00AC C2D4C3C5

REP 00AC xxxxxxxx

FCD2

NAME CMRINT2 CMRINT2

VER 00C0 C6C3C4F2

REP 00C0 xxxxxxxx New Transaction ID

FCM1

NAME CMRINT2 CMRINT2

VER 00A8 C6C3D4F1

REP 00A8 xxxxxxxx New Transaction ID

FIC2

NAME CMRINT2 CMRINT2

VER 00B8 C6C9C3F2

REP 00B8 xxxxxxxx New Transaction ID

FST2

NAME CMRINT2 CMRINT2

VER 00B0 C6E2E3F2

REP 00B0 xxxxxxxx New Transaction ID

JNL2

NAME CMRINT2 CMRINT2

VER 00B4 D1D5D3F2

REP 00B4 xxxxxxxx New Transaction ID

SMN2

(No ZAP required)

Note

While the transaction IDs may change in CICS, the original transaction IDs still appear in online Help.

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

Comments