Using model log streams
To avoid defining explicitly each log stream used by each of your CICS® regions, you can use model log stream definitions.
Using models, log streams are defined to MVS™ dynamically,
on their first usage. Figure 1 shows
example DASD-only model definitions for CICS primary
and secondary system log streams.
Figure 1. Example
model definitions for DASD-only system log streams. The
value sysname is the sysid of the MVS image
in which the CICS region or regions are running.
//DEFLOGS JOB ...
//LOGDEFN EXEC PGM=IXCMIAPU
//STEPLIB DD DSN=SYS1.MIGLIB,DISP=SHR
//SYSPRINT DD SYSOUT=*
//******************************************************************
//* *
//* Define DASD-only model log streams for CICS system log. *
//* *
//* The LOWOFFLOAD and STG_SIZE values are for illustration *
//* only -- substitute values appropriate for your environment. *
//* *
//******************************************************************
//SYSIN DD *
DATA TYPE(LOGR) REPORT(NO)
DEFINE LOGSTREAM NAME(sysname.DFHLOG.MODEL)
MODEL(YES)
DASDONLY(YES)
MAXBUFSIZE(64000)
STG_SIZE(3000)
LOWOFFLOAD(40) HIGHOFFLOAD(80)
DEFINE LOGSTREAM NAME(sysname.DFHSHUNT.MODEL)
MODEL(YES)
DASDONLY(YES)
MAXBUFSIZE(64000)
STG_SIZE(500)
LOWOFFLOAD(40) HIGHOFFLOAD(80)
For information about the mapping of CICS journal definitions to log stream names, see Setting up CICS log streams.
When using model log streams, note that, if you specify a STG_SIZE on the model definition, all new log streams created from the model have the same-sized staging data set.