You can use the sample job control statements shown in Figure 44 on the following pages to initialize a CICS® region. The sample job stream shown in Figure 44 specifies START=AUTO and XRF=YES to start an active CICS region. The notes that follow Figure 44 explain which statements are unique to XRF, and can therefore be omitted if you want to run with XRF=NO.
The sample startup job stream is based on the system initialization parameters contained in the CICS-supplied sample table, DFHSIT6$.
For more information about the DD statements in this job stream that are needed by CICS and IMS™, see the appropriate section in Defining data sets.
JCL similar to that in Figure 44 is supplied as a sample startup procedure, DFHSTART, in the CICSTS31.CICS.SDFHINST library. You can use the DFHSTART procedure to start the CIC regions, or as a basis for your own startup procedures. For information about the DFHSTART procedure, see the CICS Transaction Server for z/OS® Installation Guide.
/*
//* 1 The JOB statement
//CICSRUN JOB accounting info,name,CLASS=A,
// MSGCLASS=A,MSGLEVEL=(1,1)
//*
//* 2 The JOBPARM statement
/*JOBPARM SYSAFF=sysid
/*
//***********************************************************
//******************* EXECUTE CICS ************************
//***********************************************************
//*
//* 3 The EXEC CICS=DFHSIP statement
//CICS EXEC PGM=DFHSIP,REGION=240M,
//* 4 SIT parameters specified on PARM parameter
// PARM=('SIT=6$',
// 'DSALIM=6M,EDSALIM=120M',
// 'RENTPGM=PROTECT,STGPROT=YES',
// 'START=AUTO,SI')
//*
//* 5 SIT parameters specified on the SYSIN data set
//SYSIN DD *
GRPLIST=(DFHLIST,userlist1,userlist2),
LPA=YES,
APPLID=CICSHTH1,
DFLTUSER=CICSUSER, The default userid
MXT=30, Maximum number of user tasks is 30
INITPARM=(DFHDBCON='01',DFHD2INI=('MYDB')),
Pass DFSPZP01 suffix to DBCTL connect program
Connect to DB2 subsystem MYDB
ISC=YES, Include intersystem communication program
IRCSTRT=YES, Start interregion communication
.END
/*
//* 6 The STEPLIB library
//STEPLIB DD DSN=CICSTS31.CICS.SDFHAUTH,DISP=SHR
// DD DSN=CICSTS31.CICS.SDFJAUTH,DISP=SHR
// DD DSN=CEE.SCEERUN2,DISP=SHR
// DD DSN=CEE.SCEERUN,DISP=SHR
//*
//* 7 The CICS library (DFHRPL) concatenation
//DFHRPL DD DSN=CICSTS31.CICS.SDFHLOAD,DISP=SHR
//* Your application library
// DD DSN=your.prog.library,DISP=SHR
//* Your CICS control tables library
// DD DSN=your.table.library,DISP=SHR
//* The Language Environment runtime data sets
// DD DSN=CEE.SCEECICS,DISP=SHR
// DD DSN=CEE.SCEERUN2,DISP=SHR
// DD DSN=CEE.SCEERUN,DISP=SHR
//* The Debug Tool runtime library
// DD DSN=EQA.SEQAMOD,DISP=SHR
//* 7a The DB2 load library
// DD DSN=SYS2.DB2.SDSNLOAD,DISP=SHR
//* 8 Auxiliary temporary storage data sets
//DFHTEMP DD DSN=CICSTS31.CICS.CNTL.CICSHTH1.DFHTEMP,DISP=SHR
//*
//* 9 Intrapartition data sets
//DFHINTRA DD DSN=CICSTS31.CICS.CNTL.CICSHTH1.DFHINTRA,DISP=SHR
//*
//* 10 The auxiliary trace data sets
//DFHAUXT DD DSN=CICSTS31.CICS.CICSHTH1.DFHAUXT,DISP=SHR
//DFHBUXT DD DSN=CICSTS31.CICS.CICSHTH1.DFHBUXT,DISP=SHR
//*
//* 11 Extrapartition data sets
//DFHCXRF DD SYSOUT=*
//LOGUSR DD SYSOUT=*,DCB=(DSORG=PS,RECFM=V,BLKSIZE=136)
//MSGUSR DD SYSOUT=*,DCB=(DSORG=PS,RECFM=V,BLKSIZE=136)
//PLIMSG DD SYSOUT=*,DCB=(DSORG=PS,RECFM=V,BLKSIZE=137)
//COUT DD SYSOUT=*,DCB=(DSORG=PS,RECFM=V,BLKSIZE=137)
//CEEMSG DD SYSOUT=A
//CEEOUT DD SYSOUT=A
//*
//* 12 The CICS local catalog data set
//DFHLCD DD DSN=CICSTS31.CICS.CICSHTH1.DFHLCD,DISP=SHR
//* 13 The CICS global catalog data set
//DFHGCD DD DSN=CICSTS31.CICS.CICSHTH1.DFHGCD,DISP=SHR,
// AMP=('BUFND=33,BUFNI=32,BUFSP=
319488
')
//*
//* 14 The CAVM data sets - XRF
//DFHXRMSG DD DSN=CICSTS31.CICS.CNTL.CICSHTH1.DFHXRMSG,DISP=SHR
//DFHXRCTL DD DSN=CICSTS31.CICS.CNTL.CICSHTH1.DFHXRCTL,DISP=SHR
//*
//* 15 The transient data destination data set (CXRF)
//DFHCXRF DD SYSOUT=A
//*
//* 16 The CICS transaction dump data sets
//DFHDMPA DD DSN=CICSTS31.CICS.CICSHTH1.DFHDMPA,DISP=SHR
//DFHDMPB DD DSN=CICSTS31.CICS.CICSHTH1.DFHDMPB,DISP=SHR
//*
//* 17 MVS system dump data sets
//SYSABEND DD SYSOUT=*
//SYSMDUMP DD DSN=SYS1.SYSMDP00,VOL=SER=volid,SPACE=(CYL,(1,1)),
// DISP=OLD,UNIT=3380
//* SYSUDUMP DD SYSOUT=*
//*
//* 17a Default stdout file for C-language system services used by CICS
//SYSPRINT DD SYSOUT=*
//* 18 The CICS system definition data set
//DFHCSD DD DSN=CICSTS31.CICS.DFHCSD,DISP=SHR
//*
//* 19 The CICS BTS local request queue data set
//DFHLRQ DD DSN=CICSTS31.CICS.DFHLRQ,DISP=SHR
//*
//* 20 The EJB directory and object store data sets
//DFHEJDIR DD DSN=CICSTS31.CICS.DFHEJDIR,DISP=SHR
//DFHEJOS DD DSN=CICSTS31.CICS.DFHEJOS,DISP=SHR
//* 21 The CMAC data file
//DFHCMACD DD DSN=CICSTS31.CICS.DFHCMACD,DISP=SHR
//*
//* 22 The CDBM group command file
//DFHDBFK DD DSN=CICSTS31.CICS.DFHDBFK,DISP=SHR
//*
//* 23 FILEA & other permanently allocated data sets
//* (The FILEA DD statement below overrides the CSD definition in
//* group DFHMROFD)
//FILEA DD DISP=SHR,
// DSN=CICSTS31.CICS.CICSHTH1.FILEA
//*
//APPLICA DD DSN=CICSTS31.CICS.CICSHTH1.APPLICA,DISP=SHR
//APPLICB DD DSN=CICSTS31.CICS.CICSHTH1.APPLICB,DISP=SHR
//*
//*
//* 24
//PRINTER DD SYSOUT=A,DCB=BLKSIZE=125,OUTLIM=0
//CARDIN DD *
·
·
·
\user transactions input from sequential terminal \
·
·
·
\CESF GOODNIGHT\
/*
Notes:
1 The JOB statement
The JOB statement specifies the accounting information that you want to use for this run of CICS. For example:
//CICSRUN JOB 24116475,userid,MSGCLASS=A,MSGLEVEL=(1,1),
// CLASS=A,NOTIFY=userid
2 The JOBPARM statement
The JES JOBPARM statement is included to identify the MVS™ image on which this CICS (the active CICS region) is to run. If the alternate CICS region is to run on a different MVS image, the job stream for the alternate CICS region specifies the system identifier of the other MVS image.
3 The EXEC PGM=DFHSIP statement
DFHSIP is the program that starts CICS initialization.
CICS does not support more than one EXEC PGM=DFHSIP job step in the same MVS job.
The EXEC statement contains the REGION parameter to define the size of CICS MVS region. In this example, the value is set to 240, requesting MVS to allocate to the job all 16MB of private storage below the 16MB line, and an extended region size of 240MB.
You determine how much of the allocated private storage you want for the CICS dynamic storage areas, and how much CICS is to leave for demands on operating system storage, by setting values for the DSALIM and EDSALIM system initialization parameters. After obtaining the amount of space required for the DSAs from the total defined by the REGION parameter, the remaining storage is available to meet demands for operating system storage.
In our sample job stream, these system initialization parameters are specified in the PARM parameter (see the next topic).
For more details about the REGION parameter and CICS storage, see Storage requirements for a CICS region.
If you are running CICS with RACF® support, see the CICS RACF Security Guide for information about RACF-related parameters.
4 SIT options on the PARM parameter
You can use the PARM parameter of the EXEC statement to specify system initialization parameters as shown.
The information passed by the PARM parameter is limited to 100 characters. This limit includes all commas, but excludes the apostrophes delimiting the PARM strings, and excludes the opening and closing parentheses delimiting the PARM parameter. (Internal parentheses enclosing system initialization operands are included.) If 100 characters are not sufficient for the system initialization parameters you want to provide at startup, indicate continuation by ending the PARM field with the "SYSIN" or "CONSOLE" control keywords (or "SI" or "CN" for short). If you specify SYSIN, system initialization parameters are read from the SYSIN data set; if you specify CONSOLE, CICS prompts you to enter parameters through the console. However, if all of your runtime system initialization parameters are in the PARM parameter, you can end the PARM field simply without any control keywords, or by the .END control keyword.
In our example, DFHSIT6$ is the SIT selected, and CICS system initialization uses the values in that table, modified by the system initialization parameters supplied in the PARM field and the SYSIN data set. For this example, the following system initialization parameters are provided in the PARM parameter:
If you are running CICS with XRF, START=AUTO causes CICS to initialize as an active CICS region. To request initialization of CICS as an alternate CICS region, specify XRF=YES and START=STANDBY.
For information about the types of CICS startup and shutdown in an XRF environment, see the CICS Operations and Utilities Guide.
You can include the SYSIN data set inline as part of the job stream. System initialization parameters entered in the SYSIN data set replace any, for the same keyword, that were entered in the PARM parameter. If you include the same parameter more than once, the last value read is the value used for initialization except for INITPARM. If you specify the INITPARM keyword and its parameters more than once, each one is accepted by CICS, for example:
* The following INITPARM parameters are for DBCTL and a user program
INITPARM=(DFHDBCON='XX,DBCON2',userprog='a,b,c')
* The following INITPARM parameter is for DB2
INITPARM=(DFHD2INI= 'DBA2')
Unless you explicitly code the system initialization control keyword CONSOLE, CICS stops reading system initialization parameters when it reaches the end of SYSIN or a .END control keyword.
In the sample job, CONSOLE is not coded in either PARM or SYSIN. The .END control keyword is the last entry in SYSIN, so CICS does not prompt through the console for further system initialization parameters. After reading the SYSIN data set, CICS loads the specified SIT, applies any system initialization parameters supplied in the PARM field and the SYSIN data set, and begins the initialization process.
The SYSIN data set in our example includes several system initialization parameters, as follows:
If you want this CICS region to use XRF, you must define both a generic and specific applids; for example, by:
APPLID=(CICSID,CICSHTH1),
CICSID is the generic applid of this CICS region, and CICSHTH1 is the specific applid of the active CICS region. With XRF=YES, the active and alternate CICS regions share the same generic applid, but have different specific applids.
The specific applid can be useful for naming those data sets that are unique (for example, dump data sets). Where necessary, it can be used as the second-level qualifier to distinguish the data sets of the active and alternate CICS regions.
For guidance information about installing the CICS SVC in the LPA, and defining it to MVS, see the CICS Transaction Server for z/OS Installation Guide.
STEPLIB is the DDNAME of the library containing the modules loaded by the operating system. DFHSIP, which is loaded from STEPLIB, must receive control in an authorized state, so each partitioned data set (library) concatenated in STEPLIB must be individually APF-authorized. In this sample job stream, the CICS authorized library is CICSTS31.CICS.SDFHAUTH. CICSTS31.CICS.SDFJAUTH is also included, which is required for Java™ support, and must also be APF-authorized. If you do not require Java support, you need not include this library.
Placing user-written modules into an APF-authorized library may violate your security and integrity rules. The CICSTS31.CICS.SDFHAUTH library (and the CICSTS23.CICS.SDFJAUTH library, if used) should not be included in the MVS link list, so that you can protect the libraries and thereby ensure that only approved users are able to execute the DFHSIP module. When you define your STEPLIB DD statement, remember that all other libraries concatenated with the CICSTS31.CICS.SDFHAUTH library or the CICSTS23.CICS.SDFJAUTH library must also be APF-authorized (for example, IMS.RESLIB). This is because, if any of the libraries in a STEPLIB concatenation are not authorized, MVS regards all of them as unauthorized. (If there is a non-authorized library in the STEPLIB concatenation, CICS fails to start up, and issues message DFHKE0101 to indicate that the DFHSIP module is not in an APF-authorized library.) For information about authorizing access to CICS data sets, see the CICS RACF Security Guide.
The pregenerated DFHSIP module, which has been link-edited with the authorized attribute (SETCODE AC(1)), is supplied in CICSTS31.CICS.SDFHAUTH.
You also need the Language Environment® runtime libraries, CEE.SCEERUN
and CEE.SCEERUN2, in the STEPLIB concatenation (or the MVS linklist) to
run COBOL, PL/I, C and C++, and Java programs that run in a JVM, under Language Environment. The order of the SCEERUN and SCEERUN2 libraries
in relation to each other is important. SCEERUN2 must appear in the concatenation
before SCEERUN. Like SDFHAUTH, SCEERUN and SCEERUN2 must be an APF-authorized
library.
The CICS DB2 attachment facility has to load the DB2 program request handler, DSNAPRH. To do this, the DB2 library DSNxxx.SDSNLOAD library should be placed in the MVS linklist, or added to the STEPLIB concatenation of the CICS job.
7 CICS module load library (DFHRPL) concatenation
DFHRPL is the DD name of the library that contains modules loaded by CICS. Protect individually the partitioned data sets constituting this library to prevent unapproved or accidental modification of their contents. The DFHRPL concatenation must include the library containing your CICS application programs, shown in our example as "your.prog.library", and your CICS control tables, shown in our example as "your.table.library".
In this sample job stream, the CICS-supplied library is CICSTS31.CICS.SDFHLOAD, which must be included in the CICS DFHRPL library concatenation. The CICSTS31.CICS.SDFHLOAD library contains only programs that run in problem state and should not be authorized.
Language Environment runtime library requirements
You are recommended to use the services of Language Environment, which provides a common runtime environment for IBM implementations of assembler and those high-level languages (HLLs) supported by CICS, namely COBOL, PL/I, C, and C++.
To use the Language Environment runtime libraries to
support all your program languages, add the Language Environment runtime libraries SCEERUN2 and SCEERUN to the DFHRPL DD concatenation.
The SCEERUN2 library must appear in the concatenation before SCEERUN. If you
are running COBOL programs, also add Language Environment runtime library SCEECICS to DFHRPL. The SCEECICS library must be concatenated
before the SCEERUN library. Remove any libraries that contain runtime routines
from earlier versions of COBOL, PL/I, and C/C++ from the DFHRPL DD concatenation.
Debug Tool library
If you are using Debug Tool to debug CICS applications, include the Debug Tool library SEQAMOD in DFHRPL. For information about using Debug Tool with CICS, see the CICS Application Programming Guide.
Generally, you do not need to include any DB2 libraries in the DFHRPL DD statement. If you do need DB2 libraries in the DFHRPL concatenation for an application, they should be placed after the CICS libraries. For example, you need SDSNLOAD in the DFHRPL to support those applications that issue dynamic calls to the DB2 message handling module, DSNTIAR, or the later DSNTIA1, both of which are shipped in SDSNLOAD. DSNTIA1 is loaded by applications programs that include the DB2 application stub DSNTIAC, which issues an EXEC CICS LOAD command for program DSNTIAC.
8 Auxiliary temporary storage (DFHTEMP) data sets
Define this data set if you want to save data to use later. The temporary storage queues used, identified by symbolic names, exist until explicitly deleted. Even after the originating task is deleted, temporary data can be accessed by other tasks, through references to the symbolic name under which it is stored.
For details of how to define these data sets, and for information about space calculations, see Setting up the temporary storage data set.
If you are using temporary storage data sharing, you should ensure that you start the temporary storage server before it is required by the CICS regions.
For more information about the temporary storage server and temporary storage data sharing, see Setting up and running a temporary storage server
9 Intrapartition transient data (DFHINTRA) data sets
The transient data intrapartition data set is used for queuing messages and data within the CICS region.
For information about how to define these data sets, and about space calculations, see Defining intrapartition data sets.
10 Auxiliary trace (DFHAUXT and DFHBUXT) data sets
Define one or both of these sequential data sets, if you want to use auxiliary trace. If you define automatic switching for your auxiliary trace data sets, define both data sets. If you define only one data set, its DD name must be DFHAUXT.
For details of how to define these data sets, see Setting up and using auxiliary trace data sets.
The auxiliary trace data sets in this job stream are unique to the active CICS region, and as such are identified in our example by using the specific applid of the active CICS region (CICSHTH1) as a second-level qualifier. If you are using auxiliary trace with XRF=YES, the alternate CICS region also needs its own trace data sets. These could be identified by the specific applid of the alternate CICS region, for example, CICSHTH2.
If you allocate and catalog the auxiliary trace data sets on disk as shown in Figure 16, you can define them to CICS in the startup job stream using the following DD statements:
//DFHAUXT DD DSN=CICSTS31.CICS.applid.DFHAUXT,DCB=BUFNO=n,DISP=SHR
//DFHBUXT DD DSN=CICSTS31.CICS.applid.DFHBUXT,DCB=BUFNO=n,DISP=SHR
If you specify BUFNO greater than 1, you can reduce the I/O overhead involved in writing auxiliary trace records. A value between 4 and 10 can greatly reduce the I/O overhead when running with auxiliary trace on.
11 Extrapartition transient data queues
LOGA, CSSL, and CPLI are examples of extrapartition transient data queues.
Sample definitions of the queues used by CICS are supplied in group DFHDCTG. DFHDCTG is unlocked, so you can alter the definitions before installation.
12 The CICS local catalog data set
The CICS local catalog is used by the CICS domains to save some of their information between CICS runs, and to preserve this information across a cold start. The local catalog is not shared by any other CICS system. If you are running CICS with XRF, define a unique local catalog for the active CICS region, and another for the alternate CICS region. For details of how to create and initialize a CICS local catalog, see Setting up and using catalog data sets.
13 The CICS global catalog data set
There is only one global catalog, which is passively shared by the active and alternate CICS regions.
For details of how to create and initialize a CICS global catalog, see Setting up and using catalog data sets.
This sample job illustrates the use of the AMP parameter on the DD statement. Specifying this parameter, with its buffer subparameters, can help to improve restart and shutdown time. This example is based on the recommended DEFINE CLUSTER statements shown in Figure 13 and the associated notes given under 4 in topic Defining the global catalog. The values given are the minimum values suitable for these parameters and should not be reduced.
14 The CAVM data sets
These data sets are required when you are running CICS with XRF. They are actively shared by the active and the alternate CICS regions. For details of how to create and initialize the CICS availability data sets, see Defining the CICS availability manager data sets.
15 The DFHCXRF transient data set (CXRF)
This transient data destination is used by CICS as the target for messages sent to any transient data destination before CICS has completed intrapartition transient data initialization. It is particularly necessary in an XRF environment for use in an alternate CICS region before takeover has occurred, during the period when transient data initialization is suspended. For more information about the DFHCXRF data set, see The DFHCXRF data set.
16 CICS transaction dump data sets
CICS records transaction dumps on a sequential data set, or pair of sequential data sets, tape or disk. The data sets must be defined with the DD names DFHDMPA and DFHDMPB, but if you define only one data set, its DD name must be DFHDMPA. CICS always attempts to open at least one transaction dump data set during initialization.
For details about how to define CICS transaction dump data sets and how they are used, see Defining dump data sets.
The transaction dump data sets in this job stream are unique to the active CICS region, and as such are identified by using the specific applid of the active CICS region (DBDCCIC1) as a second-level qualifier. The alternate CICS region needs its own transaction dump data sets, and these could be identified by using the specific applid of the alternate CICS region (DBDCCIC2) as a second-level qualifier.
17 MVS system dump data sets
Use a SYSABEND, SYSMDUMP, or SYSUDUMP DD statement to direct MVS to produce a dump.
In the sample job stream (Figure 44), the SYSABEND DD statement directs a formatted dump to a printer, and the SYSMDUMP DD statement saves an unformatted dump to the SYS1.SYSMDP00 data set on disk.
MVS produces the requested dump if either of the following is true:
The dump DD statements for requesting dumps are:
To write more than one SYSMDUMP dump in the same data set on tape, specify the following:
You can ask MVS to write additional dumps only if you off-load any previous dump and write an EOF mark at the beginning of the SYS1.SYSMDPxx data set. To accomplish this, your MVS installation must install an exit routine for message IEA993. For information on this installation exit routine, see the OS/390 MVS Installation Exits manual.
The dump contents are as described only when you use the IBM-supplied defaults for the dumps. The contents of these dumps can be set during MVS system initialization and can be changed for an individual dump in the ABEND macro instruction, in a CHNGDUMP command, and by a SLIP command. For details, see the OS/390 MVS Initialization and Tuning Guide manual.
Dumps are optional; use a dump DD statement only when you want to produce a dump.
For information about how defining these MVS system dump data sets, and about printing dumps from them, see the OS/390 MVS JCL Reference manual. For information about how to interpret dumps, see the OS/390 MVS Diagnosis: Tools and Service Aids manual.
17a Default stdout file for C-language system services used by CICS
The SYSPRINT statement is opened as the stdout file by C-language system service routines that are used by CICS (such as system SSL.) If it is omitted, multiple sysout files might be dynamically allocated by the operating system instead.
18 The CICS system definition file
The system definition file (CSD) is required by CICS to hold some resource definitions.
You may want to provide job control DD statements for the CSD. If you do, the CSD data set is allocated at the time of CICS job step initiation, and remains allocated for the duration of the CICS job step.
On the other hand, you may prefer to use dynamic allocation of the CSD. For dynamic allocation, do not specify a DD statement for the CSD. Specify the data set name (DSNAME) and the data set disposition (DISP) either in a SET FILE command or in the SIT (as parameters CSDDSN and CSDDISP). CICS uses the DSNAME and DISP to allocate the file as part of OPEN processing.
For information about creating and initializing the CSD, see Setting up the CICS system definition data set.
If you are running CICS with XRF, particularly in a multi-MVS environment, there are special considerations concerning CSD sharing; these considerations are discussed under Sharing the CSD in non-RLS mode.
19 The CICS BTS local request queue data set
DFHLRQ is a file-control-managed VSAM key-sequenced data set (KSDS), used by CICS business transaction services (BTS). The IBM-supplied file resource definition for DFHLRQ is supplied in CSD group DFHCBTS, which is automatically included in DFHLIST group list when you initialize or upgrade your CSD. The file definition specifies that it is to be opened on first reference, which occurs at the end of CICS initialization when it is opened by BTS. CICS issues warning messages DFHFC0951 and DFHSH0109 if the data set is not found. Although CICS continues running without this data set, you are recommended to define the DFHLRQ data set, even if you are not using BTS. For information about DFHLRQ, see the CICS Business Transaction Services manual.
20 The EJB directory (DFHEJDIR) and the EJB object store (DFHEJOS)
DFHEJDIR is a VSAM key-sequenced data set (KSDS) that contains a request streams directory, which must be shared by all the regions (listeners and AORs) in a logical EJB server. Request streams are used in the distributed routing of method requests for enterprise beans and CORBA stateless objects.
DFHEJOS is a VSAM key-sequenced data set (KSDS) that contains details of stateful session beans that have been passivated. It must be shared by all the AORs in the logical EJB server.
For information about defining the EJB directory and object store, see Figure 27 and Figure 26.
21 CMAC data file (DFHCMACD)
DFHCMACD is a VSAM key-sequenced data set (KSDS) that is used by the CMAC transaction to provide online descriptions of CICS messages and codes. Before its first use it must be defined and loaded as a KSDS data set.
Defining the CMAC messages data set describes DFHCMACD in greater detail.
22 CDBM group command file (DFHCDBK)
DFHDBFK is a VSAM key-sequenced data set (KSDS) that is used by the CDBM transaction to store Group commands. Before its first use it must be defined as a KSDS data set. The DFHDBFK DD statement is only required if you intend to use the command storage functions of the CDBM transaction.
Defining the CDBM GROUP command data set describes DFHDBFK in greater detail.
23 Sample program file (FILEA) and other permanently allocated data sets
You may want to provide job control DD statements for those user files that are defined in the CSD (if you are using RDO) or in a file control table (for BDAM files only). If you do, the data sets are allocated at the time of CICS job step initiation, and remain allocated for the duration of the CICS job step. FILEA, the distributed library containing the data for the sample application programs, is included in our startup job stream as an example of direct allocation by job control statement.
On the other hand, you may prefer to take advantage of the CICS dynamic allocation of files. For dynamic allocation, do not specify a DD statement for the CSD. CICS then uses the full data set name as specified in the DSNAME parameter of the file resource definition (up to 44 characters), together with the DISP parameter, to allocate the file as part of OPEN processing. This form of dynamic allocation applies equally to files that are defined to be opened explicitly, and those that are to be opened on first reference by an application. For more information about file opening, see Defining user files. For information about the parameters that you can code on file resource definitions, see the CICS Resource Definition Guide.
The card reader/line printer (CRLP) simulated terminals shown in our sample job stream are defined in the sample TCT (not used in this startup job). See the copy member DFH$TCTS, in CICSTS31.CICS.SDFHSAMP, for the source statements you need for such devices. For information about defining these devices in a TCT, see the CICS Resource Definition Guide.
24 Quiescing sequential devices
For sequential devices, the last entry in the input stream can be CESF GOODNIGHT\ to provide a logical close, and quiesce the device. However, if you close a device in this way, the receive-only status is recorded in the warm keypoint at CICS shutdown. This means that the terminal is still in RECEIVE status in a subsequent warm start, and CICS does not then read the input file.
Note the end-of-data character (the "\" symbol) at the end of each line of the sample.
[[ Contents Previous Page | Next Page Index ]]