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 › Multi-Session Managers Using Virtual LU Names

Multi-Session Managers Using Virtual LU Names

Multi‑session manager products, for example CA TPX Session Management (CA TPX), can be configured to assign an LU name to a user's terminal at the time the user selects the CICS application.

Important! This assignment means that a user can enter CICS each time with a different terminal ID which can cause problems for CA View application.

For example: If a user uses a multi-session manager to end a session, or shuts the PC down, CA View does not know that the user has left. Another user might select CICS, be assigned to the same LU name as the previous user, and enter CA View with the same terminal ID as the previous user. CA View believes that there are two active users on the same terminal.

To prevent this situation, you can add a small amount of code to the CICS Autoinstall Control Program.

Note: The default name of this program is DFHZATDX and its source is located in SDFHSAMP.

If you are not a CICS systems programmer, discuss this situation with the person in your company who is responsible for CICS support and maintenance.

The sample code that follows shows how to clear an active user from the CA View application at terminal deletion time. Insert this code in your Autoinstall Control Program.

The source that is shipped with CICS contains this line:

 * ==> PUT DELETE CODE HERE

Insert the code after that line.

LOAD  EP=EC2XSLOC,ERRET=RETURN   
         LR    R6,R0                  GET EBCXSLOC ADDRESS  
         ICM   R8,B'1111',0(R6)       ADDR OF MAIN CONTROL BLOCK
         BZ    RETURN                 GET OUT IF NONE           
         LA    R7,4(,R8)              LOOK LIKE FIRST USER BLOCK
XSU_LOOP DS    OH                                               
         ICM   R7,B'1111',8(R7)       USER BLOCK ADDR           
         BZ    RETURN                 GET OUT IF DONE           
         CLC   DELETE_TERM_ID,104(R7) FOR THIS TERMINAL?        
         BNE   XSU_LOOP               NO 
	  TM    120(R7),X'01'	    ACTIVE ENTRY?  
	  BZ	 XSU_LOOP		    NO
         OI	 120(R7),X'02'	    SHOW SESSION DONE
	  B	 RETURN		    EXIT PROGRAM          

This code does the following:

1. Attempts to load program EC2XSLOC
   • If the load fails, this is not the region containing CA View and it exits.
   • If CA View is active in this region, the first word of EC2XSLOC contains the address of the main control block.

     If this word is zero, CA View is not active and the program exits.

2. Scans the chain of CA View user control blocks to find the terminal to be deleted
   • If the program finds the terminal ID, it makes sure that the user block is in use and is active, then it clears the appropriate fields.
   • If the block does not represent an active user, the program continues to search the chain to the end.
   • If the program gets to the end of the chain without finding the terminal ID, the program exits.

If you implement this change to the terminal deletion section of the Autoinstall Control Program, you can prevent the problems caused by the methods that were used to leave the CA View application.

Install the IMS Online Retrieval Option

Use these steps to install the IMS online retrieval option.

Important! This facility uses the cross-memory feature distributed with CA View and must be installed with that feature.

Note: For more information about cross-memory, see the topic Installing Cross-Memory Services in this chapter.

Installation Steps

This list summarizes the steps required to install the IMS Online Retrieval Option. Detailed instructions are in the sections that follow.

1. Code the IMS TRANSACT, PSB, and APPLCTN macros.
2. Run the PSB, ACB, and SYSGEN procedures.
3. Load EC2IMSUX Modules

   Move load modules to IMSVS.PGMLIB.

Important! All JCL and macros provided in this section are provided as general examples only and must be modified according for your site's systems and standards.

Step 1: Code the Macros

Use the examples in this section as a guide as you code these macros, and implement them in your IMS system.

• (IMS) TRANSACT macro
• PSB macros
• APPLCTN macro