Operator Communication

This message indicates the successful completion of the Com-plete initialisation process. Com-plete is now ready to accept users and operator commands.

This is an informational message only, no action is required.

This message is associated with Com-plete computer operator commands. Command $1 with operand $2 has been accepted and processed by Com-plete. This message is sent to the console at the completion of processing the following commands: ADD, DELETE, IGNORE, RESTART, CANCEL, STALL, UNSTALL, SETCTL, UNCTL, and LOGOFF.

The appropriate action is performed according to the command entered.

This is an informational message only. No action is required.

This message is associated with Com-plete computer operator commands. This message indicates that the user ID $2 referred to in command $1 is not logged on to Com-plete.

The command is ignored.

The operand field ($2) must be a valid user Id for a user who is currently logged on to Com-plete.

This message is associated with Com-plete computer operator commands. The system operator (or a privileged terminal user) has entered a Com-plete system command, but Com-plete was unable to identify the command verb or not enough characters were entered to uniquely identify the verb.

The command is not executed.

This message is sent to the console that entered the erroneous data (or the master console, if entered by a terminal user). Examine the failing command and reenter using a valid verb.

This message is associated with Com-plete computer operator commands. Device support for TID $3 is not included in the Com-plete nucleus, or that TID $3 is either a batch or attached TID.

The command is ignored unless $3 is a member of group $2. In that case, the remainder of group $2 will be processed.

After verifying that the correct TID or LID was entered in the command, notify the system programmer. The system programmer should include the device support modules for TID $3 in the next link edit of the Com-plete nucleus.

This message is associated with Com-plete computer operator commands. operator commands. It indicates that the EOJ command was invalid.

The command was ignored.

Refer to the Com-plete Computer Operator's Manual for the explanation of the use of the EOJ command.

This message is associated with Com-plete computer operator commands. In command $1, $2 is invalid. Here, $2 must be a valid TID, LID, user ID, group name or ALL.

The command is ignored.

Reenter the command with a valid $2 field.

This message is associated with Com-plete computer operator ADD and RESTART commands. Terminal (online) $2 was activated at Com-plete initialisation or by a previous ADD or RESTART command and has not been IGNORED.

The command is ignored.

The terminal is already in the active state. A terminal must be in the non-active state (via the IGNORE command) before a RESTART command can be issued for it.

This message is associated with the Com-plete computer operator CANCEL command. It indicates that more than one TID, TIBNAME, or user ID ($2) was entered for command $1.

The command is ignored.

Only one terminal may be cancelled at a time. Here, $2 may only be one valid TID, TIBNAME, or user ID.

This message is issued if an attempt is made to CANCEL or LOGOFF an APPC TIB while this TIB is waiting for input.

The command is ignored.

This message is issued in response to a CANCEL command entered by the computer operator. It indicates that a privileged program (UQ, UEDIT, etc.) or a Com-plete service routine had control of terminal $2 when the CANCEL command ($1) was issued.

The program running on terminal $2 has been flagged to be terminated at the end of the current process.

It is not recommended that privileged programs or the service routine be cancelled; however, by reentering the CANCEL command, the computer operator may be able to cancel the current process.

A DELETE command was entered for a locally attached terminal or remote line ($2) that is still active (has not been ignored).

The command is ignored.

IGNORE the local terminal or the remote line prior to attempting to DELETE it.

An IGNORE command has been issued for a terminal ($2) that has already been ignored.

The command is ignored.

The terminal or line is already ignored, so no further action need be taken.

TID $3 is rolled out and cannot be ignored.

The command is ignored unless $3 is a member group, in which case processing of the group continues.

The program that is active for the terminals ($3) being ignored must be allowed to finish processing or be cancelled before the terminal can be ignored.

The program associated with the terminal is active in the thread and must be cancelled before the terminal can be ignored.

The command ($1) is ignored unless $3 is a member of group $2, in which case processing of the group continues.

If the program associated with a terminal remains active in the thread, the proper action is to cancel it rather than to ignore the terminal. This condition can be the result of a missing I/O interrupt or an outstanding console reply. These conditions should be checked prior to cancelling a program.

