Timing Services

Each time an application program is dispatched by Com-plete, it is given a certain amount of CPU time in which to complete its transaction and write a reply to the terminal. If an application program exceeds this amount of time, this message appears. This condition may be caused by an indefinite loop in application program '$'.

The user program is abnormally terminated with a Com-plete online dump.

The CPU time limit for the THREAD-GROUP parameter of Com-plete is used to set the CPU time limits for each thread. If this parameter is not specified, the CPU time limit is set to two seconds for each thread. For more information, refer to the Com-plete System Programmer's Manual.

The CPU time limit is set for each thread at the time Com-plete is initialised. This message indicates that a program has exceeded the set thread time (probably because it was looping). If the program needs more time than is allowed, the time may be extended by using the ROLLOUT function within the program. For more information, refer to the Com-plete Application Programmer's Manual.

Contact the application programmer responsible for the program in use when the error occurred.

Each time an application program is dispatched by Com-plete, it is given a certain amount of elapsed time in which to complete its transaction and write a reply to the terminal. If an application program exceeds this amount of time, the computer operator is informed by either the TMR0003 or TMR0004 messages, but the application program is not automatically terminated by Com-plete, because there is now way of ensuring that the application program is responsible for the elapsed time being exceeded (e.g., the CPU could have been in STOP mode or a SYSTEM-MUST- COMPLETE function could be transpiring in another region). The computer operator may choose to cancel the program once it has been determined that the problem is being caused by the application program and not by other circumstances. This message appears when the computer operator has elected to cancel the application program and has done so by entering the CAN command.

The program is abnormally terminated with a Com-plete online dump.

Contact the application programmer responsible for the program in use when the error occurred.

This situation indicates that the program was using more than its share of time in the thread. If the program needs more than 1 or 2 seconds of elapsed time in the thread, use the ROLLOUT function within the program to periodically relinquish the thread resource. For more information about the ROLLOUT function, refer to the Com-plete Application Programmer's Manual.

Each time an application program is dispatched by Com-plete, it is given a certain amount of elapsed time in which to complete its transaction and write a reply to the terminal. The amount of time is set by a Com-plete initialisation parameter. If an application program exceeds the set amount of time, this message appears. The program name is indicated by $1, terminal ID by $3, and $2 is the amount of excess time that has elapsed.

No action is required. Com-plete cannot automatically cancel the application program because the application program may not be responsible for the elapsed times being exceeded (for instance, the CPU could have been in STOP mode or a SYSTEM-MUST-COMPLETE function could have been transpiring in another region).

The REAL time limit for the THREAD-GROUP parameter of Com-plete is used to set the elapsed time limits for each thread. If this parameter is not specified, the elapsed time limit is set to seven seconds for each thread. For more information, refer to the Com-plete System Programmer's Manual.

Take the necessary action to determine if the application program is responsible for the time being exceeded. If so, enter the operator CAN command to cancel it. For more information about the CAN command, refer to the Com-plete Computer Operator's Manual.

Each time an application program is dispatched by Com-plete, it is given a certain amount of elapsed time in which to complete its transaction and write a reply to the terminal. The amount of time is set by a Com-plete initialisation parameter. If an application program program exceeds the set amount of time, this message appears. The program name is indicated by $1; the terminal ID of the terminal with which the program is in conversation is indicated by $2.

No action is required. Com-plete cannot automatically cancel the application program because the application program may not be responsible for the elapsed times being exceeded (for instance, the CPU could have been in STOP mode or a SYSTEM-MUST-COMPLETE function could have been transpiring in another region).

The REAL time value in the THREAD-GROUP parameter is used to set the elapsed time limits for each thread. If this parameter is not specified, the elapsed time limit is set to seven seconds for each thread. For more information refer to the Com-plete System Programmer's Manual.

Take the necessary action to determine if the application program is responsible for the time being exceeded. If so, enter the operator CAN command to cancel it. For more information about the CAN command, refer to the Com-plete Computer Operator's Manual.

User $1 running on tid number $2 luname $3 will be logged off by the Com-plete system as enter has not been hit at the terminal within the time specified in the AUTOLOGOFF Com-plete sysparm.

The system will attempt to log the user off.

This message shows that a scheduled request was performed by the timer monitor for the Userid $1.

This message shows that the timer monitor is working correctly, and which TID it attached.

While attempting to load the exit UTMEX2 an error was encountered.

The UTIMER monitor program UTIMRM is terminated.

Determine what caused the error and correct it.

Not enought storage was available to load the user exit UTMEX2 into the thread for UTIMER.

The UTIMER monitor program UTIMRM is terminated.

Increase the region size for UTIMRM with ULIB.

During start up, UTIMRM established that the monitor program was already active on another terminal in the system.

UTIMRM terminates.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

The UTIMRM exit UTMEX3 was invoked and returned an unexpected return code.

The return code is ignored and execution continues.

UTMEX3 gave a return code which was logically not expected at that point by U2TSUB, a subroutine of UTIMRM. Correct the error in the exit causing the bad return code to be returned. Refer to the system programmer's guide for more information regarding return codes expected from UTMEX3.

UTIMRM attempted to honour a request from UTIMER to submit a job, however, the SYSJOBS DD/DLBL statement could not be found and therefore the job could not be found to submit.

The request to submit the job is ignored.

The Jobs to be submitted by the timer monitor are expected in a dataset referenced by a SYSJOBS DD statement in Com-plete's startup procedure. ensure that this DD statement exists.

The UTIMRM monitor program attempted to submit a job but discovered that the Com-plete JES interface had not been successfully initialised and is not therefore available.

The job is not submitted to the JES.

If this processing is required, ensure that a JES is availble via the JES sysparm and that it manages to initialise successfully.

UTIMRM attempted to submit job $1, however, during the submission process, the Com-plete JES interface module returned an unexpected return code $2.

Submission of the jobn is terminated.

A Timer Monitor JES Operation could not be performed. Contact your local support centre with details of the error.

UTIMRM attempted to use a function of the Com-plete JES interface which is not supported.

The request is aborted.

This Message results from a return code 12 from the JES interface module. It could not perform the requested action.

UTIMRM requested that the Com-plete JES interface module issue a $1 request, however, the JIM did not support this.

This message results from a return code 16 from the JES interface module. The spool action is not supported. Contact you local support centre for more information.