REx Messages

Messages › REx Messages

REx Messages

RE0101

INCORRECT PARAMETER SPECIFIED P1=P2

Reason:

An incorrect keyword parameter was supplied to an internal procedure.

System Action:

The action is rejected.

User Action:

Contact your systems support representative.

RE0102

RULESET P1 LOADED

Reason:

The ruleset P1 has been successfully loaded.

System Action:

Eventview processes the rules in the ruleset.

User Action:

None.

RE0103

RULESET P1 ALREADY INCLUDED IN P2 - IGNORED

Reason:

The ruleset P2 was being loaded by EventView. During the processing of included rulesets, it was found that the ruleset P1 was already included. The additional include of the ruleset is ignored.

System Action:

The included ruleset is ignored this time and ruleset loading continues.

User Action:

None.

RE0104

RULESET P1 NOT ACTIVE

Reason:

An attempt was made to load a ruleset which had a ruleset status of INACTIVE.

System Action:

The named ruleset is not loaded. If the load was attempted because the ruleset was included in another ruleset, the load of the other ruleset continues.

User Action:

If you want the ruleset loaded, update the ruleset and change status to ACTIVE.

RE0105

RULESET HANDLER ALREADY RUNNING

Reason:

An attempt was made to start a ruleset handler for EventView, however the ruleset handler was already running.

System Action:

The new ruleset handler process ends.

User Action:

None.

RE0106

REGISTRATION FOR RULESET P1 FAILED, VARTABLE P2 ZFDBK= P3

Reason:

An attempt was made to load or unload the ruleset P1 and error on the registration vartable occured during a P2 action. The feedback code P3 indicates the nature of the error.

System Action:

Processing continues.

User Action:

Determine the cause of the error by examining the ZFDBK code, correct and retry.

RE0107

UNLOAD FAILED, GDB ZFDBK P1 ON P2

Reason:

An attempt was made to unload a ruleset P1 and a GDB error occurred during a P2 action. The feedback code P1 indicates the nature of the error.

System Action:

The load fails.

User Action:

Determine the cause of the error by examining the ZFDBK code, correct and retry.

RE0108

RULESET P1 INCLUDED BY RULESET P2

Reason:

The ruleset P1 has been loaded as a result of being included in ruleset P2.

System Action:

EventView processes the rules in the ruleset.

User Action:

None.

RE0109

RULESET P1 UNLOADED

Reason:

The ruleset P1 has been unloaded from the running system. This could be caused by the update of ruleset definitions.

System Action:

EventView no longer processes the rules in the ruleset.

User Action:

None.

RE0110

RULESET P1 IS NOT LOADED

Reason:

This message is issued in response to a query on EventView for the ruleset P1 which is not currently loaded.

System Action:

None.

User Action:

None.

RE0111

RULESET P1 DOES NOT EXIST

Reason:

An attempt was made to load a ruleset which is not defined.

System Action:

The named ruleset is not loaded. If the load was attempted because the ruleset was included in another ruleset, the load of the other ruleset continues.

User Action:

Correct the ruleset name.

RE0112

RULESET P1 ALREADY LOADED

Reason:

This message is issued when a ruleset is included in another ruleset, but the ruleset has already been loaded by another ruleset. For example, ruleset1 is being loaded, which includes ruleset2, which in turn includes ruleset1 again.

System Action:

The included ruleset is ignored this time and ruleset loading continues.

User Action:

Correct the include ruleset definition.

RE0113

RULESET ACTIVITY LOGGING STARTED

Reason:

The ruleset control options for the primary loaded ruleset indicate that activity logging should take place. Activity logging has started.

System Action:

The actions performed by EventView are logged.

User Action:

Activity logging increases the cost of running EventView. It is intended for use as a ruleset debugging facility. When the ruleset is running correctly you should turn off activity logging by updating the ruleset control options.

RE0114

RULESET ACTIVITY LOGGING STOPPED

Reason:

The ruleset control options for the primary loaded ruleset have been changed to indicate that activity logging should stop.

System Action:

The actions performed by EventView are no longer logged.

User Action:

None.

RE0115

EVENTVIEW IS NOT ACTIVE

Reason:

There is no EventView ruleset active. This is probably because the current system image does not name a ruleset to load.

System Action:

None.

User Action:

None.

RE0120

P1 RULE FOR P2 RESULTED IN P3

Reason:

This message indicates that a rule resulted in the action P3. The rule is indicated by P2 as follows: IACTION-name The named initial action GROUP-name The named message group rule TIMER-name The named timer rule msgid A message with this MSGID If P1 is (TEST) the action was not actually done because the ruleset control option 'Perform Action?' was set to no, or the 'Perform Action in Manual Mode?' field in the AUTOIDS parameter group was set to NO.
This message is part of eventview ruleset activity logging. Ruleset activity logging is controlled by a ruleset control option.

System Action:

None.

User Action:

None.

RE0121

P1 RULE FOR P2 SET EVENTVIEW VARIABLE: P3

Reason:

This message indicates that a rule resulted in an EventView variable being set to the value shown in P3. The rule is indicated by P2 as follows:
IACTION-name The named initial action
GROUP-name The named message group rule
TIMER-name The named timer rule
msgid A message with this MSGID
If P1 is (TEST) the action was not actually done because the ruleset control option 'Perform Action?' was set to no, or the 'Perform Action in Manual Mode?' field in the AUTOIDS parameter group was set to NO.
This message is part of eventview ruleset activity logging. Ruleset activity logging is controlled by a ruleset control option.

System Action:

None.

User Action:

None.

RE0122

P1 RULE FOR P2 ISSUED COMMAND: P3

Reason:

This message indicates that a rule resulted in the system command P3 being issued. The rule is indicated by P2 as follows:

IACTION-name: The named initial action
GROUP-name: The named message group rule
TIMER-name: The named timer rule
msgid: A message with this MSGID

If P1 is (TEST), the action was not actually done because the ruleset control option 'Perform Action?' was set to NO or the 'Perform Action in Manual Mode?' field in the AUTOIDS parameter group was set to NO.

This message is part of EventView ruleset activity logging. Ruleset activity logging is controlled by a ruleset control option.

System Action:

None.

User Action:

None.

RE0123

P1 RULE FOR P2 REPLIED: P3

Reason:

This message indicates that a rule resulted in the reply command P3 being issued. The rule is indicated by P2 as follows:
IACTION-name The named initial action
GROUP-name The named message group rule
TIMER-name The named timer rule
msgid A message with this MSGID
If P1 is (TEST) the action was not actually done because the ruleset control option 'Perform Action?' was set to no, or the 'Perform Action in Manual Mode?' field in the AUTOIDS parameter group was set to NO.
This message is part of eventview ruleset activity logging. Ruleset activity logging is controlled by a ruleset control option.

System Action:

None.

User Action:

None.

RE0124

P1 RULE FOR P2 ISSUED AUTOMATION COMMAND: P3

Reason:

This message indicates that a rule resulted in the automation command P3 being issued. The rule is indicated by P2 as follows:
IACTION-name The named initial action
GROUP- name The named message group rule
TIMER-name The named timer rule
msgid A message with this MSGID
If P1 is (TEST) the action was not actually done because the ruleset control option 'Perform Action?' was set to no, or the 'Perform Action in Manual Mode?' field in the AUTOIDS parameter group was set to NO.
This message is part of eventview ruleset activity logging. Ruleset activity logging is controlled by a ruleset control option.