This message is associated with Com-plete computer operator commands. It indicates that Com-plete was unable to issue its hello message to all the terminals in the Com-plete system for one or more of the following reasons:

1. The security violation occurred because TID 1 was not authorised to send a class 2 message.

2. DEST CODE $ was translated by Com-plete to define more than 100 terminals.

3. DEST CODE $ was higher than the highest code defined to Com-plete.

4. DEST CODE $ was not defined in TIBTAB.

5. DEST CODE $ defined a terminal that was not authorised to receive class 2 messages.

The destination code indicated by DEST CODE $ is bypassed (i.e., the Com-plete hello message is not sent to the terminals defined by DEST CODE $).

This message is associated with the Com-plete operator commands ADD and RESTART. For an ADD command, it indicates that the terminal ($2) cannot be ADDed because it is already active to another user or job within the system. For a RESTART command, it indicates that the terminal ($2) is already active under Com-plete.

The command is ignored.

For an ADD command, the terminal must first be released from its current user/owner. For a RESTART command, the terminal must be deactivated via an IGNORE operator command prior to issuing the RESTART command.

TID $3 is in a Com-plete queue and cannot be restarted.

The command $1 is ignored unless $3 is a member of a group ($2). in which case processing of the remainder of the group continues.

This message indicates a logic problem in the Com-plete nucleus. Contact your technical representative.

This message is associated with Com-plete computer operator commands. It indicates that Com-plete was unable to perform the EOJ operation specified by the computer operator because the batch job indicated by $ was using a Com-plete function at the time the EOJ command was issued.

The EOJ command is ignored.

Wait until the batch job $ terminates and then reissue the EOJ command.

This message is associated with the Com-plete computer operator commands. It indicates that Com-plete was unable to perform the CANCEL operation requested by the computer operator because the TID specified by the computer operator is active in the thread and is currently waiting for an ENQ/LOCK function to complete.

The CANCEL command is ignored.

Determine why the program associated with this TID is waiting to ENQ/LOCK on a resource and attempt to make the resource available. If the cause of the wait cannot be determined or the resource cannot be made available, issuing a second CANCEL command for this TID will cause the program associated with this TID to be cancelled. This will cause the resource for which the program was waiting to be left enqueued with no associated program to later dequeue it. The Com-plete program termination cleanup is unable to DEQUEUE/UNLOCK this resource since it is in the waiting status. The UENQ Com-plete utility can be used to DEQUE/UNLOCK the resource left as a result of cancelling the TID; however, care should be taken not to DEQUEUE/UNLOCK the wrong resource.

Before issuing the CANCEL command for this TID a second time, seek the assistance of the Com-plete system programmer.

Self-explanatory message.

The OC task was attempting to print something to SYSPRINT and found that the DD/DLBL statement did not exist in the job control. Therefore the DD/DLBL statement was dynamically allocated to make it available for use.

To avoid this message, the SYSPRINT DD/DLBL statement must be coded in the Com-plete job control.

This message is associated with Com-plete VTAM support. An invalid operand field was entered with the VTAM command.

The command is ignored.

The operand field for the VTAM command must be STOP or START.

Com-plete's OC task was attempting to print something to the SYSPRINT DD/DLBL but found that it didn't exist in the job control. An attempt was made to allocate it dynamically, however, this failed. For MVS systems $1 and $2 are the error and information codes respectively returned by the DYNALLOC function.

The attempt to print is terminated.

Using the diagnostic information, determine why the dynamic allocation of the DD/DLBL statement didn't work. If installation related, then correct the error. If not, contact your local support centre with the details of the error.

Tracing is active in the system where a certain amount of storage has been reserved for the trace areas. As the buffers area filled they may be written to CAPTURE and reinitialised or simply reinitialised if the data is not being CAPTUREd. When a buffer is full, an attempt is made to find the next 'reinitialised' or available trace buffer. If this cannot be found due to delays in CAPTURE or the speed of the machine, the requested data cannot be traced and therefore trace entries are lost. The message registers the number of trace entries $1 lost in the previous 60 seconds or so.

The trace entry is lost and processing continues.

It is very unlikely that this message will be seen when trace data is NOT being CAPTUREd as the CAPTURE buffers will be reinitialised for use as soon as they are filled. It may occur if a minimum of trace buffers are made available and large numbers of trace records are being written.

This can occur when trace data is being CAPTUREd and the volume of tracing is filling the allocated buffers faster than they can be written to CAPTURE. In this case enough buffers must be allocated to ensure that the filled buffers are CAPTUREd and reinitialised BEFORE the 'free' buffers are filled again.

This message is associated with the Com-plete operator communications processor and is the normal response to an EOJ (shutdown) request from the operator or a privileged terminal user.

Com-plete begins its normal termination processing. Thread activity is quiesced, no user is allowed to enter any data, and active programs are terminated. No further operator communications will be accepted.

This is an informational message only; no action is required.

This message is associated with the Com-plete operator communications processor and is the normal response to an EOJ (shutdown) request from the operator or a privileged terminal user. Com-plete has finished its normal termination processing and is exiting the operating system.

Com-plete terminates normally with return code of zero.

This is an informational message only; no action is required.

This message is issued in response to a DISALLOW LOGON command entered by the computer operator. It indicates that the request was successfully performed.

All future LOGON requests will not be honored; however, all users who are already logged on to the Com-plete system will be able to continue until they log off.

When ready to allow new users to log on to Com-plete, use the ALLOW command. For information about this command, refer to the Com-plete Computer Operator's Manual.

This message is issued in response to an ALLOW LOGON command entered by the computer operator. It indicates that the request was successfully performed.

Com-plete will resume honoring LOGON requests from terminals.

For information about the ALLOW command, refer to the Com-plete Computer Operator's Manual.

This message is issued in response to a DISALLOW RJE command entered by the computer operator. It indicates that the request was successfully performed.

All future RJE requests from application programs will receive a return code indicating that RJE is disallowed.

When ready to allow RJE requests from application programs, use the ALLOW command. For details about this command, refer to the Com-plete Computer Operator's Manual.

This message is issued in response to an ALLOLW RJE command entered by the computer operator. It indicates that the request was successfully performed.

Com-plete will resume honoring RJE requests from application programs.

For information about the ALLOW command, refer to the Com-plete Computer Operator's Manual.

This message is issued in response to a DISALLOW ULIB command entered by the computer operator. It indicates that the request was successfully performed.

All future use of the ULIB utility will result in an error message indicating that ULIB is disallowed.

When ready to allow use of the ULIB utility, use the ALLOW command. For information about this command, refer to the Com-plete Computer Operator's Manual.

This message is issued in response to an ALLOW ULIB command entered by the computer operator. It indicates that the request was successfully performed.

The ULIB utility will resume honoring requests.

For information about the ALLOW command, refer to the Com-plete Computer Operator's Manual.

This message is issued in response to a DISALLOW UQ command entered by the computer operator. It indicates that the request was successfully performed.

