Previous Topic

Next Topic

Book Contents

Book Index

Messages SIM0 through SIM0xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

SIM075S OPEN OF DDNAME "DASIMOUT" FAILED. SIMULATION STOPPED

Explanation: Open of simulation printout file failed (the DASIMOUT DD statement - the CTMSIM utility).

This is due to one of the following:

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

SIM076I SIMULATION STARTED

Explanation: This information message indicates that simulation started (the CTMSIM Control-M utility).

This message is issued by the CTMSIM Control-M utility, which activates the Simulation and Forecasting Facility.

Corrective Action: No action is required.

SIM077S OPEN OF DDNAME "DASIMPRM" FAILED. SIMULATION STOPPED

Explanation: Open of simulation parameters file failed (the DASIMPRM DD statement - the CTMSIM utility)

This could be due to one of the following:

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

SIM078I SIMULATION ENDED

Explanation: This information message indicates that simulation ended (the CTMSIM Control-M utility).

Corrective Action: No action is required.

SIM079S INVALID SIMULATION PARAMETER: - parm

Explanation: Invalid simulation parameter (the CTMSIM Control-M utility). For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the simulation parameters (the DASIMPRM DD statement).

SIM080S SIMULATION INTERVAL MUST BE FROM 3 TO 99 SECONDS

Explanation: Invalid interval parameter for Control-M simulation facility. Simulation interval must be from 3 to 99 seconds, inclusive. For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the simulation interval (the DASIMPRM DD statement).

SIM081S INVALID DAYTIME FORMAT. "yymmddhhmm" EXPECTED

Explanation: Invalid format of SIMSTART SIMEND, ADD, DELETE or CHANGE simulation parameters. The SIMSTART and SIMEND simulation parameters or the ONDAYTIME subparameter (of the ADD, DELETE and CHANGE command) should be in day-time format yymmddhhmm. For more information, see the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct SIMSTART or SIMEND or ONDAYTIME simulation parameter (the DASIMPRM DD statement).

SIM082S MULTIPLE USE OF PARAMETER. ONLY ONE OCCURRENCE IS ALLOWED

Explanation: Result of multiple use of INTERVAL, SIMSTART or SIMEND simulation parameters (the CTMSIM Control-M utility).

Only one occurrence of INTERVAL, SIMSTART or SIMEND simulation parameters is allowed. For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Please omit one of the multiple occurrences of the relevant simulation parameter (the DASIMPRM DD statement).

SIM083S SIMULATION START TIME IS GREATER THAN SIMULATION END TIME

Explanation: The daytime specified in the SIMEND simulation parameter is prior to the daytime specified in the SIMSTART parameter (the CTMSIM Control-M utility).

For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the SIMSTART or SIMEND simulation parameter (the DASIMPRM DD statement).

SIM084S MISSING OBLIGATORY SIMULATION PARAMETERS

Explanation: Missing obligatory simulation parameters: INTERVAL, SIMSTART or SIMEND. For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the simulation parameters (the DASIMPRM DD statement).

SIM085S LOADING OF SIMULATION CONTROL TABLE FAILED. SIMULATION STOPPED

Explanation: Loading of simulation control table failed. The CTMSMT module is not in the IOA SIML library, or there is insufficient memory.

Corrective Action: Check the IOA SIML library or increase region size.

Simulation stops.

SIM086W MEMBER memName LIBRARY lib WILL NOT TAKE PART IN THE SIMULATION

Explanation: The status of the job on the simulation input Active Jobs file (AJF) is not WAIT SCHEDULE.

The Control-M simulation facility processes only jobs which have a WAIT SCHEDULE status on the simulation input Active Jobs file. Jobs with other status’s are ignored.

Control-M simulation continues processing.

Corrective Action: No action is required.

SIM087W MEMBER memName LIBRARY lib - DEFAULT ELAPSED TIME USED

Explanation: Result of request for execution of simulation for a Quick Submit job on which Control-M does not have statistical information in the Job Execution Statistics file (the DASTAT DD statement).

The default elapsed time of 3 minutes was used for a Quick Submit job. The job execution statistical data must be periodically accumulated from the Log file by the CTMJSA utility. You can specify expected execution time of a new job with the NEWJOB statement. For details, refer to the Control-M for z/OS User Guide.

Corrective Action: No action is required.

SIM088S INVALID RC WHILE READING JOBS EXECUTION STATISTICS FILE. RC=rc ERROR=err

Explanation: Invalid return code rc while reading the job execution statistics file.

The job execution statistics file is a VSAM file. The return code (rc) is the general VSAM return code, and the error (err) is the VSAM FDBK area.

The simulation stops executing with a condition code of 08.

Corrective Action: Check the relevant IBM literature for the meaning of the return code and FDBK area.

