3270 Reporting (VTAM)
This section describes Performance Test for VTAM reporting options:
- Transaction journal
- Reports — Automated documentation and summary reports
- Logs — Comparison, exception, and REXX logs
These utilities provide a method of tracking test scripts and testing data.
“Print” data sets in Performance Test for VTAM are the comparison log, exception log, transaction journal, REXX log, summary report, AutoDoc, and trace. Performance Test can write print data as members of a Partitioned Data Set Extended (PDSE) or as a sequential data set.
If you want your print data sets to be members of a partitioned data set, you must use PDSEs rather than PDSs. Using members of a PDSE allows you to group related output within a single data set, simplifying the management of printed output.
If you supply the same data set and member prefix across several GROUP statements, or across several keywords within one GROUP statement, what is contained in the overlapping members is undefined. This situation is not flagged as an error. Choose data set and member names so that such an overlap does not occur.
Sequential data sets are deleted and reallocated if REUSE=NO is set in the Performance Test defaults table. Sequential data sets are overwritten if REUSE=YES is set.
PDSEs used for print files are never deleted by Performance Test, regardless of the REUSE value contained in the Performance Test for VTAM defaults table. Performance Test creates a PDSE if it does not already exist. Members created by Performance Test that already exist within a data set are overwritten and no warning message is issued. If you want an existing PDSE to contain only members from the current execution of Performance Test, you must empty the PDSE before running Performance Test.
This section provides information about the following topics: