Starting Your Product › How to Complete Configuration With CA MSM › Install CICS Support (Optional) › CICS Table Considerations

CICS Table Considerations

There are several CICS internal tables that you must update in order for the interface to function. Some tables can be assembled through batch jobs. The CEDA transaction can define or alter some of the resources such as the TCT, PCT, and PPT interactively.

For additional information, the CICS/OS/VS Resource Definition Book (online) describes the CEDA transaction, and the CICS/OS/VS Resource Definition book (macro) describes how to code the tables you require.

• Transaction Table (Program Control Table - PCT)

  Entries to this table should look like the following:

  DFHPCT TYPE=ENTRY,
       TRANSID=DSP1,
       PROGRAM=CADSINTC,
  DFHPCT TYPE=ENTRY,
       TRANSID=DSP2,
       PROGRAM=VCICICS,
       TWASIZE=400
  

  Note: The TRANSID fields can be changed as per your installation's transaction requirements. However, if you change DSP2, the new transaction ID must be the same as in DSUCFC3. For more information, see the Define the CICS Interface step.

• Program Table (Processing Program Table - PPT)

  Entries to this table should look like the following:

  DFHPPT TYPE=ENTRY,PROGRAM=CADSINTC,RES=YES,RELOAD=NO,LANG=ASSEMBLER
  DFHPPT TYPE=ENTRY,PROGRAM=VCICICS,RES=NO,RELOAD=NO,LANG=ASSEMBLER
  

  Be aware of the following:

  • Program CADSINTC stores CSECT addresses within the 4-byte CWA. Program VCICICS utilizes these addresses to branch to the appropriate CSECT within CADSINTC. Even though transaction DSP1 is executed once, the module (CADSINTC) it invokes is continuously being branched to by VCICICS. Because of this, it must be a resident module.
  • Abends can occur if you use the same interface modules for access to both a main region and an OLVO region; this is the result of concurrent usage of a temporary storage queue.

    You can prevent this situation by using the CADSQID parameter as follows:

  • Create an interface for both the main and OLVO region but use a different CADSQID for each.
  • If symbolic CADSQID is not specified, the default queue name CADSMAIN will be used. The following example defines a default temporary storage queue named CADSMAIN:

    	CADSINTC IDMSINTC XA=YES,CWADISP=0,OPSYS=MVS,SYSCTL=CAICTL
    	END
    

    Note: If symbolic CADSQID=xxxx is specified, a queue name of CADSxxxx is used. Symbolic CADSQID cannot specify blanks and it must be 4 characters long. The following example defines a temporary storage queue named CADSOLVO:

        CADSINTC IDMSINTC XA=YES,CWADISP=0,OPSYS=MVS,SYSCTL=CAICTL,CADSQID=OLV
        END
    

• List Table (Program List Table - PLT)

  Entries to this table should look like the following:

  DFHPLT TYPE=ENTRY,PROGRAM=CADSINTC
  

  Note: If transaction DSP1 is entered by an operator, terminal lockup will result since no terminal I/O processing occurs in the program. Simply press the RESET key to continue processing.