03.03.2015 Views

CA Dynam for VSE User Guide

CA Dynam for VSE User Guide

CA Dynam for VSE User Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Reporting Commands<br />

<strong>User</strong>-defined Reports<br />

If you'd rather customize a report, prepare the selection and title lists yourself.<br />

This JCL produces a customized report on two particular data sets.<br />

// JOB REPORT on PROCESSING OF TWO DATA SETS<br />

// EXEC AUDTUTIL,SIZE=128K<br />

PROGRAM DYNAM/T<br />

REPORT<br />

INPUT TAPE=SYS005<br />

FIELDS DSNAME VOLSER VERSION VOLSEQ JOB FUNCTION I/O CONTROL<br />

TITLE 'SPECIAL AUDIT REPORT'<br />

TITLE (DSNAME 2) 'NAME'<br />

TITLE (VOLSER 2) 'VOLUME'<br />

TITLE (VOLSEQ 2) 'SEQ'<br />

TITLE (CONTROL 2) 'CONT'<br />

SELECT (DSNAME TEST.FILE1)<br />

SELECT (DSNAME TEST.FILE3)<br />

GENERATE<br />

/*<br />

/&<br />

One report that traces the audit records <strong>for</strong> the two data sets will be<br />

generated. Note that some of the default titles are being overridden.<br />

As in the predefined reports, the following must be adhered to:<br />

• The PROGRAM statement must precede the REPORT statement<br />

• GENERATE must be the last statement be<strong>for</strong>e processing the report<br />

• FIELDS, INPUT, SELECT and TITLE must follow REPORT<br />

For a customized report, you must at least supply FIELDS and GENERATE<br />

statements.<br />

Multiple Reports in One Execution<br />

Several reports may be defined in one job stream. Each one is processed when<br />

a GENERATE statement is encountered. Note that report definitions are cleared<br />

after each GENERATE statement is executed so each GENERATE statement<br />

must be paired with a REPORT statement. See the REPORT command <strong>for</strong><br />

examples.<br />

12–14 <strong>User</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!