CP-AMS run-time user messages appear in OS 2200 Console View. They are generally displayed by CP-AMS run time using unsolicited log (LG) commands. The use of log commands ensures that the message is entered into the host's system log.
Following is a list of CP-AMS run-time messages.
msg-id MODE IS UNATTENDED, REQUEST REJECTED
where msg-id is the message identifier for the read-and-reply message being answered.
This message is issued in response to a read-and-reply message generated by a MSG,W request when the system is running in unattended mode.
Example
0 MODE IS UNATTENDED, REQUEST REJECTED
LG *run-id ERROR DUE TO R-AND-R MSG IN UNATTENDED MODE
where run-id is the system-generated run-id of the run about to be abnormally terminated. The run-id is obtained from the run-id field passed with the extended message attributes.
This message is issued when a run with an outstanding message is about to be abnormally terminated by CP-AMS. The following conditions must be present for error termination to occur:
System is running in unattended mode.
The TRME option is set (ON).
The message is read-and-reply.
The run generating the message is nonprivileged.
There was no pattern matching the message in the AMS database.
Example
The nonprivileged run ELISE is aborted because it issued a nonmatching read-and-reply message in unattended mode when the TRME option was turned on.
LG *ELISE ERROR DUE TO R-AND-R MSG IN UNATTENDED MODE
LG $AMS-ACTN$ AMS AUTO-ACTION FAILED - INFORMATION FOLLOWS
An error occurred when CP-AMS attempted to perform an action. This message is displayed when a text substitution attempt has failed, when the result of text substitution is invalid, or when certain other errors are detected for the associated action. An alarm is sent to each instance of OS 2200 Console View connected to this console and an alert event report is sent to Operations Sentinel. CP-AMS continues to process any valid remaining actions associated with the matching pattern. This message is always followed by the $AMS-MTCH$, $AMS-MSG $, $AMS-ERR $, $AMS-action$ message sequence.
Example
In this example, assuming standard delimiters (spaces), the highlight action failed when token 4, RING, was substituted into the action text as a highlight identifier.
LG $AMS-ACTN$ AMS AUTO-ACTION FAILED - INFORMATION FOLLOWS LG $AMS-MTCH$ GROUP = ’LOAD’, NBR = 1 LG $AMS-MSG $ LOAD SAVE01 TA0 RING OBACKUP1 - 1 SAVALL LG $AMS-ERR $ INVALID HIGHLIGHT LG $AMS-HILT$ \_TOKEN4\
LG $AMS-ACTV$ database
where database is the ACTIVATE action text. The text is retrieved from the associated action corresponding to the current system operating mode.
Identifies the database name that would have been activated. This message is issued if the OM keyin DBUG option is ON, if the action resulted from a match of a pattern marked as TEST, or if the database name generated by substitution is invalid.
Example
LGF$AMS-ACTV$FSAMPLE
LG $AMS-ALRM$ alarm-id
where alarm-id is the alarm action text. If the action results from a database match, the text is retrieved from the associated action corresponding to the current system operating mode. Otherwise, the text corresponds to any system default actions that would have been taken.
The alarm-id is used as the alert-id in the alert event report sent to Operations Sentinel. This message is issued if the OM keyin DBUG option is ON, the action resulted from a match of a pattern marked as TEST, or the alarm-id generated by substitution is invalid.
Example
LG $AMS-ALRM$ 13
LG $AMS-ANSR$ text
where text is the answer action response text. The response number indicator is not included. The response text is truncated at 50 characters because of input limitations of the LG command. If the action results from a pattern match, the text is retrieved from the pattern action corresponding to the current system operating mode.
Identifies the answer to an outstanding read-and-reply message that would have been sent to the host. This message is issued if the OM keyin DBUG option is ON, if the action resulted from a match of a pattern marked as TEST, or if the command text generated by substitution is invalid.
Examples
The first example is an error example; it does not have a read-and-reply number. The second example is a debug example and includes the read-and-reply number.
LGF$AMS-ANSR$FGO LGF$AMS-ANSR$F0FGO LG $AMS-CMD $ text
where text is the command action text. The action text is truncated at 50 characters because of input limitations of the LG command. If the action results from a pattern match, the text is retrieved from the pattern action corresponding to the current system operating mode. Otherwise, the text corresponds to any default action that would have been taken.
Identifies an unsolicited command that would have been sent to the host. This message is issued if the OM keyin DBUG option is ON, the action resulted from a match of a pattern marked as TEST, or the command text generated by substitution is invalid.
Examples
Note that the second example is truncated after 50 characters (that is, USERID is truncated to USE).
LG $AMS-CMD $ RC CMS
LG $AMS-CMD $ ST,P QUALIFIER*FILENAME.ELEMENT,,RUNID,ACCOUNT/USE
LG $AMS-CREA$ variable-group:target
where:
variable-group
is the name of the variable group to which the member belongs.
target
is the variable or fixed text that contains the name of the member that is to be created.
variable-group:target is retrieved from the CREATE action.
Identifies the target used to create a member in a variable group. This message is issued if the OM keyin DEBUG option is ON, the CREATE resulted from a match of a pattern marked TEST, or the target is invalid. It is followed by an $AMS-MBR $ message, which identifies the member to be created.
Examples
LGF$AMS-CREA$FRUNS:_RUNID LGF$AMS-MBRF$FCMSA F LGF$AMS-CREA$FRUNS:"CMSA" LGF$AMS-MBRF$FCMSA LG $AMS-DACT$
Indicates that the currently active database would have been deactivated. This message is issued if the OM keyin DBUG option is ON or the action resulted from a match of a pattern marked as TEST.
Example
LG $AMS-DACT$
LG $AMS-DB $ ACTIVATION OF db-name ATTEMPTED BY requester
where:
db-name
is the name of a database that could not be read.
requester
is the entity requesting the database activation. Requesters can be
computer.user
DATABASE database-name
INITIALIZATION
AMS RECOVERY
An attempt to activate a new database failed. This message is always followed by a message explaining the reason for the failure and a second message explaining the current state of the AMS database. A corresponding error message is written to the system console error log file. AMS will attempt to continue operation using the previously active database (if any).
Examples
LG $AMS-DB $ ACTIVATION OF S2 ATTEMPTED BY DATABASE B2
LG $AMS-ERR $ DATABASE S2 DOES NOT EXIST
LG $AMS-DB $ DATABASE SHIFT1 REMAINS ACTIVE
LG $AMS-DB $ ACTIVATION OF A1 ATTEMPTED BY WS2.Shift1
LG $AMS-ERR $ DATABASE A1 COULD NOT BE READ
LG $AMS-DB $ NO DATABASE ACTIVE
LG $AMS-DB $ DATABASE db-name ACTIVATED BY AMS INITIALIZATION
where db-name is the name of the active database.
AMS was initialized with the database currently marked as active. All console messages processed after this point use the indicated database for pattern matching.
Example
LG $AMS-DB $ DATABASE S1 ACTIVATED BY AMS INITIALIZATION
LG $AMS-DB $ DATABASE db-name ACTIVATED BY computer.user
where:
db-name
is the name of the active database.
computer
is the name of the Operations Sentinel workstation where OS 2200 Console View is executing.
user
is the name of the user that started OS 2200 Console View.
A new database was activated because of an activate request from OS 2200 Console View and RADB (Reactivate AMS Database). All console messages processed after this point use the indicated database for pattern matching.
Example
LG $AMS-DB $ DATABASE SHIFT1 ACTIVATED BY SPOWRK1.Oper LG $AMS-DB $ DATABASE db-name1 ACTIVATED BY DATABASE db-name2
where:
db-name1
is the name of the currently active database.
db-name2
is the name of the previously active database containing the activate action.
A new database was activated because of an activate action in the previously active database. All console messages processed after this point use the indicated database for pattern matching.
Example
LG $AMS-DB $ DATABASE RUN1 ACTIVATED BY DATABASE BOOT1 LG $AMS-DB $ DATABASE db-name DEACTIVATED BY computer.user
where:
db-name
is the name of the deactivated database.
computer
is the name of the Operations Sentinel workstation where OS 2200 Console View is executing.
user
is the name of the user that started OS 2200 Console View.
The active database was deactivated because of a deactivate request from OS 2200 Console View. No pattern matching is performed subsequent to this, but default actions and OM keyin options are still available.
Example
LG $AMS-DB $ DATABASE B1 DEACTIVATED BY DATABASE ACTION LG $AMS-DB $ DATABASE db-name DEACTIVATED DUE TO INTERNAL ERROR
where db-name is the name of the deactivated database.
The active database was deactivated because of a deactivate action. No pattern matching is performed subsequent to this, but default actions and OM keyin options are still available.
Example
LGF$AMS-DB $ DATABASE S1 DEACTIVATED DUE TO INTERNAL ERROR
LG $AMS-DB $ DATABASE db-name REMAINS ACTIVE
where db-name is the name of the deactivated database.
AMS detected a run-time internal database error and automatically deactivated the active database. This database should be checked for corruption and restored from a backup copy if necessary. An alarm is sent to each instance of OS 2200 Console View connected to this console and an alert event report sent to Operations Sentinel. AMS attempts to continue operation without a database. No pattern matching is performed subsequent to this, but default actions and OM keyin options are still available.
Example
LG $AMS-DB $ DATABASE S1 DEACTIVATED DUE TO INTERNAL ERROR LG $AMS-DB $ DATABASE db-name REMAINS ACTIVE
where db-name is the name of the recovered active database.
An attempt to activate a new database failed and the previously active database was reactivated. All console messages processed after this point continue to use the indicated database for any pattern matching that is performed. This message is always preceded by a database activation failure message.
Example
LG $AMS-ERR $ DATABASE SHIFT2 DOES NOT EXIST LG $AMS-DB $ DATABASE SHIFT1 REMAINS ACTIVE LG $AMS-DB $ NO DATABASE ACTIVE
CP-AMS was initialized with no database marked as active, a database activation request failed with no previously active database, or CP-AMS automatically deactivated a database because of an internal database error. No pattern matching is performed subsequently, but default actions and OM keyin options are still available.
Example
LG $AMS-DB $ NO DATABASE ACTIVE LG $AMS-DB $ REACTIVATE REQUEST FOR <database name>BY <computer name>.<user name>
where:
<database name>
is the name of database to reactivate
<computer name>
is the name of system where request was sent from
<user name >
is the name of the user that initiated the request
Indicates the start of processing a database reactivate request.
LG $AMS-DB $ REACTIVATE COMPLETED SUCCESSFULLY
The CP-AMS database has successfully completed the activation request.
Example
LG $AMS-DB $ REACTIVATE REQUEST FOR MYDB BY MYPC.MYUSER
LG $AMS-DB $ DATABASE MYDB ACTIVATED BY MYPC.MYUSER
LG $AMS-DB $ REACTIVATE COMPLETED SUCCESSFULLY
LG $AMS-DB $ REACTIVATE IGNORED - DATABASE
<database name> IS NOT ACTIVE
The database name specified by the reactivate request is not the active database. This message is also logged when no database is active.
Example
LG $AMS-DB $ REACTIVATE REQUEST FOR MYDB BY MYPC.MYUSER LG $AMS-DB $ REACTIVATE IGNORED - DATABASE MYDB IS NOT ACTIVE LG $AMS-DB $ REACTIVATE COMPLETED WITH ERRORS
An error occurred while activating the database.
Example
LG $AMS-DB $ REACTIVATE REQUEST FOR MYDB BY MYPC.MYUSER
LG $AMS-DB $ ACTIVATION OF MYDB ATTEMPTED BY MYPC.MYUSER
LG $AMS-ERR $ MYDB IS NOT A VALID AMS DATABASE
LG $AMS-DB $ ACTIVATION OF MYDB ATTEMPTED BY AMS RECOVERY
LG $AMS-ERR $ MYDB IS NOT A VALID AMS DATABASE
LG $AMS-DB $ NO DATABASE ACTIVE
LG $AMS-DB $ REACTIVATE COMPLETED WITH ERRORS
LG $AMS-DEST$ variable-group:target
where:
variable-group
is the name of the variable group to which the member belongs.
target
is a variable or fixed text that identifies the name of the member to be destroyed, or _ALL to identify that all members are to be destroyed.
variable-group:target is retrieved from the DESTROY action.
Identifies the member (or all members) of the variable group to be destroyed. This message is issued if the OM keyin DEBUG option is ON, the DESTROY resulted from a match of a pattern marked "TEST", or the target is invalid. It is followed by an $AMS-MBR $ message, which identifies the member to be destroyed.
Examples
LG $AMS-DEST$ RUNS:_RUNID LG $AMS-MBR $ CMSA LG $AMS-DEST$ RUNS:"CMSA" LG $AMS-MBR $ CMSA LG $AMS-DFLT$
Indicates a console message met some conditions that caused AMS to generate default actions. Default actions are those that occur when a message does not match a database pattern. Such actions include ringing an alarm when a read-and-reply message occurs in casual or unattended mode. This message is generated only if the OM keyin DBUG option is ON.
Example
LGF$AMS-DFLT$
LG $AMS-DISP$ text
where text is the supplemental display action text. The display text is truncated at 50 characters because of input limitations of the LG command. Also, because of the limitations of the host input format, the display text used in the LG command is the uppercase version of the text stored in the database.
Identifies the supplemental text associated with the matched message that would have displayed on the system operation screen. This message is issued if the OM keyin DBUG option is ON, the action resulted from a match of a pattern marked as TEST, or text substitution failed.
Example
LG $AMS-DISP$ valid responses are LG $AMS-DISP$ A Retry or continue the process. LG $AMS-DISP$ E Confirm error; stop process. LG $AMS-DISP$ Q Stop printing and requeue the curre LG $AMS-DISP$ T Stop the process.
Note that the Q line is truncated after 50 characters.
LG $AMS-ELIF$level$ expression
where:
level
is the depth of conditional nesting.
expression
is the expression that is evaluated. The expression is retrieved from the ELSEIF of a conditional construction.
Identifies the expression evaluated for an ELSEIF command. This message is issued if the OM keyin DBUG option is ON, the ELSEIF resulted from a match of a pattern marked TEST, or the expression is in error. It is followed by a $AMS-RSLT$ message which identifies the result of the evaluated expression or a $AMS-OPRD$ message with the operand in error if an error occurred while evaluating the expression.
Example
LG $AMS-ELIF$2$ ERROR_COUNT = 4
LG $AMS-RSLT$2$ 1
LG $AMS-ELSE$level$
where level is the depth of conditional nesting.
Identifies that an ELSE command is executed. This message is issued if the OM keyin DBUG option is ON or the ELSE resulted from a match of a pattern marked TEST.
Example
LG $AMS-ELSE$1$ LG $AMS-ENDI$level$
where level is the depth of conditional nesting.
Indicates that an ENDIF command is executed. This message is issued if the OM keyin DBUG option is ON or the ENDIF resulted from a match of a pattern marked TEST.
Example
LGF$AMS-ENDI$1$ LG $AMS-ERR $ ACTION NOT ALLOWED ACTIVATE/DEACTIVATE IN PROGRESS
An AMS database activation or deactivation internal message matched a pattern in the database and the action that follows cannot be executed during an activate or deactivate. This message is followed by a message indicating the action that is not allowed.
Example
LG $AMS-ERR $ ACTION NOT ALLOWED ACTIVATE/DEACTIVATE IN PROGRESS LG $AMS-DISP$ Starting Weekend Operations LG $AMS-ERR $ ACTION NOT ALLOWED NO VISIBLE MESSAGE
A hold or read-and-reply release internal message matched a pattern in the database and the action that follows cannot be executed because these messages are not sent to the OS 220 Console View. This message is followed by a message indicating the action that is not allowed.
Example
LG $AMS-ERR $ ACTION NOT ALLOWED NO VISIBLE MESSAGE LG $AMS-DISP$ Starting Weekend Operations LG $AMS-ERR $ ACTION TOO LONG DUE TO TEXT SUBSTITUTION
The resulting action from a text substitution contained more characters than the maximum allowed for that action. The maximum number of characters allowed for action text depends on the type of action.
Example
LG $AMS-ERR $ ACTION TOO LONG DUE TO TEXT SUBSTITUTIONLG LG $AMS-ACTV$ SHIFT\_TOKEN3\ LG $AMS-ERR $ CANNOT ACCESS ACTIVATION FOLDER
CP-AMS cannot activate the database because the database activation folder does not exist and cannot be created. Databases are copied to this folder during activation. This error indicates a problem with the registry entry HKLM\Software\ Operations Sentinel \x.y.z\Voyager\Vsop\os2200-inuse or HKLM\Software\ Operations Sentinel \x.y.z\DataLocation, or there is a problem with the installation-data-folder \os2200-inuse folder. This message is always followed by a message explaining the current CP-AMS database state.
Example
LG $AMS-DB $ ACTIVATION OF TEST ATTEMPTED BY AMS INITIALIZATION LG $AMS-ERR $ CANNOT ACCESS ACTIVATION FOLDER LG $AMS-DB $ NO DATABASE ACTIVE
LG $AMS-ERR $ CANNOT CONVERT NON-NUMERIC CHARACTERS TO INTEGER
While evaluating an expression, an attempt was made to convert a string that contained nonnumeric characters to an integer value. If the expression is part of an IF or ELSEIF command, the result of the expression is false and processing proceeds to the next ELSEIF, ELSE, or ENDIF command. If the expression is part of a SET action, the variable or member of a variable group is left unchanged. This message is followed by the action being processed and an $AMS-OPRD$ message with the operand in error.
Examples
LG $AMS-ERR $1$ CANNOT CONVERT NON-NUMERIC CHARACTERS TO INTEGER LG $AMS-IF $1$ #"\_TOKEN4 [3,4]\" = 24 LG $AMS-OPRD$1$ "\_TOKEN4 [3,4]\"
LG $AMS-ERR $ CANNOT CONVERT NON-NUMERIC CHARACTERS TO INTEGER LG $AMS-SET $ b = a + #_NEGTOKEN2LG $AMS-OPRD$ _NEGTOKEN2
LG $AMS-ERR $ CANNOT COPY DATABASE db-name TO ACTIVATION FOLDER
where db-name is the name of the database that could not be activated.
CP-AMS cannot activate the database because the database file could not be copied into the database activation folder. This error indicates a problem with the installation-data-folder \os2200-inuse\ server.partition.console folder.
where:
server
is the name of the ClearPath Enterprise Systems server.
partition
is the name of an OS 2200 partition on the server.
console
is the name of one of the partition's consoles.
This message is always followed by a message explaining the current database state.
Examples
LG $AMS-DB $ ACTIVATION OF TEST ATTEMPTED BY AMS INITIALIZATION LG $AMS-ERR $ CANNOT COPY DATABASE TEST TO ACTIVATION FOLDER LG $AMS-DB $ NO DATABASE ACTIVE
LG $AMS-DB $ ACTIVATION OF SHIFT2 ATTEMPTED BY AMS INITIALIZATION LG $AMS-ERR $ CANNOT COPY DATABASE SHIFT2 TO ACTIVATION FOLDER LG $AMS-DB $ DATABASE SHIFT1 REMAINS ACTIVE
LG $AMS-ERR $ CHARACTER POSITION SUBSTITUTION OUT OF RANGE
An action text string contained a reference to a starting character position that does not exist in the generated insertion text. This error can only occur when character position extraction is used within a substitution sequence. Check the action for the correct character position reference. Check the subtoken substitution delimiter list, set, and subtoken substitution number if specified. Also check the message and pattern to determine if the pattern was intended to match that message.
Example
LG $AMS-ERR $ CHARACTER POSITION SUBSTITUTION OUT OF RANGE LG $AMS-CMD $ RV \_TOKEN4[8,14]\ LG $AMS-ERR $ COULD NOT ACCESS EXECUTE SCRIPT
The script name specified for an execute or a transparent execute action identifies a file on the Operations Server mass storage that is corrupted or could not be accessed for an unknown reason. The file must be accessible for proper CP-AMS execution. This error can occur when there are system problems or when software installed on the Operations Server has been corrupted.
Example
LG $AMS-ERR $ COULD NOT ACCESS EXECUTE SCRIPT
LG $AMS-TEXE$ SCRIPT1
LG $AMS-ERR $ DATABASE db-name COULD NOT BE READ
where db-name is the name of the database that could not be read.
An attempt to activate a new database failed because a system I/O error occurred while reading the database. The mass storage version of the database has been corrupted, and the database should be restored from a backup copy. This message is always followed by a message explaining the current database state.
Examples
LG $AMS-ERR $ DATABASE SHIFT2 DOES NOT EXIST LG $AMS-DB $ DATABASE SHIFT1 REMAINS ACTIVE LG $AMS-ERR $ DATABASE SHIFT2 DOES NOT EXIST LG $AMS-DB $ NO DATABASE ACTIVE LG $AMS-ERR $ DEACTIVATION MESSAGE MATCHING FAILED
A serious error occurred while attempting to match the database deactivation internal message. This error indicates corruption of the database or a software problem. The database is then deactivated. If this deactivation was part of activating another database, CP-AMS attempts to activate the new database. Note that the values of all variables are lost.
Examples
LG $AMS-ERR $ DEACTIVATION MESSAGE MATCHING FAILED LG $AMS-DB $ DATABASE DB1 DEACTIVATED BY DATABASE ACTION
LG $AMS-ERR $ DEACTIVATION MESSAGE MATCHING FAILED LG $AMS-DB $ DATABASE DB2 ACTIVATED BY DATABASE ABC
LG $AMS-ERR $ DIVIDE BY ZERO
While evaluating an expression, an attempt was made to divide by zero. If the expression is part of an IF or ELSEIF command, the result of the expression is false and processing proceeds to the next ELSEIF, ELSE, or ENDIF command. If the expression is part of a SET action, the variable or member of a variable group is left unchanged. This message is followed by the action being processed and an $AMS-OPRD$ message with the operand in error.
Examples
LG $AMS-ERR $1$ DIVIDE BY ZERO LG $AMS-IF $1$ 1 + 2 / A LG $AMS-OPRD$1$ A LG $AMS-ERR $ DIVIDE BY ZERO LG $AMS-SET $ b = 1 + 2 / A LG $AMS-OPRD$ A LG $AMS-ERR $ EXECUTE SCRIPT COULD NOT BE READ
An OS 2200 Console View macro name specified in an EXECUTE or a TEXECUTE action identifies a file on the Operations Server mass storage that cannot be read. The file must be readable for proper CP-AMS execution.
Example
LG $AMS-ERR $ EXECUTE SCRIPT COULD NOT BE READ LG $AMS-TEXE$ SCRIPT1 LG $AMS-ERR $ EXECUTE SCRIPT DOES NOT EXIST
An OS 2200 Console View macro name specified in an EXECUTE or TEXECUTE action identifies a file on the Operations Server mass storage that does not exist.
Example
LG $AMS-ERR $ EXECUTE SCRIPT DOES NOT EXIST LG $AMS-TEXE$ SCRIPT1 LG $AMS-ERR $ HOST IS NOT ACCEPTING INPUT FROM THIS CONSOLE
CP-AMS could not perform the action because the Exec is not ready for console commands or for a response to a read-and-reply message. The Exec is in this state early in the system boot process. During this time, CP-AMS can match messages and perform any actions except ANSWER, COMMAND, and RESPONSE actions.
This message, and the other messages associated with it, are displayed only on the console screen and are not placed in the system log.
Example
LG $AMS-ERR $ HOST IS NOT ACCEPTING INPUT FROM THIS CONSOLE LG $AMS-CMD $ AT LOG SW L1
Messages Resulting from Invalid Substitution
Error messages can occur while attempting text substitution at run time. These error messages are immediately followed by an action specification message that contains the original (that is, unsubstituted) action text associated with the attempted action.
The following messages are the result of invalid substitution.
LG $AMS-ERR $ INTERNAL SUBSTITUTION ERROR - error-code
where error-code is the unexpected value returned.
An internal error occurred when an unexpected error code was returned from the text substitution routine.
Example
LG $AMS-ERR $ INTERNAL SUBSTITUTION ERROR - -6 LG $AMS-ACTV$ SHIFT\_TOKEN3\
LG $AMS-ERR $ INVALID ALARM-ID
An invalid alarm identifier was generated for an alarm action. A valid alarm identifier is 1 or 2 digits, with a value less than 34. This error occurs when an improper message token is substituted into an alarm -id.
Example
LG $AMS-ERR $ INVALID ALARM-ID LG $AMS-ALRM$ 1A
LG $AMS-ERR $ INVALID AMS DATABASE NAME
An invalid AMS database name was generated for an activate action. A valid CP-AMS database name is 1 to 255 characters, and cannot include slashes, backslashes, colons, asterisks, question marks, double quotes, les than symbols, greater than symbols, and vertical bars. SMART AMS database names are 1 to 8 alphanumeric characters and hyphens.
This error occurs when an improper message token is substituted into a database name specification.
Example
LG $AMS-ERR $ INVALID AMS DATABASE NAME LG $AMS-ACTV$ SHIFT#2 LG $AMS-ERR $ INVALID ATTRIBUTE VALUE PAIR FORMAT
At least one invalid attribute value pair (AVP) was generated for an event report action. Event reports consist of a series of AVPs separated by AVP separators (³). AVPs have the format:
attribute-name = attribute-value
where:
attribute-name
is the name of the attribute to which attribute-value is applied.
=
is the AVP assignment character.
attribute-value
is the value to be assigned to attribute-name. This field is optional. If it is omitted, the null string is assigned to attribute-name.
This error occurs when an AVP is missing the attribute-name, the AVP assignment character, or both.
Example
LG $AMS-ERR $ INVALID ATTRIBUTE VALUE PAIR FORMAT LG $AMS-EVRT$ TYPE=AC | CLASS | INSTANCE LG $AMS-ERR $ INVALID HIGHLIGHT
An invalid highlight identifier was generated for a highlight action. Valid highlight identifiers are GREEN, RED, WHITE, YELLOW, COLOR1, COLOR2, COLOR3, and COLOR4. This error occurs when an improper message token is substituted into a highlight specification.
Example
LG $AMS-ERR $ INVALID HIGHLIGHT LG $AMS-HILT$ BLACK LG $AMS-ERR $ INVALID HOLD-ID
An invalid hold identifier was generated for a hold or release action. A valid hold identifier is 1 to 12 printable ASCII characters excluding backslashes and embedded spaces. This error occurs when an improper message token is substituted into a hold‑id.
Example
LG $AMS-ERR $ INVALID HOLD-ID LG $AMS-HOLD$ LOAD XYZ TA0
LG $AMS-ERR $ INVALID RRID SUBSTITUTION FOR NON READ-REPLY
Read-and-reply identifier substitution was specified in one of the actions for a pattern that matched a read-only or read-alert message. This is an internal error that should not occur, and it indicates possible database corruption.
Example
LG $AMS-ERR $ INVALID RRID SUBSTITUTION FOR NON READ-REPLY LG $AMS-CMD $ AMS*DATA LI001 \_RRID\ LG $AMS-ERR $ INVALID SCRIPT NAME
An invalid OS 2200 Console View macro name was generated for an execute or a transparent execute action. This error occurs when an improper message token is substituted into an execute or transparent execute command.
Example
LG $AMS-ERR $ INVALID SCRIPT NAME LG $AMS-TEXE$ My:Macro* LG $AMS-ERR $ INVALID SUBSTITUTION SEQUENCE
An invalid substitution sequence was found in the AMS database. This is an internal error that should never occur. Database corruption is possible.
Example
LG $AMS-ERR $ INVALID SUBSTITUTION SEQUENCE LG $AMS-CMD $ ST \FILE\ LG $AMS-ERR $ db-name IS NOT A VALID AMS DATABASE
where db-name is the name of the invalid database.
An attempt to activate a new database failed because the named file did not contain a valid CP-AMS or SMART AMS database header. The mass storage copy of the database on the Operations Server or the Operations Sentinel server may have been corrupted. The database should be restored from a backup copy.
This message is always followed by a message explaining the current CP-AMS database state.
Examples
LG $AMS-ERR $ SHIFT2 IS NOT A VALID AMS DATABASE LG $AMS-DB $ DATABASE SHIFT1 REMAINS ACTIVE
LG $AMS-ERR $ SHIFT2 IS NOT A VALID AMS DATABASE LG $AMS-DB $ NO DATABASE ACTIVE
LG $AMS-ERR $ rrid IS NOT A VALID RRID
The token inserted into the response number indicator (\rridno\-) is not a valid read-and-reply identifier, or a hyphen did not follow the \rridno\. A valid read-and-reply identifier consists of 8 digits (assigned to each read-and-reply message by the system console).
Examples
LG $AMS-ERR $ LS001 IS NOT A VALID RRID LG $AMS-ANSR$ GO
LG $AMS-ERR $ 12334455678 IS NOT A VALID RRID LG $AMS-ANSR$ GO
LG $AMS-ERR $ 10010547GO IS NOT A VALID RRID LG $AMS-ANSR$ 10010547GO
LG $AMS-ERR $ MISSING REQUIRED ATTRIBUTE VALUE PAIR
At least one required attribute value pair (AVP) was missing from an event report action. Event reports consist of a series of AVPs separated by AVP separators (³).
The first three AVPs in all event reports must be
TYPE = er-type | CLASS = class | INSTANCE = instance
This order is important. This error occurs if any of the three required AVPs is missing, misspelled, or out of order.
Example
LG $AMS-ERR $ MISSING REQUIRED ATTRIBUTE VALUE PAIR LG $AMS-EVRT$ TYPE=LG | CLASS=2200_HOST
LG $AMS-ERR $ NO READ-AND-REPLY ASSOCIATED WITH COMMAND RESPONSE
An attempt was made to respond to a read-and-reply message that did not exist. The error is caused by a command action or transparent command action whose response number does not correspond to any outstanding read-and-reply message on the console. This message is followed by a message showing the command action.
Example
LG $AMS-ERR $ NO READ-AND-REPLY ASSOCIATED WITH COMMAND RESPONSE LGS $AMS-CMD$ 1 GO LG $AMS-ERR $ RESPONSE FOR NON-READ-AND-REPLY MESSAGE
A read-only or read-alert message matched a pattern that has a response action. This is an internal error that should not occur, and it indicates possible database corruption.
Example
LG $AMS-ERR $ RESPONSE FOR NON-READ-AND-REPLY MESSAGE LG $AMS-RSPN$ GO
LG $AMS-ERR $ RRID SUBSTITUTION FOR ANSWERED READ-AND-REPLY
A pattern with an action using read-and-reply identifier substitution (\_RRID\) matched a read-and-reply message that is no longer outstanding, so the rrid of the message is no longer available.
Example
LG $AMS-ERR $ RRID SUBSTITUTION FOR ANSWERED READ-AND-REPLY LG $AMS-CMD $ AMS*DATA LI001 \_RRID\ LG $AMS-ERR $ SUB-TOKEN SUBSTITUTION OUT OF RANGE
An action text string referred to a subtoken that did not exist. This error can only occur when a delimiter list or delimiter set is used within a substitution sequence. Check the action for the correct subtoken substitution delimiter list, delimiter set, and subtoken substitution number if specified. Also check the pattern to determine if the pattern was intended to match that message.
Example
LG $AMS-ERR $ SUB-TOKEN SUBSTITUTION OUT OF RANGE LG $AMS-CMD $ RV \_IMAGE " ///" 4\
LG $AMS-ERR $ TOKEN SUBSTITUTION OUT OF RANGE
An action text string referred to a message token that did not exist. This error can occur only when the matching pattern is nonstandard (that is, it contains a DELIMITERS command). Check the action for the correct token substitution number. Also check the message and pattern to determine if the pattern was intended to match that message.
Example
LG $AMS-ERR $ TOKEN SUBSTITUTION OUT OF RANGE LG $AMS-CMD $ RV \_TOKEN9\ LG $AMS-ERR $ VARIABLE GROUP DOES NOT HAVE ANY MEMBERS
The predefined variable _ALL was used to refer to all members in a variable group, but the group does not contain any members. This message is followed by a message indicating the action (DESTROY, RESET, or SET) that encountered the error.
Example
LG $AMS-ERR $ VARIABLE GROUP DOES NOT HAVE ANY MEMBERS LG $AMS-SET $ RUNS:_ALL = 0 LG $AMS-ERR $ VARIABLE GROUP MEMBER DOES NOT EXIST
When this message results from an IF or ELSEIF command, a reference was made to a variable group member that did not exist. Consequently, the result of the expression is false and processing proceeds to the next ELSEIF, ELSE, or ENDIF command. When this message results from a SET action, a reference was made (on the right side of the equal sign) to a variable group member that does not exist, and in addition, the variable group member is not the target of the expression. As a result of this error, the target is left unchanged. This message is followed by the action being processed and an $AMS-OPRD$ message with the operand in error.
Examples
LG $AMS-ERR $3$ VARIABLE GROUP MEMBER DOES NOT EXIST LG $AMS-IF $3$ RUNS:_RUNID > 5 & RUN_STATUS:_TOKEN4 = 2 LG $AMS-OPRD$3$ RUNS:_RUNID
LG $AMS-ERR $ VARIABLE GROUP MEMBER DOES NOT EXIST LG $AMS-SET $ RUN_COUNT = RUNS:_RUNID LG $AMS-OPRD$ RUNS:_RUNID
LG $AMS-EVRT$ text
where text is an event report to send to Operations Sentinel. The event report text is truncated at 50 characters because of input limitations of the LG command. Also because of limitations of the host input format, the event report text used in the LG command is an uppercase version of the text stored in the database and sent to Operations Sentinel.
Identifies the event report that would have been sent to Operations Sentinel. This message is issued if the OM keyin DBUG option is ON, the action resulted from a match of a pattern marked as TEST, or the event report generated by substitution is invalid.
Example
LG $AMS-EVRT$ TYPE=AC | CLASS=2200_HOST | INSTANCE=TEST | DATA_C
Note that DATA_COLLECTION=completed is truncated after 50 characters to DATA_C.
LG $AMS-EXE $ text
where text is the action text that is executed. The action text is truncated at 50 characters because of input limitations of the LG command. If the action results from a pattern match, the text is retrieved from the pattern action corresponding to the current system operating mode.
Identifies the OS 2200 Console View macro containing unsolicited commands that would have been sent to the host. This message is issued if the OM keyin DBUG option is ON, the action resulted from a match of a pattern marked TEST, or the macro name generated by substitution is invalid.
Example
LGF$AMS-EXEF$FSCRIPT100
LG $AMS-HILT$ highlight
where highlight is the highlight action text. The text is retrieved from the associated action corresponding to the current system operating mode.
Identifies the highlight color in which the matched message would have been displayed on the system operations session. This message is issued if the OM keyin DBUG option is ON, the action resulted from a match of a pattern marked as TEST, or the highlight generated by substitution is invalid.
Example
LG $AMS-HILT$ YELLOW
LG $AMS-HOLD$ [ hold-id ]
where hold-id is the hold-id action text if a hold-id was specified in the hold action; otherwise this value is omitted. The text is retrieved from the pattern action corresponding to the current system operating mode.
Indicates that the matched message would have been held on the system operations screen. It also identifies the hold-id (if present) that would have been attached to the held message. This message is issued if the OM keyin DBUG option is ON, the action resulted from a match of a pattern marked as TEST, or the hold-id generated by substitution is invalid.
Example
LGF$AMS-HOLD$FLOAD-MSG LG $AMS-IF $n$ expression
where:
n
is the level of conditional nesting.
expression
is the expression that is evaluated. The expression is retrieved from the IF command of a conditional construction.
Identifies the expression that is evaluated for the IF command. This message is issued if the OM keyin DBUG option is ON, the IF command resulted from a match of a pattern marked TEST, or the expression is in error. It is followed by either an $AMS-RSLT$ message, which identifies the result of the evaluated expression, or an $AMS-OPRD$ message, with the operand in error, if an error occurred while evaluating the expression.
Example
LG $AMS-IF $2$ ERROR_COUNT = 4 LG $AMS-RSLT$2$ 1 LG $AMS-INFO$ BLANKS SUBSTITUTED FOR NON-ASCII CHARACTERS
Informational message that precedes an $AMS-MSG $ or $AMS-DISP$ message that contained non-ASCII characters. The host system does not accept non-ASCII input although the system console can display non-ASCII output. Blanks are substituted for all non-ASCII characters in the matched message or supplemental display text before the LG command is sent to the host.
Examples
LG $AMS-INFO$ BLANKS SUBSTITUTED FOR NON-ASCII CHARACTERS LG $AMS-MSGF$ BERPR FEN DER DATEN BERTRAGUNG LG $AMS-INFO$ BLANKS SUBSTITUTED FOR NON-ASCII CHARACTERS LG $AMS-DISP$ BERPR FEN DER DATEN BERTRAGUNG ZWISCHEN LG $AMS-INFO$ TIME DELAYED ACTIONS DESTROYED
Indicates that AMS destroyed all timed delayed actions after the Systems Operations session lost its connection with the Exec. This message appears after the System Operations session regains its connection with the Exec. This message does not appear if the ClearPath OS 2200 logical console terminates and then re-starts.
Example
LG $AMS-INFO$ TIME DELAYED ACTIONS DESTROYED
LG $AMS-MBR $ member-name
where member-name is the name of a variable group member.
Identifies the target member of a variable group for a CREATE or a DESTROY action. It is also logged for a RESET or a SET action if the target is a variable group member reference. This message appears after a CREATE, DESTROY, RESET, or SET action message. The result is truncated at 50 characters because of input limitations of the LG command.
Example
LG $AMS-SET $ RUN_STATUS:_RUNID = STATUS_CODES:_TOKEN4 LG $AMS-MBR $ APP1 LG $AMS-RSLT$ APPLICATION FINISHED SUCCESSFULLY
LG $AMS-MSG $ text
where text is the console message text that matched a pattern in the database or that met default action criteria. The entire console message is not logged. Only the first 50 characters of the message portion used for pattern matching is logged. Note that the message response number and any attached run-id for privileged messages have been stripped off. If the message text contains data outside the normal ASCII range (greater than octal 177), this message is preceded by a $AMS-INFO$ message explaining that blanks were substituted for the non-ASCII characters.
Identifies the console message that caused AMS actions to be generated. The actions can be the result of a pattern match or the result of meeting default action conditions. This message is issued if the OM keyin DBUG option is ON, the action resulted from a match of a pattern marked as TEST, or the action text generated by substitution is invalid.
Examples
LG $AMS-MTCH$ GROUP = ’CMS’, NBR = 1 LG $AMS-MSG $ CMS ERROR FIN LG $AMS-DFLT$ LG $AMS-MSG $ A USER MESSAGE LG $AMS-INFO$ BLANKS SUBSTITUTED FOR NON-ASCII CHARACTERS LG $AMS-MSG $ BERPR FEN DER DATEN BERTRAGUNG LG $AMS-MTCH$ GROUP = ’group-name’, NBR = pattern-number
where:
group-name
is the name of the group containing the pattern that matched the console message.
Note: Because of the limitations of the host input format, the group-name inserted into the LG command is an uppercase version of the group-name stored in the database. Therefore, this parameter may not appear in the exact form required to perform a database lookup.
pattern-number
is the number of the pattern (within the group) that matched the console message.
Indicates that a console message matched a pattern in the AMS database. This message is issued if the OM keyin DBUG option is ON, a match occurred on a pattern entry marked as TEST, or an action generated by substitution is invalid. This message is always followed by an $AMS-MSG $ message.
Example
LG $AMS-MTCH$ GROUP = 'APPLICATION', NBR = 1234
LG $AMS-MSG $ THIS IS A MATCHING APPLICATION
LG $AMS-OPRD$ operand
where operand is an operand that caused an error in an expression; it is usually a variable, variable group, or substitution reference.
Identifies the operand in an expression that caused an error in an expression for an IF, ELSEIF, or SET action. It follows an IF, ELSEIF, or SET message. The result is truncated at 50 characters because of input limitations of the LG command.
Examples
LG $AMS-ERR $3$ VARIABLE GROUP MEMBER DOES NOT EXIST LG $AMS-IF $3$ RUNS:_RUNID > 5 & RUN_STATUS:_TOKEN4 = 2 LG $AMS-OPRD$3$ RUNS:_RUNID
LG $AMS-ERR $ VARIABLE GROUP MEMBER DOES NOT EXIST LG $AMS-SET $ RUN_COUNT = RUNS:_RUNID LG $AMS-OPRD$ RUNS:_RUNID
LG $AMS-RELS$ hold-id
where hold-id is the hold-id action text. The text is retrieved from the pattern action corresponding to the current system operating mode.
Identifies the hold-id of the message that would have been released. This is issued if the OM keyin DBUG option is ON, the action resulted from a match of a pattern marked as TEST, or the hold-id generated by substitution is invalid.
Example
LGF$AMS-RELS$FLOAD-MSG
LG $AMS-RSET$ target
where target is a variable or a reference to a member of variable group.
Indicates the execution of a RESET action. This message is issued if the OM keyin DBUG option is ON, the DESTROY action resulted from a match of a pattern marked TEST, or the target is invalid. If target is a reference to a member of a variable group, it is followed by an $AMS-MBR $ message, which identifies the member to be created.
Examples
LG $AMS-RSET$ ERROR_COUNT LG $AMS-RSET$ RUNS:_RUNID LG $AMS-MBR $ APP1
LG $AMS-RSLT$ result
where result is the result of an expression.
Identifies the result of an expression for IF, ELSEIF, or SET actions. It follows an IF, ELSEIF, or SET message. The result is truncated at 50 characters because of input limitations of the LG command.
Examples
LG $AMS-IF $2$ 2 + 14 / A LG $AMS-RSLT$2$ 8
LG $AMS-SET $ RUN_STATUS:_RUNID = STATUS_CODES:_TOKEN4 LG $AMS-MBR $ APP1 LG $AMS-RSLT$ APPLICATION FINISHED SUCCESSFULLY
LG $AMS-RSPN$ n-text
where:
n
is the appropriate message response number.
text
is the response action text. The action text is truncated at 50 characters because of input limitations of the LG command. If the action results from a pattern match, the text is retrieved from the pattern action corresponding to the current system operating mode. Otherwise, the text corresponds to any system default actions that would have been taken.
Identifies the response number and text that would have been sent to the host. This message is issued if the OM keyin DBUG option is ON, the action resulted from a match of a pattern marked as TEST, or the response generated by substitution is invalid.
Example
LG $AMS-RSPN$ 0-A
LG $AMS-SET $ target = expression
where:
target
is a variable or variable group member reference.
expression
is the expression to evaluate.
Indicates execution of a SET action. This message is issued if the OM keyin DBUG option is ON, the SET action resulted from a match of a pattern marked TEST, or the target is invalid. If target is a reference to a member of a variable group, it is followed by an $AMS-MBR $ message, which identifies the member to be created.
Example
LG $AMS-SET $ RUN_STATUS:_RUNID = STATUS_CODES:_TOKEN4 LG $AMS-MBR $ APP1 LG $AMS-RSLT$ APPLICATION FINISHED SUCCESSFULLY LG $AMS-SPRS$
Indicates that the matched message would have been suppressed. This message is issued if the OM keyin DBUG option is ON or the action resulted from a match of a pattern marked as TEST.
Example
LG $AMS-SPRS$
LG $AMS-TCMD$ text
where text is the transparent command action text. The action text is truncated at 50 characters due to input limitations of the LG command. The text is retrieved from the pattern action corresponding to the current system operating mode.
Identifies the unsolicited transparent command that would have been sent to the host but would not appear in the OS 2200 Console View traffic pane. This message is issued if the OM keyin DBUG option is ON, the action resulted from a match of a pattern marked as TEST, or the command text generated through substitution is invalid.
Examples
LG $AMS-TCMD$ RC CMS
LG $AMS-TCMD$ ST,P QUALIFIER*FILENAME.ELEMENT,,RUNID,ACCOUNT/USE
Note that the second example is truncated after 50 characters (that is, USERID is truncated to USE).
LG $AMS-TEXE$ text
where text is the transparent execute action text. The action text is truncated at 50 characters because of input limitations of the LG command. The text is retrieved from the pattern action corresponding to the current system operating mode.
Identifies the OS 2200 Console View macro containing unsolicited transparent commands that would have been sent to the host but would not appear in the OS 2200 Console View traffic pane. This message is issued if the OM keyin DBUG option is ON, the action resulted from a match of a pattern marked TEST, or the macro name generated by substitution is invalid.
Example
LG $AMS-TEXE$ SCRIPT100 LG $AMS-TERM$ AMS TERMINATED, SEE PC ERROR LOG
An internal error was received somewhere within the CP-AMS system. It can be related to system resource problems or a problem with CP-AMS itself. An alarm is sent to each instance of OS 2200 Console View connected to this console and an alert event report is sent to Operations Sentinel. Further AMS processing is terminated until the system console is reinitialized.
Example
LG $AMS-TERM$ AMS TERMINATED, SEE CONSOLE LOG
LG $AMS-WAIT$ delay unit
where:
delay
is the number of seconds or minutes.
unit
is either SECONDS or MINUTES.
Indicates that an action would be delayed by the given number of minutes or seconds. The action is identified in a message immediately preceding this message.
Example
LG $AMS-CMD $ ST,P ABC*REPORT.WEEK,,ADMIN,1000
LG $AMS-WAIT$ 20 SECONDS
LG $AMS-WARN$ ACTION TOO LONG - ACTION TRUNCATED TO length
where length is the maximum number of characters allowed.
Indicates that the following action was truncated to the maximum length allowed and then executed. This warning can be generated for a DISPLAY, HOLD, or RELEASE action.
Example
LG $AMS-WARN$ ACTION TOO LONG - ACTION TRUNCATED TO 12 LG $AMS-HOLD$ AVERYLONGHOLDID
LG $AMS-WARN$ READ-AND-REPLY MESSAGE ALREADY ANSWERED
Indicates that the read-and-reply message for a response generated by an ANSWER or RESPONSE (timed delay) action is no longer outstanding, most likely because an operator has already responded to the message. The ANSWER or RESPONSE action that generated the response follows.
Example
LG $AMS-WARN$ READ-AND-REPLY MESSAGE ALREADY ANSWERED LG $AMS-ANSR$ G LG $AMS-WARN$ VARIABLE GROUP MEMBER DOES NOT EXIST
Indicates that the target of a DESTROY, RESET, or SET action does not exist. In the case of SET or RESET, the member is created in the variable group and assigned the appropriate value. In the case of DESTROY, no action is taken since the member does not exist. This message is followed by the action that caused the warning.
Example
LG $AMS-WARN$ VARIABLE GROUP MEMBER DOES NOT EXIST LG $AMS-SET $ RUNS:_RUNID = RUNS:_RUNID + 1 LG $AMS-MBR $ 3BJS LG $AMS-RSLT$ 1
LG $AMS-WARN$ VARIABLE GROUP MEMBER ALREADY EXISTS
Indicates that the target of a CREATE action already exists. The member of the variable group is not changed. This message is followed by the action that caused the warning.
Example
LG $AMS-WARN$ VARIABLE GROUP MEMBER ALREADY EXISTS LG $AMS-CREA$ RUNS:_RUNID LG $AMS-MBR $ 3BJS