SDF-SIM checks the command defined in the active syntax file hierarchy for syntax errors. This check is conducted within an environment defined by means of the DEFINE-ENVIRONMENT statement.
Simulation preparation
If a parameter file (*STD or <filename>) is specified in the PARAMETER-FILE operand, the names of the system syntax file and the group syntax file assigned to the profile ID of TSOS (SYS-TSOS) are read from the parameter file and activated for the simulation.
If the parameter file contains an error or the syntax files are invalid, the system syntax file and the TSOS group syntax file with the standard names are used.
If the name of the system, group or user syntax file is entered and an error occurs during activation of the syntax file, an error message is output. In the case of an error in the system or group syntax file, the syntax files with the standard names are activated. If there is an error in the user syntax file, no user syntax file is activated. At least one system or group syntax file must be activated, otherwise simulation is impossible as there is no global information available. If *STD is entered for the system syntax file, only the current basic system syntax file is activated. If *CURRENT is entered as the system syntax file, then the current basic system syntax file and the current subsystem syntax file are activated.
Simulation
Once simulation has been started, the command to be simulated can be entered in guided or unguided dialog. This is also contingent upon the specification in the MODIFY-SDF-OPTIONS command (see the example on "Testing with the maximum guidance level"). Both in simulated procedure mode and in batch mode (statement DEFINE- ENVIRONMENT PROC-MODE=*YES or TASK-TYPE=*BATCH), the command entered must be preceded by a slash (/). The commands may also be entered in lowercase letters (see the example on "Simulation of procedure or batch mode").
Output
A log is output after the syntax analysis. This log contains the name of the entry point, the type of the programming language interface, the generated character string (ISP format) or the standardized transfer area for commands defined by way of the SDF-A statement ADD-CMD ...,IMPLEMENTOR=*TPR(...,CMD-INTERFACE=*NEW/*TRANSFER-AREA...).
Replacing job variables
Job variables are replaced in SDF-SIM in exactly the same way as when simulation is not being performed (see the example on "Replacing job variables"). Procedure parameters, however, cannot be replaced.