System Action:

None.

User Action:

None.

RE0125

P1 RULE FOR P2 ISSUED MESSAGE: P3

Reason:

This message indicates that a rule resulted in the message P3 being issued as a WTO. The rule is indicated by P2 as follows:
IACTION-name The named initial action
GROUP- name The named message group rule
TIMER-name The named timer rule
msgid A message with this MSGID
If P1 is (TEST) the action was not actually done because the ruleset control option 'Perform Action?' was set to no, or the 'Perform Action in Manual Mode?' field in the AUTOIDS parameter group was set to NO.
This message is part of eventview ruleset activity logging. Ruleset activity logging is controlled by a ruleset control option.

System Action:

None.

User Action:

None.

RE0126

P1 RULE FOR P2 STARTED AUTOMATION PROCESS: P3

Reason:

This message indicates that a rule resulted in the automation process P3 being started. The rule is indicated by P2 as follows:
IACTION-name The named initial action
GROUP- name The named message group rule
TIMER-name The named timer rule
msgid A message with this MSGID
If P1 is (TEST) the action was not actually done because the ruleset control option 'Perform Action?' was set to no, or the 'Perform Action in Manual Mode?' field in the AUTOIDS parameter group was set to NO.
This message is part of eventview ruleset activity logging. Ruleset activity logging is controlled by a ruleset control option.

System Action:

None.

User Action:

None.

RE0127

P1 RULE FOR P2 ISSUED OCS COMMAND: P3

Reason:

This message indicates that a rule resulted in the P3 command being issued. The rule is indicated by P2 as follows:
IACTION-name The named initial action
GROUP-name The named message group rule
TIMER-name The named timer rule
msgid A message with this MSGID
If P1 is (TEST), the action was not actually done because the ruleset control option 'Perform Action?' was set to no, or the 'Perform Action in Manual Mode?' field in the AUTOIDS parameter group was set to NO.
This message is part of EventView ruleset activity logging. Ruleset activity logging is controlled by a ruleset control option.

System Action:

None.

User Action:

None.

RE0130

P1 RULE FOR P2 SET ATTRIBUTES: P3

Reason:

This message indicates that a rule resulted in the message attributes being altered to P3. The rule is indicated by P2 as follows:
IACTION-name The named initial action
GROUP- name The named message group rule
TIMER-name The named timer rule
msgid A message with this MSGID
If P1 is (TEST) the attributes were not actually altered because the ruleset control option 'Perform Message Modification?' was set to no, or the 'Perform Action in Manual Mode?' field in the AUTOIDS parameter group was set to NO.
This message is part of eventview ruleset activity logging. Ruleset activity logging is controlled by a ruleset control option.

System Action:

None.

User Action:

None.

RE0131

P1 RULE FOR P2 MODIFIED TEXT TO: P3

Reason:

This message indicates that a rule resulted in the message text being altered to P3. The rule is indicated by P2 as follows:
IACTION-name The named initial action
GROUP-name The named message group rule
TIMER-name The named timer rule
msgid A message with this MSGID
If P1 is (TEST) the message was not actually altered because the ruleset control option 'Perform Message Modification?' was set to no, or the 'Perform Action in Manual Mode?' field in the AUTOIDS parameter group was set to NO.
This message is part of eventview ruleset activity logging. Ruleset activity logging is controlled by a ruleset control option.

System Action:

None.

User Action:

None.

RE0132

P1 RULE FOR P2 SET ROUTE CODE TO: P3

Reason:

This message indicates that a rule resulted in the message route code being altered to P3. The rule is indicated by P2 as follows:
IACTION-name The named initial action
GROUP-name The named message group rule
TIMER-name The named timer rule
msgid A message with this MSGID
If P1 is (TEST) the route code was not actually altered because the ruleset control option 'Perform Message Modification?' was set to no, or the 'Perform Action in Manual Mode?' field in the AUTOIDS parameter group was set to NO.
This message is part of eventview ruleset activity logging. Ruleset activity logging is controlled by a ruleset control option.

System Action:

None.

User Action:

None.

RE0133

P1 RULE FOR P2 SET DESCRIPTOR CODE TO: P3

Reason:

This message indicates that a rule resulted in the message descriptor code being altered to P3. The rule is indicated by P2 as follows:
IACTION-name The named initial action
GROUP-name The named message group rule
TIMER-name The named timer rule
msgid A message with this MSGID
If P1 is (TEST) the descriptor code was not actually altered because the ruleset control option 'Perform Message Modification?' was set to no or the 'Perform Action in Manual Mode?' field in the AUTOIDS parameter group was set to NO.
This message is part of eventview ruleset activity logging. Ruleset activity logging is controlled by a ruleset control option.

System Action:

None.

User Action:

None.

RE0134

RULESET CONTROL OPTIONS FOR MESSAGE MODIFICATION & ACTIONS DISABLED

Reason:

The Perform Message Modification? and the Perform Action? EventView ruleset control options were disabled by the following:

- The global operation mode is MANUAL.

- The value in the Perform Action in Manual Mode? field of the AUTOIDS parameter group is NO.

System Action:

None.

User Action:

None.

RE3001

INCORRECT PARAMETER SPECIFIED P1= P2

Reason:

An incorrect keyword parameter was supplied to an internal procedure.

System Action:

The action is rejected.

User Action:

Contact your systems support representative.

RE3002

GDB ERROR, ZFDBK P1 ON P2 KEY= P3

Reason:

An attempt was made to load a rule and a GDB error occurred during a P2 action. The feedback code P1 indicates the nature of the error. The key value P3 indicates which record was being actioned.

System Action:

The load fails.

User Action:

Determine the cause of the error by examining the ZFDBK code, correct and retry.

RE3003

WARNING, IGNORING EXTENDED VALIDATION FOR RULEID= P1 BECAUSE P2= P3

Reason:

Some extended validation characteristics of a rule with id P1 were ignored because they are not supported. The value P3 is not supported for the field P2.

System Action:

Not all validation for the rule is done.

User Action:

Correct the rule definition.

RE3004

VARTABLE ERROR: ID= P1 ACTION= P2 ZFDBK= P3

Reason:

An unexpected error occured while a message rule was being loaded. The ID of the vartable is P1 The action which failed is P2 The ZFDBK code is P3

System Action:

The load of this rule fails.

User Action:

Determine the cause of the error by examining the ZFDBK code, correct and retry.

RE3005

GROUP RULE P1, RULESET P2, DROPPED - MORE THAN P3 MEMBERS

Reason:

The Group rule P1 in ruleset P2 was found to have too many members. The load process ignores the message group rule. The maximum number of members allowed in a group rule is P3.

System Action:

The group rule will not be processed.

User Action:

Correct the rule definitions.

RE3006

NO RULESETS LOADED

Reason:

An ACTION=DUMP display was requested for a message, but there are no EventView rulesets active.

System Action:

None.

User Action:

None.

RE3007

SEARCHING LOADED RULESETS FOR MESSAGE: P1

Reason:

An ACTION=DUMP display was requested for the message P1 and EventView is searching for rules which might be executed for that message.

System Action:

None.

User Action:

None.

RE3008

