UMS Utility

Overview of Messages

UMS0001 | UMS0003 | UMS0004 | UMS0005 | UMS0006 | UMS0007 | UMS0008 | UMS0009 | UMS0010 | UMS0011 | UMS0012 | UMS0013 | UMS0014 | UMS0015 | UMS0016 | UMS0018 | UMS0019 | UMS0020 | UMS0021 | UMS0022 | UMS0023 | UMS0025 | UMS0026 | UMS0027 | UMS0028 | UMS0030 | UMS0031 | UMS0041

UMS0001 MSG Id $1 has been sent
Explanation:

This message is associated with message switching. It appears when Com-plete has queued the message indicated by MSG ID $1 as requested. It does not, however, necessarily indicate that the message has actually been written to the designated terminal(s). If the designated terminal was in conversation with the program, was inoperative, or was disabled at the time the message indicated by MSG ID $1 was queued, the message will be sent to its alternate terminal. If no alternate was assigned to the receiving device, the message will be available for display when the terminal is once again able to receive messages.

System action:

The message indicated by MSG ID $1 is either written to the receiving terminal, or placed in the queue of its assigned alternate.

Terminal operator info:

Determine whether the message indicated by MSG ID $1 has been written to the receiving terminal by displaying the status of the receiving terminal and its alternate. If MSG ID $1 does not appear on the display, it may be assumed that the message has been received. For information about displaying the status of a Com-plete terminal, refer to the Com-plete User Utilities Manual.


UMS0003 Invalid DEST code, MSG Id, or terminal specified
Explanation:

This message is associated with message switching. It appears when the terminal operator has entered a message request and one of the following conditions prevented Com-plete from successfully sending the message: sending the message:

  1. The destination code (DEST CODE) specified by the terminal operator was not defined in TIBTAB.

  2. The (DEST CODE) specified by the terminal operator was translated by TIBTAB into an invalid TID number.

  3. The terminal entry did not conform to the rules of syntax for message switching commands.

  4. The TID number specified by the terminal operator was higher than the highest TID number in the Com-plete system.

System action:

The message request is ignored.

Terminal operator info:

Check the parameters specified in the message request. If an error was made, correct and reenter the request. If an error was not made, seek the assistance of the Com-plete system programmer.

System programmer info:

The destination code may be added to the destination code table in the TIBTAB so that the error will not occur on future messages.


UMS0004 Message too long
Explanation:

This message is associated with message switching. It appears when the terminal operator has attempted to enter a message segment with a combined length (destination code and text) greater than 1000 bytes.

System action:

The message request is ignored.

Terminal operator info:

Messages that exceed 1000 bytes in length must be entered by dividing the text of the message into two or more portions and sending them as separate message segments. Com-plete will combine these segments into one message prior to displaying it at the receiving terminal(s). For more information, refer to the Com-plete User Utilities Manual.


UMS0005 More than 100 destination tids
Explanation:

This message is associated with message switching. It appears when the terminal operator has attempted to send a message to more than 100 terminals at a time.

System action:

The message request is ignored.

Terminal operator info:

Messages may be sent to more than 100 receiving terminals by repeatedly entering the request and specifying a different group of receiving terminals each time. Correct the error and reenter the request.


UMS0006 Invalid class code(s) specified
Explanation:

This message is associated with message switching. It appear when the terminal operator has entered a message request containing class code(s) that were invalid for one or more of the following reasons:

  1. The class code specified contained a non-numeric character.

  2. The number specified for class codes was not between 1 and 16.

System action:

The message request is ignored.

Terminal operator info:

Check the validity of the class codes specified in the message request. Correct the error and reenter the request.


UMS0007 No message text entered
Explanation:

This message is associated with message switching. It appears when the terminal operator has entered a message request containing a valid destination code and class code, but no text was entered.

System action:

The message request is ignored.

Terminal operator info:

Add the message text and reenter the request.


UMS0008 Control block error. Reenter message
Explanation:

Com-plete has dequeued the first segment of a multi-segmented message during the interval in which the first and current segments were being entered. The two most common causes of this conditions are:

  1. The message disk was overlayed before the second segment was sent.

  2. The first segment was dequeued because the DELETE command was issued for the first segment before the second segment was sent.

System action:

The message request is ignored.

Terminal operator info:

To send a message, reenter it from the beginning.

System programmer info:

If this message was issued due to disk overlay, the size of the message file may have to be expanded. For information on how to accomplish this, refer to the Com-plete System Programmer's Manual.


UMS0009 Security violation
Explanation:

This message is associated with message switching. It appears when the terminal operator has entered a message request containing one or more of the following errors:

  1. One or more of the receiving terminals was not authorized to receive one or more of the class codes specified in the request.

  2. The user terminal was not authorized to send one or more of the class codes specified in the message request.

  3. At least one class code between one and four was not specified in the message request.

