gtpo1mhe | Operations |
You can specify the DOF options in the JCL EXEC statement instead of entering them in response to console messages.
The following EXEC statements are examples of how you can specify the DOF options by using the PARM= parameter.
// EXEC PGM=PPCP,REGION=250K, // PARM=('TV,Y,DP=PRINT(19,57,104,175)','TR,IO,SI=(ALL).')
// EXEC PGM=PPCP,REGION=512K, // PARM=('TV,Y,DP=SKIP(2,4,6,8),CT,SM,SI=(CRTS,1977).')
// EXEC PGM=PPCP,REGION=512K // PARM=('TV,Y,DP=GOTO(175),SM,NOPR,SI=(1980).')
// EXEC PGM=PPCP,REGION=250K, // PARM=('RS,Y,DP=NO,TR.Y'), // 'DP=PRINT(1045,1046),IO,GO.')
The RTL/RTA tape being processed contains multi-test unit output from PTV test units (the RS option). In the first test unit, print only the real-time trace (RTT) and selective file dump and trace (SFDT) output. In the second and all succeeding test units (GO option), print system error dump numbers 1045 and 1046 plus the PTV input/output message stream of the test unit.
// EXEC PGM=PPCP,REGION=250K,PARM='N'
The RTL/RTA tape being processed was generated on a TPF system that did not support PTV or that supported PTV only in STV mode. As a result, the TV or RS option is not coded. The N option requests all of the default DOF options. In a system without PTV support, DOF prints all trace output, all CCP trace output, and all system error dumps. In a system where PTV is supported only in STV mode, DOF also prints the PTV input/output message stream plus the output from all generated simulators.
When specifying the DOF options in the EXEC statement, use extreme care with the punctuation that is required by the IBM MVS system and the use of PPCP, especially for multiple card input. Commas (,) required to end a continued card are passed to PPCP as part of the parameter field.