RULES WITH TEST TEXT: P1

Reason:

An ACTION=DUMP display was requested for a message and EventView has found rules with the test text P1 which match it. Rules with the test text P1 follow. Note: the test text has been truncated at the first wildcard character.

System Action:

None.

User Action:

None.

RE3009

**END** P1 RULE(S) FOUND

Reason:

An ACTION=DUMP display was requested for a message and EventView has found P1 rules which match the message.

System Action:

None.

User Action:

None.

RE3010

RULE ID P1, RANK P2

Reason:

An ACTION=DUMP display was requested for a message and EventView has found the rule with ID P1 which matches the message. The rule ID is an internal name for the rule. The rank value of the rule id P2, when comparing rules, the lowest rank value is the best.

System Action:

None.

User Action:

None.

RE3011

RULE VALIDATION: P1

Reason:

The rule named in the previous RE3010 message has the validation operations P1 Validation operations tell EventView how to check that a rule is valid for a message.

System Action:

None.

User Action:

None.

RE3012

RULE EXECUTED EVEN IF NOT BEST FIT

Reason:

The rule named in the previous RE3010 message will have its actions performed, even if it is not the best ranked rule.

System Action:

None.

User Action:

None.

RE3013

MESSAGE MODIFICATIONS:

Reason:

The rule named in the previous RE3010 message will cause the following modifications to the message.

System Action:

None.

User Action:

None.

RE3014

MESSAGE REPLACEMENT: P1

Reason:

The rule named in the previous RE3010 message will cause the message replacement: P1
P1 is a string of text operations which tell EventView how to generate the replacement text.

System Action:

None.

User Action:

None.

RE3015

MESSAGE THRESHOLD: P1

Reason:

The rule named in the previous RE3010 message has a threshold specified. This message details the threshold.

System Action:

None.

User Action:

None.

RE3016

ROUTECODE SET TO P1, DESCRIPTOR CODE SET TO P2

Reason:

The rule named in the previous RE3010 message specifies a change in route or descriptor codes.
P1 is the route code to be set (blank if unchanged)
P2 is the descrptor code to be set (blank if unchanged)

System Action:

None.

User Action:

None.

RE3017

ATTRIBUTE KEY P1, SETS ATTRIBUTES P2

Reason:

The rule named in the previous RE3010 message specifies a change in message attributes.
P1 is the key to the attibute table
P2 is the list of attributes set

System Action:

None.

User Action:

None.

RE3018

RULE ACTIONS:

Reason:

The rule named in the previous RE3010 message will cause the following actions to be performed.

System Action:

None.

User Action:

None.

RE3019

RULE IS IN GROUP P1, CORRELATOR ( P2), INTERVAL P3, OTHER MEMBERS:

Reason:

The rule named in the previous RE3010 message is a member of a message group rule P1 The group correlator is P2 . The lifetime of a group is
P3. Messages showing other members of the group follow.

System Action:

None.

User Action:

None.

RE3020

P1 RULE ID P2

Reason:

The group rule named in the previous RE3019 message contains the rule with test text P1 and an ID of P2.

System Action:

None.

User Action:

None.

RE3021

GROUP RULE ACTIONS:

Reason:

The group rule named in the previous RE3019 message will cause the following actions to be performed.

System Action:

None.

User Action:

None.

RE3022

MESSAGE REPLY: P1

Reason:

The rule being displayed results in a reply command being issued, as described by P1

System Action:

None.

User Action:

None.

RE3023

COMMAND: P1

Reason:

The rule being displayed results in a command being issued, as described by P1

System Action:

None.

User Action:

None.

RE3024

BEFORE OTHER ACTIONS SET VAR ZREV P1 TO P2

Reason:

The rule being displayed results in an EventView variable P1 being set to the value described by P2 The variable is set before other actions for the rule are performed.

System Action:

None.

User Action:

None.

RE3025

AFTER OTHER ACTIONS SET VAR ZREV P1 TO P2

Reason:

The rule being displayed results in an EventView variable P1 being set to the value P2 The variable is set after other actions for the rule are performed.

System Action:

None.

User Action:

None.

RE3026

OCS COMMAND: P1

Reason:

The rule being displayed results in the P1 command being issued.

System Action:

None.

User Action:

None.

RE3027

AUTOMATION PROCESS TO START: P1

Reason:

The rule being displayed results in the automation process P1 being started.

System Action:

None.

User Action:

None.

RE3028

AUTOMATION COMMAND: P1

Reason:

The rule being displayed results in the automation command P1 being executed.

System Action:

None.

User Action:

None.

RE3029

MESSAGE ISSUED: P1 WITH ROUTE CODE= P1 DESCRIPTOR CODE= P2

Reason:

The rule being displayed results in the WTO message P1 being issued with route code P1 descriptor code P2

System Action:

None.

User Action:

None.

RE3030

MESSAGE REPLY CMD: P1

Reason:

A rule results in the P1 reply command being issued. The command will be issued from the region rather than from the subsystem interface.

System Action:

None.

User Action:

None.

RE3031

SYSTEM COMMAND: P1

Reason:

A rule results in the P1 command being issued. The command will be issued from the region rather than from the subsystem interface.

System Action:

None.

User Action:

None.

RE6001

INCORRECT PARAMETER SPECIFIED P1= P2

Reason:

An incorrect keyword parameter was supplied to an internal procedure.

System Action:

The action is rejected.

User Action:

Contact your systems support representative.

UNKNOWN CLASS( P1)

Reason:

Class specified in the calling parameter is unknown to the system.

System Action:

The request is rejected.

User Action:

Contact System Administrator.

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the procedure.

System Action:

The request is rejected.

User Action:

Contact System Administrator.

P1 DOES NOT EXIST

Reason:

P1 specified is not known to the system.

System Action:

None.

User Action:

Create Ruleset Control Option before creating rules.

P1 COMPLETED

Reason:

P1 process specified has been completed.

System Action:

None.

User Action:

None.

INVALID COMMAND

Reason:

Command specified is not recognized by the system.

System Action:

The request is rejected.

User Action:

Specify a valid command.

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the service procedure.

System Action:

The request is rejected.

User Action:

Contact System Administrator.

REQUIRED FIELD/S NOT ENTERED

Reason:

Validation found no entry specified on mandatory field/s.

System Action:

The request is rejected.

User Action:

Specify entry on field/s in error.

NO P1 SPECIFIED

Reason:

Nothing to be done because P1 was not specified.

System Action:

The request is rejected.

User Action:

Specify P1 name before requesting an action for P1 .

CANNOT CREATE OBJECT ID

Reason:

Object ID required for processing cannot be created because of missing Ruleset name, class or ruleid in the calling parameters.

System Action:

The request is rejected.

User Action:

Contact System Administrator.

WARNING, THERE ARE P1 CORRELATED MESSAGE RULES TO THIS MESSAGE GROUP

Reason:

Only the first 10 correlated message rules can be displayed.

System Action:

None.

User Action:

None.

MESSAGE GROUP RULE( P1) DOES NOT EXIST FOR RULESET( P2)

Reason:

The Related Message Group P1 defined for this Message Rule does not exist under ruleset P2.

System Action:

The request is rejected.

User Action:

Create the required Message Group Rule P1 and save/file the Message Rule

