CA Dynam for VSE User Guide
CA Dynam for VSE User Guide CA Dynam for VSE User Guide
Reporting Commands Note that if you separate the fields onto individual lines, you are limited to defining the title for the first FIELDS statement. The second report puts data set name, volser and unit on one line; volser and unit are separated by 5 spaces. This line is followed by two blank lines. The report will look like this: NAME VOLUME UNIT (title) TEST.FILE1 SYSWK1 0160 (record 1) (blank line) (blank line) TEST.FILE1 SYSWK2 0167 (record 2) The third report puts data set name, volser and unit on one line. Fields are separated by 1 space by default. The report will look like this: VOLUME ----- D A T A S E T N A M E ------ SERIAL UNIT (default title) TEST.FILE1 SYSWK1 0160 (record 1) TEST.FILE1 SYSWK2 0167 (record 2) Note: • You cannot issue the FIELDS command for predefined reports. • Fields are printed in the order in which you specify them in the FIELDS command. • The length of each field differs and is listed along with the field definitions in the section "Report Fields." • Indicate spaces between fields with $SPn, where n is the number of spaces to insert. • If two fields are specified with no intervening $SPn, spaces are inserted between the fields. • To insert a blank line into the report, issue a FIELDS command with the single field name '$SP'. For example, FIELDS DSNAME VOLSER FIELDS $SP This prints the data set name and volser on one line. This is followed by one blank line. • If all or part of any field falls outside position 120, the field will be completely omitted. • Each FIELDS command defines a separate report line. If you issue more than one FIELDS command, each audit entry will have more than one output line on the report. 12–16 User Guide
Reporting Commands GENERATE Command The GENERATE command executes the report generation function using all commands issued since the previous REPORT command. No operands are required with this command. Note: GENERATE is required to print a report. It must be the last command entered for a given report. Example // JOB REPORTS // EXEC AUDTUTIL,SIZE=128K PROGRAM DYNAM/T REPORT DATASET MAINT GENERATE PROGRAM DYNAM/D REPORT TITLE 'VOLUME AUDIT REPORT' TITLE DSNAME 'NAME' TITLE VOLSER 'VOLUME' FIELDS DSNAME VOLSER SELECT (DSNAME TEST.FILE1) SELECT (DSNAME TEST.FILE3) GENERATE /* /& (2 predefined reports printed) (a customized report printed) INPUT Command The INPUT command specifies which Audit Trail data file is to be used for generating a report. If you omit all operands, the default is INPUT DATASET. The format of the command is shown below. INPUT [ DATASET ] [ ] [ TAPE=[SYSnnn] [MULTITAPE=nn] ] DATASET Optional parameter. Uses the Audit Trail file on disk for generating a report. DATASET is the default if no parameters are specified, or if the entire INPUT statement is omitted. Note: DATASET and TAPE are mutually exclusive. Chapter 12: Maintaining and Reporting on the Audit Trail 12–17
- Page 531 and 532: DYNACC User Exits DYNACC User Exits
- Page 533 and 534: Test Program Generator - DYNATEST W
- Page 535 and 536: Test Program Generator - DYNATEST F
- Page 537 and 538: DYNACC Version 2 Parameter List Con
- Page 539 and 540: DYNACC Version 2 Parameter List Con
- Page 541 and 542: DYNACC Version 2 Parameter List Con
- Page 543 and 544: DYNACC Version 2 Parameter List Con
- Page 545: DYNACC Version 2 Parameter List Con
- Page 548 and 549: AUDIT Data Set Browse Selection Pan
- Page 550 and 551: AUDIT Data Set Directory Panel—Al
- Page 552 and 553: AUDIT Data Set Directory Panel—CA
- Page 554 and 555: AUDIT Data Set Detail Panel—DYNAM
- Page 556 and 557: AUDIT Data Set Directory Panel—CA
- Page 558 and 559: AUDIT Data Set Directory Panel—CA
- Page 560 and 561: AUDIT Data Set Detail Panel—CA Dy
- Page 562 and 563: CAIAUDIT in Command Mode DSN=1|2 Sp
- Page 564 and 565: Printable Fields Name Length Descri
- Page 567 and 568: Chapter 12: Maintaining and Reporti
- Page 569 and 570: Maintaining the Audit Trail File
- Page 571 and 572: AUDTUTIL Control Statement Syntax A
- Page 573 and 574: Maintenance Commands Note: • The
- Page 575 and 576: Maintenance Commands Backing up the
- Page 577 and 578: Reporting Commands EXTENDED Default
- Page 579 and 580: Reporting Commands The following jo
- Page 581: Reporting Commands FIELDS Command T
- Page 585 and 586: Reporting Commands INPUT TAPE=SYS00
- Page 587 and 588: Reporting Commands Note: • The RE
- Page 589 and 590: Reporting Commands (field-name lowv
- Page 591 and 592: Reporting Commands MANUAL OPEN OUTP
- Page 593 and 594: Reporting Commands Examples // JOB
- Page 595 and 596: Report Fields • The total number
- Page 597 and 598: Report Fields Field Name Length Des
- Page 599 and 600: Report Fields Field Name Length Des
- Page 601 and 602: Report Fields Field Name Length Des
- Page 603 and 604: Chapter 13: DYNCOPY−CA Dynam File
- Page 605 and 606: Parameters Startingposition, Length
- Page 607 and 608: Parameters LRECL=n BLKSIZE=n Specif
- Page 609 and 610: Sample JCL Example 2: Produce a cha
- Page 611 and 612: Appendix A: CA Dynam Report Example
- Page 613 and 614: TDYNUTL Reports Title Report No. Pr
- Page 615 and 616: TDYNUTL Reports CA ALL TAPES BY VOL
- Page 617 and 618: TDYNUTL Reports CA CURRENT ACTIVITY
- Page 619 and 620: DYNCAT Reports DYNCAT Reports // JO
- Page 621 and 622: DYNCAT Reports CA LISTCAT REPORT PA
- Page 623 and 624: TDYNVLT Reports LOCATION MOVEMENT S
- Page 625 and 626: TDYNLIST Reports DATE 01/11/07 TIME
- Page 627 and 628: TDYNSYNC Reports EXTRACT CATNAME=CA
- Page 629 and 630: Standard DYNPRINT Reports Standard
- Page 631 and 632: Standard DYNPRINT Reports FILEDEFS
Reporting Commands<br />
Note that if you separate the fields onto individual lines, you are limited to<br />
defining the title <strong>for</strong> the first FIELDS statement.<br />
The second report puts data set name, volser and unit on one line; volser and<br />
unit are separated by 5 spaces. This line is followed by two blank lines. The<br />
report will look like this:<br />
NAME VOLUME UNIT (title)<br />
TEST.FILE1 SYSWK1 0160 (record 1)<br />
(blank line)<br />
(blank line)<br />
TEST.FILE1 SYSWK2 0167 (record 2)<br />
The third report puts data set name, volser and unit on one line. Fields are<br />
separated by 1 space by default. The report will look like this:<br />
VOLUME<br />
----- D A T A S E T N A M E ------ SERIAL UNIT (default title)<br />
TEST.FILE1 SYSWK1 0160 (record 1)<br />
TEST.FILE1 SYSWK2 0167 (record 2)<br />
Note:<br />
• You cannot issue the FIELDS command <strong>for</strong> predefined reports.<br />
• Fields are printed in the order in which you specify them in the FIELDS<br />
command.<br />
• The length of each field differs and is listed along with the field definitions<br />
in the section "Report Fields."<br />
• Indicate spaces between fields with $SPn, where n is the number of spaces<br />
to insert.<br />
• If two fields are specified with no intervening $SPn, spaces are inserted<br />
between the fields.<br />
• To insert a blank line into the report, issue a FIELDS command with the<br />
single field name '$SP'. For example,<br />
FIELDS DSNAME VOLSER<br />
FIELDS $SP<br />
This prints the data set name and volser on one line. This is followed by<br />
one blank line.<br />
• If all or part of any field falls outside position 120, the field will be<br />
completely omitted.<br />
• Each FIELDS command defines a separate report line. If you issue more<br />
than one FIELDS command, each audit entry will have more than one<br />
output line on the report.<br />
12–16 <strong>User</strong> <strong>Guide</strong>