System action:

The message request is ignored.

Terminal operator info:

Examine the message request to be sure that the appropriate class codes are specified. Since class codes 1 trough 4 are the only class codes used for security purposes (12 through 16 are used for status only), every message must specify at least one of these codes. The class codes may be determined by checking the status of both the sending and receiving terminals. If there is a common class code that may be used by both, change the class code of the message accordingly and reenter the request. For information on how to determine the status of Com-plete ree messages and terminals, refer to the chapter entitled 'UM - Message Switching Utility' in the Com-plete User Utilities Manual.


UMS0010 I/O error during message disk write
Explanation:

This message is associated with message switching. It appears when a disk I/O error has occurred as Com-plete was attempting to write a message to the message file.

System action:

The message request is ignored. The UMS00010 message is accompanied on the system console by one or more ZMD00001 or ZMD00005 messages that indicate more precisely the nature of the error.

Terminal operator info:

Seek the assistance of the Com-plete system programmer.

System programmer info:

Refer to the system console for additional messages.


UMS0011 Too many receiving terminals specified
Explanation:

This message is associated with message switching. It appears when the number of terminals specified to receive a message exceeds 100.

System action:

The message request is ignored.

Terminal operator info:

A message may be sent to more than 100 receiving terminals by repeatedly entering the request and specifying a different group of receiving terminals each time.


UMS0012 Invalid time index specified
Explanation:

This message is associated with message switching. It appears when the terminal operator has specified an invalid time index while attempting to display the message switching status of a terminal with '*UM.DT'.

System action:

The message request is ignored.

Terminal operator info:

Correct the time parameter of the display status command and reenter the request. For information about how to use the *UM.DT command, refer to the chapter entitled 'UM - Message Switching Utility' in the Com-plete User Utilities Manual.


UMS0013 Message too long for class 16
Explanation:

This message is associated with message switching. It appears when the combined length of the destination code list and message text exceeds 240 characters for a class 16 message request.

System action:

The message request is ignored.

Terminal operator info:

Since class 16 messages are not queued to a disk, the combined data must fit into one message buffer. For information on how to calculate the maximum text length, refer to the Com-plete User Utilities Manual.


UMS0014 Enter next segment
Explanation:

This message is associated with message switching. It appears during the entry of a multi-segmented message and indicates that Com-plete is ready to receive the input for the next segment.

System action:

When this message appears, Com-plete is ready to receive more input for the message text.

Terminal operator info:

Continue entering the message. The entry immediately following the UMS00014 message is considered by Com-plete to be a continuation of the text of the message. If the NULL INPUT key is pressed at this point, the action will be interpreted by Com-plete to mean that all of the text has been entered, and the message will be sent. If the CLEAR key is pressed or if '*EOJ' is entered, the message will be aborted.


UMS0015 Index to requested time not available
Explanation:

This message is associated with message switching. It appears when the terminal operator attempted to display the status of a terminal during a interval that did not exist in the timetable maintained by Com-plete .

System action:

The message request is ignored.

Terminal operator info:

The UMS00015 message normally indicates that Com-plete was inoperative during the specified interval of time. Ask the computer operator when the inoperative condition started and ended, change the extents of the specified interval accordingly, and reenter the request. For information about how to use the '*UM.D.t' command, refer to the chapter entitled 'UM - Message Switching Utility" in the Com-plete User Utilities Manual.


UMS0016 Unauthorized privileged request entered
Explanation:

This message is associated with message switching. It appears when the terminal operator has attempted to perform a privileged message switching function from an unauthorized terminal.

System action:

The message request is ignored.

Terminal operator info:

Ask the computer operator to perform the privileged function.


UMS0018 Tid not specified
Explanation:

This message is associated with message switching. It appears when the terminal operator has failed to specify a TID when attempting to change the class codes of a terminal.

System action:

The message request is ignored.

Terminal operator info:

Add the appropriate TID number of the terminal being changed and reenter the request. For information about changing the class codes assigned to a terminal, refer to the chapter entitled 'UM - Message Switching Utility' in the Com-plete System Utilities Manual.


UMS0019 Message not found
Explanation:

This message is associated with message switching. It appears when the terminal operator has attempted to restart or recall the current message, and one or more of the following conditions prevented the successful execution of the command:

  1. The message was not available, it was deleted by a disk overlay.

  2. The message was not available, because it was deleted by the DELETE command.

  3. No message was currently being displayed at the user terminal.

System action:

The message request is ignored.

Terminal operator info:

Attempt to recall the message using the '*UM.n' command. If this action is unsuccessful, the current message may be recalled.

System programmer info:

If this message was issued due to disk overlay, expansion of the message file may be desired. For information on how to accomplish this, refer to the Com-plete System Programmer's Manual.