VARTABLE( P1) WAS NOT ALLOCATED FOR THIS EVENTVIEW REGION

Reason:

The vartable identified by P1 has not been allocated.

System Action:

The current process continues.

User Action:

Contact your local support representative.

P1 DOES NOT EXIST

Reason:

P1 specified is not known to the system.

System Action:

None.

User Action:

Use '?' to select P1

REQUEST DENIED - USER P1 P2 THE MESSAGE LEARNING DATABASE

Reason:

The update request is rejected because userid P1 was previously P2 the Message Learning database. P2 will indicate whether the user was deleting or resetting the database.

System Action:

The request is rejected.

User Action:

Try again later.

UPDATE IN PROGRESS BY P1

Reason:

Update is in progress on this definition by other user.

System Action:

The request is rejected.

User Action:

Try again later.

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the procedure.

System Action:

The request is rejected.

User Action:

Contact System Administrator.

REQUIRED FIELD/S NOT ENTERED

Reason:

Validation found no entry specified on mandatory field/s.

System Action:

The request is rejected.

User Action:

Specify entry on field/s in error.

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the procedure.

System Action:

The request is rejected.

User Action:

Contact System Administrator.

VALUE NOT SELECTED FROM LIST

Reason:

No value selected from the selection list displayed.

System Action:

None.

User Action:

None.

MESSAGE TEXT MUST BE SUPPLIED

Reason:

Message Text is required and no value was entered in that field.

System Action:

The panel is redisplayed with the field(s) in error highlighted.

User Action:

Enter a valid value in the highlighted field(s).

INVALID P1 SPECIFIED

Reason:

Validation routine rejected the value of P1 specified.

System Action:

The panel is redisplayed with the field in error highlighted.

User Action:

Enter a valid value for P1 in the highlighted field.

VARIABLE NAME MUST BE SPECIFIED

Reason:

Validation routine rejected the value because no variable name specified

System Action:

The panel is redisplayed with the field in error highlighted.

User Action:

Enter a valid variable name for the value specified.

VALUE NOT SELECTED FROM LIST

Reason:

No value selected from the selection list displayed.

System Action:

None.

User Action:

None.

P1 DOES NOT EXIST

Reason:

P1 specified is not known to the system.

System Action:

None.

User Action:

Use '?' to select P1.

SPECIFY P1 IF PARAMETER SPECIFIED

Reason:

There is no use specifying parameter without P1 name to process.

System Action:

None.

User Action:

Specify P1 name or use '?' to select P1.

P1 USED IN THE EXPRESSION

Reason:

If condition specified then it has to be referenced in the expression and vice versa.

System Action:

Validation failed.

User Action:

Specify condition if referenced in the expression or refer the condition in the expression.

P1 MUST BE SPECIFIED

Reason:

P1 must be specified for a valid test condition.

System Action:

None.

User Action:

Enter a valid P1 to create a valid test condition.

END TIME MUST BE GREATER THAN START TIME

Reason:

When a time range specified, the end time must be greater than the start time for a valid duration.

System Action:

None.

User Action:

Enter a valid time duration.

RULESET( P1) ALREADY EXISTS

Reason:

The ruleset P1 already defined for EventView.

System Action:

The request is rejected.

User Action:

Specify another valid ruleset name.

FIRST WORD OF MESSAGE TEXT MAY NOT BE MODIFIED

Reason:

The first word of the Message Text value is used as the key of the message in the Learnt Message database. Therefore, the first word may not be changed.

System Action:

The panel is redisplayed with the field(s) in error highlighted.

User Action:

Ensure the first word of the Message Text is the same as it was before the field was modified.

INVALID CHARACTERS ENCOUNTERED

Reason:

DBCS data was encountered during validation. DBCS data is not valid in this field.

System Action:

The panel is redisplayed with the field in error highlighted.

User Action:

Enter a non-DBCS value in the highlighted field.

WILDCARD MESSAGE RULES ARE NOT ALLOWED

Reason:

This region does not allow you to define a message rule with only a wildcard character.

System Action:

The panel is redisplayed with the field(s) in error highlighted.

User Action:

Define a more specific message rule, or contact your Systems Administrator. Refer to Global Variable $RE$WIRU = NO

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the service procedure.

System Action:

The request is rejected.

User Action:

Correct the calling procedure to the service procedure and rerun exec.

NO RULE FOUND

Reason:

No rule found to be displayed in the selection list.

System Action:

None.

User Action:

None.

RULESET NOT SELECTED FOR ADDING A MESSAGE RULE

Reason:

Process cancelled because no ruleset was selected.

System Action:

The request is rejected.

User Action:

Ruleset must be selected to add a message rule.

RULESET HAS P1 RULES

Reason:

The ruleset cannot be deleted because there are rules under this ruleset.

System Action:

The request is rejected.

User Action:

Ruleset must not have any rules for a successful deletion.

THIS RULESET IS INCLUDED BY RULESET( P1)

Reason:

The ruleset cannot be deleted because it is included by other ruleset/s.

System Action:

The request is rejected.

User Action:

Use Delete Entire to delete this ruleset.

THIS RULE IS CORRELATED TO P1 MESSAGE RULE/S

Reason:

The rule cannot be deleted because it is correlated to message rule/s.

System Action:

The request is rejected.

User Action:

Remove all correlation to this rule by updating the message rule/s and retry the delete process.

REQUEST DENIED - USER P1 P2 THE MESSAGE LEARNING DATABASE

Reason:

The requested action is rejected because userid P1 was previously P2 the Message Learning database. P2 will indicate whether the user was deleting or resetting the database.

System Action:

The request is rejected.

User Action:

Try again later.

NO MESSAGES FOUND IN MESSAGE LEARNING DATABASE

Reason:

There are no learnt messages available for display.

System Action:

None.

User Action:

None.

GENERATE REJECTED. MESSAGE STARTS WITH A DBCS CHARACTER.

Reason:

The message you have selected by using the GR action code starts with a DBCS character. Message rules cannot be defined for such messages.

System Action:

The action is rejected.

User Action:

None.

P1 is now P2

Reason:

This message confirms that a request to activate or inactivate an object completed successfully.

System Action:

None.

User Action:

None.

P1 is already P2

Reason:

A request to activate or inactivate an object failed because the object is already in the state requested. P1 is the object class and P2 is the current state of the object.

System Action:

The request is rejected.

User Action:

Select another object or another action.

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the procedure.

System Action:

The request is rejected.

User Action:

Contact System Administrator.

NCL PROCEDURE P1 DOES NOT EXIST IN LIBRARY P2

Reason:

The procedure P1 specified on the EXEC, START or FSPROC command does not exist in the procedure library P2.

System Action:

The command is rejected.

User Action:

Correct the procedure name. If the procedure name is correct ensure that it exists in the procedure library specified for use by this userid. This can be determined by the SHOW EXEC command or alternatively the LIST command could be used to display the procedure without execution.

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the procedure.

System Action:

The request is rejected.

User Action:

Contact System Administrator.

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the service procedure.

System Action:

The request is rejected.

User Action:

Correct the calling procedure to the service procedure and rerun exec.

P1 DOES NOT EXIST

Reason:

P1 specified is not known to the system.

System Action:

None.

User Action:

Use '?' to select P1.

INVALID NAME SPECIFIED

Reason:

An invalid name was passed to the service procedure.

