Simulation Output Files

The simulation run produces the following output files:

• Simulation Messages file

  The DASIMOUT DD statement references a sequential file containing a list of the simulation parameters used, and special messages for error codes, warning situations, and so on. In addition, it contains all the SHOUT messages to TSO/ROSCOE users and to the computer operator.

• SIMLOG—Simulation Log file

  The DALOGOUT DD statement references a sequential output file in a format similar to that of the IOA Log file.

  At the end of the simulation process, this file contains all the log messages describing events that occurred during the simulation run, for example, JOB SUBMITTED, JOB ENDED OK, or COND xxxx ADDED.

  This file can be used as input to all Control-M reports that are normally produced from the IOA Log file. The standard set of reports produced from the IOA Log can be used to analyze the simulation run. Therefore, it is not necessary to write special simulation reports.

• SIMOAJF—Active Jobs file

  The DACKPTOU DD statement references a file in the format of the Active Jobs file. All jobs that were present in the input Active Jobs file are written to this file with the status assigned to them during the simulation run, for example, ENDED OK, EXECUTING, or WAIT SCHEDULE.

  The file can be scanned online or in batch mode using standard Control-M facilities.

• SIMOCND—Conditions file

  The SIMOCND DD statement references a file in the format of the IOA Conditions file. All conditions that were present at the end of the simulation run are written to this file.

  The file can be scanned online or in batch mode using standard Control-M facilities.

• SIMORES—Resources file

  The SIMORES DD statement references a file in the format of the Control-M Resources file. All Quantitative resources and Control resources that were present at the end of the simulation run are written to this file.

  The file can be scanned online or in batch mode using standard Control-M facilities.