CICS VR Journal Print Utility – DWWJUP

Introduction:
Journal print utility helps to find information about record logged on them, it also reads data from MVS log stream and displays in readable format. DWWJUP print utility use IXGCONN and IXGBRWSE to establish/disconnect connection to the log stream and reads the log stream contents appropriately. STARTTIME and STOPTIME parameters denotes ranges, also CICS VR journal print utility DWWJUP will supports INCLUDE, EXCLUDE commands to filter the data from a specific log stream to generate specific report.
Command format:
​​

Figure 1: Fig 1 command format

Flow chart
​

Figure 2: Flow Chart

Brief Description:
Limitation:

• There is no limitation for INCLUDE/EXCLUDE command but maximum FILEID will be 99 on each command.
• 26 character for log stream name.
• Multiple INCLUDE,EXCLUDE can be specified. (Note EXCLUDE have priority than INCLUDE)
• QSAM copy DWWLOG dd statement is a must, also DSN should refer log stream copy
• Timestamp must be in the format yyyy/ddd/hh/mm/ss, where:

           yyyy Is the four-digit year number (2001)
           ddd Is the day of the year (001–366)
           hh Is the hour of the day (00–23)
           mm Is the number of minutes (00–59)
           ss Is the number of seconds (00–59)
           You can separate these values with a slash
           (ex. STARTTIME(2001.159/01:23:00)
Usage Note:
Consider the following when using the EXCLUDE command:

• At least one keyword must be specified for each EXCLUDE command.
• Multiple EXCLUDE commands and INCLUDE commands can be specified in the same job step. The Journal Print utility processes a log record against all EXCLUDE commands before it processes the log record against all INCLUDE commands.
• For each log record, if the EXCLUDE criteria is met, the record is excluded. If the EXCLUDE criteria is not met, the Journal Print utility matches the log record against the next EXCLUDE command.
• When the log record has been examined against all the EXCLUDE commands, the utility examines the log record against the first INCLUDE command.
• If INCLUDE criteria is met the record is used in the utility. If it is not met, the Journal Print utility matches the record against the next INCLUDE command.
• If the log record does not match any of the INCLUDE commands, do not use the log record. Journal Print utility repeats this process for the next log record by matching it first against the EXCLUDE commands and then INCLUDE commands.
• If one or more EXCLUDE commands are entered and no INCLUDE commands are entered, all log records that do not match the entered exclude criteria are printed.

         For example, if you specify:
                     EXCLUDE FILEID(DD1),TERMID(T1)
         The utility ignores log records that have a FILEID of DD1 and TERMINALID of T1.
        If you want to ignore log records that have a FILEID of DD2 or TERMINALID of T2, specify           two EXCLUDE commands as follows:
                    EXCLUDE FILEID(DD2)
                    EXCLUDE TERMID(T2)

Note:
Do not specify EXCLUDE and INCLUDE criteria that conflict.
For example,
INCLUDE FILEID(DD1) and EXCLUDE FILEID(DD1).
If conflicting criteria is specified, no records are printed, and no error messages are produced.

Sample DWWJUP (Journal print job):
​​

Sample report:
​

Reading DWWJUP reports (Journal print report):
Journal print report has following three sections:

• Block header
• Record header 
• Summary report

 

1. Block header – have block identifier, block length and logged time.
2. Record header – Each record has identified by its record number. Each record has its own record header information, such as replication and forward recovery eligibility flag, type of record, record log created time, VSAM file name, VSAM supplied DD name along with that based on VSAM file type its associated information like key or RBA information for KSDS VSAM, RRN for RRDS, and VRRDS VSAM.

          RBA for ESDS VSAM file will be present in report for easy to debug.
​    3.  Summary report – have first and last reference, statistics of logged record (i.e.) count of               each type of record will be present in summary report. 

Reference:
https://www.ibm.com/support/knowledgecenter/SSQJMU_5.1.0/dwwig/printinformationaboutrecordsloggedbycicsvr.html

Implementation Guide and Reference, Version 5 Release 2

​Contact
Balaji Sathiyanarayanan  (Senior Technical Lead, HCL Software)
Ajith P (Senior software developer, HCL Software)