System Action:

The request is rejected.

User Action:

Correct the name required and rerun exec.

RULESET NOT SELECTED FROM LIST

Reason:

No value was selected from the displayed list.

System Action:

None.

User Action:

Select a ruleset from the list.

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the service procedure.

System Action:

The request is rejected.

User Action:

Correct the calling procedure to the service procedure and rerun exec.

Statistics processing not started - SMF not enabled

Reason:

Statistics processing cannot be started because SMF has not been enabled due to one or both of the following:

- To write SMF records, the SMF Record Identification must have a non-zero value. This value is specified in the Customizer SMF parameter group.

- To collect EventView SMF records, specify YES in the Customizer SMFDATA parameter group.

System Action:

The procedure terminates with a RC of 8 and writes an error message to the system log.

User Action:

Contact your system administrator.

Unable to reset VARTABLE ( P1)

Reason:

The vartable identified by P1 does not exist in the current region.

System Action:

The procedure terminates with a RC of 8 and writes an error message to the system log.

User Action:

Contact your Systems Administrator.

Unable to allocate VARTABLE ( P1)

Reason:

The vartable identified by P1 cannot be allocated in the current region.

System Action:

The procedure terminates with a RC of 8 and writes an error message to the system log.

User Action:

Contact your Systems Administrator.

RECALL01

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the procedure.

System Action:

The request is rejected.

User Action:

Contact System Administrator.

RECALL02

UNABLE TO CREATE INCLUDE RECORD

Reason:

Target ruleset name is not specified in the calling parameter.

System Action:

The request is rejected.

User Action:

Contact System Administrator.

RECALL03

ENTER TARGET RULESET

Reason:

Target ruleset name must be specified for copy process.

System Action:

The request is rejected.

User Action:

Specify the target ruleset name in the highlighted field.

RECALL04

TARGET RULESET( P1) ALREADY EXISTS

Reason:

Target ruleset name specified already exists in the system.

System Action:

The request is rejected.

User Action:

Specify a new target ruleset name in the highlighted field.

RECALL05

INVALID COMMAND

Reason:

Command specified is not recognized by the system.

System Action:

The request is rejected.

User Action:

Specify a valid command.

RECALL06

P1 P2 CANCELLED

Reason:

The function P1 being performed on P2 was cancelled at the user's request.

System Action:

None.

User Action:

None.

RECALL07

CANNOT CREATE OBJECT ID

Reason:

Object ID required for procesing cannot be created because of missing Ruleset name, class or ruleid in the calling parameters.

System Action:

The request is rejected.

User Action:

Contact System Administrator.

RECALL08

UNKNOWN CLASS( P1)

Reason:

Class specified in the calling parameter is unknown to the system.

System Action:

The request is rejected.

User Action:

Contact System Administrator.

RECALL09

UPDATE IN PROGRESS BY P1

Reason:

Update is in progress on this definition by other user.

System Action:

The request is rejected.

User Action:

Try again later.

RECALL10

EventView API called with invalid data

Reason:

The $RECALL EventView API was called with invalid operands. This could be caused by invalid data (for example, special characters in a ruleset name).

System Action:

The request is rejected.

User Action:

Correct the input data, and retry.

REDBAPI01

SYNTAX ERROR: P1

Reason:

A call Syntax Error has been detected while processing a RAMDB Maintenance Request. P1 contains the details of the error.

System Action:

The request is rejected.

User Action:

Correct the API Call request and re-submit.

REDBAPI02

P1 EXCEEDS MAXIMUM LENGTH P2

Reason:

The value presented in P1 exceeds the maximum length allowable for that variable.

System Action:

The request is rejected.

User Action:

Reduce the length of the value to less than or equal to the value indicated by P2.

REDBAPI03

INVALID CLASS( P1) SPECIFIED

Reason:

An invalid class has been specified in the request. The valid classes are 93 (Rulesets), 94 (Message Rules), 95 (Message Group Rules) and 98 (Timer Rules).

System Action:

The request is rejected.

User Action:

Specify a valid class value or remove and retry.

REDBAPI04

' P1' IS AN INVALID VALUE FOR P2

Reason:

The value P1 is an invalid value for the field P2.

System Action:

The request is rejected.

User Action:

Correct the value for the field and retry.

REDBAPI05

P1( P2) ALREADY EXISTS

Reason:

On a CREATE call a record of type P1 with the name P2 was found on the database and therefore cannot be added.

System Action:

The call is rejected.

User Action:

Choose a different name or delete the existing record.

REDBAPI06

FOR CLASS 93 "NAME" MUST BE THE SAME AS "RULESET"

Reason:

For calls dealing with class 93 (RULESETS) the value for NAME, if supplied, must be the same as the value for RULESET.

System Action:

The call is rejected.

User Action:

Change either the value of the NAME or RULESET keyword and retry.

REDBAPI07

P1 SERVICE COMPLETED SUCCESSFULLY

Reason:

The service P1 was performed successfully.

System Action:

None.

User Action:

None.

REDBAPI08

RULESET( P1) DOES NOT EXIST

Reason:

The RULESET P1 specified in the request does not exist on the database.

System Action:

The call is rejected.

User Action:

Choose a different name or create the required ruleset.

REDBAPI09

' P1' IS A REQUIRED FIELD WHEN CREATING A P2

Reason:

The field P1 is required when performing a CREATE for P2 type records.

System Action:

The request is rejected.

User Action:

Supply a value for the field and retry.

REDBAPI10

LENGTH OF ' P1' EXCEEDS THE MAXIMUM OF P2

Reason:

The length of field P1 exceeds the maximum allowable length, P2, for this field.

System Action:

The request is rejected.

User Action:

Either supply a shorter value for the field or invoke $REDBAPI with TRUNCATE=YES to automatically truncate fields which exceed the maximum length.

REDBAPI11

NO P1 RECORDS LISTED

Reason:

Issued in response to a SERVICE=LIST request, if no records of class P1 have been listed as a result of the request.

System Action:

None.

User Action:

None.

REM00201

P1 does not exist

Reason:

Event Rule Ruleset P1 is not known to the system.

System Action:

None.

User Action:

Use '?' to display and select an existing ruleset.

REM00202

Invalid Ruleset Name specified

Reason:

An invalid ruleset name was entered.

System Action:

The request is rejected.

User Action:

Correct the ruleset name and retry the operation.

REM00203

Ruleset not selected from list

Reason:

No ruleset was selected from the displayed list.

System Action:

None.

User Action:

Select a ruleset from the list.

REM00301

Database scan terminated - System Parameter Record Limit Exceeded

Reason:

The database scan required to display the selected Message Learning list was terminated because the number of records returned by the scan would have exceeded the maximum allowed by the system parameters NDB Default Record Limit and/or NDB Maximum Record Limit.

System Action:

The requested database scan terminates and processing returns to the Message Learning menu.

User Action:

Contact your system administrator about increasing the values of the NDB record limits in the system's Initialization Parameters.

REML2001

P1 IS AN INVALID VALUE FOR KEYWORD PARAMETER P2

Reason:

The Message Learning API procedure was called with keyword P2 set to a value ( P1 ) which the API does not support.

System Action:

The procedure sets a return code of '16' and returns processing to the caller.

User Action:

Check the defined allowed values for the keyword P2 and retry.

