|
|
|
Reason:
The System Support Services procedure $SSPM03M failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $SSPM03M terminates.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
A request to access the System Support Services menu was denied because the userid P1 was not authorized.
System Action:
The request is rejected.
User Action:
None.
Reason:
The user identified by P1 is not authorised to use the System Support menu option.
System Action:
None
User Action:
Contact your local security administrator.
Reason:
The Domain ID identified by P1 does not conform to the specification for a valid Domain ID.
System Action:
None
User Action:
Correct the entry and retry the operation.
Reason:
No domains were selected from the displayed list.
System Action:
None
User Action:
None
Reason:
The selected option is invalid if multiple domains have been selected. The option is valid only for a single domain ID.
System Action:
None
User Action:
Correct the entry and retry the operation.
Reason:
The data entered into the field specified in the message contains one or more embedded blanks.
System Action:
Option not processed.
User Action:
Correct the field and retry the operation.
Reason:
An invalid call was made to the procedure. The keyword in error is identified by P1 and the value by P2 .
System Action:
None
User Action:
Contact your local Systems Administrator.
Reason:
Procedure $SSGP11H failed because an &VARTABLE verb gave an unexpected return code. In the message:
P1 is the VARTABLE name
P2 is the &VARTABLE request type
P3 is the key for the entry
P4 is the return code
System Action:
The request is rejected and the procedure terminates. Control is returned to the procedure which executed $SSGP11H.
User Action:
Contact your systems administrator.
Reason:
The Domain ID identified by P1 does not conform to the specification for a valid Domain ID.
System Action:
None
User Action:
Correct the entry and retry the operation.
Reason:
No domains were selected from the displayed list.
System Action:
None
User Action:
None
Reason:
The selected option is invalid if multiple domains have been selected. The option is valid only for a single domain ID.
System Action:
None
User Action:
Correct the entry and retry the operation.
Reason:
The System Support : User List service procedure failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and the procedure terminates. Control is returned to the procedure which executed $SSUA12L. If the procedure was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $SSUA12L. If the procedure was executed from OCS, check the command entered on the command line and retry.
Reason:
The System Support : User List service procedure failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $SSUA12L terminates.
User Action:
Contact your local Systems Administrator.
Reason:
The attempted action is not valid for one of the following reasons:
- The line is a message line
- ForceCancel and Disconnect are invalid for a disconnected user
System Action:
None
User Action:
None
Reason:
The System Support : User List service procedure failed because an &VARTABLE verb gave an unexpected return code. In the message:
P1 is the VARTABLE name
P2 is the &VARTABLE request type
P3 is the key for the entry
P4 is the return code
System Action:
The request is rejected and the list terminates. Control is returned to the procedure which executed $SSUA12L.
User Action:
Contact your systems administrator.
Reason:
No user IDs on this domain match the selection criteria.
System Action:
None
User Action:
None
Reason:
User P1 has attempted to invoke a function of the Network Management feature but is not authorized to do so.
System Action:
The process is terminated.
User Action:
Contact your systems administrator if you feel you should have access to the Network Management feature.
Reason:
An invalid selection option has been placed in the "Select Option" field of the Netmaster Primary Menu. P1 is the invalid option.
System Action:
The process waits for input from the terminal.
User Action:
Enter a valid selection and retry.
Reason:
An invalid selection has been placed alongside an option of the Netmaster Primary Menu. P1 is the invalid option.
System Action:
The process waits for input from the terminal.
User Action:
Enter a valid option and retry.
Reason:
A valid selection option has been placed alongside a menu item of the Netmaster Primary Menu but cannot be acted upon because that option is not currently active. P1 is the option selected.
System Action:
The process waits for input from the terminal.
User Action:
Ensure that the option is typed against the correct entry and retry.
Reason:
P1 is not a valid keyword.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
The keyword P1 has been specified more than once.
System Action:
The process is terminated.
User Action:
Correct the parameters and retry.
Reason:
User P2 has no access priviledge to the resource P1.
System Action:
Access to the resource is denied.
User Action:
Contact your security administrator if you require access to this resource.
Reason:
A request has timed out whilst waiting for a response from a device. P1 is the amount of time waited for before the request was abandoned.
System Action:
The process is terminated.
User Action:
Retry the function.
Reason:
P1 is not valid for P2 .
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
The node P1 has reported an event through the CNM interface.
System Action:
This message is passed to CA NSM.
User Action:
See the NEWS Dynamic Attentions display for details of the error condition.
Reason:
Alert forwarding using the CA NSM API received a zero return code following prior failures. The interface is now operational.
System Action:
None.
User Action:
None.
Reason:
Alert forwarding using the CA NSM API received a non-zero return code.
Return code values are:
4 ENF not active.
8 Error in ENF processing.
16 Error in EMWTO parameter list.
System Action:
This message will be logged once on first failure. Message SV0102 will be logged if alert forwarding to CA NSM recovers.
User Action:
Check that CA NSM has been installed. If necessary contact Technical Support.
Reason:
The NetMaster for SNA API $NSCALL failed because it received an invalid value for a passed parameter. The parameter name was P1 and its value was P2.
System Action:
Procedure $NSCALL terminates.
User Action:
Correct the NCL procedure or command that invokes $NSCALL and retry.
Reason:
The NetMaster for SNA API $NSCALL failed because it received an unknown option and name combination. The option (OPT=) was P1 and name (NAME=) was P2.
System Action:
Procedure $NSCALL terminates.
User Action:
Correct the NCL procedure or command that invokes $NSCALL and retry.
Reason:
The NetMaster for SNA API $NSCALL failed because the NCL Procedure that handles the function does not exist in the user's NCL Procedure Library. The request, identified by option ( P1 ) and name ( P2 ), requires procedure P3 which does not exist.
System Action:
Procedure $NSCALL terminates.
User Action:
Review the user's COMMANDS definition. Ensure that the relevant NCL procedure libraries are in the COMMANDS concatenation and/or move the NCL procedure to a library that is included in the COMMANDS library concatenation.
Reason:
The NetMaster for SNA API $NSCALL failed because the function requires additional parameters via the PARMS= operand but this was omitted. The request is identified by option ( P1 ) and name ( P2 ).
System Action:
Procedure $NSCALL terminates.
User Action:
Correct the NCL Procedure that invokes $NSCALL and retry.
Reason:
User P1 has attempted to invoke a function of the Network Management feature but is not authorized to do so.
System Action:
The process is terminated.
User Action:
Contact your systems administrator if you feel you should have access to the Network Management feature.
Reason:
Access to the requested function has been denied.
System Action:
Access to the function is denied.
User Action:
Contact the system administrator if the function is required.
Reason:
A request to pass NEWS dynamic attention messages to an external source has been successfully processed.
System Action:
Message SV0208 is issued to identify the receiver.
User Action:
None.
Reason:
A request to pass NEWS dynamic attention messages to CA NSM at the IP host P1 has been successfully processed.
System Action:
The CA NSM gateway procedure is started.
User Action:
None.
Reason:
A request to pass NEWS dynamic attention messages to an external source has failed as the process is already active.
System Action:
None.
User Action:
Use SHOW NCL=ALL PROC=$NSTN01Z to determine the process forwarding NEWS dynamic attentions.
Reason:
A socket error occurred forwarding NEWS dynamic attentions as SNMP traps
The socket action was P1 , the return code was P2 , the feedback code was P3, the error number was P4 - P5 is the name of the error, and the TCPIP vendor specific error code is P6 .
System Action:
The action fails, but recovery is attempted.
User Action:
If the problem persists determine the cause from the error codes and correct the problem.
Reason:
The NetMaster for SNA API ($NSCALL) has been called with a function that is obsolete in the current release. The particular call is identified by the ACTION (P1 ) and TYPE ( P2 ) parameters.
System Action:
The function is not actioned.
User Action:
Amend the calling procedure to remove the call to $NSCALL. Refer to the Migration Guide.
Reason:
A request to display the audit log failed because an audit log does not exist.
System Action:
The request is rejected.
User Action:
None.
Reason:
The requested entity does not exist in the indicated MODS data set ( P1 ). This may arise because another user has moved or deleted the entity.
System Action:
The request is rejected.
User Action:
Refresh the entity list and retry.
Reason:
The requested entity exists in the indicated MODS data set ( P1 ), but no-replace was specified.
System Action:
The request is rejected.
User Action:
If you want to replace the entity, use the replace action.
Reason:
This message provides details for a specific data set action as part of a MODS administration action. The message shows:
P1 The file action (added or deleted)
P2 The MODS DBID on which the action was performed
P3 An identification of the specific record actioned
System Action:
This message is written to the audit log for the administration process. There may be several actions (and messages) for a single record and for an entire MODS entity.
User Action:
None.
Reason:
The requested entity has been copied from the MODS data set ( P1 ) to MODS data set ( P2 ).
System Action:
None.
User Action:
None.
Reason:
The requested entity has been moved from the MODS data set ( P1 ) to MODS data set ( P2 ).
System Action:
None.
User Action:
None.
Reason:
The requested entity has been deleted from the MODS data set ( P1 ).
System Action:
None.
User Action:
None.
Reason:
No MODS IDs exist after applying selection criteria (DBID prefix and/or access mode).
System Action:
None.
User Action:
None.
Reason:
No MODS ID was selected from the prompt list.
System Action:
The request is ignored.
User Action:
Enter a unique SYSDB ID or select an item from the list.
Reason:
A request to browse, update, delete, or copy an application definition failed because the application definition is not defined. The identifier of the application was P1 .
System Action:
The request is rejected.
User Action:
Specify an application identifier previously defined and retry.
Reason:
An application definition was successfully added, updated, or deleted. The identifier of the application definition was P1 and the action successfully performed was P2 .
System Action:
None.
User Action:
None.
Reason:
A request to add an application definition failed because the application definition is already defined. The identifier of the application is P1 .
System Action:
The request is rejected.
User Action:
Specify an application identifier not previously defined and retry.
Reason:
An application identifier was entered in the Application ID field on the Application Definition panel that was previously defined. The application identifier entered was P1 .
System Action:
The Application Definition panel is displayed with the Application ID field set in error.
User Action:
Enter an application identifier not previously defined and retry.
Reason:
A message prefix was entered in the P1 field on the Application Definition panel that was generically equal to a message prefix defined in another application definition, or a message prefix defined in another application definition was generically equal to the entered prefix. The ID of the application found that contained the matching prefix was P2 and that message prefix was P3 .
System Action:
The Application Definition panel is displayed with the P1 field set in error.
User Action:
Enter a message prefix that does not generically equal a message prefix defined in another application definition, and then retry.
Reason:
An application ID was entered in the P1 field on the Application Definition panel that did not start with Y.
System Action:
The Application Definition panel is displayed with the P1 field set in error.
User Action:
Enter an application ID starting with Y in the P1 field, and then retry.
Reason:
A value was entered in the P1 field on the Application Definition panel that was not the same as the value in the P2 field.
System Action:
The Application Definition panel is displayed with the P1 field set in error.
User Action:
Enter the value of the P2 field in the P1 field and retry.
Reason:
Command P1 was successfully added, updated, or deleted.
System Action:
None.
User Action:
None.
Reason:
A request to add a Command entry failed because the new command to add is already in the database.
System Action:
The request is rejected.
User Action:
Specify a Command entry that is not defined to the database.
Reason:
A request to modify, browse, or retrieve Command entry P1 failed because the entry cannot be found in the database.
System Action:
The request is rejected.
User Action:
Specify a Command entry that is already added to the database.
Reason:
The Command ID P1 cannot be added because a definition with that ID already exists.
System Action:
The panel is redisplayed and the Command ID field is set in error.
User Action:
Correct the field by entering a unique Command ID.
Reason:
The command ID specified is a system reserved name and cannot be used in the command table.
System Action:
The panel is redisplayed and the Command ID field is set in error.
User Action:
Specify a unique command ID and retry the request.
Reason:
A command was entered in the Command field on the Criteria Description panel that was a valid command; however, it is not allowed to be specified on that panel.
System Action:
The command is rejected.
User Action:
Clear the Command field.
Reason:
An invalid value was entered in the P1 field on the Criteria Description panel.
System Action:
The Criteria Description panel is displayed with the P1 field set in error.
User Action:
Enter PUBLIC or PRIVATE in the P1 field and retry. The first two characters need to be entered only.
Reason:
P3 was entered in the P2 field on the Criteria Description panel and a value was entered in the P1 field.
System Action:
The Criteria Description panel is displayed with the P1 field set in error.
User Action:
Clear the P1 field or change the value of the P2 field and retry.
Reason:
A criteria name was entered in the Criteria Name field on the Criteria Description panel that is already defined. The criteria name entered was P1 and it was a public criteria.
System Action:
The Criteria Description panel is displayed with the Criteria Name field set in error.
User Action:
Enter a criteria name not previously defined and retry.
Reason:
A criteria name was entered in the Criteria Name field on the Criteria Description panel that is already defined. The criteria name entered was P1 and it was a private criteria owned by user ID P2 .
System Action:
The Criteria Description panel is displayed with the Criteria Name field set in error.
User Action:
Enter a criteria name not previously defined and retry.
Reason:
A criteria definition was successfully added, updated, or deleted. The name of the criteria definition was P1 and it was a public criteria. The action successfully performed was P2 .
System Action:
None.
User Action:
None.
Reason:
A criteria definition was successfully added, updated, or deleted. The name of the criteria definition was P1 and it was a private criteria owned by user ID P2. The action successfully performed was P3 .
System Action:
None.
User Action:
None.
Reason:
A request to add a criteria definition failed because the criteria definition is already defined. The name of the criteria was P1 and it was a public criteria.
System Action:
The request is rejected.
User Action:
Specify a criteria name not previously defined and retry.
Reason:
A request to add a criteria definition failed because the criteria definition is already defined. The name of the criteria was P1 and it was a private criteria owned by user ID P2 .
System Action:
The request is rejected.
User Action:
Specify a criteria name not previously defined and retry.
Reason:
A request to browse, update, delete, or copy a criteria definition failed because the criteria definition is not defined. The name of the criteria was P1 and it was a public criteria.
System Action:
The request is rejected.
User Action:
Specify a criteria name previously defined and retry.
Reason:
A request to browse, update, delete, or copy a criteria definition failed because the criteria definition is not defined. The name of the criteria was P1 and it was a private criteria owned by user ID P2 .
System Action:
The request is rejected.
User Action:
Specify a criteria name previously defined and retry.
Reason:
The type of entity that was selected ( P1 ) is a common service and is not part of an application ID.
System Action:
None.
User Action:
Clear the Application ID field and retry.
Reason:
The specified entity type ( P1 ) is not a valid MODS entity type.
System Action:
The request is rejected.
User Action:
Specify a valid entity type or use the prompt list.
Reason:
The source data set (identified by From ID or DSN) and target data set (identified by From ID or DSN) are the same data set. This is not valid.
System Action:
The request is rejected.
User Action:
Correct the source or target details and retry.
Reason:
No definitions exist for the type indicated ( P1 ) after applying selection criteria.
System Action:
None.
User Action:
None.
Reason:
The requested action ( P1 ) is not supported for this entry. For example, the List Entries (LE) action is applicable for a table with a table edit type of TABLE only.
System Action:
None.
User Action:
None.
Reason:
No definitions exist for the type indicated ( P1 ) after applying selection criteria.
System Action:
None.
User Action:
None.
Reason:
The Locate command is not available when a list of all resource types is displayed.
System Action:
None.
User Action:
None.
Reason:
A MODS administration action has started. The type of action ( P1 ), user ID (P2 ), date ( P3 ), and time commenced ( P4 ) are shown.
System Action:
This message is written to the audit log for the administration process. Additional messages showing data set details and specific record action are also written to the audit log.
User Action:
None.
Reason:
A MODS administration action has started. The DBID ( P1 ) and data set name ( P2 ) for the From MODS file are shown.
System Action:
This message is written to the audit log for the administration process.
User Action:
None.
Reason:
A MODS administration action has started. The DBID ( P1 ) and data set name ( P2 ) for the To MODS file are shown.
System Action:
This message is written to the audit log for the administration process.
User Action:
None.
Reason:
A MODS administration action has ended. The type of action ( P1 ), user ID (P2 ), date ( P3 ), and time commenced ( P4 ) are shown.
System Action:
This message is written to the audit log for the administration process.
User Action:
None.
Reason:
System Action:
User Action:
Use the update option to alter existing help text, or change the name
Reason:
Help was successfully added, updated, or deleted.
System Action:
None.
User Action:
None.
Reason:
The help that you have attempted to process does not exist on the help database. You may have specified an incorrect record or the help record could have been deleted by another user.
System Action:
None.
User Action:
If the name of the help record was specified incorrectly, correct it and retry.
Reason:
The help record that you attempted to update or delete is currently being updated or deleted by user P1.
System Action:
The action is rejected.
User Action:
Wait until the record is no longer in use and retry.
Reason:
Function level help should exist to create window or field level help successfully.
System Action:
Request rejected.
User Action:
Create function level help before creating a window or field help.
Reason:
The Delete Function Level Help request failed because the help function has window or field level help in the highest CAS concatenation level.
System Action:
The action is rejected.
User Action:
Delete all window and field level help for this function in the highest CAS concatenation level, and then retry.
Reason:
Function level help should exist to create window or field level help
System Action:
User Action:
Reason:
System Action:
User Action:
Use the update option to alter existing help text, or change the name
Reason:
The help that you attempted to process does not exist on the help database. You may have specified an incorrect record or the help record may have been deleted by another user.
System Action:
None.
User Action:
If the name of the help record was specified incorrectly, correct it and retry.
Reason:
The application ID that you specified is not three characters in length.
System Action:
The cursor is placed on the field in error and the field is highlighted.
User Action:
Correct the application ID.
Reason:
The copy command was entered with an invalid operand.
System Action:
The copy command is rejected.
User Action:
Correct the copy command operands and retry. Press Help for information about COPY command.
Reason:
The panel name specified in the copy command does not exist in the specified (or default) panels library.
System Action:
The copy command is rejected.
User Action:
Correct the panel or library name and retry.
Reason:
The function name specified is invalid because it is more than 12 characters long.
System Action:
The copy command is rejected.
User Action:
Correct the function name on the copy command and retry.
Reason:
The field name specified is invalid because it is more than 12 characters long.
System Action:
The copy command is rejected.
User Action:
Correct the field name on the copy command and retry.
Reason:
One or more of the cursor coordinates specified on the copy command was not a positive integer less than or equal to 999.
System Action:
The copy command is rejected.
User Action:
Correct the cursor coordinates on the copy command and retry.
Reason:
The specified panel was copied into the help text successfully.
System Action:
None.
User Action:
None.
Reason:
The panel specified in the copy command was not found in the current panel path. P2 is the number of libraries that were searched.
System Action:
The copy command is rejected.
User Action:
Correct the panel name in the copy command and retry.
Reason:
An invalid panel name was specified on the copy command.
System Action:
The copy command is rejected.
User Action:
Correct the panel name on the copy command and retry.
Reason:
The library name specified in the LIB operand on the copy command is too long. A library name can be up to eight characters in length.
System Action:
The copy command is rejected.
User Action:
Correct the library name on the copy command and retry.
Reason:
The help definition cannot be saved because no help text lines have been entered in the editor.
System Action:
None.
User Action:
Enter at least one line of help text in the editor and retry.
Reason:
The requested menu does not exist.
System Action:
The request is rejected.
User Action:
Correct the name of the menu and retry.
Reason:
The shortcut value entered is already in use on this menu or another menu (P1).
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the field value and retry.
Reason:
The entered shortcut, menu option, panel path, or command was invalid (for example, the syntax might be incorrect or the required function is not licensed in this region).
If you want to access a function, use one of the following methods (examples are given in parentheses):
- Enter a shortcut (/LEVELS or =/LEVELS)
- Enter a combined shortcut and menu option (/BCAST.S or =/BCAST.S) - Enter a menu option
- Enter a panel path (=H.I.P)
Note: Some shortcuts and options might be displayed but their operation suppressed for the following reasons:
- The shortcut or option requires a product or component that is not configured in this region.
- Access to the shortcut or option is denied because you do not have sufficient authority.
System Action:
None.
User Action:
If the syntax is incorrect, correct the shortcut, option, panel path or command, and retry.
SHORTCUTS
Enter a shortcut name, preceded by a slash, at the ===> prompt (for example, /LEVELS, /INFO, or /IPMON). This will take you directly to the function.
To see a list of all shortcuts and their associated functions, enter a single slash (/) at the ===> prompt. Select the desired shortcut from the list by entering S beside it.
If a shortcut exists for a menu option, it is displayed in turquoise to the right of the option description. If the value is -, it indicates that the option has no shortcut.
Shortcuts may also be combined with menu options (for example, /BCAST.S or =/BCAST.S).
You can invoke shortcuts in two ways:
- A nested shortcut - A shortcut skip
To retain and nest the current panel level, use a nested shortcut:
/shortcut_name
Exiting brings you back to the last nested panel. Panels may be nested to a maximum of 64 levels.
To close all currently nested panel levels, use a shortcut skip:
=/shortcut_name
Exiting takes you back to the Primary Menu. If you no longer need any nested panels, a shortcut skips saves storage and resources.
(If you are currently at the Primary Menu, a nested shortcut and a shortcut skip behave the same way.)
MENU OPTION
Each menu option is identified by a 1 to 3 character option string, displayed in yellow. Enter the option you want at the ===> prompt. Like shortcuts, panel paths move directly to a function without having to access each submenu between it and the current menu. A panel path consists of multiple menu options separated by periods (for example, =U.M).
Also like shortcuts, the = sign functions as a skip character, closing all nested panels and effectively entering the path from the Primary Menu. (If you are currently at the Primary Menu, the skip character is not required.)
PANEL PATH
Frequently used panel paths have associated shortcuts. If you do not remember a shortcut, enter / at the ===> prompt for a list. Select one from the list, or enter it at the ===> prompt.
There is no difference between accessing a function using a panel path skip or a shortcut skip, although the shortcut should be easier to remember. Both close the current panels and go straight to the function.
Entering == at the ===> prompt closes all nested panels and returns you to the Primary Menu.
Reason:
The value entered for a PAGE command was not numeric or was not within the range of pages for this record.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the command and retry.
Reason:
A scroll backward command was entered, but the top of the data has already been reached.
System Action:
None.
User Action:
None.
Reason:
A scroll forward request was made, but the bottom of the data has already been reached.
System Action:
None.
User Action:
None.
Reason:
A request was made to add a new menu or menu map, but a menu or menu map of that name already exists on the database.
System Action:
The add request is rejected.
User Action:
Either change the name of the menu or menu map which is to be added or use the update option to alter the existing menu or menu map.
Reason:
The entry being created or updated has been written to the database successfully.
System Action:
None.
User Action:
None.
Reason:
The specified entry was successfully deleted from the database.
System Action:
None.
User Action:
None.
Reason:
No data was entered in a mandatory field.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Enter a valid value in the field.
Reason:
An invalid value was entered in an input field.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the field value and retry.
Reason:
An invalid value was entered in an input field. P1 provides more details.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the field value and retry.
Reason:
A Description, Shrvars or Action value was entered, but no value has been entered in the Option field.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Either enter a value in the option field or erase the field in error.
Reason:
#MH was entered as a value on a Shrvars list. This variable name prefix is reserved for use by the Menu Handler.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Erase the #MH prefix from the Shrvars list.
Reason:
One or more spaces were entered in a field value. Imbedded spaces are invalid in this field.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the field value.
Reason:
Too many prefixes were specified in the Shrvars field.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Reduce the number of prefixes in the Shrvars field.
Reason:
Brackets may not be specified in the Shrvars field.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Erase the brackets from the Shrvars field.
Reason:
An ACTION was specified which did not begin with 'EXEC' or 'START'.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the value in the action field.
Reason:
An action was specified which did not contain an NCL procedure name to be executed.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the Action field value.
Reason:
An option has been specified twice on the one menu.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Change or erase one of the duplicate options.
Reason:
Each input field specified must have the options to which it relates entered.
System Action:
The cursor is placed in the field in error and the field is highlighted. All possible options are placed in the 'Optional for' field so that the user does not have to refer back to the previous page for the valid options.
User Action:
Enter the related options in either the 'Required for' or 'Optional for' field.
Reason:
An option entered in either the 'Required for' or 'Optional for' field which was not defined on the Options Maintenance page.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Delete the invalid option from the 'Required for' or 'Optional for' field.
Reason:
A field name was specified more than once on a menu.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Change or erase one of the duplicate field names.
Reason:
A request was made to create an additional option or input field entry, but the maximum number have already been created.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Erase the line command or delete another entry to create the necessary space.
Reason:
A Move or Copy line command was entered without the corresponding Before or After line command.
System Action:
None.
User Action:
Either specify the corresponding Before or After line command or erase the Move or Copy command.
Reason:
A menu number must be an positive integer.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the field value.
Reason:
The menu number must be an integer between 1 and 225.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the field value.
Reason:
An input field was specified incorrectly in the menu definition.
System Action:
If the invalid line is visible on the window, the cursor is placed on it and the field is highlighted.
User Action:
Correct the line definition.
Reason:
Only one option/input field may be moved or copied at a time. The current request is attempting to move/copy more than one entry, or has possibly specified more than one target for the entry.
System Action:
The request is rejected.
User Action:
Only specify one entry to be moved/copied to one destination at a time.
Reason:
A user cannot specify an 'X' option as this is the automatically generated, standard option for 'EXIT'.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Change or erase the 'X' option.
Reason:
The menu definition can not be filed/saved because there are no options defined in this new menu.
System Action:
The request is rejected.
User Action:
Specify option/s for this menu before filing/saving.
Reason:
The same value was assigned to two or more menu input field attributes. These characters will be used when displaying the menu and as such it is invalid for the same character to represent different display modes.
System Action:
The fields are highlighted in error.
User Action:
Use a different character for each menu input field attribute.
Reason:
A value was assigned to a menu input field attribute which was longer than one character. This is inavlid. All menu input field attributes must be single characters.
System Action:
The field is highlighted in error.
User Action:
Use a single character for each menu input field attribute.
Reason:
A call was made to the Message Handler without the MSGID keyword parameter.
System Action:
The call to the Message Handler is rejected.
User Action:
Correct the procedure call and retry.
Reason:
A request was made to add a message that already exists in the database.
System Action:
The add request is rejected.
User Action:
Change the message ID of the message being added or use the update option to change the existing message definition.
Reason:
The requested message definition does not exist on the database.
System Action:
The action is rejected.
User Action:
None.
Reason:
The message definition P1 was successfully added, deleted, or updated.
System Action:
None.
User Action:
None.
Reason:
The Message Text field cannot be browsed and edited with the full screen text editor. It has a maximum of three lines.
System Action:
The action is rejected.
User Action:
None.
Reason:
You did not place the cursor over a text field before you pressed Browse or Edit.
System Action:
None.
User Action:
To invoke the full screen editor for a text field, place the cursor over the field you want to update and press Browse or Edit.
Reason:
The full screen edit of the text field was canceled. The text remains in the state that it was in before the full screen editor was invoked.
System Action:
None.
User Action:
None.
Reason:
A request was made to add a message that already exists on the database.
System Action:
The add request is rejected.
User Action:
Change the message ID of the message you want to add or use the update option to change the existing message definition.
Reason:
A SECCALL GET request for the Review Userid failed.
System Action:
The update request is rejected.
User Action:
Change the Review Userid to a valid user ID.
Reason:
You have attempted to add a message that does not have its message prefix defined in the application register.
System Action:
Issue error message. Prevent the message from being saved.
User Action:
Add the application you are defining a message for to the application register. Each application in the application register has a unique message prefix specified in the application definition. When the application is defined, add the message.
Reason:
A Message Handler Message ID must have at least one numeric digit in it. For example, the Message ID MSGONE is invalid because it does not contain a digit. The Message ID MSG1 is valid because it does contain a digit.
System Action:
Message ID field placed in error.
User Action:
Enter a Message ID that contains at least one numeric digit.
Reason:
You are not authorized to perform the requested function.
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator if the function is required.
Reason:
The MODS ID specified ( P1 ) is not allocated or is not a MODS data set.
System Action:
The request is rejected.
User Action:
Specify a valid MODS data set ID or use the prompt list.
Reason:
The MODS ID specified ( P1 ) is open with read-only access. Read-write access is required.
System Action:
The request is rejected.
User Action:
Specify a valid MODS data set ID or use the prompt list.
Reason:
The MODS data set name specified ( P1 ) does not exist or is not a MODS data set.
System Action:
The request is rejected.
User Action:
Specify a valid SYSDB data set name and retry.
Reason:
The table definition was successfully added, deleted, or updated.
System Action:
None.
User Action:
None.
Reason:
The table definition and table entries were successfully added to or deleted from the database.
System Action:
None.
User Action:
None.
Reason:
The table definition to be added already exists on the database.
System Action:
None.
User Action:
Change the name of the record required or use the update option to modify the existing record.
Reason:
The requested table definition does not exist in the database.
System Action:
None.
User Action:
Correct the name of the requested record and retry, or use the ADD option to create a new record.
Reason:
The table definition cannot be deleted because table entries for the definition are present in the database.
System Action:
None.
User Action:
Delete all table entries for the definition before you delete the table definition.
Reason:
Page 2 of the Table Definition is not relevant unless EDIT type is TABLE.
System Action:
None.
User Action:
None.
Reason:
The requested command is permitted for table definitions that have an edit type of TABLE only.
System Action:
The request is rejected.
User Action:
None.
Reason:
The requested page number is not present in the current series of panels.
System Action:
The request is rejected.
User Action:
Correct the page number entered in the command line and retry.
Reason:
The validation tables were loaded into memory successfully.
System Action:
None.
User Action:
None.
Reason:
The field value entered is invalid.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The two fields are mutually exclusive and one or the other may be entered only.
System Action:
None.
User Action:
Erase one of the conflicting fields.
Reason:
A value must be entered for Field P1 if field P2 is present.
System Action:
None.
User Action:
Enter a value for the field in error or erase field P2.
Reason:
A value must not be entered in P1 unless a value is entered in field P1.
System Action:
None.
User Action:
Clear the field that is in error or enter a value in the second field.
Reason:
A Text Description field contains an invalid character. Certain characters are used internally by Validation Manager; therefore, cannot be used in the Text Description fields.
System Action:
None.
User Action:
Remove any invalid characters from the field value and retry.
Reason:
A request was made to add a Table Definition that already exists.
System Action:
The request is rejected.
User Action:
Correct the name of the field to be added and retry.
Reason:
A request was made to add a Table Definition with a name that is an NCL keyword.
System Action:
The request is rejected.
User Action:
Change the name of the field to be added and retry.
Reason:
The input data or requested action was rejected by the validation exit, but an error message was not returned.
System Action:
None.
User Action:
Correct the input data or action and retry.
Reason:
The table entry was successfully added, deleted, or updated.
System Action:
None.
User Action:
None.
Reason:
The table entry to be added already exists on the database.
System Action:
None.
User Action:
Change the name of the record required or use the update option to modify the existing record.
Reason:
The requested table entry does not exist on the database.
System Action:
None.
User Action:
Correct the name of the requested record and retry, or use the ADD option to create a new record.
Reason:
The table definition for the requested record does not exist in the database.
System Action:
None.
User Action:
Correct the name of the table definition required, or use the ADD option option in the Table Definition Menu to create a new definition.
Reason:
Entry records cannot be added to the requested table because the table definition does not have an edit type of TABLE.
System Action:
None.
User Action:
None.
Reason:
The requested command cannot be used in the current window.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
None.
Reason:
An attempt was made to copy a table entry from one table to another, but there were conflicts between the original and target table definitions.
System Action:
The request is rejected.
User Action:
None.
Reason:
The requested command is not allowed on the currently displayed window.
System Action:
None.
User Action:
Erase the command from the command line.
Reason:
The requested page number is not present in the current series of panels.
System Action:
The request is rejected.
User Action:
Correct the page number entered in the command line and retry.
Reason:
A request was made to add a Table Entry that already exists.
System Action:
The request is rejected.
User Action:
Correct the value of the entry that you want to add and then retry.
Reason:
A request was made to save or file a Table Entry with an abbreviated value that has already been used for another entry in the same table.
System Action:
The request is rejected.
User Action:
Change the abbreviated value of the entry and retry.
Reason:
$TICALL was invoked, but a required keyword parameter was omitted.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
$TICALL was invoked with an invalid value in the FUNC keyword parameter.
System Action:
The request is rejected.
User Action:
Specify a correct value for the FUNC keyword parameter.
Reason:
$TICALL was invoked, but too much data was provided on the specified operand.
System Action:
The request is rejected.
User Action:
Specify a valid value for the parameter.
Reason:
An invalid date was specified for the parameter named.
System Action:
The request is rejected.
User Action:
Specify a date in the format yyyymmdd, where yyyy is a valid four digit year, mm is a valid 2 digit month and dd is a valid (2 digit) day of the month. eg 19911225 is the 25th of December 1991.
Reason:
An expiry date was specified, but it was before the starting date.
System Action:
The request is rejected.
User Action:
Specify an expiry date which is the same as or later than the start date.
Reason:
A time was specified, but it was not in the correct format for a time.
System Action:
The request is rejected.
User Action:
Specify a correct time in the format hh.mm.ss where hh is the hour (a number from 0 to 24), mm is the minutes past the hour (a number from 0 to 59), ss is the second within the minute (0 to 59). hh.mm.ss must be in the range 00.00.01 to 24.00.00
Reason:
An end time was specified, but it was before the starting time.
System Action:
The request is rejected.
User Action:
Specify an end time which is the same as or later than the start time.
Reason:
An invalid number was specified for the specified parameter.
System Action:
The request is rejected.
User Action:
Enter a valid number (integer).
Reason:
An invalid value was specified for the FTYPE parameter.
System Action:
The request is rejected.
User Action:
Specify a valid value for FTYPE. Valid values are MONTHS, DAYS and TIME.
Reason:
An invalid day was specified for the specified parameter.
System Action:
The request is rejected.
User Action:
Specify a valid value. The DAYLIST parameter may be blank, or a list of days of the week in the form (MON,TUE,WED,THU,FRI,SAT,SUN). The parentheses may be omitted.
Reason:
An invalid value was specified for the parameter.
System Action:
The request is rejected.
User Action:
Specify either YES or NO for the parameter.
Reason:
An invalid value was specified for the parameter.
System Action:
The request is rejected.
User Action:
Specify either ACTIVE or INACTIVE for the parameter.
Reason:
An invalid value was specified for the parameter.
System Action:
The request is rejected.
User Action:
Specify a non-zero number for the parameter.
Reason:
An invalid value was specified for the parameter.
System Action:
The request is rejected.
User Action:
Specify MON, LOG or SYS for the parameter.
Reason:
An invalid value was specified for the parameter.
System Action:
The request is rejected.
User Action:
Specify a valid userid for the parameter.
Reason:
An invalid value was specified for the parameter.
System Action:
The request is rejected.
User Action:
Specify a frequency which is more than the stated minimum. The minimum value allowed is set by the SYSPARMS EVCMDMIN command.
Reason:
An invalid value was specified for the parameter.
System Action:
The request is rejected.
User Action:
Specify a valid name (PDS name rules). The name may be up to the length specified in the message text.
Reason:
If specified, the DAYLIST value must contain the day, P2 for compatibility with the SDATE (start date) which falls on that day when the FTYPE (frequency type) is DAYS and the FREQ (frequency) is a multiple of 7.
System Action:
The add or update timer request is rejected.
User Action:
Change the DAYLIST value to P2 or leave it unspecified and retry. Changing the value of SDATE and/or FREQ will also correct the incompatibility error.
Reason:
The timer was saved, but timer processing is not active.
System Action:
The timer definition is stored in the saved timers file.
User Action:
None.
Reason:
The timer already exists in the saved timer file. Saved timer processing is not active.
System Action:
The existing definition is not changed.
User Action:
Update the timer definition by using PUT rather than ADD, or alter the name to add a new definition.
Reason:
The timer was not saved due to an error on the saved timer file. Saved timer processing is not active.
System Action:
The request is not processed.
User Action:
Check the VSAMFDBK code to determine the cause of the error. Correct and retry.
Reason:
An attempt was made to ADD, PUT or DELete a timer with SAVE=NO specified but timer processing was not active.
System Action:
The request is not processed.
User Action:
Correct the error and retry.
Reason:
An attempt was made to ADD a timer but it was already defined.
System Action:
The request is not processed.
User Action:
Correct the error and retry.
Reason:
Timer processing has issued the command for the timer definition of the named 'class.subclass.name'. Only the first 80 characters of the command are displayed.
System Action:
The command is issued.
User Action:
None.
Reason:
The timer was not saved due to an error on the saved timer file. It was added to the table of active timers.
System Action:
The timer is defined in the timer table but could not be saved. It will remain only until SOLVE is stopped.
User Action:
Check the VSAMFDBK code to determine the cause of the error. Correct and retry.
Reason:
The timer was ADDed or PUT successfully. The current status (ACTIVE or INACTIVE) is displayed.
System Action:
The timer is defined. If is is ACTIVE the command will be executed at the correct intervals.
User Action:
None.
Reason:
The timer was deleted from the file. Timers are not being processed at this time.
System Action:
The timer is deleted.
User Action:
None.
Reason:
An attempt was made to GET or DELete a timer, but it is not defined.
System Action:
The request is not processed.
User Action:
Correct the error and retry.
Reason:
The timer was not deleted due to an error on the saved timer file.
System Action:
The request is not processed.
User Action:
Check the VFS file to determine the cause of the error. Correct and retry.
Reason:
The timer was not in the table of active timers, but has been deleted from the saved timer file.
System Action:
The saved timer definition is deleted.
User Action:
None.
Reason:
The timer has been deleted from the table of active timers. Unless SAVE=NO was specified, the timer was also deleted from the stored timer file.
System Action:
The timer definition is deleted.
User Action:
None.
Reason:
Timer processing is starting. The timer named is subject to catch up processing and the command should have been issued at the given date and time. The command is now issued.
System Action:
The command is issued. The command will only be issued once, regardless of the number of times it would have executed if the system had been operative the whole time.
User Action:
None.
Reason:
The timer was not updated due to an error on the saved timer file. Timer processing is not active.
System Action:
The request is not processed.
User Action:
Check the VFS file to determine the cause of the error. Correct and retry.
Reason:
The timer was updated in the active timer table, but the update was not saved due to an error on the saved timer file (VFS).
System Action:
The timer is updated in the timer table only. The changes will be effective until SOLVE is stopped.
User Action:
Check the VFS file to determine the cause of the error. Correct and retry.
Reason:
The timer definition was retrieved from the timer table and the saved definition.
System Action:
The timer information is displayed.
User Action:
None.
Reason:
The timer definition was retrieved from the timer table. The timer was not stored so some information (creation and modification statistics) is not available.
System Action:
The timer information is displayed.
User Action:
None
Reason:
The timer definition was retrieved from the timer table. Some information (creation and modification statistics) is not available due to an error on the saved timer file.
System Action:
The timer information is displayed.
User Action:
Determine the cause of the file error on the VFS file, correct and retry if necessary.
Reason:
The timer definition was retrieved from the saved timer file. The timer is not in the active timer table or timer processing is not active.
System Action:
The timer information is displayed.
User Action:
None.
Reason:
An attempt was made to start timer processing but it was already active.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to start timer processing, but no timers can be restored because the VFS file is not authorised for this user.
System Action:
Timer processing is ready, but no timers are defined.
User Action:
Contact the System Administrator to obtain authorisation to access the VFS file.
Reason:
Timer processing was started successfully and the displayed number of saved timers were restored. Some timers may have been deleted because they were past their expiry date.
System Action:
Timer processing is now active.
User Action:
None.
Reason:
An unexpected message was received when attempting to set the wakeup timer for timer processing. The message indicating the problem is in the activity log.
System Action:
Timer processing will not be able to proceed.
User Action:
Refer to the activity log to determine the cause of the error, correct and retry.
Reason:
An attempt was made to stop or list timer processing, but it was not active.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to alter timer processing, but you are not authorized to perform the action.
System Action:
The request is rejected.
User Action:
Obtain authorization from the System Administrator to issue the purge command. Normally USERAUTH of 2 is required.
Reason:
An unexpected message was received when attempting to purge the wakeup timer for timer processing. The message indicating the problem is in the activity log.
System Action:
Timer processing is not affected.
User Action:
Refer to the log to determine the cause of the error, correct and retry.
Reason:
Timer processing was stopped successfully. All managed timers have been stopped, and will not be 'caught-up' when timer processing is restarted.
System Action:
Timer processing is stopped.
User Action:
None.
Reason:
Managed timer commands are executed (when they are due) using an AT command. An unexpected message was received when attempting to issue the command for the named timer.
System Action:
The command is not performed.
User Action:
Refer to the activity log for the message indicating the problem.
Reason:
This is a heading message for the $TICALL FUNC=LIST output. The timers which are listed following this message belong to the named class and subclass.
System Action:
None.
User Action:
None.
Reason:
This is the heading message for the $TICALL FUNC=LIST output.
NAME: The name of the timer within the CLASS and SUBCLASS
NEXT ACTIVATION: The date and time the timer will next be executed, or if the timer is inactive, *INACTIVE* will be displayed.
FTYPE: the frequency type of the timer, MONTHS, DAYS or TIME.
FREQ: the frequency of the timer in the above units.
DESCRIPTION: the user defined description associated with the timer.
System Action:
None.
User Action:
None.
Reason:
This is the detail message for the $TICALL FUNC=LIST output. Refer to the TI0133 message explanation for a description of the data.
System Action:
None.
User Action:
None.
Reason:
This message is displayed when a $TICALL FUNC=LIST command is issued and no timers match the CLASS, SUBCLASS and NAME supplied.
System Action:
None.
User Action:
None.
Reason:
This is the end of the $TICALL FUNC=LIST command output.
System Action:
None.
User Action:
None.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |