Gener/OL RDO definitions for CICS Transaction Server
search cancel

Gener/OL RDO definitions for CICS Transaction Server

book

Article ID: 264703

calendar_today

Updated On:

Products

Gener/OL

Issue/Introduction

How do we update GENER/OL with the RDO definitions for CICS

Resolution

The Gener/OL installation comes with a PDS named myhlq.BASE.R71.BUILD.SAMPJCL which includes
member SMPBAS71 which contains the Resource Definitions Online (RDO) definitions needed to define
Gener/OL.


Please follow these steps:

  1. To define your CICS RDO Program entries please copy lines 1086 to 1899 (same definitions as in Chapter 14 Step 14A in the Gener/OL Installation Guide) to a separate dataset or member and use this as input to the DFHCSDUP CICS Utility

  2. To define your CICS RDO Transaction entries please copy lines 1899 to 1923 (same definitions as in Chapter 14 Step 14B in the Gener/OL Installation Guide) to a new separate dataset or member and use this as input to the DFHCSDUP CICS Utility

  3. To define your CICS RDO File Control Table (FCT) Entries please copy lines 1923 to 2041 (same definitions as in Chapter 14 Step 14C in the Gener/OL Installation Guide) to a separate dataset or member and use this as input to the DFHCSDUP CICS Utility

  4. Add the group GENEROL to a startup list for CICS Startup.
    • Example: ADD GROUP(GENEROL) LIST(STARTUP) – Change STARTUP to a valid list name for the startup list

  5. Please add the following allocation to the DFHRPL DD statement in the CICS Startup job (same definitions as in Chapter 14 Step 15 in the Gener/OL Installation Guide).

    //*
    // DD DSN=yourHLQ.C$C7LLT,DISP=SHR
    //*

  6. Add the following 6 DD statements to in the CICS Startup job (same definitions as in Chapter 14 Step 15 in the Gener/OL Installation Guide)

    //*
    //PRTASA DD SYSOUT=A,DCB=(LRECL=137,RECFM=VA,BLKSIZE=141)
    //GOLRDR DD SYSOUT=(A,INTRDR) <=== Required for DB2 only
    //*
    //* THE NEXT FIVE STATEMENTS PUT GENER/OL FILES IN YOUR CICS JCL
    //*
    //SGTLIB1 DD DSN=SGTLIB1,DISP=SHR
    //SGTLIBU DD DSN=SGTLIBU,DISP=SHR
    //TRNPRIM DD DSN=TRNPRIM,DISP=SHR
    //SGTLIBP DD DSN=SGTLIBP,DISP=SHR
    //SGTLIBC DD DSN=SGTLIBC,DISP=SHR

  7. Follow these instructions from Informational APAR RI53592 to upgrade any other RCT and DCT definitions to RDO format.
    Note that DFHCSDUP CICS Utility is also used here to add the Resource Definition Entries to your CSD.


***** Product Documentation Change *****


CICS TS 5.1 has discontinued the support of the following two CICS
Control Tables:


DCT - Destination Control Table
RCT - Resource Control Table


Resource Definitions are used instead. The TDQUEUE(PRTQ) Resource Definition replaces the DCT and
MUST be included. The DB2ENTRY, DB2TRAN, and TDQUEUE(GOLR) Resource Definitions replace the
RCT if using DB2.


CA Gener/OL implementation requires the following changes:


1. The DCT entry required for the PRINT command when the destination parameter specified a transient
data set:

 
DFHDCT TYPE=SDSCI,DSCNAME=PRTASA,BLKSIZE=141,                                                 X
            TYPEFLE=OUTPUT,RECSIZE=137,RECFORM=VARUNBA,BUFNO=2
DFHDCT TYPE=EXTRA,DESTID=PRTQ,DSCNAME=PRTASA


Should be changed to the following Resource Definition entry:


DEFINE TDQUEUE(PRTQ) GROUP(GENEROL) DESC('PRINT COMMAND DESTINATION')
                                             TYPE(EXTRA) DDNAME(PRTASA)BLOCKFORMAT(UNBLOCKED)
                                             RECORDFORMAT(VARIABLE) RECORDSIZE(137) BLOCKSIZE(141)
                                             PRINTCONTROL(ASA) DATABUFFERS(2) SYSOUTCLASS(A)
                                            TYPEFILE(OUTPUT)


2. The DCT entry required to submit the GOLBIND procedure for execution:


DFHDCT TYPE=SDSCI,DSCNAME=GOLRDR,BLKSIZE=80,                                                         X
            TYPEFLE=OUTPUT,RECSIZE=80,RECFORM=FIXUNB
DFHDCT TYPE=EXTRA,DESTID=GOLR,DSCNAME=GOLRDR


Should be changed to the following Resource Definition entry:


DEFINE TDQUEUE(GOLR) GROUP(GENEROL) DESC('GOLBIND INTERNAL READER')
                                             TYPE(EXTRA) DDNAME(GOLRDR) BLOCKFORMAT(UNBLOCKED)
                                            RECORDFORMAT(FIXED) RECORDSIZE(80)
                                            SYSOUTCLASS(A) TYPEFILE(OUTPUT)


3. The RCT entry required to identify the Dynamic SQL plan to be used:


DSNCRCT TYPE=ENTRY,TXID=GOL1,PLAN=DQGOLxxx,AUTH=USERID


Should be changed to the following Resource Definition entry:


DEFINE DB2ENTRY(GENDB2) GROUP(GROUPNAME) PLAN(DQGOLxxx) AUTHID(USERID)


4. Use the following Resource Definition entries to identify the Static SQL plan to be used after the Static
Bind:


DEFINE DB2ENTRY(GENnnn) GROUP(GROUPNAME) PLAN(DQGSTnnn) AUTHID(USERID)
DEFINE DB2TRAN(GENxxxx) GROUP(GROUPNAME) ENTRY(GENnnn) TRANSID(xxxx)

nnn = identifiable number for the DB2ENTRY, PLAN, and ENTRY parameters
xxxx = identifiable transaction id for DB2TRAN and TRANSID parameters
Note: There can be multiple Static SQL plans, each requiring their
own DEFINE DB2ENTRY and DEFINE DB2TRAN

Powered by Wolken Software