The UQ utility will not allow the H, R, S, C, DE, and OC commands to be issued against any batch job that does not have the special UQ JCL security statements (//*UQ USER ID, //*UQ ACCOUNT, etc.). This is the same as though UQDEFAULT=NO had been specified in the Com-plete initialisation parameters.

This message is issued in response to an ALLOW UQ command entered by the computer operator. It indicates that the request was successfully performed.

The UQ utility will not perform any security on the H, R, S, C, DE or OC commands when they are issued against a batch job that does not have the special UQ JCL security statements (//*UQ USER ID, //*UQ ACCOUNT, etc.). This is the same as though UQDEFAULT=YES had been specified in the Com-plete initialisation parameters.

This message is issued in response to an ALLOW or DISALLOW command entered by the computer operator. It indicates that the parameter supplied was not one of following: LOGON, RJE, ULIB, or UQ. For information about the ALLOW and DISALLOW commands, refer to the Com-plete Computer Operator's Manual.

The command is ignored.

This indicates that the operator has issued a $1 command and the request has been process successfully by ENQing the user's terminal.

The $1 command will be processed asynchronously to eventual completion.

The user will be logged off asynchronously.

The $1 command has been processed successfully.

This message is associated with the Com-plete operator communications processor and is the normal response to an IGNORE operator command. The system operator or a privileged terminal user has entered a request to ignore input/output requests for a terminal, line, or group of terminals and lines. The IGNORE command has been successfully processed.

Normal processing continues. No data will be entered from or sent to the designated terminal(s)/line(s).

This message is sent to the console that entered the command (or to the master console if entered by a terminal user). The requested terminal(s) or line(s) are now allocated to Com-plete and are ineligible for allocation by other teleprocessing systems or jobs. It will be necessary to issue a DELETE operator command in order to allow the terminal(s) or line(s) to be allocated by another job.

During Com-plete termination processing, Com-plete attempted to load module $1, however, the module was not found in the load libraries available to Com-plete.

If the module is not required, processing wil continue as normal. If the module is required for termination, a message will be issued indicating that termination may not finish successfully without this module.

Determine if the module is necessary for correct termination and if so make it available in the load libraries available to Com-plete.

During termination processing, Com-plete attempted to load module $1. During load processing, an error occurred and the module could not be loaded.

If the module is not required, processing continues as normal, however, if it is required, a warning will be issued that termination may not complete correctly wihtout this module.

Usually the operating system will issue message in relation to the error. Use this information to determine why an error occurred loading the module and correct the error.

During termination processing, Com-plete attempted to load module $1. Either the BLDL or the LOAD failed as indicated by $2. The error code $3 is the abend code returned from the load, if load processing failed. If BLDL processing failed, this code is the contents of R0 after the failed BLDL.

If the module is not required, processing continues as normal. If the module is required, a warning message will be issued indicating that termination processing may not complete successfully.

Determine based on the provided diagnostic information why the function failed and correct the error for the next Com-plete termination.

During startup or termination processing, module $2 was called and returned a return code $1.

If this happens during startup, then in most cases the initialization process is stopped. During termination, processing continues with the next module.

If the module is a Com-plete module, report the return code to your local support centre as it indicates some form of unexpected error. If the module is a user module or exit, then determine why the module returned the code it did and correct the problem or the module to cause a zero return code as required.

During termination processing, an error was encountered with a module which was required to successfully execute to bring about normal termination. The module $1 did not successfully execute and therefore termination may not be normal. The reason that the module did not successfully execute will be clear from the message immediately preceeding this related to the same module name.

Processing continues with the next termination module.

Determine what the error with the module is and correct this to ensure normal termination of Com-plete the next time around.

This message is associated with the computer operator command IGNORE. It indicates that Com-plete was unable to honor the request because the program running under the specified terminal was rolled out waiting for an event to complete (such as a call to ADABAS or a timed rollout).

The IGNORE command is not honored.

The continual appearance of this message normally indicates that the application program is waiting for an event that will not complete in a reasonable amount of time (such as a program that has rolled out for an extremely long time) or that may never complete at all (such as an application program waiting for ADABAS when ADABAS has terminated). If this is the case, cancel the program (CANCEL command) before the terminal is ignored. For information about how to accomplish this, refer to the Com-plete Computer Operator's Manual.

Com-plete termination processing reaches a point whereby it expects all threads to be quiesced ie. at the 'WAIT WORK' status. This message indicates that that status has been reached.

Termination processing proceeds to the next stage.

If it seems that the threads will never go to wait work, either force 'normal' termination via the 'EOJ FORCE' command, or cancel Com-plete with a dump to provide some diagnostic information for the problem.

The $1 command has been accepted and initiated via a cancel of the user or terminal specified via $2.

The requested action will asynchronously continue until completion.

This indicates that the request was successfully processed, however, if the asynchronous processing fails, the 'successful' completion may be mislead and, for example, as user who you attempted to logoff wasn't logged off correctly. If this occurs, try again, however as a final measure, the user could be forced.

An ADD command has been issued for a local CTAM device or remote line. Com-plete attempted to allocate the device as a result, however, this failed. A previous message will have been issued indicating why the allocate failed. Please refer to this for details.

This message is associated with the Com-plete online program rollout and termination thread cleanup processor. The application program has terminated or rolled out with an unanswered WTOR (Write To Operator with Reply), and the Com-plete thread cleanup processor has cancelled the associated reply. The X'$1' is the ID number of the cancelled reply.

The application program is rolled or terminated. The operator reply is cancelled.

Identify the program issuing the WTOR and either eliminate the WTOR or satisfy the WTOR prior to doing a ROLL function or program termination.

Notify the Com-plete system programmer.

The request $1 caused the user identified by $2 to be forced.

The 'FORCE' command should only be used as a last resort on the basis that it can conceivably cause Com-plete abends in certain cases.

Consult your system programmer in relation to using the 'FORCE' command as it can effect the integrity of the system.

This message is associated with Com-plete computer operator commands. It indicates that the action of a CANCEL command has been delayed because the TID being cancelled is processing within an area that may not be interrupted by a CANCEL command (i.e., a must-complete condition exists).

Cancel status is set for the specified TID when the CANCEL is delayed. Once the must-complete condition has cleared, the cancel action will be taken. If a second CANCEL command is entered for a TID that already has a delayed cancel pending, the CANCEL will be rejected.

Determine the cause of the delayed cancel. The 'must-complete' status is set while writing the capture file, RJE processing, operator command processing. If the cause cannot be determined, cancel Com-plete with a dump and contact your Com-plete support representative.

Wait for the delayed cancel to take effect. If the cancel has not completed after a reasonable time period, contact the installation system programmer.

Self-explanatory message.

An attempt was made to delete a device ($2) which was already deleted.

No action is necessary as the terminal or line is already deleted.

The command $1 was issued against the user defined by $2, however, the command could not complete successfully as the TIB for the user was in an invalid state, or was waiting in one of Complete's internal queues. In this case, the requested operation can only be marked for the user.

Use UCTRL subfunctions US/QO/PL/SG/TL to determine if there is a lock situation somewhere causing the TIB to be hung in a queue. If there is, try to remove the reason for the hang (e.g. by cancelling the user locking up a thread or subtask). If the TIB is not on any queue, then this message generally indicates a Complete logic error which should be reported to your local support centre. To get rid of the TID/User when it's not on a queue, the 'FORCE' command can be used which should clear up the situation. If the same message results from the issuing of the 'FORCE' command, it indicates that the TIB is in a state whereby it would more than likely cause an abend if it the TIB was to be FORCEd. In this case, the TIB and Userid are lost until the next time Com-plete is brought down and back up again.

When a command fails in this way, refer the problem to the system programmer.

The system programmer has the option to specify an eight byte character string which must be entered with the EOJ command to ensure that it comes from an authorised user knowing the verfiy data. This message indicates that a verify string must be entered and/or the incorrect verify string was provided.

The EOJ command is ignored.

ensure that the verify string is known to users authorised to bring Com-plete down.

If authorised to bring Com-plete down, your system programmer must provide you with the verify data in order for the EOJ command to work.

When REVIEW is installed in the SYSTEM, it is necessary for a REVIEW EOJ program to be attached. This message indicates that this has just occurred.

The EOJ command must be entered again after the REVIEW EOJ program has terminated successfully.

Wait for the successful completion of the REVIEW EOJ program and issue the EOJ command again.

An operator command related to CAPTURE processing has been entered, however, CAPTURE is not active in the system.

This message will be received in response to a DCTRL operator command. This will cause a heading line to be printed with this message number followed by a list of control tids.

This message will be issued in response to a PLIST or TLIST operator command. The first message will contain a heading describing the format of the lines to follow and it will be followed by the lines of information requested.

Com-plete EOJ has been requested with the FORCE option. This will cause Com-plete to terminate without waiting for various termination processes to complete.

Com-plete EOJ is in progress and a logoff has been issued for all users. Having issued the logoff, Com-plete must wait until all users are logged off. The message is issued periodically with the number of users left to logoff ($1).

Com-plete waits for a number of seconds and rechecks to see if all users are logged off.

In error situations, all users may not logoff. The operator can then FORCE each individual user or can reissue the EOJ command with the 'FORCE' option to bypass the check.

The Com-plete main task has abended. Diagnostic ZAB messages will be issued along with this message.

The Com-plete recovery routines have detected an operating system cancel request.

After certain necessary cleanup, the cancel will be allowed to continue without any attempt at recovery.

This message indicates that OC has tried to attach a program for one of the following events.

1. As a result of the STARTUPPGM parameter

2. As a result of an attach due to the contents of ULPGMTAB

3. As a result of a 'USER' operator command

4. At EOJ processing for REVIEW.

The attach failed due to return code $2. The reason for failure is as follows..

04 - The requested program could not be found.

08 - A security violation has occurred.

12 - An invalid program name was provided.

16 - A logic error has occurred while processing the request.

20 - No eligible thread was available in which to run the program.

24 - No TIB was available on which to run the program.

28 - A valid and supported terminal type could not be established.

32 - Insufficient storage in the general buffer pool for request.

No action is taken, the program is simply not attached.

Correct the error based on the return code as follows...

• 04 - This return code indicates that the program is not available to run in a thread. This may simply be that the program is not in the loadlibs/CILs available to Com-plete or due to installation options.

• 08 - Access to the program has been denied by a security exit.

• 12 - A valid program name must start with an alpha character and be no more than 8 characters long.

• 16 - Report this error to your local support centre.

• 20 - The program you requested has been catalogued with a region size larger than any thread currently defined. Either recatalog the program to a size small enough to run in one of the currently defined threads or define a thread large enough to run the program.

• 24 - Define more dynamic TIBs in your TIBTAB.

• 28 - Device support for at least one of the 3270 family of terminals must be defined in your TIBTAB (eg. 3278).

• 32 - Review your storage estimates for your general buffer pool.

Action should be taken based on the return code received. Refer to the documentation for system programmers for more information.

The operator entered requested that a user be forced off the system. This command is invalid without a previous logoff attempt for the user in the case of a non-attached terminal or a previous cancel attempt for an attached task.

The request is ignored.

Before attempting to force a user, you must first attempt a 'LOGOFF' command for a non-attached user or a CANCEL command for an attached user. If after this has been attempted the user is still in the system, the force will be accepted.

The requested command has been attempted for an attached user. This command cannot be issued for an attached user.

The request is ignored.

Attached users are a special case, so, in most cases, there is another operator command which will cause the effect you require. You must determine what thes command is and issue for the user.

The main Com-plete task 'OC' requires a storage area to build a list upon which it can wait. The storage for this list was not available.

Com-plete will terminate with an abend.

This indicates that there was insufficient storage available in the general buffer pool. Review the storage allocation for Com-plete generally and the general buffer pool in particular.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Parameter DISK/NODISK is not longer supported.

The dump was written to the POWER queue

This message is issued when the VSE Trace facility (UPSI) has been activated.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

The operator command $2 has been issued with an operand of $1. This operand is not valid for the command. When the string '*no operand*' appears, it indicates that the command was issued without an operand when an operand was required. Refer to the operators manual for the correct syntax of the command.

The command $1 $2 was issued by the operator. As a result, the program running on TID $4 was terminated by abending the program. This indicates that the program was associated and running on a task.

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

The command $1 $2 was issued by the computer operator. This resulted in the user program running on TID $4 being cancelled by posting the program active. This indicates that the program was associated with a task but was waiting on one or more ECBs to be posted active.

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

An attempt to display or modifiy the task group $1 failed as the task group does not exist.

Use the UCTRL utility PG function to determine what task groups are currently active on the system.

An attempt to display or modify the thread group $1 failed because the thread group does not exist.

Use the UCTRL utility TG function to determine what thread groups are currently active on the system.

HWM = High Water Mark, i.e., the maximum value at any one time during the given run of Com-plete. The number of sessions includes terminal sessions and sessions from other address spaces (e.g., through the BATCH interface). It does not include asynchronuous ("attached") processes.

Self-explanatory message.

This message is issued in response to any Com-plete operator command. This command could have been issued from an operator console or generated internally during startup or termination.

The command parsing and processing follows.

This is an informational message only and no action is required.

Self-explanatory message.