Invoking the CSQ1LOGP utility

You run the WebSphere MQ log print utility as a z/OS batch program. We can specify:

• A bootstrap data set (BSDS)

• Active log data sets (with no BSDS)

• Archive log data sets (with no BSDS)

Sample JCL to invoke the CSQ1LOGP utility is shown in figures Figure 70, Figure 71, Figure 72 and Figure 73.

These DD statements should be provided:

SYSPRINT

All error messages, exception conditions and the detail report are written to this data set. The logical record length (LRECL) is 131.

SYSIN

Input selection criteria can be specified in this data set (see Input control parameters for more information).

The logical record length (LRECL) must be 80, but only columns 1 through 72 are significant; columns 73 through 80 are ignored. At most 50 records can be used. Records with an asterisk (*) in column 1 are interpreted as comments and are ignored.

SYSSUMRY

If a summary report is requested, by specifying the parameter SUMMARY(YES) or SUMMARY(ONLY), the output is written to this data set. The logical record length (LRECL) is 131.

BSDS

Name of the bootstrap data set (BSDS).

ACTIVEn

Name of an active log data set you want to print (n=number).

ARCHIVE

Name of an archive log data set you want to print.

If you specify the keyword EXTRACT(YES), provide one or more of the following DD statements, depending on what types of data you want to extract. Do not specify an LRECL, as it is set internally by the utility.

CSQBACK

This data set will contain persistent messages written to the log by units of work that were rolled back during the log range specified.

CSQCMIT

This data set contains persistent messages written to the log by units of work that were committed during the log range specified

CSQBOTH

This data set contains persistent messages written to the log by units of work that were either committed or rolled back during the log range specified.

CSQINFLT

This data set contains persistent messages written to the log by units of work that remained inflight during the log range specified.

CSQOBJS

This data set contains information about object alterations that occurred during the log range specified.

If you are processing active log data sets, the utility runs even if WebSphere MQ is running, provided that the BSDS and active log data sets are defined using at least SHAREOPTIONS(2 3).

Figure 70. Sample JCL to invoke the CSQ1LOGP utility using a BSDS

//PRTLOG EXEC PGM=CSQ1LOGP
//STEPLIB  DD DISP=SHR,DSN=thlqual.SCSQANLE
//         DD DISP=SHR,DSN=thlqual.SCSQLOAD
//BSDS     DD DSN=qmgr.bsds.dsname,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSSUMRY DD SYSOUT=*
//SYSIN    DD *
* extract records for pageset 3. Produce both summary and detail reports
PAGESET(3)
SUMMARY(YES)
/*

Figure 71. Sample JCL to invoke the CSQ1LOGP utility using active log data sets

//PRTLOG  EXEC PGM=CSQ1LOGP
//STEPLIB  DD DISP=SHR,DSN=thlqual.SCSQANLE
//         DD DISP=SHR,DSN=thlqual.SCSQLOAD
//ACTIVE1  DD DSN=qmgr.logcopy1.ds01,DISP=SHR
//ACTIVE2  DD DSN=qmgr.logcopy1.ds02,DISP=SHR
//ACTIVE3  DD DSN=qmgr.logcopy1.ds03,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSSUMRY DD SYSOUT=*
//SYSIN DD *
  insert your input control statements here
/*

Figure 72. Sample JCL to invoke the CSQ1LOGP utility using archive log data sets

//PRTLOG  EXEC PGM=CSQ1LOGP
//STEPLIB  DD DISP=SHR,DSN=thlqual.SCSQANLE
//         DD DISP=SHR,DSN=thlqual.SCSQLOAD
//ARCHIVE  DD DSN=qmgr.archive1.ds01,DISP=SHR
//         DD DSN=qmgr.archive1.ds02,DISP=SHR
//         DD DSN=qmgr.archive1.ds03,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSSUMRY DD SYSOUT=*
//SYSIN    DD *
  insert your input control statements here
/*

Figure 73. Sample JCL showing additional statements for the EXTRACT keyword

//PRTLOG  EXEC PGM=CSQ1LOGP
...
//CSQBACK   DD DSN=backout.dataset,DISP=(NEW,CATLG)
//CSQCMIT   DD DSN=commit.dataset,DISP=(NEW,CATLG)
//CSQBOTH   DD DSN=both.dataset,DISP=(NEW,CATLG)
//CSQINFLT  DD DSN=inflight.dataset,DISP=(NEW,CATLG)
//CSQOBJS   DD DSN=objects.dataset,DISP=(NEW,CATLG)