SIM089S INSUFFICIENT MEMORY TO PERFORM SIMULATION

Explanation: Insufficient memory to perform simulation.

The CTMSIM utility that activates the simulation may use a large amount of CPU and memory. For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Increase the job region size (of the CTMSIM utility).

SIM090S VALID MEMBER NAME EXPECTED AFTER "NEWJOB"/"OLDJOB" STATEMENT

Explanation: Invalid missing member name after NEWJOB (or OLDJOB) statement (the DASIMPRM DD statement).

The NEWJOB statement is used to specify the expected execution time of the new job. The OLDJOB statement is used to specify the execution time of a job when it is different from the average. The member is the basis for identifying the job order in the Active Jobs file.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the member parameter in the NEWJOB (or OLDJOB) statement (the CTMSIM utility).

SIM091S VALID GROUP NAME OF 1-20 CHARACTERS IS EXPECTED AFTER "GROUP" SUB-COMMAND

Explanation: Invalid or missing GROUPNAME parameter in sub-command GROUP of the NEWJOB statement (the DASIMPRM DD statement).

The GROUPNAME should be from 1 through 20 characters. The NEWJOB parameters member and group name are the basis for identifying the job order in the Active Jobs file. For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the GROUP sub-command in the NEWJOB statement (the CTMSIM utility).

SIM092S CPU ID OF ONE CHARACTER IS EXPECTED AFTER "CPUID" SUB-COMMAND

Explanation: The CPUID parameter in CPUID sub-command of NEWJOB statement (the DASIMPRM DD statement) is invalid or missing.

In a multiple CPU environment, the job can have different execution times on different CPUs. Therefore it is necessary to specify the expected elapsed time for each CPU the job may run on. The CPUID parameter should be of one character - identical to the CPUID used by JES for this CPU. For details, refer to the simulation parameters in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the CPUID parameter in the CPUID sub-command of NEWJOB statement (the CTMSIM utility).

SIM093S INVALID EXECTIME FORMAT. "mmmm.xx" EXPECTED

Explanation: Invalid or missing EXECTIME parameter in NEWJOB statement. (the DASIMPRM DD statement).

The EXECTIME is given in minutes (mmmm) and hundredths of a minute (xx). For more information, see the NEWJOB statement in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the EXECTIME parameter in the NEWJOB statement (the CTMSIM utility).

SIM094S MISSING "EXECTIME" SUB-COMMAND AFTER "NEWJOB"/ "OLDJOB" COMMAND

Explanation: Missing EXECTIME sub-command after NEWJOB (or OLDJOB) command (the DASIMPRM DD statement).

EXECTIME sub-command is obligatory in NEWJOB (or OLDJOB) statement. For details, refer to the NEWJOB or OLDJOB statement in the Control-M for z/OS User Guide.

Corrective Action: Add the EXECTIME sub-command or omit the NEWJOB (or OLDJOB) statement (the CTMSIM utility).

SIM095S MISSING EITHER "CONDITION" OR "RESOURCE" IN COMMAND

Explanation: Missing either CONDITION or RESOURCE in simulation command (the DASIMPRM DD statement).

ADD, DELETE or CHANGE commands can be used either with CONDITIONS or with RESOURCES. For details, refer to the simulation parameters in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the ADD, DELETE, or CHANGE simulation command.

SIM096S CONDITION/RESOURCE NAME MUST BE 1-20 CHARACTERS

Explanation: Invalid/missing CONDITION or RESOURCE name in simulation parameters (the DASIMPRM DD statement).

CONDITION or RESOURCE name must be 1-20 characters. For details, refer to the simulation parameters the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Please correct the CONDITION or RESOURCE name in the simulation parameters (the CTMSIM utility).

SIM097S MISSING "ONDAYTIME" SUB-COMMAND

Explanation: Missing ONDAYTIME sub-command in the simulation parameters (the DASIMPRM DD statement).

ONDAYTIME sub-command is obligatory in ADD, DELETE or CHANGE commands of the simulation parameters. For details, refer to the simulation parameters in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Please add an ONDAYTIME sub-command to the ADD, DELETE or CHANGE command of the simulation parameters.

SIM098I TASK taskName DID NOT FINISH EXECUTING

Explanation: This information message indicates that taskName task (job/started task) did not finish executing within simulation time limits (SIMEND).

The task started executing and was still executing at the end of the simulation.

Corrective Action: No action is required.

SIM099I TASK taskName STILL WAITS SCHEDULE

Explanation: This information message indicates that taskName task is still waiting to be scheduled after the simulation end time specified in the SIMIEND ONDAYTIME.

The job/started task was in wait schedule state at simulation end time. It probably did not execute.

Corrective Action: No action is required.

Parent Topic

SIM messages