Chapter 3. Using CMFMON’s Write Facility 39
Table 7 describes JCL statements shown in Figure 27 on page 38, and Figure 28 above.
//JOBCARD JOB
//*
//*--------------------------------------------------------------------
//*
//* SAMPLE JCL FOR EXECUTING CMFMON IN BATCH.
//*
//* REVIEW THE JCL FOR APPLICABILITY TO YOUR INSTALLATION
//* STANDARDS
//*
//* CHANGE ?HILEVEL TO THE HIGH-LEVEL QUALIFIER YOU CHOSE FOR
//* YOUR BBLINK AND UBBPARM DATA SETS.
//*
//* CHANGE ?RECDSN TO THE NAME OF THE DATASET TO WHICH TYPE 79
//* RECORDS ARE TO BE WRITTEN.
//*
//*--------------------------------------------------------------------
//*
//CMFMON EXEC PGM=CX10GV79,REGION=2M
//STEPLIB DD DISP=SHR,DSN=?HILEVEL.BBLINK
//C79OUT DD DISP=SHR,DSN=?RECDSN
//SYSUDUMP DD SYSOUT=*
//CMF79LOG DD SYSOUT=*
//SYSINC79 DD DISP=SHR,DSN=?HILEVEL.UBBPARM(CMFMON00)
//*
Figure 28. Sample Batch JCL (CMONJCL)
Table 7. Explanation of CMFMON JCL (Page 1 of 2)
Job Control Statement Description
CMFMON EXEC Specifies the program name (CX10GV79), assigns a region size (2 megabytes), and, in
CMONSTC, specifies the suffix of the control statement member used by CMFMON
(00).
Notes:
• The default control statement member is named CMFMON00 and is
distributed in hilevel.BBPARM (which was copied to hilevel.UBBPARM
after installation). See “Default Control Statement Member” on page 58 for
a description of this member. If you do not specify the C79 parameter,
CMFMON uses the control statements in CMFMON00.
• If the C79 parameter identifies a control statement member that cannot be
located, CMFMON terminates with an error message.
• Boole & Babbage recommends that you begin running with a 2-megabyte
region size. Depending on the environment and options you use, you may
be able to reduce this size later. For example, if you are not planning to do
enqueue sampling, a region size of 1 megabyte will probably suffice.
STEPLIB DD Defines a PDS that contains the CMFMON load modules. This PDS must be an
APF-authorized library.