REML2002

MESSAGE LEARNING DATABASE P1 SUCCESSFULLY

Reason:

The requested Message Learning database P1 function completed successfully.

System Action:

None.

User Action:

None.

REML2101

P1 FAILED FOR VARTABLE P2 - ZFDBK= P3, MSGID= P4

Reason:

The Message Learning secondary AOMProc's attempted P1 for vartable P2 failed. P3 contains the feedback code returned and P4 contains the Message ID of the record which was being actioned. This message implies that something extraordinary occurred whilst processing the vartable.

System Action:

The message is not processed.

User Action:

Contact Systems Administrator.

REML2102

P1 FAILED - MSGID P2 NOT FOUND IN VARTABLE P3

Reason:

The Message Learning secondary AOMProc received a message with message ID P2 from the primary AOMProc but there was no corresponding record in vartable P3.

System Action:

The message is not processed.

User Action:

Contact Systems Administrator.

REML2103

P1 FAILED FOR GDB RECORD MSGID= P2 - ZFDBK= P3

Reason:

The Message Learning secondary AOMProc's attempted P1 failed for the GDB record whose message ID is P2. P3 contains the feedback code returned. This message implies that something extraordinary occurred whilst processing the GDB.

System Action:

The message is not processed.

User Action:

Contact Systems Administrator.

REML2104

P1 FAILED FOR GDB RECORD MSGID P1 - NO ENTRY FOUND

Reason:

The Message Learning secondary AOMProc received a message with message ID P1 from the primary AOMProc but there was no corresponding record in the GDB.

System Action:

The message is not processed.

User Action:

Contact Systems Administrator.

REML2105

** MESSAGE LEARNING STOPPED - GDB AREA FOUND TO BE CORRUPT **

Reason:

The Message Learning secondary AOMProc attempted to process a GDB record but failed because the GDB was found to be corrupted. This is a serious situation and no further messages will be learned which require any GDB processing.

System Action:

Message Learning is stopped - no new messages will be learned but the user interface functions are still available.

User Action:

Contact Systems Administrator.

REML2106

ALLOC FAILED FOR VARTABLE P1 - ZFDBK= P2

Reason:

The Message Learning secondary AOMProc's attempted allocation of process vartable P1 failed. P2 contains the feedback code returned.

System Action:

The procedure sets a return code of '8' and ends.

User Action:

Contact Systems Administrator.

REML2107

ADD FAILED FOR VARTABLE P1 - KEY P2 ALREADY EXISTS

Reason:

The Message Learning secondary AOMProc attempted to add a record to the scope=process vartable P1 but failed because a record with that key value (' P2 ') was already in the vartable. This implies that the secondary AOMProc has received a duplicate event, that is, an event for a message which has previously been processed.

System Action:

The message is not processed.

User Action:

Contact Systems Administrator.

REML2108

RECORD NOT ADDED - MESSAGE LEARNING DATABASE BEING P1

Reason:

The Message Learning secondary AOMProc was unable to gain a shared lock on the Message Learning database because a P1 action was in progress which modifies the whole database. Message Learning discarded the message it was attempting to add. The secondary AOMProc will wait for up to 2 minutes before discarding a new message.

System Action:

The new message is discarded. The secondary AOMProc issues this message to monitor class users and the log and then continues processing.

User Action:

If this message occurs repeatedly, check for any processes which are holding an exclusive lock against the Message Learning database.

REML2109

** MESSAGE LEARNING STOPPED - MESSAGE LEARNING AOM TABLE NOT FOUND **

Reason:

The Message Learning secondary AOMProc attempted to add a message but was unable to do so because the Message Learning AOM vartable was not found. This message implies that the Message Learning AOM vartable has been deleted or that &AOMGFLAG 33 has been set 'ON' by something external to Message Learning whilst Message Learning was inactive.

System Action:

Message Learning is stopped - no new messages will be learned but the user interface functions are still available.

User Action:

To restart the learning function, set to 'NO' the value of the 'Learn New Messages?...' field in the active EventView ruleset and save the change. Then reset the same field to 'YES' and again save the change. Message Learning will restart with a larger vartable capacity.

REML2110

********************************************************

Reason:

This message is used only to highlight message REML2112 - see the description for message REML2112 for explanation of the relevant error.

System Action:

None.

User Action:

None.

REML2111

** **

Reason:

This message is used only to highlight message REML2112 - see the description for message REML2112 for explanation of the relevant error.

System Action:

None.

User Action:

None.

REML2112

** MESSAGE LEARNING STOPPED - MESSAGE LEARNING AOM TABLE AT ITS LIMIT **

Reason:

The Message Learning secondary AOMProc attempted to add a message but was unable to do so because the Message Learning AOM vartable was at its limit.

System Action:

Message Learning is stopped - no new messages will be learned but the user interface functions are still available.

User Action:

REML2201

DATABASE SCAN TERMINATED - SYSTEM PARAMETER RECORD LIMIT EXCEEDED

Reason:

System Action:

The requested database scan terminates and processing returns to the Message Learning menu.

User Action:

Contact your system administrator about increasing the values of the NDB record limits in the system's Initialization Parameters.

REML2301

P1 IS AN INVALID VALUE FOR KEYWORD PARAMETER P2

Reason:

The Message Learning confirmation display utility procedure was called with keyword P2 set to a value ( P1 ) which the procedure does not support.

System Action:

The procedure sets a return code of '8' and returns processing to the caller.

User Action:

Check the defined allowed values for the keyword P2 and retry.

REML2302

P1 IS A REQUIRED KEYWORD PARAMETER

Reason:

When the Message Learning confirmation display utility procedure was called the required keyword P2 was not set.

System Action:

The procedure sets a return code of '16' and returns processing to the caller.

User Action:

Check the defined allowed values for the keyword P1 and retry.

REML2303

MESSAGE LEARNING DATABASE P1 IN PROGRESS (AT P2) BY P3

Reason:

The requested action is rejected because a database P1 is already in progress. The P1 was requested at P2 by user P3.

System Action:

The request is rejected.

User Action:

Try again later.

REML2304

COMMAND IS INVALID FOR THIS WINDOW

Reason:

You entered a command at the command line whilst in the Message Learning database Reset/Delete confirmation window.

System Action:

The request is rejected. The confirmation window is redisplayed with the error message.

User Action:

None.

REML2305

P1 OF MESSAGE LEARNING DATABASE CANCELLED

Reason:

The function P1 being performed on the Message Learning database was cancelled at the user's request.

System Action:

None.

User Action:

None.

REML2401

UNEXPECTED MESSAGE RECEIVED ON INTERNAL EVENT READ QUEUE

Reason:

The Message Learning table loader procedure received a message other than an expected EDS event on its internal queue. This message serves only as a warning. This message is followed by the message received. Subsequent errors will not result in a warning being written to the log.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2402

P1 FAILED FOR VARTABLE P2 - ZFDBK= P3

Reason:

The Message Learning table loader procedure tried to perform a P1 action on AOM vartable P2 but the action failed. P3 contains the feedback code returned.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2403

ALLOCATE FAILED FOR VARTABLE P1 - 16 TABLES ALREADY EXIST

Reason:

The Message Learning table loader procedure tried to allocate AOM vartable P1 but the allocation failed - there are already the maximum allowed number of SCOPE=AOM tables allocated.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2404