UMS0020 Unbalanced parenthesis in request
Explanation:

This message is associated with message switching. It appears when the terminal operator has entered an unbalanced pair of parentheses in a message switching request.

System action:

The message request is ignored.

Terminal operator info:

Correct the error and reenter the request.


UMS0021 Requested message or printout incomplete
Explanation:

This message is associated with message switching and printout spooling. It appears when the terminal operator has attempted to recall a message or printout while it was still being entered at the sending terminal.

System action:

The message is ignored.

Terminal operator info:

This error often occurs because the terminal operator has attempted to recall a multi-segmented message before the last segment was entered. Wait a few moments and then reenter the request.


UMS0022 Requested operation complete
Explanation:

This message is associated with message switching. It appears when the operation requested by the terminal operator has been successfully performed.

System action:

None.

Terminal operator info:

None.


UMS0023 Too much information specified in message request
Explanation:

This message is associated with message switching. It appears when the terminal operator has supplied excessive information in an ENABLE, DISABLE, or PURGE request.

System action:

The message request is ignored.

Terminal operator info:

Correct the error and reenter the request, For information regarding the ENABLE, DISABLE, or PURGE commands, refer to the Com-plete User ding Utilities Manual or the Com-plete System Utilities Manual.


UMS0025 Specified ALTernate has different receiving class codes
Explanation:

This message is associated with message switching. It appears when Com-plete was unable to assign an alternate terminal as requested by the terminal operator because the designated alternate and the original terminal did not have the same receiving class codes.

System action:

The message request is ignored.

Terminal operator info:

The status of any terminal may be determined by using '*UM.D'. Specify an alternate terminal that has the same receiving class codes. If unable to do this successfully, seek the assistance of the Com-plete system programmer.

System programmer info:

The '*UM.RCLASS' command may be used to temporarily reset the class codes assigned to a terminal.


UMS0026 Missing parenthesis in message request
Explanation:

This message is associated with message switching. It appears when the terminal operator has failed to isolate the class code parameter in a message switching command with the required set of parentheses.

System action:

The message is ignored.

Terminal operator info:

Correct the error and reenter the request.


UMS0027 Requested MSG or PO queued to different Tid
Explanation:

This message is associated with message switching and printout spooling. It appears when one or more of the following conditions existed while the terminal operator attempted to DELETE a message or printout:

  1. The requested message/printout was not queued to the specified TID.

  2. The requested message/printout was not in the message disk file

  3. The requested message/printout had already been deleted.

System action:

The message request is ignored.

Terminal operator info:

Examine the request to be sure that the correct TID has been specified. If the correct TID has been specified, the requested message is not available for display. If the TID is not correct, correct the error and reenter the request.


UMS0028 Tid identified Lib
Explanation:

This message is associated with message switching. It appears when the TID number specified by a terminal operator in a message switching command identified a valid LIB but not a valid TIB (Terminal Information Block).

System action:

The message request is ignored.

Terminal operator info:

Correct the error and reenter the request.


UMS0030 Bad Tib chain or invalid MCQRTID
Explanation:

This message is associated with message switching. It appears when Com-plete was unable to perform the requested message switching operation because an error was detected in a message core queue field.

System action:

The message request is ignored.

Terminal operator info:

Seek the assistance of the Com-plete system programmer.

System programmer info:

This error is caused by one or more of the following conditions:

  1. The TIB- (MCQPNTR) or RB-chain (MCQPNTRB) associated with a core queue encountered by Com-plete contained an invalid displacement.

  2. Com-plete was unable to find the appropriate core queue while following the TIB chain for the TID specified in MCQRTID.

Both of these conditions are usually caused by the destruction of all or part of the Com-plete buffer subpool.

Notify Com-plete technical support of this error condition.


UMS0031 Unauthorized attempt to send class 4 message
Explanation:

This message is associated with message switching. It appears when the terminal operator attempted to send a class 4 message.

System action:

The message request is ignored.

Terminal operator info:

Class 4 is reserved for Com-plete internal use only.


UMS0041 Bad Tib chain or invalid MCQRTID
Explanation:

This message is associated with message switching. It appears when Com-plete was unable to perform the requested message switching operation because an error was detected in MCQRTID.

System action:

The message request is ignored.

Terminal operator info:

Seek the assistance of the Com-plete system programmer.

System programmer info:

This error is caused by one or more of the following conditions:

  1. The TIB- (MCQPNTR) or RB-chain (MCQPNTRB) associated with a core queue encountered by Com-plete contained an invalid displacement.

  2. Com-plete was unable to find the appropriate core queue while following the TIB chain for the TIB specified in MCQRTID.

Both of these conditions are usually caused by the destruction of all or part of the Com-plete buffer subpool. Cancel Com-plete (with a dump) and notify Com-plete technical support of this error condition.