Analyzing and Comparing Scripts (MQ)

There are many ways to use script analysis. With regard to these scenarios, use it to compare the sample scripts to the scripts you generate and edit to ensure you filtered the repository and edited the scripts correctly. The main focus of this exercise is to familiarize you with script analysis, the HTML Exception Report, and the concept of building a baseline.

To compare the scripts you created to the sample scripts:

1. Locate the sample report member, MQRREXCB, for the HTML Exception Report. Complete the statement by providing a ddname on the BASELINE parameter and an HFS path on the INTO parameter. Save the edited report member in your personal report control library. See HTML Exception REPORT Statement.
2. Use the edited LOG file to run an ANALYZE job on the scripts specified by the log file. Override the temporary dataset on the SET SORTED statement with a permanent dataset to save the data collected from the analyze job. This will be the baseline database. See Unattended Playback for help with this and the next step.
3. Use the sample log to run an analyze job on the sample scripts and generate the exception report simultaneously. Complete SET REPTDS with your personal report control library, SET SORTED with a unique dataset name, and SET REPTMEM with the HTML Exception report member. Add a DD statement for the baseline database specified on the report statement’s BASELINE parameter and the HFS path specified on the statement’s INTO parameter.
4. Once both analysis jobs have completed, review the report to see if any differences exist between the two scripts from your log file and the two sample scripts from the sample log file.