ALLOCATE FAILED FOR VARTABLE P1 - STORAGE WOULD BE EXCEEDED

Reason:

The Message Learning table loader procedure tried to allocate AOM vartable P1 but the allocation failed - its allocation would have caused total storage allocated for vartable mirroring to exceed the maximum defined by SYSPARMS AOMMAXTS.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2405

P1 FAILED FOR P2 - ZFDBK= P3, MSGID= P4

Reason:

The Message Learning table loader procedure tried to perform a P1 action on P2 but the action failed. P3 contains the feedback code returned and P4 contains the Message ID of the record which was being actioned.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2406

P1 FAILED FOR VARTABLE P2 - KEY P3 IS TOO LONG

Reason:

The Message Learning table loader procedure tried to perform a P1 action on vartable P2 but the key value supplied, P3, was too long for the vartable key definition.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2407

P1 FAILED - VARTABLE P2 DOES NOT EXIST

Reason:

The Message Learning table loader procedure tried to perform a P1 action on vartable P2 but the table was not found in the AOM region.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2408

P1 FAILED - VARTABLE P2 IS AT ITS LIMIT

Reason:

The Message Learning table loader procedure tried to perform a P1 action on vartable P2 but the table has already reached its limit for number of records stored.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2409

P1 FAILED - VARTABLE P2 DISABLED DUE TO STORAGE ERROR

Reason:

The Message Learning table loader procedure tried to perform a P1 action on vartable P2 but the vartable has been disabled due to a previous storage error.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2410

PUT FAILED - GDB IS AT ITS LIMIT

Reason:

The Message Learning table loader procedure tried to perform a PUT action on the GDB but the GDB has reached its maximum storage limit.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2411

PUT FAILED - GDB IS CORRUPTED

Reason:

The Message Learning table loader procedure tried to perform a PUT action on the GDB but the GDB has been corrupted.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2412

DELETE FAILED - RECORD DOES NOT EXIST FOR MSGID P1 ON THE GDB

Reason:

The Message Learning table loader procedure tried to perform a DELETE action on the GDB but no record was found in the GDB for the specified message ID P1.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2413

WARNING: EVENTVIEW MESSAGE LEARNING PROCESSING ERROR

Reason:

An error or unexpected result occurred whilst the Message Learning table loader procedure was processing. This message is written to the activity log and precedes a message which will describe the particular error.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2414

NO MESSAGE RECEIVED IN RESPONSE TO PROFILE P1 COMMAND

Reason:

The Message Learning table loader procedure did not receive a response to a PROFILE P1 command, which was issued internally.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2415

P1 FAILED FOR VARTABLE P2 - KEY P3 NOT FOUND

Reason:

The Message Learning table loader procedure tried to perform a P1 action on vartable P2 but a table entry was not found for the key value,
P3, supplied.

System Action:

The procedure writes the message to the activity log and continues.

User Action:

Contact Systems Administrator.

REML2416

MESSAGE LEARNING STOPPED BY EVENTVIEW REQUEST

Reason:

The Message Learning table loader procedure ended processing because it received a SHUTDOWN request message on its internal message stack from another part of EventView. This may be because a new ruleset has been activated which requires Message Learning to be turned off.

System Action:

The procedure writes the message to the activity log and terminates.

User Action:

None.

REML2417

MESSAGE LEARNING PROCESSING ENDED - REASON CODE P1

Reason:

The Message Learning table loader procedure has ended processing. P1 contains the value of the return code at the time the procedure ended.

System Action:

The procedure writes the message to the activity log and terminates.

User Action:

None.

RETM1001

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the service procedure.

System Action:

The request is rejected.

User Action:

Correct the calling procedure to the service procedure and rerun exec.

RETM1002

VARTABLE( P1) IS NOT ALLOCATED IN THIS EVENTVIEW REGION

Reason:

The vartable identified by P1 has not been allocated.

System Action:

The current process terminates.

User Action:

Contact your local support representative.

RETM1003

UNABLE TO OPEN CATCHUP DB FILE( P1) FILERC( P2)

Reason:

An OPEN request for the file identified by P1 failed with FILERC P2.

System Action:

Processing continues but CATCHUP processing will not be available.

User Action:

Contact you local support representative.

RETM1004

FUNCTION( P1) FAILED WITH DBRC( P2) AND MSG( P3)

Reason:

The database function P1 failed with RC P2 and message P3.

System Action:

The current process terminates.

User Action:

Contact your local support representative.

RETM1005

NO RECORDS FOUND IN VARTABLE( P1) FOR KEY( P2) FDBK( P3)

Reason:

No records for the record key P2 were found in vartable P1.

System Action:

The Current process is terminated

User Action:

Check to see whether any valid timer rules have been defined for the ruleset and retry the function.

RETM1006

RECORD WITH KEY( P1) NOT DELETED FROM VARTABLE( P2) FDBK( P3)

Reason:

The record with key identified by P1 was not deleted from vartable P2.

System Action:

The Current process is terminated

User Action:

Check to see whether any valid timer rules have been defined for the ruleset and retry the function.

RETM1007

FUNCTION( P1) FAILED FOR VARTABLE( P2) FDBK( P3)

Reason:

The function identified by P1 failed for record key P2 on vartable P3.

System Action:

The Current process is terminated.

User Action:

Check to see whether any valid timer rules have been defined for the ruleset and retry the function.

RETM1008

FUNCTION( P1) FAILED FOR KEY( P2) FOR FILE( P3) FILERC( P4)

Reason:

The function identified by P1 failed for record key P2 on file P3.

System Action:

The Current process is terminated.

User Action:

Check to see whether any valid timer rules have been defined for the ruleset and retry the function.

RETM1009

EVENTVIEW TIMER( P1) WAS NOT PURGED

Reason:

The timer associated with EventView was not purged.

System Action:

The timer driver procedure may not execute at the correct time for the next timer rule to be actioned.

User Action:

View the log to determine the reason for the timer not being purged. Contact your local support representative.

RETM1010

NO RECORDS FOUND IN VARTABLE( P1) FDBK( P2)

Reason:

No records were found in the vartable identified by P1. The feedback value is P2.

System Action:

The current process terminates.

User Action:

Check to see whether any valid timer rules have been defined for the ruleset and retry the function.

RETM1011

FUNCTION( P1) FOR RULESET( P2) RULEID( P3) FAILED

Reason:

The function identified by P1 failed for ruleset P2 ruleid P3.

System Action:

The current process terminates.

User Action:

View the log to determine the reason for the timer not being set. Contact your local support representative.

RETM1012

GET REQUEST FAILED BECAUSE A REQUIRED PARAMETER WAS OMITTED

Reason:

A get request from the active timer vartables failed because one of the required parameters was omitted from the request.

System Action:

The current process terminates.

User Action:

Correct the request and retry.

RETM1013

Eventview timer adjustment failed - P1

Reason:

An attempt to reevaluate EventView timer rules after a time change failed. P1 is the failure reason.

System Action:

Processing continues. Some timers may not be issued when expected.

User Action:

This is an internal error. Contact Technical Support.

RETM1014

Execution of timer rule P1 in ruleset P2 adjusted for time change

Reason:

The EventView timer rule P1 has been impacted by a time change such as a Daylight Saving change, and its execution time has been adjusted.

