Instead of entering commands each time the test is run, you can save the commands and then submit batch tests when required.
The format of the commands follows the general simulator command format.
All commands are supported in the batch environment, although the simulator trace information is condensed. The EJECT command is a batch‑only command and causes a page eject before the simulator executes the next command.
To execute the simulator in a batch environment, use the following JCL:
//SIMULATE EXEC PGM=TSSSIM
//SIM$$LOG DD SYSOUT=A
//SIM$$IN DD *
.
.
.
(TSSSIM commands)
/*
//
Note: When you invoke TSSSIM through JCL, single TSSSIM commands cannot exceed 80 characters. To run a simulation command that is longer than 80 characters, use TSSSIM under a non-SPF environment.
Example: Invoke the Simulator in a Batch Environment
This example invokes the simulator in a batch environment to perform resource checking on data set SYS1.PROCLIB with UPDATE access. The data set can be accessed only through privileged program IEBUPDTE. This example also checks whether USER01 has CREATE access on the DASD volume SYSRES. The administrator signs on with the simulated ACID USER01 in a TSO facility. The TRACE function is also activated.
//SIMULATE EXEC PGM=TSSSIM
//SIM$$LOG DD SYSOUT=A
//SIM$$IN DD *
LOGON ACID(USER01) FACILITY(TSO) TRACE
$DSN('SYS1.PROCLIB') ACC(UPDATE) PRIVPGM(IEBUPDTE)
$DASDVOL(SYSRES) ACC(CREATE)
END
/*
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|