Installing the Online Interfaces › How to Complete Configuration of the XMS Online Interfaces with CA CSM › Define Security Requirements › Step 2: Code the PCT and PPT Table Entries to CICS › Optional DCT Entries

Optional DCT Entries

Specify a value for the DESTID parameter in the EBCXMOPT macro in the EC2XMCTR module and corresponding DCT entries. This value defines a transient data destination for messages issued by the subtask.

Note: Specify a blank for DESTID to suppress the generation of informational messages from the subtask.

The DCT entries for a DESTID of XMC2 are:

SARLOG   DFHDCT TYPE=SDSCI,   FOR CICS MESSAGES AND SHUTDOWN
               BLKSIZE=250,   STATISTICS
               BUFNO=1,
               DSCNAME=SARLOG,
               RECFORM=VARUNBM,
               RECSIZE=242,
               TYPEFLE=OUTPUT
XMC2G    DFHDCT TYPE=EXTRA,
               DESTID=XMC2,
               DSCNAME=SARLOG

Step 3: (Optional) Invoke the Product from a CICS Menu System

If you want to invoke CA View from a user-written CICS menu system, and then return to that menu system when you exit from CA View, do the following:

Invoke CA View from the menu system using the following CICS command:

EXEC CICS START TRANSID(VIEW transaction-id)
     TERMID(EIBTRMID)
     FROM(data-area)
     LENGTH(4)

where:

TRANSID(VIEW transaction-id)

Specifies the CA View transaction ID.

TERMID(EIBTRMID)

Specifies the terminal that a CA View transaction will communicate with.

FROM(data-area)

Specifies the optional variable length character string.

The format of the data-area parameter is:

tran,mode,sysoutid,jobnum,code

where:

tran

Specifies the return menu CICS transaction to be started when CA View finishes

mode

Specifies the CA View user mode (ALL, SAR, SARO, EXP, EXPO) for this user

If mode is not specified, the last mode that the user was in is used.

sysoutid

Specifies the SYSOUT ID or generic ID (with *) to be selected

jobnum

Specifies the JES2 job number of the SYSOUT ID to be selected

code

Indicates the selection code to be used (S, Pn, Vn, Jn, and so on)

If code is not specified, the user is presented with the SYSOUT Selection List.

Note: None of the data-area parameters is required.

LENGTH (4)

Specifies the number of bytes in the data field being passed.

When CA View receives control, it retrieves the four-byte return transaction ID and saves it from iteration to iteration.

If the retrieve fails, CA View retains the information that it was started directly from a terminal, not a menu system.

When CA View finishes processing, it determines whether it should return to a menu system by starting the return transaction.

If there is a saved transaction ID, the product starts the return transaction before it exits to CICS by issuing:

EXEC CICS START TRANSID(return transaction-id)
     TERMID(EIBTRMID)
     NOCHECK

CICS Notes

The cross‑memory CICS access involves two different address spaces: the CICS address spaces and the XMS address spaces.

CICS Address Spaces

The user's CICS transactions and the cross memory support subtask reside in these address spaces.

• If multiple CICS regions are used to access CA View, each CICS region will have an XMS support subtask
• If you are using CICS/MRO, CA View normally runs in an AOR (application region).

XMS Address Spaces

Be aware of the following:

• The primary SARXMS region can be started with the XMSSUB=YES or XMSSUB=NO parameter.
• CICS has a router subtask in its region and does not require the XMSSUB=YES function. However, we recommend that you start the primary XMS region with XMSSUB=YES.
• If multiple SARXMS regions are started, they must be started with XMSSUB=NO parameter.

  Only the primary XMS region can have XMSSUB=YES specified.

• The XMS regions must have the XMS=YES parameter to make it accessible.
• The SUBSYS= parameter must match the EC2XMCTR table entry for the CICS transaction.
• The EBCXMCTR table must be assembled during installation to define the relationship between CA View and CA Deliver database high-level qualifiers.

  The table contains an EBCXMOPT macro to define initialization options and the EBCXMTRN macro for each CICS user transaction.

The EBCXMTRN macro also contains options for the specific database as follows:

• SUBSYS= parameter can be used to route the CA View transaction to an alternate XMS subsystem ID. The SUBSYS= of the cross‑memory task must match the SUBSYS= parameter specified in the EBCXMCTR table entry.
• TRANID=parameter specifies the CA View transaction identifier for CICS.
• RECON=YES can be used to allow reconnection (after a CICS terminal error) at the point of exit.

  Note: Do not specify RECON=YES if you use a multi‑session manager that assigns LU names from a pool of names. Coding RECON=YES under these conditions could allow you to be connected to another user's session.

  For more information, see Multi‑Session Managers later in this chapter.

• TIMEOUT= specifies how long CICS is to wait for the XMS session to respond after the user enters input, in seconds.

  We recommend as high a value as possible but not less than 240 (4 minutes).