System Action:

The timer rule is adjusted as follows.

For a forward time change:

If the timer was scheduled to execute in the skipped period and it is not an EVERY timer, it is executed immediately.
If an EVERY timer is active and its interval is less than or equal to the time change amount, the timer continues at the defined interval for the defined number of times.
If an EVERY timer is active and its interval is greater than the time change amount, and it was due to execute in the skipped period, it executes immediately. The next execution will be at the next scheduled time, in the new local time.

For a backward time change:

If an EVERY timer is active and the interval is less than or equal to the time change amount, the timer continues at the defined interval for the defined number of times.
If an EVERY timer is active and the interval is greater than the time change amount, the next execution will be at the next scheduled time, in the new local time.

User Action:

None.

RETM1601

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the service procedure.

System Action:

The request is rejected.

User Action:

Correct the calling procedure to the service procedure and rerun exec.

RETM1602

SCRLLIST CANCELLED AT USER REQUEST - UPDATES NOT SAVED

Reason:

The user has requested a cancel of the SCRLLIST function. All updates made while in SCRLLIST mode will be lost.

System Action:

Control is returned to the calling procedure. Updates made while in
SCRLLIST mode will not be saved.

User Action:

None.

RETM1603

MAXIMUM NUMBER OF SCHEDULE ITEM ENTRIES ALREADY EXIST

Reason:

A Repeat of a schedule item entry has been attempted which would cause the maximum number of entries to be exceeded.

System Action:

Action disallowed.

User Action:

None.

RETM1604

VARTABLE( P1) IS NOT ALLOCATED, FEEDBACK ( P1)

Reason:

The vartable identified by P1 has not been allocated. Vartable feedback information is P2.

System Action:

The current process terminates.

User Action:

Contact your local support representative.

RETM1701

FUNCTION ( P1) NOT CURRENTLY SUPPORTED

Reason:

The function identified by P1 is not supported by the procedure.

System Action:

A message is issued to the user. Processing continues.

User Action:

None.

RETM1702

PUT OF VARTABLE RECORD ( P1) FAILED - FEEDBACK ( P2)

Reason:

The vartable PUT function failed for the record identified by P1 with vartable feedback P2.

System Action:

A message is issued to the user. Processing continues.

User Action:

Contact you local support representative.

RETM1703

GET OF VARTABLE RECORD ( P1) FAILED - FEEDBACK ( P2)

Reason:

The vartable GET function failed for the record identified by P1 with vartable feedback P2.

System Action:

A message is issued to the user. Processing continues.

User Action:

Contact you local support representative.

RETM1801

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the service procedure.

System Action:

The request is rejected.

User Action:

Correct the calling procedure to the service procedure and rerun exec.

RETM1802

EITHER ( P1) OR ( P2) MUST BE SPECIFIED

Reason:

One of the fields identified by P1 and P2, must be specified on this screen.

System Action:

Field(s) highlighted in error.

User Action:

Enter a valid value for one of the specified fields.

RETM1803

( P1) IS A REQUIRED FIELD

Reason:

While defining a resource availability map the field identified by P1 was not entered and is a required field.

System Action:

Field highlighted in error.

User Action:

Enter a value for the specified field.

RETM1804

UNABLE TO EXPAND SCHEDULE ITEM - NOT ENOUGH LINES AVAILABLE ON PANEL

Reason:

A generic value of '*', 'W/D' or 'W/E' was specified, which would cause the maximum number of timers on the panel to be exceeded if it were expanded out.

System Action:

Field(s) highlighted in error.

User Action:

Clear the fields for the entry and press PF10 to invoke the scrollable list. Retype the entry in the scrollable list and press ENTER to resolve the entry.

RETM1805

UNABLE TO EXPAND SCHEDULE ITEM. ITEM LIMIT OF ( P1) WILL BE EXCEEDED

Reason:

A generic value of '*', 'W/D' or 'W/E' was specified which would cause the maximum number of timers ( P1 ) to be exceeded if it were expanded out to one timer entry for each day covered.

System Action:

Field(s) highlighted in error.

User Action:

Correct the number of timer entries to remain below the limit.

RETM1806

( P1) IS NOT A VALID VALUE FOR ( P2)

Reason:

The value identified by P1 is not valid for the field identified by P2.
This message may also have a list of valid values for the field appended to the end of it.

System Action:

Field highlighted in error.

User Action:

Enter a valid value for the specified field.

RETM1807

DAY AND DATE VALUES CANNOT BOTH BE SPECIFIED

Reason:

Both 'day' and 'date' values have been specified. Only one of these values may be specified, as calculation of the next execution date for a generic date will result in a different day value each time.

System Action:

Both Fields highlighted in error.

User Action:

Specify a value for only one of either 'day' or 'date'.

RETM1808

DAY MUST BE BETWEEN 1 AND P1

Reason:

The DAY portion of a date must be a value between 1 and P1.

System Action:

Field(s) highlighted in error.

User Action:

Change day to conform with message.

RETM1809

DATE VALUE ( P1) IS A PAST DATE

Reason:

The 'date' value identified by P1 is a date in the past.

System Action:

The 'date' field is highlighted in error.

User Action:

Specify a date value for a date in the future.

RETM1810

DUPLICATE SCHEDULE ITEM DEFINITION

Reason:

A combination of DAY, DATE and TIME may only appear once within a timer rule.

System Action:

Fields highlighted in error.

User Action:

Change the DAY, DATE or TIME to make the schedule item unique.

RETM1811

DATE ( P1) OCCURS IN THE PAST

Reason:

The date and time identified by P1 has already passed.

System Action:

The 'date' and 'time' fields are highlighted and an error message is displayed to the user.

User Action:

Reenter new date and/or timer values.

RETM1812

'Delete on Expiry?' is YES but there are no expiring timers

Reason:

This rule does not contain a timer that activates on a specific date. The timers specified currently never expire.

Delete on Expiry? is effective only for timers that activate on specific dates. Other types of timers (for example, timers that activate on a particular day of the week) do not expire.

System Action:

The Delete on Expiry? field is highlighted.

User Action:

If you plan to include a timer that activates on a specific date, add the timer; otherwise, change the value of the Delete on Expiry? field to
NO .

RETM1901

INVALID KEYWORD VALUE SPECIFIED - KEYWORD( P1) VALUE( P2)

Reason:

An invalid keyword was passed to the service procedure.

System Action:

The request is rejected.

User Action:

Correct the calling procedure to the service procedure and rerun exec.

RETM1902

TIME VALUE OMITTED - UNABLE TO PERFORM CALCULATION FOR SCHEDULE ITEM

Reason:

The time value for the schedule item does not exist so the calculation routine is unable to perform calculation for the schedule item.

System Action:

The system stops processing for the timer rule.

User Action:

Check the Timer Rule definition in the DB to ensure that valid schedule items exist for the timer rule.

RETM1903

DAY AND DATE VALUES OMITTED - UNABLE TO PERFORM CALCULATION FOR ITEM

Reason:

Both the day and date values for the schedule item are null. The date calculation routine is unable to perform caluclation for the schedule item.

System Action:

The system stops processing for the timer rule.

User Action:

Check the Timer Rule definition in the DB to ensure that valid schedule items exist for the timer rule.

Tell Technical Publications how we can improve this information