CICS Tables Function and Syntax

CICS is configured under your control during system initialization. You select a SIT and, through it, CICS selects other control tables. Each control table is created separately and may be recreated at any time prior to system initialization. You have to prepare the required control tables by coding the appropriate macro instructions.

All CICS tables (except DFHSIT) must have TYPE=INITIAL and TYPE=FINAL as the first and last macros to be coded.

Notation used in the following parameters {OPT1|OPT2|OPT3} Pick one of the available options First option is ususally the default [optional entry] Entry may be used but is not required UPPERCASE Required syntax lowercase User supplied value
  • ALT Application Load Table
  • DCT Destination Control Table
  • DDIR DL/I Data Base Directory
  • PDIR DL/I Program Specification Block Directory
  • FCT File Control Table
  • JCT Journal Control Table
  • MCT Monitoring Control Table
  • CLT Nucleus Load Table
  • PCT Program Control Table
  • PLT Program List Table
  • PPT Processing Program Table
  • SIT System Initialization Table
  • SNT Sign-On Table
  • SRT System Recovery Table
  • TCT Terminal Control Table
  • TLT Terminal List Table
  • TST Temporary Storage Table
  • XLT Transaction List Table
    • ALT Application Load Table

    The application load table (ALT) enables you to use virtual storage efficiently by allowing you to control the order of loading application programs at system initialization. All programs specified in the ALT are made permanently resident.

    The ALT is an optional feature.

    If you use an ALT, the application programs specified in the table will be loaded first, in the order specified by the ALT, and with the options specified in the ALT.

    After the programs specified in the ALT, if there is one, resident application programs will be loaded according to the order of the groups in the DFHSIT GRPLIST operand and, within group, in alphabetic order of program name. (If you also have a PPT load module, the resident application programs defined there will be loaded first, in PPT order.) Any programs specified as permanently resident but not specified in the ALT will be loaded with the options specified by the PROGRAM definition.

    ALT Application Load Table - syntax for TYPE=INITIAL DFHALT TYPE=INITIAL [,SUFFIX=xx] % Table Suffix ALT Application Load Table - syntax for TYPE=ENTRY label DFHALT TYPE=ENTRY ,PROGRAM=(name[,...]) % Name of programs [,ALIGN={NO|ENTRY|YES}] % Page alignment [.CLASS={SPECIFIC|GENERIC}] [,FIX={NO|YES}] % Page Fixed [,PAGEOUT={NO|YES}] % CICS to force out not in use [,SHR={NO|YES}] % use from link pack area (LPA) DCT Destination Control Table

    The destination control table (DCT) contains an entry for each remote, extrapartition, intrapartition, and indirect destination. Extrapartition entries address data sets external to the CICS region. Indirect destination entries address the DCT entry for the destination to which they indirectly refer. Intrapartition destination entries contain the information required to locate the queue in the intrapartition data set. Entries are made in the DCT by generating the DFHDCT macro instruction.

    Whether the specified destinations are extrapartition or intrapartition (or indirect destinations pointing to either extrapartition or intrapartition destinations), yhou have to provide the symbolic names of the destinations. CICS uses several destinations for its own purposes. These entries must be included in the generation of the DCT if the associated functions are being used.

    DCT Destination Control Table - syntax for TYPE=INITIAL DFHDCT TYPE=INITIAL [,SEPASMB={NO|YES}] [,SUFFIX=xx] % Table suffix [,TRNSUFX=(xx[,xx],...)] DCT Destination Control Table - syntax for TYPE=EXTRA label DFHDCT TYPE=EXTRA ,DESTID=name % symbolic name of destination [,DSCNAME=name] % file name in TYPE=SDSCI [,OPEN={INITIAL|DEFERRED}] [,RESIDNT={YES|NO} % resident data set control blocks [,RSL={0|number|PUBLIC}] % security level of destination DCT Destination Control Table - syntax for TYPE=INDIRECT label DFHDCT TYPE=INDIRECT ,DESTID=name % symbolic name of destination ,INDDEST=name % name of real destination DCT Destination Control Table - syntax for TYPE=INTRA label DFHDCT TYPE=INTRA ,DESTID=name % symbolic name of destination [,DESTFAC={(TERMINAL[,trmidnt]) |FILE|(SYSTEM,sysidnt)}] [,DESTRCV={NO|PH|LG}] % recoverability attributes [,REUSE={YES|NO}] [,RSL={0|number|PUBLIC}] % security level of destination [,TRANSID=name] % Trans to be auto initiated [,TRIGLEV={1|number}] % Trans to accumulate DCT Destination Control Table - syntax for TYPE=REMOTE label DFHDCT TYPE=REMOTE ,DESTID=name % symbolic name of destination ,SYSIDNT=name % name of system or region [,LENGTH=length] % length in bytes of fixed recs [,RMTNAME=name] [,RSL={0|number|PUBLIC}] % security level of destination DCT Destination Control Table - syntax for TYPE=SDSCI label DFHDCT TYPE=SDSCI % Data Set Control Information ,DSCNAME=name % DDname [,BLKSIZE=length] [,BUFNO={1|number}] [,ERROPT={IGNORE|SKIP}] [,RECFORM={FIXUNB|FIXUNBA|FIXBLK|FIXBLKA| VARBLK|VARBLKA|VARUNB|BARUNBA}] [,RECSIZE=length] [,REWIND={LEAVE|REREAD}] [,SUFFIX=xx] % for non-resident control blk [,TYPEFLE={INPUT|OUTPUT|RDBACK}] DDIR DL/I Data Base Directory

    The DL/I data base directory (DDIR) contains an entry for each physical data base description (DBD).

    DDIR DL/I Data Base Directory - syntax for TYPE=INITIAL DFHDLDBD TYPE=INITIAL [,{DLI|DL1}=y.y.y] % IMS/VS level ver.rel.mod [,SUFFIX=xx] % Table suffix DDIR DL/I Data Base Directory - syntax for TYPE=ENTRY label DFHDLDBD TYPE=ENTRY ,DBD=dbdname % name of the DBD [,ACCESS={RO|RD|UP|EX}] % access intent of CICS PDIR DL/I Program Specification Block Directory DFHDLPSB TYPE=INITIAL [,{DLI|DL1}=y.y.y] % IMS/VS level ver.rel.mod [,SUFFIX=xx] % Table suffix label DFHDLPSB TYPE=ENTRY ,PSB=psbname % name of the DBD [,MXSSASZ=value] % access intent of CICS [,RMTNAME=name] [,SYSIDNT=name] % name of system or region FCT File Control Table

    The file control table (FCT) describes to CICS the user files that are processed by file management. CICS user files correspond to physical data sets that must have been defined to MVS and allocated to the CICS system before they are used. Because CICS file management processes only VSAM and BDAM data sets, any sequential data sets must be defined as extrapartition destinations by using the DFHDCT macro instruction. (see DCT)

    FCT File Control Table - syntax for TYPE=INITIAL DFHFCT TYPE=INITIAL [,SUFFIX=xx] % Table suffix FCT File Control Table - syntax for TYPE=DATASET label DFHFCT TYPE=DATASET ,DATASET=name % DDname for file ,ACCMETH={BDAM|VSAM} [,DISP={OLD|SHR}] % Type of enqueue [,DSNAME=name] % Actual Data Set Name [,FILSTAT=({ENABLED|DISABLED} ,{CLOSED|OPENED})] [,JID={NO|SYSTEM|nn}] % Auto Journalling [,JREQ={ALL|(request[,request,...)}] [,LOG={NO|YES}] % Automatic logging [,RECFORM=([{UNDEFINED|VARIABLE|FIXED}] ,[{BLOCKED|UNBLOCKED}] ,[DCB format])] [,RSL={0|number|PUBLIC}] % security level of destination [,SERVREQ=([ADD][,BROWSE][,DELETE][,READ][,UPDATE])] FCT File Control Table - syntax for TYPE=DATASET (VSAM only) [,BASE=name] % Group files with same base [,BUFND=number] % Number of data buffers [,BUFNI=number] % Number of index buffers [,DSNSHR={ALL|UPDATE}] % [,LSRPOOL={1|number|NONE}] % Local shared resource pool [,PASSWD=password] % Password for dataset [,STRNO={1|number}] % Number of concurrent strings FCT File Control Table - syntax for TYPE=DATASET (BDAM only) [,BLKKEYL=length] [,BLKSIZE=(length[,length])] [,KEYLEN=length] [,LRECL=length] [,RELTYPE={BLK|DEC|HEX}] [,RKP=number] % Relative key position [,SRCHM=number] [,VERIFY=YES] JCT Journal Control Table

    The journal control table (JCT) is the means by which you describe the system log and user journals and their characteristics to CICS for access through journal management. The JCT contains control information and operating system control blocks describing each journal.

    A journal may reside on tape or disk and may occupy either one or two tape drives or disk data sets. On MVS systems, the SMF data set may be used for user journals. This is specified through the JTYPE keyword of the DFHJCT TYPE=ENTRY macro instruction. The greater speed with which data can be written to tape should be considered in selecting the device to be used. This is especially significant when a disk drive contains other data sets that mey be used concurently with journaling or when you specify synchronous journal operations. Tape is also the better choice when journaled data is to be retained for a length of time.

    Standard labeled tape volumes can be used for system log and user journal data sets. Journal tapes are normally rewound and unloaded at end-of-volume or when the journal is closed. If two tape drives are assigned to a journal, the device is automatically switched at end-of-volume.

    Journal data sets on disk are reused when filled. If two data sets are specified, the system switches back and forth between them. If JOUROPT=PAUSE is specified through the DFHJCT TYPE=ENTRY macro instruction, a data set will not start to be reused until the console operator allows it. This protects the data until the operator verifies that it is no longer needed; the operator may wish to dump the data to tape or process it in some other way before it is destroyed. All disk extents for journal data sets must be preformatted prior to use in a CICS execution. After formatting, extents can be reused for successive CICS executions.

    You can specify where logging output will continue after a restart, using the JOUROPT operand.

    JCT Journal Control Table - syntax for TYPE=INITIAL DFHJCT TYPE=INITIAL [,SUFFIX=xx] % Table suffix JCT Journal Control Table - syntax for TYPE=ENTRY label DFHJCT TYPE=ENTRY ,JFILEID={SYSTEM|nn} % Journal Id number ,BUFSIZE=nnnnn % Buffer size [,BUFSUV=nnnnn] % Buffer shift up value [,FORMAT=SMF] [,JOUROPT=([CRUCIAL][,INPUT][,PAUSE][,RETRY] [,{LRU|EXTA}])] [,JTYPE={TAPE1|TAPE2|DISK1|DISK2|SMF}] [,LABEL={NO|STANDARD}] [,LAYOUT={LINEAR|CYCLIC}] [,OPEN={INITIAL|DEFERRED}] [,RSL={0|number|PUBLIC}] % security level of destination [,SYSWAIT={STARTIO|ASIS}] [,VOLCNT=number] MCT Monitoring Control Table

    The monitoring control table (MCT) describes the way the user data fields in the accounting and performance class monitoring records are to be manipulated at each user event monitoring point (EMP). It also identifies the CICS user journals in which the data for each monitoring class is to be recorded.

    User EMPs are defined in application programs using the EXEC CICS ENTER command or the DFHEMP macro instruction.

    MCT Monitoring Control Table - syntax for TYPE=INITIAL DFHMCT TYPE=INITIAL [,EVENT=YES] % use of SYSEVENT macro [,SUFFIX=xx] % Table suffix MCT Monitoring Control Table - syntax for TYPE=EMP label DFHMCT TYPE=EMP % User event monitoring points ,CLASS=([ACCOUNT][,PERFORM]) ,ID={number|(PP,number)|entryname.number} [,ACCOUNT=(option[,...])] [,CLOCK=(number,name1[,name2,...])] [,COUNT=(number,name1[,name2,...])] [,FIELD=(1,name)] [,PERFORM=(option[,...])] MCT Monitoring Control Table - syntax for TYPE=RECORD label DFHMCT TYPE=RECORD % Control data recording ,CLASS={ACCOUNT|EXCEPTION|PERFORM} [,CPU={NO|YES}] [,CONV=YES] ,DATASET=number [,EXCLUDE={ALL|n1[,...])}] [,EXIT={NO|YES}] ,FREQ=number [,INCLUDE=(m1[,...])] ,MAXBUF=number NLT Nucleus Load Table

    The nucleus load table (NLT) is provided to enable you to utilize virtual storage efficiently, by creating a load order that provides the smallest possible working set. The table is used by CICS to control the load order of the CICS nucleus. It allows you the option of changing the default load order established by the CICS system initialization program.

    The NLT is an optional feature of CICS. You specify the NLT to be used in the system initialization table. If NLT=NO is coded in DFHSIT (see ;)1.1.12 ) ,the default load order will be used.

    The modules specified in the NLT are loaded in the order and at the relative location specified in each DFHNLT TYPE=ENTRY macro instruction. When all specified modules have been loaded, a default list is used to load the remaining modules. The default NLT is contained in the system initialization module DFHSIB1. This module would be a good reference for any installation considering altering the default list.

    NLT Nucleus Load Table - syntax for TYPE=INITIAL DFHNLT TYPE=INITIAL [,PROTECT={NO|YES}] % Load in protect key 0 storage [,SHR={NO|YES}] % Use link pack area (LPA) [,SUFFIX=xx] % Table suffix NLT Nucleus Load Table - syntax for TYPE=ENTRY DFHNLT TYPE=ENTRY ,MODULE=name % CICS module name [,ALIGN={NO|ENTRY|YES}] % Page alignment [,FIX={NO|YES}] % Page Fixed [,PROTECT={NO|YES}] % Load in protect key 0 storage [,SHR={NO|YES}] % Use link pack area (LPA) PCT Program Control Table

    The program control table (PCT) contains the control information to be used by CICS for identifying and initializing a transaction. This table is required by CICS to verify the incoming transaction request, and to supply information about the transaction such as the transaction priority, the security key, and the length of the transaction work area (TWA). Task control uses a portion of each PCT entry to accumulate transaction statistics.

    PCT Program Control Table - syntax for TYPE=INITIAL DFHPCT TYPE=INITIAL [,DTB={YES|NO|(YES,NO)|(YES,WAIT)}] [,EXTSEC={NO|YES}] % External security facility [,FDUMP={(ASRA,ASRB)|ASRA|ASRB}] [,SCRNSZE={DEFAULT|ALTERNATE}] [,SUFFIX=xx] % Table suffix [,TRANSEC=([MASTER(nn)] [,SVR(nn)][,FE(nn)][,EDF(nn)] [,INTERPRETER(nn)][,MIRROR(nn)] [,ROUTING(nn)][,RDO(nn)])] PCT Program Control Table - syntax for TYPE=ENTRY label DFHPCT TYPE=ENTRY ,PROGRAM=name % Name of program ,TASKREQ=xxxx % External security facility ,TRANSID=transaction-identification [,ANTICPG={NO|YES|nn}] [,DTB={YES|NO|(YES,NO)|(YES,WAIT)}] [,DTIMOUT={NO|numeric-value}] [,DUMP={YES|NO}] [,DVSUPRT={ALL|NONV|VTAM}] [,EXTSEC={NO|YES}] % External security facility [,FDUMP={(ASRA,ASRB)|ASRA|ASRB}] [,PARTSET={psetname|KEEP|OWN}] [,PRMSIZE=decimal-value] [,PTRCOMP={NO|YES}] [,RESTART={NO|YES}] [,RSL={0|number|PUBLIC}] % security level of destination [,RSLC={NO|YES|EXTERNAL}] [,RTIMOUT={NO|numeric-value}] [,SCRNSZE={DEFAULT|ALTERNATE}] [,SPURGE={NO|YES}] [,TCLASS={NO|transaction-class}] [,TPURGE={NO|YES}] [,TRACE={YES|NO}] [,TRANSEC={1|decimal-value}] [,TRNPRTY={1|decimal-value}] [,TRNSTAT={ENABLED|DISABLED}] [,TWASIZE={0|decimal-value}] [,XTRANID=hexadecimal-transaction-identifier] VTAM only [,INBFMH={EODS|ALL|DIP|NO}] [,JFILEID={NO|SYSTEM|nn}] [,LOGREC={NO|YES}] [,MODENAM=modename] [,MSGJRNL={INPUT|OUTPUT|(INPUT,OUTPUT)}] [,NEPCLAS={0|integer}] [,OPTGRP=name] [,RAQ={NO,YES}] PCT Program Control Table - syntax for TYPE=GROUP label DFHPCT TYPE=GROUP % Special entries ,FN=([AKP][,AUTOSTAT][,BMS][,CONSOLE] [,DLI][,EDF][,FE][,HARDCOPY][,INTERPRETER] [,ISC][,JOURNAL][,MASTTERM][,MSWITCH] [,MVS][,NUMERICS][,OPENCLSE][,OPERATORS] [,RDO][,RESEND][,RESPLOG][,RMI][,SIGNON] [,STANDARD]) [,EXTSEC={NO|YES}] % External security facility [,KEYID=xxxx] PCT Program Control Table - syntax for TYPE=OPTGRP label DFHPCT TYPE=OPTGRP % Transaction desc options [,MSGPOPT=([CCONTRL][,MSGINTEG] [,ONEWTE][,PROTECT])] [,MSGPREQ=([CCONTRL][,MSGINTEG] [,ONEWTE][,PROTECT])] PCT Program Control Table - syntax for TYPE=PROFILE label DFHPCT TYPE=PROFILE % Session processing options ,PROFILE=name [,INBFMH={NO|ALL}] [,JFILEID={NO|SYSTEM|nn}] [,MODENAM=modename] [,MSGJRNL=([INPUT][,OUTPUT])] [,NEPCLAS={0|integer}] PCT Program Control Table - syntax for TYPE=REMOTE label DFHPCT TYPE=REMOTE % Remote transactions ,SYSIDNT=name % System identifier ,TASKREQ=xxxx % External security facility ,TRANSID=transaction-identification [,DTB={YES|NO|(YES,NO)|(YES,WAIT)}] [,DTIMOUT={NO|numeric-value}] [,DVSUPRT={ALL|NONV|VTAM}] [,EXTSEC={NO|YES}] % External security facility [,FDUMP={(ASRA,ASRB)|ASRA|ASRB}] [,JFILEID={NO|SYSTEM|nn}] [,LOCALQ={NO|YES}] [,LOGREC={NO|YES}] [,MSGJRNL=([INPUT][,OUTPUT])] [,NEPCLAS={0|integer}] [,OPTGRP=name] [,PTRCOMP={NO|YES}] [,RAQ={NO,YES}] [,RESTART={NO|YES}] [,RSL={0|number|PUBLIC}] % security level of destination [,RSLC={NO|YES|EXTERNAL}] [,RTIMOUT={NO|numeric-value}] [,SCRNSZE={DEFAULT|ALTERNATE}] [,SPURGE={NO|YES}] [,TCLASS={NO|transaction-class}] [,TPURGE={NO|YES}] [,TRACE={YES|NO}] [,TRANSEC={1|decimal-value}] [,TRNPRTY={1|decimal-value}] [,TRPROF={DFHCICSS|name}] [,TWASIZE={0|decimal-value}] [,XTRANID=hexadecimal-transaction-identifier] PLT Program List Table

    A program list table (PLT) contains a list of related programs. You may wish to generate several PLT's for one or more of the following reasons:

    Any number of PLT's can be generated for the above purposes provided that:

    1. Each PLT has a unique suffix.
    2. Each PLT is named in an entry in the PPT as if it were a program.
    3. Each program named in a PLT must also be name in an entry in the PPT.
    PLT Program List Table - syntax for TYPE=INITIAL DFHPLT TYPE=INITIAL [,SUFFIX=xx] % Table suffix PLT Program List Table - syntax for TYPE=ENTRY DFHPLT TYPE=ENTRY ,PROGRAM=(program[,program,...]) PPT Processing Program Table

    The processing program table (PPT) allows you to describe to program control the control information for all user-written and CICS-supplied application programs and maps. In addition, program control uses portions of each table entry to retain certain information for maintaining control of your programs and to capture program statistics.

    This table is required by CICS to verify the processing program identification, to keep count of the number of tasks using that program, to maintain the address of the processing program, to maintain the direct access address and size of the program, and to maintain statistics on the processing program.

    PPT Processing Program Table - syntax for TYPE=INITIAL DFHPPT TYPE=INITIAL [,SUFFIX=xx] % Table suffix PPT Processing Program Table - syntax for TYPE=ENTRY DFHPPT TYPE=ENTRY {,PROGRAM=name|,MAPSET=name|PARTSET=name} [,PGMLANG={ASSEMBLER|COBOL|PL/I}] [,PGMSTAT={ENABLED|DISABLED}] [,RELOAD={NO|YES}] [,RES={NO|ALIGN|FIX|PGOUT|YES}] [,RSL={0|number|PUBLIC}] % security level of destination [,USAGE=MAP] SIT System Initialization Table

    The initialization of CICS is both flexible and dynamic.

    Flexibility at the time of initialization is provided by the system initialization table (SIT). The contents of the SIT macro instruction, which is assembled as a table, supplies the system initialization program with the information to initialize the system to suit your unique environment.

    SIT System Initialization Table - syntax for TYPE=CSECT DFHSIT TYPE={CSECT|DSECT} [,ABDUMP={YES|NO}] % system dump for ASRB abends [,AKPFREQ={200|nnnnn} % Activity keypoint frequency [,ALT={NO|xx|YES}] % Application load table [,AMXT={MXT-value|nnnnn}] % Max dispatchable tasks [,APPLID={DBDCICS|name}] % VTAM APPLID [,AUTINST=({100|nnnnn},{DFHZATDX|name})] % term auto install [,AUXTR={OFF|ON}] % Auxilary trace [,BFP={YES|NO}] % Built in functions program [,BMS=({FULL|MINIMUM|STANDARD}[,COLD] [,{UNALIGN|ALIGN}][,{DDS|NODDS}])] % Basic mapping opt [,CICSSVC={216|nnn}] % CICS type 2 SVC [,CMXT=([V1][,V2]...[,V10])] % Max task per transaction class [,COBOL2={NO|YES}] % VS COBOL II [,CSA=COLD] % cold start the CSA [,DATFORM={MMDDYY|DDMMYY|YYMMDD}] [,DBP={NO|xx|YES}] % Dynamic transaction backout prog [,DBUFSZ={500|nnnnn}] % buffer size for dynamic backout [,DCT=([{YES|xx|NO}][,COLD])] % Destination control table [,DDIR={YES|xx}] % suffix for DDIR list [,DIP={NO|YES}] % batch data interchange program [,DLDBRC={NO|YES}] % data base recovery control [,{DLI|DL1}=({NO|YES}[,COLD])] % DL/I code [,DLIRLM={NO|YES|name}] % IMS/VS resource lock manager [,DLLPA={NO|YES}] % IMS/VS use of LPA [,DLMON={NO|YES}] % IMS/VS monitoring [,DLTHRED={1|nnnnn}] % num threads for IMS/VS interface [,DLXCPVR={NO|YES}] % page-fix ISAM or OSAM buffers [,DMBPL={4|nnnnn}] % IMS/VS DMB pool size [,DTB={MAIN|AUX}] % DTB buffer spill [,DUMP={NO|{FORMAT|PARTN|FULL][,{SNAP|SDUMP}])] [,DUMPDS={AUTO|A|B}] % Dump dataset to be opened [,ENQPL={2|nnnnn}] % IMS/VS ENQ control block space [,EXEC={YES|NO}] % Command level support [,EXITS={NO|YES}] % user exit interface [,EXTSEC=({NO|YES}[,{NOPREFIX|PREFIX}])] % external security [,FCT=([{YES|xx|NO}][,COLD])] % File control table [,FLDSEP='xxxx'] % [,FLDSTRT='x'] % [,GMTEXT={WELCOME TO CICS/VS|'text'}] [,GMTRAN={CSGM|name}] % tran initiatied when VTAM logon [,GRPLIST=name] % list of groups for CSD [,ICP=COLD] % cold start interval control prog [,ICV={1000|nnnnn}] % region exit time in milliseconds [,ICVR={5000|nnnnn}] % runaway task time interval [,ICVS={20000|nnnnn}] % system stall time interval [,ICVTSD={500|nnnnn}] % terminal scan delay facility [,IOCP={0|nnnnn}] % percent of short term events wait [,IRCSTRT={NO|YES}] % interregion environment for DL/I [,ISC={NO|YES}] % Intercommunication group programs [,JCT={YES|xx|NO}] % Journal control table [,LGNMSG={NO|YES}] % VTAM logon data passed to applic [,LPA={NO|YES}] % CICS modules used from the LPA [,MAXSMIR={999|nnnnn}] % max num suspended mirror tasks [,MCT={NO|YES|xx}] % Monitor control table [,MONITOR=([ACC][,PER][,EXC][,EVE])] [,MSGLVL={1|0}] % Messages displayed during init [,MXT={5|nnnnn}] % max number of tasks [,NLT={NO|xx|YES}] % Nucleus load table [,OPNDLIM={10|nnnnn}] % OPNDST and CLSDST request limit [,OSCOR={8192|nnnnn}] % Storage reserved for OS [,PCDUMP={YES|NO}] % system dump for ASRA abends [,PCT={YES|xx|NO}] % Program control table [,PDIR={YES|xx}] % suffix for the PDIR list [,PGCHAIN=character(s)] % [,PGCOPY=character(s)] % [,PGPURGE=character(s)] % [,PGRET=character(s)] % [,PGSIZE={2048|4096}] % CICS virtual page size [,PISCHD={YES|NO}] % program isolation scheduling [,{PLI|PL1}={NO|YES}] % PL/I programs to be processed [,PLISHRE={NO|YES}] % PL/I shared library support [,PLTPI={NO|xx|YES}] % PLT at initialization [,PLTSD={NO|xx|YES}] % PLT at shutdown [,PPT={YES|xx|NO}] % Processing program table [,PRGDLAY={0|hhmm}] % BMS purge delay time interval [,PRINT={NO|YES|PA1|PA2|PA3}] [,PSBCHK={NO|YES}] % DL/I Security checking [,PSBPL={4|nnnnn}] % DL/I PSB pool size [,RAMAX={256|nnnnn}] % I/O area for Receive any [,RAPOOL={2|nnnnn}] % num fixed RPL's generated [,SCS={12288|nnnnn}] % Storage cushion in bytes [,SIMODS={(A1,B1,C1,D1,E1,F1,G1,H1,I1,J1)| (phase,...)}] % System initialization modules [,SKRxxxx='page-retrieval-command'] % single keystroke retrev [,SPOOL={NO|YES}] % system spooling interface [,SRBSVC={215|nnn}] % CICS type 6 SVC [,SRT={YES|xx|NO}] % System recovery table [,START={AUTO|COLD}] % Type of start [,STARTER=YES] % prefixes with $ and # allowed [,SUFFIX=xx] % Table suffix [,SVD={1|nn|YES|NO}] % storage violation dump [,SYSIDNT={CICS|name}] % ident of this CICS region [,TBEXITS=([name1][,name2][,name3][,name4])] [,TCAM={NO|YES}] % TCAM support [,TCP={YES|xx|NO}] % BSC Terminal control program [,TCT={YES|xx|NO}] % Terminal control table [,TD=({3|nnn}[,{3|nnn}])] % Transient data program & buffers [,TRACE=([{125|nnn}][,{ON|OFF}])] % num entries and status [,TRAP={OFF|ON}] % FE global trap activated [,TS=([COLD] [,{3|0|nnn}] [,{3|nnn}])] % Temporary storage [,TSMGSET={4|nnn}] % temp storage message set [,TST={NO|YES|xx}] % Temporary storage table [,VSP={NO|YES}] % MVS subtasking facility [,VTAM={YES|NO}] % VTAM support [,WRKAREA={512|nnn}] % CSA user work area size [,XLT={NO|xx|YES}] % Transaction list table [,XDCT={YES|name|NO}] % RACF for DCT [,XFCT={YES|name|NO}] % RACF for FCT [,XJCT={YES|name|NO}] % RACF for JCT [,XPCT={YES|name|NO}] % RACF for PCT [,XPPT={YES|name|NO}] % RACF for PPT [,XPSB={YES|name|NO}] % RACF for PSB [,XTP={NO|YES}] % Trans routing transformer prog [,XTRAN={YES|name|NO}] % RACF for attached trans entries [,XTST={YES|name|NO}] % RACF for temp storage entries [,ZCP=({YES|xx}[,NOHPO|HPO}])] % VTAM terminal control program SNT Sign-On Table

    The sign-on table (SNT) provides a place for retaining terminal operator data permanently. It is accessed when a terminal operator initiates the sign-on procedure via the CESN or (CSSN) transaction. The SNT is the only table that cannot be suffixed.

    SNT Sign-On Table - syntax for TYPE=INITIAL DFHSNT TYPE=INITIAL [,EXTSEC={NO|YES}] % External security system SNT Sign-On Table - syntax for TYPE=ENTRY DFHSNT TYPE=ENTRY [,EXTSEC={NO|YES}] % External security system [,NAMFORM=DEC] % OP ID reader on terminal [,OPCLASS={1|(n1[,n2],...)}] % Operator classes [,OPIDENT=xxx] % Operator identification [,OPNAME='operator name'] % Operator name [,OPPRTY={0|nnn}] % Operator priority [,PASSWRD=xxxxxxxx] % Operator password [,RSLKEY=(n1[,n2],...)] % Resource security level key [,SCTYKEY={1|(n1[,n2],...)}] % Security key values [,TIMEOUT=nnn] % sign off unused terminal [,USERID=xxxxxxxx] % RACF user identification SRT System Recovery Table

    The system recovery table (SRT) contains a list of abend codes that will be intercepted. It also contains the identification of logic to be executed in the form of either a user- or a CICS-supplied routine.

    SRT System Recovery Table - syntax for TYPE=INITIAL DFHSRT TYPE=INITIAL [,SUFFIX=xx] % Table suffix SRT System Recovery Table - syntax for TYPE={SYSTEM|USER} DFHSRT TYPE={SYSTEM|USER} ,ABCODE=(abend,...) % abend codes to be handled {[,PROGRAM=program]| % program to be given control [,ROUTINE=name]} % resident routine name TCT Terminal Control Table

    The terminal control table (TCT) describes a configuration of terminals, logical units, and other DB/DC systems in a CICS network that the CICS system can communicate with. In an SNA network, logical units (LU's) are ports through which a user of the network gains access to the network facilities. CICS communicates with logical units that are associated with its terminals.

    TCT Terminal Control Table - syntax for TYPE=INITIAL DFHTCT TYPE=INITIAL ,ACCMETH=(VTAM[,NONVTAM][,GAM]) [,ERRATT={NO|([LASTLINE][,INTENSIFY] [,{BLUE|RED|PINK|GREEN|TURQUOISE |YELLOW|NEUTRAL}] [,{BLINK|REVERSE|UNDERLINE}])}] [,MIGRATE={YES|COMPLETE}] [,RESP={FME|RRN}] [,SUFFIX=xx] % Table suffix TCT Terminal Control Table - syntax for TYPE=TERMINAL DFHTCT TYPE=TERMINAL ,ACCMETH=VTAM ,TRMIDNT=name ,TRMTYPE=type [,ALTPGE=(lines,columns)] [,ALTPRT=(label[,COPY])] [,ALTSCRN=(lines,columns)] [,ALTSFX=number] [,BMSFEAT=([NOROUTE][,NOROUTEALL] [,OBOPID][,OBFMT])] [,BRACKET={YES|NO}] [,BUFFER=buffer-size] [,CHNASSY={NO|YES}] [,CONNECT=AUTO] [,DEFSCRN=(lines,columns)] [,ERRATT={NO|([LASTLINE][,INTENSIFY] [,{BLUE|RED|PINK|GREEN|TURQUOISE |YELLOW|NEUTRAL}] [,{BLINK|REVERSE|UNDERLINE}])}] [,FEATURE=(feature[,feature],...)] [,FF={NO|YES}] [,GMMSG={NO|YES}] [,HF={NO|YES}] [,LASTTRM=VTAM] [,LOGMODE=name] [,NETNAME={name-in-TRMIDNT|name}] [,OPERID=operator-id-code] [,OPERPRI=operator-priority-code] [,OPERRSL=(number,[,...])] [,OPERSEC={1|(number,[,...])}] [,PGESIZE=(lines,columns)] [,PGESTAT={AUTOPAGE|PAGE}] [,PRINTTO=(label[,COPY])] [,RELREQ=({NO|YES},{NO|YES})] [,RUSIZE={256|number}] [,SIGNOFF={YES|NO}] [,TCTUAL=number] [,TIOAL={value|(value1,value2)}] [,TRANSID=transaction-identification-code] [,TRMMODL=number] [,TRMPRTY={0|number}] [,TRMSTAT={TRANSACTION|(status[,status],...)}] [,USERID=userid] [,VF={NO|YES}] TLT Terminal List Table

    A terminal list table (TLT) generated by the DFHTLT macro instruction allows terminal and/or operator identifications to be grouped logically.

    TLT Terminal List Table - syntax for TYPE=INITIAL DFHTLT TYPE=INITIAL [,:DC=aa] % Logical device code [,SUFFIX=xx] % Table suffix TLT Terminal List Table - syntax for TYPE=ENTRY DFHTLT TYPE=ENTRY ,TRMIDNT=([termid-1[*ldc-1][/opid-1] [,termid-2[*ldc-2][/opid-2],...]) TST Temporary Storage Table

    The temporary storage table (TST) is a list of generic mnemonics used to identify temporary storage DATAID's. When a task modifies temporary storage data designated as recoverable, the data is protected from modification by a concurrent task by enqueuing on the data identification (DATAID). The DATAID is not dequeued until the task terminates or issues a task sync point request to designate the end of a logical unit of work. At this time a log record is written to the system log data set to provide external information sufficient to recover the data if the system subsequently terminates abnormally.

    TST Temporary Storage Table - syntax for TYPE=INITIAL DFHTST TYPE=INITIAL [,SUFFIX=xx] % Table suffix [,TSAGE={0|number}] % TS aging limit TST Temporary Storage Table - syntax for TYPE=ENTRY/RECOVERY DFHTST TYPE={RECOVERY|ENTRY} [,DATAID=(char-string,char-string,...)] TST Temporary Storage Table - syntax for TYPE=REMOTE DFHTST TYPE=REMOTE ,DATAID=char-string ,SYSIDNT=name [,RMTNAME=character-string] TST Temporary Storage Table - syntax for TYPE=SECURITY DFHTST TYPE=SECURITY ,DATAID=char-string [,RSL={0|number|PUBLIC}] XLT Transaction List Table

    The transaction list table (XLT), generated by the DFHXLT macro instruction, is a list of logically related transaction identifications. The XLT can be used to define:

    XLT Transaction List Table - syntax for TYPE=INITIAL DFHXLT TYPE=INITIAL [,SUFFIX=xx] % Table suffix XLT Transaction List Table - syntax for TYPE=ENTRY DFHXLT TYPE=ENTRY [,TASKREQ=(kkkk[,kkkk],...)] [,TRANSID=(xxxx[,xxxx],...)]