|
|
|
Reason:
An invalid shortcut, menu option, panel path or command was entered from the Primary Menu.
Navigating to the function you want from the Primary Menu can be done in any of these ways:
System Action:
None.
User Action:
Enter a valid shortcut, menu option, panel path, or command.
SHORTCUTS
Enter a shortcut name, preceded by a slash, at the ===> prompt (for example, /levels or /parms 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.
Shortcuts may also be combined with menu options (for example, /bcast.s or =/bcast.s).
Shortcuts can be invoked in two ways:
To retain and nest the current screen level, use a nested shortcut: /shortcut_name
Exit will bring you back to the last nested screen in this window. Screens may be nested to a maximum of 64 levels.
To close all currently nested screen levels, use a shortcut skip: =/shortcut_name
Exit will take you back to the Primary Menu. If you no longer need any nested screens, a shortcut skip saves storage and resources.
(If you are currently at the Primary Menu, a nested shortcut and a shortcut skip behave the same.)
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.
PANEL PATH
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 screens and effectively entering the path from the primary menu. (If you are currently at the Primary Menu, the skip character is not required.)
Frequently used panel paths have associated shortcuts. If you don't 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 screen and go straight to the function.
Entering == at the ===> prompt from any panel closes all nested screens and returns you to the Primary Menu.
Reason:
An attempt was made to exit with Fullscreen MAI sessions still in existence.
System Action:
None.
User Action:
Press Enter to return to the menu. Press F3/F15 to resume the logoff and terminate all MAI sessions.
Reason:
A user has attempted to exit the Primary Menu while current MAI sessions exist. The MAIESC system parameter is set to NO, preventing a user from exiting while there are current MAI sessions.
System Action:
The request is rejected.
User Action:
Terminate your MAI sessions before attempting to exit. If required the MAIESC system parameter may be set to YES or WARN to allow users to exit with active MAI sessions. In which case active MAI sessions will be force terminated.
Reason:
The user's request to continue processing without reconnection to earlier processing regions has been honoured.
System Action:
None.
User Action:
The RECONN command may be used to perform reconnection.
Reason:
The user's request to continue processing without reconnection to earlier processing regions has been honoured. In addition cancel processing for the disconnected region(s) was initiated.
System Action:
None.
User Action:
None.
Reason:
The primary menu is unable to display the named panel. The following message indicates the nature of the problem. In most cases a Panel Services message stating that the panel is undefined or incorrectly coded is related.
System Action:
The primary menu procedure terminates and the window is closed. This may result in user logoff.
User Action:
Report the problem to your installation help desk. If necessary a panels LIBPATH DEFINE may need to be issued. Also ensure that the distribution panels library is available.
Reason:
A function key was pressed which has no defined action in the current window.
System Action:
None.
User Action:
None.
Reason:
The ENTER key was pressed, but no option, command or shortcut was entered.
System Action:
None.
User Action:
Enter a valid shortcut, menu option, panel path, or command.
SHORTCUTS
Enter a shortcut name, preceded by a slash, at the ===> prompt (for example, /levels or /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 will be displayed in turquoise, to the right of the option description.
Shortcuts may also be combined with menu options (for example, /bcast.s or =/bcast.s).
Shortcuts can be invoked in two ways: 1. A 'nested' shortcut 2. A shortcut skip
To retain and nest the current screen level, use a nested shortcut:
/shortcut_name
Exit will bring you back to the last nested screen in this window. Screens may be nested to a maximum of 64 levels.
To close all currently nested screen levels, use a shortcut skip:
=/shortcut_name
Exit will take you back to the Primary Menu. If you no longer need any nested screens, a shortcut skip saves storage and resources.
(If you are currently at the Primary Menu, a nested shortcut and a shortcut skip behave the same.)
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.
PANEL PATH
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 screens and effectively entering the path from the primary menu. (If you are currently at the Primary Menu, the skip character is not required.)
Frequently used panel paths have associated shortcuts. If you don't 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 screen and go straight to the function.
Entering == at the ===> prompt from any panel closes all nested screens and returns you to the Primary Menu.
Reason:
The User Services option was selected from the Primary Menu, but the User Services procedure defined for the user was either:
- not found in the COMMANDS library
- has attempted to execute another NCL procedure that was not found in the COMMANDS library at the next, or a nested level.
System Action:
The request is rejected.
User Action:
Correct the name of the User Services procedure in the user's UAMS definition, or place the procedure in the user's commands library.
This message can occur for an undefined NCL procedure at a nesting level below the procedure defined in the user's UAMS record. As a result, the procedure name in the message text (P1) is the name of the User Services procedure in the user's UAMS record and is not necessarily the procedure that is in error or undefined.
Reason:
A command was invoked from the Primary Menu that ended with a non-zero return code. This non-zero return code was not accompanied with an error message and the success or otherwise of the command could not be determined.
System Action:
The command is highlighted.
User Action:
Check the success of the command from another source.
Reason:
The userid P1 is not authorized to access Operator Control Services and therefore the execution of commands is not allowed.
System Action:
The command is rejected.
User Action:
Contact the System Administrator if the function is required.
Reason:
The procedure P1 was not found when the selected option was made. This procedure is defined as the procedure to execute when the selection is made.
System Action:
The selection is rejected.
User Action:
Contact the System Administrator.
Reason:
The user's request to continue processing without reconnection to earlier processing regions has been honoured. In addition cancel processing for the disconnected region(s) was initiated.
System Action:
None.
User Action:
None.
Reason:
This message appears as the option description for the CI option on the Reconnection menu.
System Action:
None.
User Action:
None.
Reason:
This message appears as the option description for the CC option on the Reconnection menu.
System Action:
None.
User Action:
None.
Reason:
This message appears as the option description for a reconnection on the Reconnection menu.
System Action:
None.
User Action:
None.
Reason:
This message appears as the heading line of the line messages display. The line messages following the heading line were issued whilst the screen was in fullscreen mode.
System Action:
None.
User Action:
Review the line messages displayed. They may indicate indicate an application or system error condition. If a problem is indicated then notify your help desk.
Reason:
The scroll amount entered is not a recognized scroll value.
System Action:
Scrolling is disabled.
User Action:
Reenter a valid scroll amount. Valid values are CSR, DATA, PAGE, HALF or a numeric value.
Reason:
The search character string P1 was found.
System Action:
None.
User Action:
None.
Reason:
An invalid command was entered from the Environment Messages display.
System Action:
The command is rejected.
User Action:
Re-enter a valid command.
Reason:
The specified character string was not found from the point of the search start to the top of the data.
System Action:
None.
User Action:
Repeat the find to continue the search from the end of the data.
Reason:
A request to display messages from the owning environments message queue could not be performed because there were no messages to display.
System Action:
None.
User Action:
None.
Reason:
An invalid find command option was specified.
The valid options are FIRST or F, LAST or L, NEXT or N, PREV or P.
The general syntax of the find command is - FIND xxx yyy , where xxx and yyy are both positional parameters and xxx represents the character string to be searched (the default and '*' are equivalent to the last string searched) and yyy is a directional option which can be one of FIRST, LAST, NEXT or PREV (the default being NEXT).
The search string can contain any characters and must be quoted if it contains blanks, asterisks, single quotes or double quotes. Quotes that are part of the search argument and are of the same type as the string is quoted in must be doubled up. For example to search for the string abc'xyz you can specify FIND "abc'xyz" and to search for the string abc'xyz"lmn you can specify FIND 'abc''xyz"lnm' .
The command name and the options can be abreviated to their first character.
System Action:
The find command is rejected.
User Action:
Correct the option and retry the command.
Reason:
An invalid find command string was entered.
The search string can contain any characters and must be quoted if it contains blanks, asterisks, single quotes or double quotes. Quotes that are part of the search argument and are of the same type as the string is quoted in must be doubled up. For example to search for the string abc'xyz you can specify FIND "abc'xyz" and to search for the string abc'xyz"lmn you can specify FIND 'abc''xyz"lnm' .
The general syntax of the find command is - FIND xxx yyy , where xxx and yyy are both positional parameters and xxx represents the character string to be searched (the default and '*' are equivalent to the last string searched) and yyy is a directional option which can be one of FIRST, LAST, NEXT or PREV (the default being NEXT).
The command name and the options can be abreviated to their first character.
System Action:
The find command is rejected.
User Action:
Correct the string and retry the command.
Reason:
The search character string P1 was not found.
System Action:
None.
User Action:
None.
Reason:
The specified character string was not found from the point of the search start to the bottom of the data.
System Action:
None.
User Action:
Repeat the find to continue the search from the start of the data.
Reason:
The specified character string was not found from the point of the search start to the top of the data.
System Action:
None.
User Action:
Repeat the find to continue the search from the end of the data.
Reason:
The search character string P1 was found.
System Action:
None.
User Action:
None.
Reason:
The environment mesages were successfully saved in the notepad.
System Action:
None.
User Action:
None.
Reason:
Your menu profile does not exist and the default menu style is being used. This message will be presented when you display the primary menu and there is no menu profile on the database. The default menu style settings of Classic primary menu format and Collapsed IP Summary (only available on TCP/IP products) were taken.
System Action:
Defaults used for rendering primary menu display.
User Action:
Use the PROFILE or PROF command to view and/or update your profile settings.
Reason:
The menu option P1 was invoked and the user returned back to the primary menu. P2 is the menu option's description.
System Action:
None.
User Action:
None.
Reason:
This is the title line issued by NCL procedure $NMSYVAR. This procedure is used to determine the current value of system variables on remote regions.
System Action:
Information lines follow for each variable requested.
User Action:
None.
Reason:
This is the information line issued by NCL procedure $NMSYVAR. P1 is the full name of the system variable. P2 is the actual contents of this variable.
System Action:
None.
User Action:
None.
Reason:
This message indicates the end of the display generated by the NCL procedure $NMSYVAR. It summarizes the number of variables displayed
System Action:
None.
User Action:
None.
Reason:
The terminal has been locked by the LOCK command or the terminal inactivity facility. The processing is interrupted until your current password is entered and verified.
System Action:
Waits for entry of the password. If the password verification fails then the user is reprompted. If the number of retries is exceeded then the user is disconnected.
User Action:
Enter your password to be verified.
Reason:
A LOCK request has been unable to perform panel processing. The panel P1 is not in the users panel path.
System Action:
The LOCK function terminates.
User Action:
Report the error to your system administrator.
Reason:
A LOCK function has verified the password and is terminating.
System Action:
The LOCK function terminates and the interrupted processing resumes.
User Action:
Continue the interrupted work.
Reason:
A LOCK function has reached the number of password retries allowed for the system.
System Action:
The user region is disconnected.
User Action:
Signon and reconnect to resume processing.
Reason:
A LOCK function has reached the number of password retries allowed for the system and has attempted to disconnect the region. The disconnect has failed and the user has been cancelled.
System Action:
The user region is terminated.
User Action:
Refer to the SOLVE log for messages indicating why the disconnection failed. The system may be in shutdown.
Reason:
The password entered to unlock the terminal is not valid for the user ID.
System Action:
The terminal is not unlocked. The retry counter is incremented. If the counter reaches the system password retry limit then the region is disconnected.
User Action:
Correct and re-enter.
Reason:
The password entered to unlock the terminal failed verification because the userid is not defined to the security subsystem.
System Action:
The terminal is not unlocked. The retry counter is incremented. If the counter reaches the system password retry limit then the region is disconnected.
User Action:
Notify your system administrator.
Reason:
A CA CCI call has completed.
P1 is the return code.
P2 is the error code.
P3 is the extended error code.
P4 is the error description.
P5 is the feedback code that indicates the kind of CCI call.
System Action:
The CA CCI call has completed.
User Action:
If the return code is not zero, investigate and correct the cause of the error.
Reason:
The Command Entry function has been requested from a region which does not have a full-screen interface, for example:
- A background user
- A remote operator (using ROUTE from another system)
System Action:
The command is rejected.
User Action:
Execute Command Entry (or a function which requires Command Entry) from an environment which has a real window; that is:
- Avoid submitting the command to a background region.
- Execute the command locally.
Reason:
The Command Entry function has been requested and the first parameter specifies OPT=COMMAND which indicates keyword=variable format. This format is only valid when $CMDENT is executed from another NCL procedure.
System Action:
The command is rejected.
User Action:
Use positional parameter format when invoking Command Entry in this environment.
Reason:
An attempt to change the internal command profile options has failed. -PROFILE ENV=CURRENT HOLD=9999 &&000CEPOP returned an unexpected message ( P1) .
System Action:
The profile was not changed
User Action:
Contact your systems administrator to determine why your profile cannot be changed. Verify that GLBL CEPOP is blank or contains a profile option which is valid for this environment
Reason:
The maximum number of messages to be captured has been reached.
System Action:
Additional messages are discarded and cannot be viewed.
User Action:
Either: * use the ERASE (K) command to clear the captured messages, or * increase the capture limit by entering a higher value in the LIMIT input field.
Reason:
The F4 key was pressed to request that the captured lines be printed but there are no lines captured.
System Action:
The function is ignored.
User Action:
Issue one or more commands, and so capture lines of data, before using this function.
Reason:
A request to print the captured lines has started. The Print Services request number ( P1 ) and number of lines to print ( P2 ) are shown.
System Action:
Lines are spooled to Print Services. Additional progress messages are displayed.
User Action:
Wait for the completion message.
Reason:
This is a print spooling progress message showing the number of lines spooled so far ( P1 ) and the total number of lines to print ( P2 ).
System Action:
Print spooling continues.
User Action:
Wait for the completion message.
Reason:
A request to print the captured lines has ended. The Print Services request number ( P1 ) is shown.
System Action:
None.
User Action:
None.
Reason:
The value specified in the LIMIT field is invalid because it was either: * omitted, or * a non- numeric value.
System Action:
None.
User Action:
Specify a numeric value and retry.
Reason:
The F6 key was pressed to retrieve a command from the Command Stack but there are no commands stacked.
System Action:
The function is ignored.
User Action:
Issue one or more commands before using this function.
Reason:
A value other than ON or OFF was specified in the highlighted field.
System Action:
None.
User Action:
Specify either ON or OFF and retry.
Reason:
A value of ON has been specified for both the EDIT and SCROLL fields. These are mutually exclusive and cannot both be specified as ON.
System Action:
None.
User Action:
Change the EDIT and/or SCROLL fields so that at least one of these is OFF.
Reason:
When editing lines, an invalid color was specified.
System Action:
None.
User Action:
Either omit the color specification to use the default (Green), or specify a valid color using one of the following:
G for Green
B for Blue
R for Red
Y for Yellow
W for White
P for Pink
T for Turquoise
Reason:
When editing lines, an invalid highlighting option was specified.
System Action:
None.
User Action:
Either omit the highlight specification to use the default (None), or specify a valid highlight option using one of the following:
N for None
U for Underline
B for Blink
R for Reverse
Reason:
A Minute-Minder Listener ($NMCP01Z) was started; however, a Listener is already running.
System Action:
The second Minute-Minder Listener terminates.
User Action:
Do not start a second Minute-Minder Listener while one is already running.
Reason:
An invalid value for P1 was supplied to the Minute-Minder Listener.
System Action:
The Minute-Minder Listener terminates.
User Action:
Start the Listener with a valid value for P1.
Reason:
The Minute-Minder Listener was started with an incompatible LOCPU/HICPU combination. The LOCPU value must be less than the HICPU value.
System Action:
The Minute-Minder Listener terminates.
User Action:
Start the Listener with a valid LOCPU/HICPU combination.
Reason:
The Minute-Minder Listener was started with an invalid data set name for the PMON unload data set.
System Action:
The Minute-Minder Listener terminates.
User Action:
Start the Listener with a valid data set name. The data set must be a PDS.
Reason:
The Minute-Minder Listener started successfully.
System Action:
The Minute-Minder Listener waits for CPU monitoring events.
User Action:
None.
Reason:
This message is issued when the Minute-Minder Listener starts successfully. It documents the parameters the Listener is using for its monitoring.
System Action:
The Minute-Minder Listener waits for CPU monitoring events.
User Action:
None.
Reason:
A command was issued to stop the Minute-Minder Listener; however, it is not active.
System Action:
None.
User Action:
None.
Reason:
You requested the Minute-Minder Listener to stop.
System Action:
The Minute-Minder Listener terminates.
User Action:
None.
Reason:
The Minute-Minder Listener terminated normally.
System Action:
The Minute-Minder Listener terminates.
User Action:
None.
Reason:
An attempt to read an INMC Link definition failed because the requested definition for link name ( P1 ) no longer exists on the VFS dataset.
System Action:
The request is rejected.
User Action:
Choose a different link name. This error may occur during browse or update of a definition when the record is deleted by another user.
Reason:
An attempt to add a new INMC link definition failed because there is already a definition of the same name.
System Action:
The request is rejected.
User Action:
Use the reason explanation to rectify the situation. If the problem is not obvious contact your systems administrator.
Reason:
An attempt to access the VFS dataset to read or write an INMC link definition failed. The file action ( P1 ) and failure reason ( P2 ) are shown.
System Action:
The request is rejected.
User Action:
Use the reason explanation to rectify the situation. If the problem is not obvious contact your systems administrator.
Reason:
The call to the procedure failed because the Keyword identified by P1 had an invalid value, identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your systems administrator.
Reason:
The call to the procedure failed because the identifier P1 is not of the correct type specified by P2 . For example: * TYPE=DOMAIN but ID= was the wrong format for a domain name
System Action:
The request is rejected.
User Action:
Contact your systems administrator.
Reason:
There are no INMC link definitions on file.
System Action:
None.
User Action:
Use the F4=Add function to add link definitions.
Reason:
There are no INMC link definitions on file whose link name starts with the specified prefix ( P1 ).
System Action:
None.
User Action:
Use the F4=Add function to add link definitions, or return to the previous panel and specify a different prefix.
Reason:
The transmission mode is neither Preferential or Rotate. As a result there are no sessions to display.
System Action:
None.
User Action:
None.
Reason:
The F5=Sessions command was used but either the link name or the transmission mode was blank.
System Action:
The request is rejected.
User Action:
Specify the link name and transmission mode and retry.
Reason:
A required field ( P1 ) was not specified.
System Action:
The request is rejected.
User Action:
Specify a value in the field and retry.
Reason:
An invalid value was specified for the field ( P1 ).
System Action:
The request is rejected.
User Action:
Specify a value in the field and retry. Refer to the full-screen help for field validation details.
Reason:
A field was specified ( P1 ) that is only applicable to simple transmission mode.
System Action:
The request is rejected.
User Action:
Either clear the field, or change the transmission mode.
Reason:
A field was specified ( P1 ) but the logmode field for the same session detail line was not present. The presence of the logmode field indicates that a session is to be defined; the field's abscence means that the session is not defined.
System Action:
The request is rejected.
User Action:
Either clear the field, or specify the logmode for the session.
Reason:
When defining a Rotate and Backup mode link, at least one session must be defined with a status of A (Active). No sessions were defined as active.
System Action:
The request is rejected.
User Action:
Ensure that at least one session is defined as active by specifying a status of A.
Reason:
Details were specified for a session, but the previous session details were omitted. Session details must be entered in consecutive rows and intermediate blank rows are not permitted.
System Action:
The request is rejected.
User Action:
Specify session details for the missing session(s).
Reason:
The F3=File or F4=Save function for the link definition was requested. The transmission mode specifies either Preferential or Rotate but there are no session details (the F5=Sessions function was not used).
System Action:
The request is rejected.
User Action:
Use the F5=Sessions function to define at least two sessions.
Reason:
The F3=File or F4=Save function for the link definition was requested. The transmission mode was changed to Preferential or Rotate mode from another transmission mode. The session details for new transmission mode are incomplete or invalid because the session details have not been displayed (the F5=Sessions function was not used).
System Action:
The request is rejected.
User Action:
Use the F5=Sessions function to update the session details.
Reason:
An attempt to display the status of an INMC link ( P1 ) failed because the link has been reset.
System Action:
The request is rejected.
User Action:
Use the F6=Refresh function to refresh the list.
Reason:
Errors were detected during the initialization process. P1 identifies the product name.
System Action:
None
User Action:
Examine the product activity log, determine the cause of the errors, and correct them.
Reason:
The initialization process has detected that a required map ( P1 ) is not installed in this region.
System Action:
None.
User Action:
Ensure the setup steps described in the installation and setup instructions have been performed to load the OSCNTL file with the appropriate map definitions for SOLVE.
Check that any maintenance has been applied.
Reason:
Region started with JCL parameter XOPT=NOPVLOAD, which disables the automatic option of loading persistent variables.
System Action:
Persistent variables are not loaded in this run.
User Action:
If the parameter is specified to fix the problem, restart the region without specifying XOPT=NOPVLOAD after correcting the situation. Default action, equal to specifying XOPT=PVLOAD is taken on restart.
Reason:
The initialization process has detected an internal error.
P1 is the error number.
P2 is the error message.
System Action:
Initialization continues; however, the region is probably unusable.
User Action:
If you are using $NMPARMS, fix the errors and start the region.
If you are not using $NMPARMS, contact your local Technical Support representative with a copy of the JCL log.
Ensure that maintenance is applied.
This message is followed by message BAIN7007 with more details.
Reason:
This message follows message BAIN7006 and provides more information about the error detected.
P1 is the NCL/OML procedure name.
P2 is the NCL/OML statement name.
P3 is the statement position in the line.
P4 is the source line number.
System Action:
Initialization continues; however, the region is probably unusable.
User Action:
If you are using $NMPARMS, fix the errors and start the region.
If you are not using $NMPARMS, contact your local Technical Support representative with a copy of the JCL log.
Ensure that maintenance is applied.
This message is followed by message BAIN7007 with more information.
Reason:
This message, following messages BAIN7007 and BAIN7007 indicates that there is another error in the initialization process.
System Action:
Initialization continues; however, the region is probably unusable.
User Action:
If you are using $NMPARMS, fix the errors and start the region.
If you are not using $NMPARMS, contact your local Technical Support representative with a copy of the JCL log.
Ensure that maintenance is applied.
This message is followed by message BAIN7007 with more information.
Reason:
This is the last message, issued when it is not possible to resume the program.
System Action:
Initialization continues; however, the region is probably unusable.
User Action:
If you are using $NMPARMS, fix the errors and start the region.
If you are not using $NMPARMS, contact your local Technical Support representative with a copy of the JCL log.
Ensure that maintenance is applied.
This message is followed by message BAIN7007 with more information.
Reason:
The initialization process for the product has started. The product name ( P1 ) and initialization phase ( P2 ) are indicated.
This message is only issued if the initialization process is under diagnostic control.
System Action:
None.
User Action:
None, diagnositic information only.
Reason:
The initialization process for the product has started. The product name ( P1 ) and initialization phase ( P2 ) are indicated.
This message is only issued if the initialization process is under diagnostic control.
System Action:
None.
User Action:
None, diagnositic information only.
Reason:
The procedure P1 which was nominated in a Parameter Group to be invoked to perform processing for that Parameter Group failed with return code
P2.
System Action:
Processing terminates.
User Action:
Correct the error in procedure P1 and retry the request.
Reason:
The number of buffers specified in the pool with buffer size P1 is invalid. The value must be numeric, greater than 2, less than 32,767 and less than 16,777,216 divided by P1.
System Action:
Field is set in error.
User Action:
Specify a valid number of buffers value.
Reason:
You specified an invalid value in the P1 field. The field selects the paths by which the panels in the library are editable. The valid values are as follows:
- List of path IDs separated by blanks or commas indicates that the panels in the library are editable by using those paths only.
- Blank or NO indicates that the panels in the library are not editable.
- YES indicates that the panels in the library are editable by using any of the specified paths.
System Action:
The field in error is highlighted.
User Action:
Correct the value.
Reason:
The field P1 is required if the field P2 is specified.
System Action:
Field is set in error.
User Action:
Specify a value for P1 or clear the value for P2.
Reason:
The field P1 is invalid. If must contain either YES or NO, a number between 1 and 999 or a kilobyte value between 1K and 9999K.
System Action:
Field is set in error.
User Action:
Specify a valid value for P1.
Reason:
The value P1 has already been specified in this Parameter Group.
System Action:
Field is set in error.
User Action:
Specify a unique value.
Reason:
The File ID P1 is not defined; therefore, it cannot be used in the
System Action:
User Action:
Reason:
The system cannot function correctly without at least the distributed MODS file being specified.
System Action:
Fields set in error.
User Action:
Specify at least one MODS file.
Reason:
The system cannot function correctly without at least one panel path specified.
System Action:
Fields set in error.
User Action:
Specify at least one panel path.
Reason:
A request to start an INMC link ( P1 is linkname) was successful.
System Action:
The link will only become active if/when the remote system starts a link back to this system (or one is defined dynamically).
User Action:
None
Reason:
The field P1 is required when the value of field P2 is P3.
System Action:
Field is set in error.
User Action:
Specify a value for P1.
Reason:
The log procedure P1 was started. The system then waited a few seconds before checking if the procedure was still running and found that it was no longer active. This indicates that the log procedure has errors and either terminated abnormally or ended prematurely.
System Action:
Parameter Group action fails.
User Action:
Check the log for the reason the procedure failed. Correct the error and reset the Parameter Group.
Reason:
The LSR pool specification specified an invalid buffer size.
System Action:
Field set in error.
User Action:
Enter a valid buffer size.
Reason:
The log file with ID P1 was not allocated because the key length for the file was invalid. The key length of the file was P2 and it should be a length of 20.
System Action:
The log file is not available for use.
User Action:
Change the parameters to specify a valid log file dataset and Action the parameter group.
Reason:
The system cannot function correctly without at least the distributed
System Action:
User Action:
Reason:
A request to start a link to the indicated system has failed.
System Action:
The link is not started.
User Action:
Review the Initialization Log for additional messages that indicate why the link failed to start.
Reason:
The field P1 is invalid. It must contain a valid hexadecimal number of three or four bytes.
System Action:
Field is set in error.
User Action:
Specify a valid value for P1.
Reason:
An attempt to set the SSI into a particular state could not be achieved. The current status of the SSI is P2 and this could not be changed to
P1 . This condition results in the SSI parameter group not completing its action of setting the required SSID and potentially attaching terminals. If the current status is RETRY-WAIT, then it indicates that the SSI started task has not started or that its SSID is incorrect.
System Action:
The attempt to set the SSI status is aborted. If the status of the SSI is RETRY-WAIT, then the system will retry connecting to the SSI every 30 seconds or as specified in the SSI Connection Retry Interval field.
User Action:
If the status of the SSI is RETRY-WAIT, then ensure that the SSI started task is started and that its SSID is correct. The SSI will be connected automatically when the SSI started task has initialized.
For other values of status, check the activity log for messages indicating the cause of the error.
Reason:
The field P1 must be null if the field P2 has a value of P3.
System Action:
Field is set in error.
User Action:
Clear field P1 or change the value of P2.
Reason:
You specified an invalid string for an equate. The string must not have embedded blanks and must not contain ampersand (&) characters.
System Action:
The field in error is highlighted.
User Action:
Correct the string.
Reason:
The use of + indicates that a blank character is required at the end of the equated text or string, consequently a single + is equivalent to equating to a blank, which is invalid. The field in error is P1 .
System Action:
Field set in error.
User Action:
Correct the field.
Reason:
The panel path specifies a collection of one or more libraries. Each library was searched and none of them contained the required distributed panels. The path must contain the distributed panels for the system to function correctly.
System Action:
Field set in error.
User Action:
Ensure that at least one library contains the distributed panels. It is recommended that the distributed panel libraries be specified as the last libraries of the path.
Reason:
The file ID specified is invalid for the log procedure P1. The log procedure P1 requires log file IDs to be of a specific format. The format is a fixed prefix followed by a two-character number in the range 01 to 07. The file ID must fall in the range P2 to P3.
System Action:
Field set in error.
User Action:
Ensure that the log file IDs are in the required format for the log procedure specified.
Reason:
No log files were allocated because of errors. Logging cannot be enabled until at least one log file is available for logging. The activity logging function is disabled until logs are allocated.
System Action:
Activity logging is disabled.
User Action:
1. From any panel, enter =/PARMS to list the parameter groups.
2. Review the LOGFILES parameter group. Change the parameters to specify valid log file datasets.
3. Press F6 (Action) to reactivate the logging function.
4. Press F3 (File) to save the changes.
Reason:
One or more log files were successfully allocated and logging was started. However some of the log files were not allocated. See any accompanying messages for further details of errors.
System Action:
Activity logging continues with those logs that were successfully allocated.
User Action:
Determine the reason the logs were in error. Correct the situtation and action the parameter group.
Reason:
The field contains an invalid value. The only valid values are 3270 or 560/20.
System Action:
Field is set in error.
User Action:
Specify either 3270 or 560/20.
Reason:
The LSR POOL ID must be 0 on this operating system. The other values are valid on OS/390 and z/OS systems only.
System Action:
Field is set in error.
User Action:
Specify 0.
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.
Reason:
A request was made to enable a data flow, using ISR, from a remote system. This request was successful. P1 indicates the data flow type (PPO, CNM, or SAW), P2 the direction (IN or OUT), and P3 is the linkname that identifies the remote system.
However, the data flow is also dependent on being enabled locally on the remote system (in the opposite direction).
System Action:
The data flow becomes active only if/when the remote system enables the relevant interface (PPO, CNM or SAW) locally in the opposite direction.
User Action:
If the data flow is not happening, check whether it has been enabled locally on the remote system, and that the flows are in opposite directions, for example: - Local=IN and Remote=OUT
- Local=OUT and Remote=IN
That is, use the ISRIN parameter group on one system, and the ISROUT parameter group on the other system.
Reason:
A request to enable ISR for a specific data flow type ( P1 is PPO, CNM, or SAW) for the direction ( P2 is IN or OUT) on the indicated link ( P3 ) has failed.
System Action:
The ISR data flow is not enabled.
User Action:
Review the Initialization Log for additional messages that indicate why the ISR enable failed.
Reason:
Connections to NetView regions require the Netmaster Automation region to be configured with the NetView Connect option.
System Action:
The field in error is highlighted.
User Action:
Specify NO in the highlighted Is the ISR Link to NetView? field. If connections to NetView regions are required, contact your systems administrator and request that the region is reconfigured with the NetView Connect option (PROD=NVC).
Reason:
This region is configured to run in a VTAM Generic Resource Environment, but the Sub System Interface ID field is not set correctly.
System Action:
Initialization fails.
User Action:
Set the Sub System Interface ID field and action this parameter group.
Reason:
The system SYSDB path definition has been dropped.
System Action:
There is no system SYSDB path until one is redefined.
User Action:
None.
Reason:
File ID P1 has been removed from the system SYSDB path, closed, and unallocated.
System Action:
None.
User Action:
None.
Reason:
File ID P1 has been allocated and opened for use as a SYSDB with the indicated access ( P2 = RW or RO) and share option ( P3 =NONE, LSR, or RLS). The data set name is P4.
System Action:
None.
User Action:
None.
Reason:
The system SYSDB path definition has been defined with the indicated access path ( P1 ):
- INPUT: Entities can be retrieved.
- UPDATE: Entities can be retrieved and maintained (add, update, delete) in the first SYSDB file ID only.
Note: The access level is determined by the access defined for the first (or only) SYSDB file ID in the concatenation:
- UPDATE if the file access is RW (read-write)
- INPUT if the file access is RO (read-only)
System Action:
None.
User Action:
None.
Reason:
This prefix value is already defined as an MAI ACB pool prefix.
System Action:
The update is rejected.
User Action:
Ensure unique values are used for each MAI pool prefix specification.
Reason:
An attempt to allocate and open a file for use as a SYSDB (file ID P1 ) has failed. The failure message ( P2 ) indicates the reason.
System Action:
The system SYSDB concatenation is restored. The restoration is recorded by a set of messages starting with BAINWI41 and ending with BAINWI43.
User Action:
Use the failure reason to identify the cause, make the appropriate changes, and retry.
Reason:
An error occured while redefining the system SYSDB concatenation path. As a result, the current SYSDB path is restored.
System Action:
The current system SYSDB concatenation path is restored. Additional messages indicate the files that are restored and the completion of the restoration.
User Action:
None.
Reason:
This message occurs after BAINWI41, while the system SYSDB concatenation path is being restored. The message indicates that file ID P1 has been reallocated and opened for use as a SYSDB.
System Action:
None.
User Action:
None.
Reason:
This message occurs after BAINWI41, while the system SYSDB concatenation path is being restored. The message indicates that the SYSDB path has been restored.
System Action:
None.
User Action:
None.
Reason:
The value specified for Sub-System Interface ID is invalid. The special value NO indicates that the region is not to be connected to an SSI. The value NO is equivalent to setting the field to blank and, for this reason, the field is blanked out.
System Action:
The field is set to blank.
User Action:
None.
Reason:
The number of buffers specified in pool p1 for the p2 buffer sizes was increased to the required system minimum. This pool and these buffer sizes are used by system data sets to maintain system performance and integrity.
System Action:
The number of buffers is altered to the minimum values for the p2 buffer sizes in pool p1.
User Action:
None. You can specify more buffers for these sizes, but not less.
Reason:
The highlighted field must be one of the following:
- A number between 257 and 65535
- The word "NONE" indicating that this system should not listen for inbound connections
- Omitted, to reinstate the previous value
System Action:
The field is highlighted as an error.
User Action:
Enter a correct value.
Reason:
The value entered for the port defined in P1 (which is either the web interface port or the connections port) is already assigned to the port indicated by P2 . These two ports must have different values.
System Action:
The port number is highlighted as an error.
User Action:
Enter a different value for the port number.
Reason:
The highlighted field must have a valid 1 to 8 character name.
System Action:
The field is highlighted as an error.
User Action:
Enter a correct value.
Reason:
You have requested that events of type p1 be received. However this type of event is not available from TCPaccess versions prior to 5.2
System Action:
The information based on these events is not available.
User Action:
None.
Reason:
The TCP/IP software type and the type's specific details have not been specified. The TCP/IP software type must be specified in the SOCKETS parameter group.
System Action:
The TCP/IP interface is not started. This may affect the functioning of other licensed components.
User Action:
Specify the TCP/IP software type and the type's specific details in the SOCKETS parameter group. You can access the list of parameter groups by entering the /PARMS shortcut.
Reason:
The TCP/IP software type of P1 was invalid. The system will assume that the software type is IBM.
System Action:
A software type of IBM is used and processing continues.
User Action:
Update the parameter with a valid value.
Reason:
The value for field P1 cannot be less than 5 minutes (00.05).
System Action:
Field is set in error.
User Action:
You must set a value greater than or equal to 5 minutes.
Reason:
The TCPIP STOP command was issued and confirmation for its activation has not arrived. The current status of the interface is P1.
System Action:
The request fails.
User Action:
Check the log for additional messages and correct any parameter errors. If the error persists then contact your system administrator.
Reason:
The port number P1 is already being used as the Inbound Connections Port. The Telnet port must be a different number or SHARED.
System Action:
Field is set in error.
User Action:
Specify a different port number or SHARED.
You can specify SHARED to share the Inbound Connections Port.
Reason:
The port number P1 is already being used as the WebCenter Port. The Telnet port must be a different number, it cannot be shared with the Web Interface.
System Action:
Field is set in error.
User Action:
Specify a different port number or SHARED.
You can specify SHARED to share the Inbound Connections Port.
Reason:
The port number P1 has already been specified for field P2. The Telnet port must be a different number or SHARED.
System Action:
Field is set in error.
User Action:
Specify a different port number or SHARED.
Reason:
The TCP/IP Software Type cannot be changed because there are linked regions that use this information to communicate with this region.
System Action:
The field in error is highlighted.
User Action:
To change the TCP/IP Software Type, you must first unlink this region.
Reason:
The IP Port for Inbound Connections cannot be changed because the old IP port is used by linked regions to communicate with this region.
System Action:
Field is set in error.
User Action:
To change the IP port number, you must first unlink this region.
Reason:
The TCP/IP interface failed to start. Another attempt to start the interface will be made after the interval P1 has expired.
System Action:
The parameter group completes successfully and a timer is set to re-action it after the interval P1 expires.
User Action:
None.
Reason:
The TCPIP command was issued to either START or STOP the TCP/IP interface. P1 is either START or STOP. The request failed and the previous message or messages will indicate the reason.
System Action:
The request fails.
User Action:
Contact your systems administrator.
Reason:
The initialization for TCP/IP tried to allocate a dataset to the DD name P1. No suitable data sets could be found.
System Action:
The DD is not allocated.
User Action:
Specify a valid data set name that exists.
Reason:
Initialization failed to allocate a data set P2 with the DD name P1 .
System Action:
The DD is not allocated. Processing continues.
User Action:
Enter a valid data set name for the data set required.
Reason:
The web menu options for P1 have been registered to the WebCenter interface P1 is the name of the component for which the menu was registered.
System Action:
None.
User Action:
None.
Reason:
The web port cannot be set if there are no components configured that have a web interface implemented.
System Action:
Field set in error.
User Action:
You must set the field to NONE. Alternatively, you can restart the system with a product specified that has a web interface.
Reason:
The value provided for the WebCenter SDK User Directory is not a valid HFS path.
System Action:
Field set in error.
User Action:
Either provide a valid HFS path or leave the field blank.
Reason:
You have entered an incorrect value.
System Action:
The value is rejected.
User Action:
Enter SAF if your server certificates are stored by your security system (CA Top Secret, CA ACF2, or RACF) or FILE if your server certificates are stored in an HFS file.
Reason:
An SSL profile named P1 has been created. SSL processing of WebCenter requests will use this profile.
System Action:
Processing continues.
User Action:
None.
Reason:
The server certificate named P2 will be used for SSL processing. A handle named P1 has been created to refer to this certificate.
System Action:
Processing continues.
User Action:
None.
Reason:
Server certificates will be retrieved from P1. P2 identifies which certificate to use.
Note: No validation is performed for the existence of the server certificate.
System Action:
Processing continues.
User Action:
None.
Reason:
Specifies whether SSL is used by web browsers to access WebCenter.
System Action:
Processing continues.
User Action:
None.
Reason:
The value provided is not a valid host name, IPv4, or IPv6 address. If a host name is specified, it must be a label or a sequence of labels separated by dots. Labels must start with a letter and can contain letters, numbers, and the hyphen character (-). Other special characters are not permitted.
Examples: 192.10.23.24, my.host.com, and los-angeles.ARN24
System Action:
The field is highlighted in error.
User Action:
Specify a valid IP host name or address.
Reason:
Host override P1 cannot be confirmed as valid. Either the overriding host name is not recognized by NSLOOKUP or the IP address is not associated with the stack used by this region, as specified in the SOCKETS Parameter Group (/PARMS).
System Action:
None.
User Action:
If the override value is invalid, correct it in the WEBCENTER parameter group (/PARMS). The value may be valid; this message can be caused by a domain name server problem.
Reason:
WebCenter initialization has failed, and its status could not be determined.
System Action:
No recovery is possible, and initialization fails.
User Action:
Contact Technical Support.
Reason:
The data set P2 has been read in preparation for building the DNR static cache. P1 host names were retrieved from the data set.
System Action:
None.
User Action:
None.
Reason:
The DNR static cache is not in use in this region. The DNR static cache is loaded from the hosts.local or the etc.ipnodes data set, or both, specified in the SOCKETS parameter group. If the data set is not specified, or the data sets are empty, DNR functions without a static cache, that is, all NSLOOKUP requests are resolved using the Domain Server only.
System Action:
None.
User Action:
None.
Reason:
An IPv6 address has been entered in the Access URL Host Override field, but the sockets API supports IPv4 addresses only.
System Action:
The field is highlighted in error.
User Action:
Specify a host name or IPv4 address in the Access URL Host Override field. Alternatively, check the SOCKETS parameter group (/PARMS). For IPv6 support, the TCP/IP Software Type must specify IBMV6.
Reason:
The filter statement specified on line p1 was invalid. p2 provides the reason for the error.
System Action:
The filter is rejected, and the panel set in error.
User Action:
Correct the filter statement on line p1 and retry.
Reason:
A range has been detected in the server port list and is not allowed.
System Action:
The Server Port list is rejected, and the panel set in error.
User Action:
A range is usually indicated by the presence of the : or - characters. Remove these characters from your Server Port list.
Reason:
Initialization has successfully completed. The process will now attempt to connect to the remote host. P1 is the protocol used in the connection.
System Action:
None.
User Action:
None.
Reason:
The connection manager has terminated for protocol P1.
System Action:
None.
User Action:
See previous messages.
Reason:
A keyword parameter was either not specified or was specified with an invalid value. The keyword parameter was P1 and the value was P2.
System Action:
The request is rejected and processing terminates.
User Action:
Specify the keyword parameter with a valid value.
Reason:
A request to act as the P1 process for P2 failed because another process was already performing the function. If KILLPREV=YES was specified then this process could not be flushed.
System Action:
The request is rejected and processing terminates.
User Action:
Try the action later or specify KILLPREV=YES to terminate the current process acting as the P1 for P2.
Reason:
The link manager could not continue processing because the service package P1 did not exist or the necessary procedure P2 did not exist in the package.
System Action:
Processing terminates.
User Action:
Ensure all required procedures are supported by the package or that the package name is correct.
Reason:
An error occurred executing a TCP/IP socket function. P1 is the function being performed, P2 is socket ID, P3 is the return code from the function, P4 is the feedback code from the function, P5 is the protocol being used, P6 is the port number at the remote host and P7 is the remote host name or address (if applicable).
System Action:
The request fails and the connection will be retried.
User Action:
Ensure that the Host Name/Address and Port Number are correct. Check the error codes to determine the exact nature of the error. More information may follow in subsequent messages.
Reason:
This message described additional information associated with a previous error. P1 is the vendor software specific error code and P2 is a description of the socket error number received. The vendor specific code may not be present.
System Action:
None.
User Action:
See related messages. Check the error codes and description to determine the exact nature of the error.
Reason:
A request to terminate the P1 protocol client/server process P2 was accepted. The process will terminate.
System Action:
Processing terminates as requested.
User Action:
None.
Reason:
A connection was successfully established with a remote system. The protocol being used is P1, the socket identifier is P2 and the port is
P3. The remote system is on address P4 with port P5.
System Action:
None.
User Action:
None.
Reason:
A connection failed and has been automatically scheduled to be retried in P2 minutes. The connection is for protocol P1.
System Action:
None.
User Action:
None.
Reason:
A request to act as the Client process failed because the remote host name/address P1 did not respond.
System Action:
Processing terminates.
User Action:
Ensure that the correct host name/address is specified and retry the request again.
Reason:
Initialization has completed successfully. The process is now attempting to register on a port. P1 is the protocol used in the connection, and P2 is the port number being registered for.
System Action:
None.
User Action:
None.
Reason:
Registration was successful for protocol P1 . The port that was registered is P2 , and the socket identifier is P3 .
System Action:
None.
User Action:
None.
Reason:
The remote client for a specific connection has terminated the connection to P1 .
System Action:
Processing terminates as requested.
User Action:
None.
Reason:
Initialization has completed successfully for a specific server. The protocol is P1 and the port which the client connected to is P2 . The socket being transferred is P3 .
System Action:
None.
User Action:
None.
Reason:
The Link or Domain Name field cannot be specified for certain options when the system is a subordinate in a multisystem complex.
System Action:
None.
User Action:
Blank out the Link or Domain Name field and work on the local system only.
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:
An attempt to acquire the lock with primary name=Monitor and minor name=Record.Collector failed with return code P1.
System Action:
The Monitor Record Collector procedure terminates.
User Action:
This usually indicates that there is already an instance of $NMMC000 (the Monitor Record Collector) running.
Reason:
A DIAG64 call to load the named segment P1 failed with return code P2.
System Action:
The calling procedure terminates.
User Action:
For more information, see the supplied return code in Responses in the chapter "DIAGNOSE Code X'64' - Named Saved Segment Manipulation" in CP Programming Services.
Reason:
An Inter User Communication Vehicle (IUCV) P1 operation has failed.
System Action:
The calling procedure terminates.
User Action:
Check that the other virtual machine in this IUCV connection is running. Check the OPTION IUCV statements in the directory entries for both virtual machines involved in this IUCV connection.
Reason:
An Inter User Communication Vehicle (IUCV) REPLY was issued to release a *MONITOR block of storage. The response indicates that the data was overwritten before it was copied.
System Action:
The current block of *MONITOR data is discarded. Processing continues.
User Action:
Ensure that the CA NetMaster virtual machine is assigned the necessary priority to ensure that it can process the data received from the *MONITOR system service in a timely manner.
Reason:
The CP command P2 failed with return code P1.
System Action:
Processing terminates.
User Action:
Dependent on CP command. Check subsequent NMMC00007 messages containing CP command output.
Reason:
This is output from a failed CP command.
System Action:
Processing terminates.
User Action:
Use this output to diagnose why the CP command from message NMMC00006 failed.
Reason:
This message indicates the end of CP command output contained in the series of NMMC00007 messages preceding this.
System Action:
Processing terminates.
User Action:
Use output from preceding LMDS00006 and LMDS00007 messages to determine which CP command failed and why.
Reason:
The menu option you selected is available only on focal point systems within your multi- system complex. This region is not a focal point system.
System Action:
The request is rejected.
User Action:
Logon to a focal point system to use this option.
Reason:
SAF authorization check completed successfully.
System Action:
Access is authorized.
User Action:
None.
Reason:
An internal call to the $NMSEC security procedure was invalid.
System Action:
Access is denied.
User Action:
If the security procedure has been modified, check to see if the code is correct. If it is correct or if the procedure has not been modified, contact Technical Support.
Reason:
An internal call to the $NMSEC security procedure used an invalid call type.
System Action:
Access is denied.
User Action:
If the security procedure has been modified, check to see if the code is correct. If it is correct or if the procedure has not been modified, contact Technical Support.
Reason:
The user, P2 , was not authorized for the P1 function.
System Action:
User access is denied, and the attempt is logged.
User Action:
Contact your system security personnel to gain access.
Reason:
A call to the UAMS security subsystem failed. The call was made on behalf of the P1 user ID from the P2 region.
System Action:
User access is denied, and the attempt is logged.
User Action:
This is an internal error. Contact Technical Support.
Reason:
A SAF call to verify access to a resource failed.
RC is the return code from the SAF interface (UTIL0039) SFRC is the sub-function return code SFREAS is the sub-function reason code ENV is environmental information
The most common RC/SFRC combinations are:
04 PROGRAM ACTIVATION FAILURE 04 Program not APF-authorized 08 Invalid parameter 0C Missing parameter 10 Parameters inconsistent
08 SAF INTERFACE FAILURE SAF/RACROUTE return codes: 04 Requested function was not processed 08 Requested function was processed, but failed
12 ACCESS VERIFICATION FAILURE RACROUTE REQUEST=VERIFY return codes: 04 No security profile defined 08 Password invalid 0C Password expired 10 New password invalid 14 Group definition is missing 18 Security exit denied access 1C User temporarily revoked 20 Security system not active 24 Access to group is revoked ?? Others as per specific security subsystem
16 ACCESS AUTHORIZATION FAILURE RACROUTE REQUEST=AUTH return codes: 04 Resource is not security protected 08 Resource access not allowed
99 NO ENTRY PARAMETERS
System Action:
User access is denied.
User Action:
Contact your system administrator. Use the error codes and messages provided above to investigate the cause of the error.
You also need:
- The SAF RACROUTE macro documentation
- The messages and codes documentation for your external security system (RACF, ACF2, or Top Secret)
Ensure that the region is running out of an authorized load library. Ensure that your external SAF security system is active.
Ensure that your security administrator has set up SAF security for use with this region correctly.
Reason:
A user tried to access a resource. A SAF call was done to check the user's authority level, but failed because the resource was not SAF protected. This message was written to the activity log, followed by the NMSEC019 message that lists the user ID, resource, and requested access.
System Action:
User access is denied.
User Action:
Ensure that your security administrator has set up SAF security for use with the region correctly.
Reason:
A user did not have the level of access required to perform the requested function. This message was written to the activity log, followed by the NMSEC019 message that lists the user ID and requested access.
System Action:
User access is denied.
User Action:
Contact your security administrator to gain access.
Reason:
This message was logged following any SAF check failure messages. It contains the parameters used by the failing SAF RACROUTE macro call. These parameters may include:
USRID - the ID of the user requesting access
GRPID - the user ID's SAF default group
CHKENV - the SAF checking environment (APPL|USER|FULL)
ACCTYP - the access type requested (READ|UPDATE|ALTER)
RSNAME - the SAF resource name
RSCLSS - the SAF class
System Action:
None.
User Action:
Use this information, and the information in the previous error message, to determine the cause of the error. The previous error message's User Action contains more specific suggestions.
Reason:
A CA Service Desk record was created from the alert identified by the resource and description of P3.
The record is identified by P1. P2 is its internal reference number. P4 indicates whether the record was created by automatic alert forwarding or by a trouble ticket request.
If the Service Desk server supports the ITIL user interface, an Incident record is created. Otherwise, a Request record is created.
System Action:
None.
User Action:
This record is now accessible to CA Service Desk users.
Reason:
A request was received to create a CA Service Desk record from the CA NetMaster alert with the serial number shown; however, the alert description field was not provided.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to create a CA Service Desk record from a CA NetMaster alert, but the attempt failed because of a communications error between CA NetMaster and the CA Service Desk server.
Specific error details are written to the activity log. The following are some likely causes of these failures:
System Action:
None.
User Action:
Perform the following steps:
You may need help from your Systems Programmer who implemented CAISDI/soap or your Service Desk Administrator to diagnose these conditions.
Reason:
This message provides diagnostic information for communication failures between CA NetMaster and CA Service Desk.
This communication uses the Web services SOAP protocol with the CA Common Services for z/OS CAISDI SOAP Client component named CAISDI/soap.
(CA NetMaster does not use CAISDI components CAISDI/med or CAISDI/els.)
|
Return Code |
Feedback Code |
|
|---|---|---|
|
4 |
0 |
RC 4 Feedback 0 can have a variety of causes, including, but not limited to:
|
|
4 |
4 |
CA Common Services component CAISDI/soap returned a non-zero return code; sets the values for:
|
|
8 |
0 |
Storage failure |
|
8 |
4 |
Shutdown request in progress |
|
8 |
8 |
NM SOAP subtask abend on this request |
|
8 |
12 |
NM SOAP interface disabled, excessive abends |
|
8 |
16 |
|
For more information, see the following:
System Action:
None.
User Action:
Perform the following steps:
The following are some likely causes of these failures:
You may need help from the systems programmer who implemented CAISDI/soap and/or your CA Service Desk Administrator to diagnose these conditions.
Reason:
This message is the detail line for the response to a SD* command help subcommand. A subcommand of '?' or 'HELP' lists the available SD commands and their parameters.
System Action:
None.
User Action:
None.
Reason:
You specified the SERVICEDESK type for the alert monitor trouble ticket interface or the alert forwarding destination.
Currently, Service Desk integration in this region is not fully implemented and you cannot specify the SERVICEDESK type.
Service Desk integration requires the following products:
- CA Service Desk r11 or later
- CA Common Services for z/OS r11 or later
System Action:
None.
User Action:
Discuss the implementation of CA Service Desk integration with your Systems Programmer and your CA Service Desk Administrator.
Before you can integrate with CA Service Desk from your region, you must complete the following tasks:
Ensure that Web Services access is also set up for this product. See the CA Service Desk documentation.
Note the URL/name of the server where this product is installed.
See the CA Common Services documentation and the Service Desk Integration Guide.
After you complete the tasks, you should be able to specify the SERVICEDESK type for the alert monitor trouble ticket interface or an alert forwarding destination.
Reason:
This is a CAISDI/soap interface trace message. It contains details of OML SOAP verb invocations and results. OML global variable glbl$SOAPTRC=YES controls the production of these messages.
System Action:
None.
User Action:
None.
Reason:
The SYSPARM ( P1 ) cannot be updated because it was previously updated by a Customizer parameter group ( P2 ).
System Action:
None.
User Action:
System parameters that are set by Customizer parameter groups can only be changed by updating and actioning the parameter group.
Reason:
An attempt to add a user or group definition to the UAMS database failed. P1 is the ID of the user, and P2 is the message set by the &SECCALL verb.
System Action:
The UAMS record is not added, and processing continues.
User Action:
Determine the cause of the error from the &SECCALL message. Correct the error, and rerun the $NMUAINI procedure to generate the default UAMS records.
Reason:
The default UAMS record generator encountered one or more errors when attempting to add user and group definition records to the UAMS database. P1 is the number of UAMS records which were not successfully created.
System Action:
None.
User Action:
Review the messages (with a prefix of 'BAUAIN') on the activity log to determine the cause of the errors.
Reason:
A SIGNON command was issued for the background user identified by P1 . This command failed. The reasons may be found in the activity log.
System Action:
Processing continues.
User Action:
Review the messages associated with the SIGNON command to determine the problem.
Reason:
An attempt to get a user from the UAMS database failed.
P1 is the ID of the user and P2 is the message set by the &SECCALL verb.
System Action:
Processing continues.
User Action:
Determine the cause of the error from the &SECCALL message, correct the background user name or rerun $NMUAINI with no parameters to define the background users for the region.
Reason:
A number of UAMS records were not found in the UAMS database. P1 is the number of UAMS records which were not found.
System Action:
None.
User Action:
Review the messages (with a prefix of 'BAUAIN') on the activity log to determine the cause of the errors.
Reason:
On this region, the UAMS dataset has been replaced by a full security exit.
System Action:
UAMS definitions will not be added for the background user IDs. Processing continues.
User Action:
None required. Default definitions are used if the security exit does not contain definitions for background user IDs.
Reason:
The user ID executing $NMUAINI does not have UAMS update authority.
System Action:
Background UAMS definitions are not added, and processing continues.
User Action:
To define the background users, log on to a user ID with UAMS update authority and run $NMUAINI again, with no parameters.
Reason:
The system maintenance level indicates a service pack has not been applied to the region. The VSAM file levels are not checked.
System Action:
None.
User Action:
If the region is created from a generally available (GA) product, apply service pack maintenance.
Reason:
The system maintenance level for distributed VSAM data is shown as follows:
P1 is the MODS level - menus, messages, web records, and so on.
P2 is the panels level.
P3 is the OSCNTL level - ASN1 maps.
P4 is RAMDB if Automation Services is licensed.
P5 is the RAMDB level.
Maintenance levels are in yymm, the year and month of service pack creation.
The level can also be one of the following values:
N/A indicates that the maintenance level cannot be found for the file.
user_id identifies the user that last changed the file record used to check maintenance levels. It is displayed if the maintenance level field does not start with "GL", indicating that the file may be corrupted or incorrect.
System Action:
None.
User Action:
If the levels match the LEVEL field in message N11416, the VSAM files are correct. If they do not match, check that the VSAM data installation performed at product installation is correct.
Reason:
The VSAM Monitor is active. P1 and P2 are optional monitoring conditions.
System Action:
The VSAM Monitor waits for VSAM EDS events.
User Action:
None.
Reason:
The VSAM Monitor is initializing and a procedure with NCLID P1 holds the lock required to complete initialization.
System Action:
The VSAM Monitor waits for the lock to be released.
User Action:
If this message persists, contact Technical Support.
Reason:
The VSAM Monitor has experienced message queue overflow. Some events may not be processed.
System Action:
The VSAM monitor continues to wait for events.
User Action:
Contact Technical Support.
Reason:
The VSAM Monitor has experienced message queue errors when profiling for events. P1 is the feedback code - 4 indicates a timeout and 8 is message queue overflow.
System Action:
VSAM monitoring terminates.
User Action:
Contact Technical Support.
Reason:
The VSAM Monitor has detected a file full or exceeding a threshold extent count defined in the Customizer Parameter Group, VSAMMONITOR. The Alert Text shows the extent count and High Allocated Relative Byte Address (HARBA) for data and index components. If extent count monitoring is active, data for any extent increase above the threshold is shown for up to the last 20 extensions. If a contiguous extent is obtained, the extent count does not increase; however, the HARBA for data or index is increased.
System Action:
If the file is full, no records can be added and attempts to add records fail; otherwise, file use continues.
User Action:
If the file is full, it must be increased in size. In some cases, for example, the VFS, USERIDS, OSCNTL, or RAMDB files, the region must be stopped to free the datasets that are crucial to system operation. In other cases, the file can be freed and another file allocated through a Customizer Parameter Group.
To recover from a file full:
If the extent count threshold is reached, a file full condition can probably be avoided by increasing the file size as described.
Reason:
The VSAM Monitor has received an event P2 but cannot process it. P1 is the error as follows:
Indicates that the DD name cannot be found in the event message.
Indicates that the UDB INFO request has failed with return code 8 or greater.
Indicates that the UDB INFO request failed to retrieve usage data.
Indicates that the Monitor procedure encountered processing errors and has stopped monitoring. The errors are logged in messages GP1015 and GP1016 and can be seen by issuing the ILog command for the Customizer Parameter Group VSAMMONITOR.
Indicates that the UDB INFO request failed with an MDO error. The MDO return code and feedback code are shown.
System Action:
The event is ignored and monitoring continues, except for ON ERROR count where monitoring terminates.
User Action:
For ON ERROR count or if the DD name is missing, contact Technical Support; otherwise, issue a SHOW UDB=ddname command from OCS or command entry. If the UDB does not display, the error has occurred because the UDB was closed before the VSAM event monitor could retrieve data. If the UDB is displayed, contact Technical Support.
Reason:
The VSAM Monitor has received an unexpected message when profiling for events. P1 is the message.
System Action:
VSAM monitoring terminates.
User Action:
Contact Technical Support.
Reason:
The VSAM Monitor was attempting to resize the file with DD name p1 but was unable to complete the request for the reason p2. The following reasons can be given:
The file is an NDB, and the resize function does not support NDB files.
The data set allocated to file p1 is not supported. It must be a VSAM cluster with data and index components (KSDS). The file is of type x.
The existing data set cannot be renamed because an automatically generated new data set name that was not already defined could not be determined.
This error is returned from the VSAM file information retrieval utility. The return code was n, and the MDO return code and feedback code were m and p respectively.
This error is returned from the IDCAMS utility. The return code from the utility invocation interface was n and the utility return code was m. Contact Technical Support, providing all the related messages from the log.
The resize utility could not proceed because of an error that was encountered during one of the processing phases of the operation. The message y describes the error. The possible processing phases are:
GETATTR indicates that the resize utility was attempting to get information about the file (including data set name, open options, and current size allocation). This action failed, and the file was not resized; however the existing file is still allocated, open, and in use.
CL-UNALL indicates that the resize utility tried to close and unallocate the file so that it could be resized, but the action was unsuccessful. The message was returned from the close/unallocate utility. The file may be in an inaccessible state if it was closed.
RENAME indicates that the resize utility tried to rename the existing file to a new name, but the action failed. The output from the IDCAMS utility that performed the operation is written to the log. The file may be in an inaccessible state if it was partially renamed. Check the log for the IDCAMS output to determine what the problem was and manually resize the data set (see User Action).
DEFINE indicates that the resize utility tried to define a new VSAM file with more available space, but the action failed. The output from the IDCAMS utility that performed the operation is written to the log. The original file has been renamed to a temporary name and is used to REPRO into the new file when you manually resize the file (see User Action).
ALL-OP indicates that the resize utility successfully completed the resize operation on the file, but was unable to re-allocate and re-open the file to the region. The message was returned from the allocate/open utility. The file may be in an inaccessible state and will need to be manually allocated and opened.
The data set allocated to file p1 is not supported. Only specially identified files are eligible for the automatic resizing option.
System Action:
File resizing terminates.
User Action:
Check the reason for the error, and check the log for any additional messages describing the situation.
When you know what the problem is, you can resize the data set manually. The following steps guide you in resolving the problem and resizing the file:
UDBCTL CLOSE=ddname
UNALLOC DD=ddname
Note: ddname is the file identified in the message.
Note: If the resize process failed and left the original file renamed, then use this file as the INDATASET for the REPRO command of you IDCAMS job.
Important! Do not delete the original file until you have verified that the REPRO was successful, the file is allocated to the region, and no errors are issued in the log regarding this file.
MSDB is allocated by the MSDB - MSDB File Specification parameter group.
Alternatively, you can issue the following commands to reallocate the file to the region, but be sure that you use the correct file disposition and UDBCTL OPEN parameters for that particular file:
ALLOC DD=ddname DSN=datasetname DISP=SHR
UDBCTL OPEN=ddname
Note: ddname is the file identified in the message and datasetname is the data set to be allocated to the DD (check the parameter group for the correct dataset name)
Reason:
This message is a wrapper message issued by the VSAM resizing utility. It encapsulates errors and informational messages encountered during the resizing process for a VSAM data set.
p1 is either another message or text output from the IDCAMS utility.
System Action:
None.
User Action:
Check other messages that indicate the overall success or failure of the resize process. Check the message in p1 for details of the condition being reported.
Reason:
The file p1 has exceeded the allowable number of VSAM extents or the file is full. The file will be extended to ensure that new data can be saved into the file. This message indicated that the file resizing process has begun for the file p1.
System Action:
The file resizing process begins.
User Action:
No action is required. Subsequent messages are issued to indicated the success of the operation.
Reason:
The file p1 had exceeded the allowable number of VSAM extents, or the file was full. The file was successfully extended, and new data can be saved into the file.
System Action:
None.
User Action:
No action is required. The file was resized, and operations continue normally.
Reason:
This message displays a VSAM monitor trace message. P1 is the trace ID and P2 is the trace text.
System Action:
None.
User Action:
None.
Reason:
Function key P1 was pressed and it has no action assigned to it.
System Action:
None.
User Action:
None.
Reason:
The specified command was not recognized by broadcast services.
System Action:
Command Rejected
User Action:
Respecify a valid command.
Reason:
The general broadcast lines have been updated on the VFS file and also the broadcast variables &BROLINE1..4 have been updated.
System Action:
The broadcast text stored will be used to rebuild the general broadcast lines when SOLVE is restarted.
User Action:
The message confirms the update request.
Reason:
The broadcast type requested requires the MASK operand to be specified as a valid single user id value.
System Action:
The broadcast is not sent.
User Action:
Supply a valid userid for the MASK operand/field and retry the request.
Reason:
The destination field contains a ?. The broadcast option entered does not support field prompting for the destination. The U option supports destination field prompting.
System Action:
The broadcast is not sent.
User Action:
Supply a destination mask.
Reason:
The requested broadcast has been deleted.
System Action:
The broadcast is no longer available for display.
User Action:
None.
Reason:
The broadcast type requested requires the MASK operand to be specified.
System Action:
The broadcast is not sent.
User Action:
Supply a value for the MASK operand/field and retry the request.
Reason:
The Broadcast Services menu service procedure $BS0000M failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $BS0000M 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:
You have pressed the F12 key or entered the Cancel command whilst in the Broadcast Text Editor. Any changes you have made to the text have been cancelled and the broadcast has not been sent/set.
System Action:
None.
User Action:
None.
Reason:
The broadcast send request has specified an application for which there are no current users. The broadcast was not sent to any users and was not temporarily stored in the global vartable.
System Action:
If the broadcast was specified with the retain processing option then it is stored for deferred display. Otherwise the broadcast request is ignored.
User Action:
None.
Reason:
A broadcast send request has specified a value other than 'Y' or 'N' for the 'Immediate Broadcast' field.
System Action:
The broadcast is not performed.
User Action:
Correct the value specified and retry the request.
Reason:
A list of userids was presented and at least one userid was not selected.
System Action:
None.
User Action:
Select at least one userid on the list or specify a destination mask on the Broadcast Send menu.
Reason:
The value specified in the 'Retain Broadcast' field did not contain one of the following values:
PERM - The broadcast is to be retained permanently (not across SOLVE restarts)
VIEWED - The broadcast is to be retained until all receivers have viewed the broadcast.
NO - Do not retain the broadcast. The broadcast will only be available to users who are currently logged on to SOLVE.
System Action:
The broadcast is rejected.
User Action:
Correct the value specified for the 'Retain Broadcast' field.
Reason:
A broadcast delete request has failed for the reason specified by P1.
System Action:
None.
User Action:
If deleting a broadcast with outstanding receivers then use the force delete option.
Reason:
An attempt to retrieve a broadcast from the global vartable has failed. The broadcast may have been deleted.
System Action:
None.
User Action:
None.
Reason:
You have attempted to send a broadcast that does not contain any text to SOLVE users. This is not allowed.
System Action:
The broadcast is not performed.
User Action:
Enter some broadcast text in at least one of the four broadcast lines on the panel and retry sending the broadcast,
Reason:
This message indicates whether a broadcast was sent successfully and if so how many terminals/users received the broadcast.
P1 indicates the broadcast identifier associated with the request.
P2 indicates the number of terminals that received the broadcast.
P3 indicates the number of SOLVE users that received the broadcast.
P4 indicates whether the broadcast was saved in the global vartable. The possible values are :
TMP STORED
The broadcast has been temporarily stored in a global vartable and will be deleted when all outstanding receivers have viewed the broadcast.
NOT STORED'
The broadcast was not stored in the global vartable.
RETAINED
The broadcast will be retained in the global vartable until it has been deleted from the active broadcasts selection list. The broadcast will not be retained across SOLVE restarts.
System Action:
None.
User Action:
None.
Reason:
The primary menu broadcast line has been updated on the VFS file and the system variable &ZPMTEXT1 has also been updated.
System Action:
The broadcast text stored will be used to rebuild the primary menu broadcast line when SOLVE is restarted.
User Action:
The message confirms the update request.
Reason:
$BSCALL has been called with text lines(s) longer than the maximum allowed 78 characters.
System Action:
The broadcast is not issued.
User Action:
Correct the text line(s) in error.
Reason:
A broadcast review has determined that there no active broadcasts pertinent to the requesting userid.
System Action:
None.
User Action:
None.
Reason:
The &SECCALL statement was used to check user authorization for the requested operation. This request was unsuccessful.
System Action:
The request is rejected.
User Action:
Determine the cause of the failure in the security system, and retry.
Reason:
You attempted to access Broadcast Services facilities, but you are not authorized.
System Action:
The request is rejected.
User Action:
Request authorization for Broadcast Services from your installation, and retry the request.
Reason:
When setting a primary menu broadcast, only the first broadcast line is used for the broadcast.
System Action:
Broadcast not set.
User Action:
Erase text from broadcast lines 2 - 4 and retry setting the broadcast.
Reason:
The call to the Broadcast Services API $BSCALL failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $BSCALL terminates.
User Action:
Contact the system administrator. Ensure that the keywords/values passed to the Broadcast Services API match the keywords/values stated in the documentation for the API.
Reason:
The call to the Broadcast Services API $BSCALL failed because it specifies a Group name that is not defined to this system.
System Action:
The broadcast request is ignored.
User Action:
Contact the system administrator. Use Broadcast Services List System Groups to determine the broadcast groups defined on your system.
Reason:
A group name was entered that is not a valid name.
System Action:
The broadcast is not issued.
User Action:
Reissue the broadcast using a valid name. Use '?' to select a name from the list of defined groups.
Reason:
A list of broadcast groups was presented but a group was not selected.
System Action:
The broadcast request is not actioned.
User Action:
Reissue the broadcast if desired without a group.
Reason:
An error occured while processing an NCL vartable in broadcast services. The vartable operation was P1 , the vartable ID was P2 , the feedback code set by the VARTABLE verb was P3 and the vartable key was P4 .
System Action:
This message is written to the log.
User Action:
Contact your support representative.
Reason:
An error occured whilst processing a broadcast. A vartable entry that was expected to be found did not exist.
System Action:
None.
User Action:
Contact your support representative.
Reason:
The broadcast mask cannot be specified when reviewing broadcasts when specifying a type of '*' in the 'TYPE=' keyword parameter.
System Action:
$BSCALL terminates.
User Action:
Do not specify the MASK= keyword parameter or change the value of the TYPE= keyword parameter.
Reason:
An error occured whilst attempting to use the broadcast services map $BSMAP. The mapping services return code was P1 and the feedback code was P2 .
System Action:
None.
User Action:
Make sure the broadcast services map $BSMAP is defined to mapping services.
Reason:
When sending a broadcast specifying TYPE=APPL, it is not valid to have RETAIN=PERM set. The only valid values for the RETAIN keyword when using TYPE=APPL are 'NO' AND 'VIEWED'.
System Action:
None.
User Action:
Correct the call to $BSCALL.
Reason:
The broadcast displayed was issued by the user P1 at the time and the date specified by P2 and P3 respectively.
System Action:
None.
User Action:
None.
Reason:
The broadcast displayed was issued by the user P1 at the time and the date specified by P2 and P3 respectively.
System Action:
None.
User Action:
None.
Reason:
The broadcast displayed was issued by the user P1 at the time and the date specified by P2 and P3 respectively. The broadcast was issued on the basis of your terminal's identification.
System Action:
None.
User Action:
None.
Reason:
The broadcast displayed was issued by the user P1 at the time and the date specified by P2 and P3 respectively.
System Action:
None.
User Action:
None.
Reason:
The broadcast displayed was issued by the user P1 at the time and the date specified by P2 and P3 respectively.
System Action:
None.
User Action:
None.
Reason:
The following broadcasts are active and applicable to your userid and terminal.
System Action:
None.
User Action:
None.
Reason:
A broadcast message has been sent to your user region. The broadcast types are:
General - for all users
Specific - for selected terminals
User - for selected users
System Action:
None.
User Action:
None.
Reason:
The broadcast displayed was issued at the time and the date specified.
System Action:
None.
User Action:
None.
Reason:
You have not viewed all the broadcast text. This is because the broadcast text is larger than what can be displayed on one broadcast panel. You must scroll forward to view the remaining text before you can confirm receipt of the broadcast.
System Action:
None.
User Action:
Press the F8=Forward function key to scroll forwards through the broadcast text. The message at the bottom of the broadcast panel will change to indicate you need to press F6=Confirm when all the broadcast text has been viewed.
Reason:
You have viewed all the broadcast text. There is no more broadcast text to be seen in a forwards direction.
System Action:
None.
User Action:
Press the F6=Confirm key to confirm the receipt of the broadcast.
Reason:
There is no more broadcast text to be seen in a backwards direction.
System Action:
None.
User Action:
None.
Reason:
There are too many broadcasts to display on the selection list. The list of broadcasts will be truncated at P1 broadcasts.
System Action:
None.
User Action:
Perform broadcast message maintenance and delete some of the existing broadcasts.
Reason:
A broadcast issued to a remote system gave a non-zero return code.
P1 indicates the remote systems identification. P2 is the return code received. P3 is the associated error message.
System Action:
The message is logged and broadcasting to multiple systems continues.
User Action:
Use the P3 value to determine the cause of the failure. Error messages associated with APPC may indicate that the system is not configured for APPC communication.
Reason:
A broadcast was issued successfully to a remote system. P1 indicates the remote systems identification. P2 is the broadcast identifier on the remote system. P3 is the resulting message from the remote system.
System Action:
The message is logged and broadcasting to multiple systems continues.
User Action:
None.
Reason:
A request to access the broadcast group P1 failed because the group is not defined to the system.
System Action:
The request fails.
User Action:
Check that the broadcast group name used specifies a defined broadcast group. Use Option MS.B.LS to list the defined broadcast groups.
Reason:
A file request for a broadcast group failed. P1 is the file request type P2 is the FILERC value returned P3 is the VSAM feedback code P4 is the file key
System Action:
The request fails.
User Action:
Retry the request. If necessary report the problem to your product support representative.
Reason:
An attempt to add a broadcast services group definition has failed because a group of the same name already exists.
System Action:
The request fails.
User Action:
Retry the request specifying a unique name for the group.
Reason:
The broadcast group P1 has been succesfully added.
System Action:
The system VFS is updated.
User Action:
None.
Reason:
The broadcast group P1 has been succesfully updated.
System Action:
The system VFS is updated.
User Action:
None.
Reason:
The broadcast group P1 has been succesfully deleted.
System Action:
The system VFS is updated.
User Action:
None.
Reason:
A broadcast was issued to multiple systems. P1 indicates the number of systems on which it was issued and P2 the number of systems from which a non-zero return code resulted.
System Action:
Message BS0151 is written to the log for each successful broadcast to a remote system. Message BS0150 is logged for each unsuccessful broadcast.
User Action:
Refer to the log for error details.
Reason:
A broadcast was issued using a system group. P1 indicates the number of systems on which the broadcast was issued.
System Action:
Message BS0151 is written to the log for each remote system.
User Action:
None.
Reason:
The number of messages to be processed exceeded the maximum that could be processed.
System Action:
The broadcast is not performed.
User Action:
Reissue the broadcast as a general broadcast to all users.
Reason:
The broadcast group P1 is a dynamically added group representing a VTAM generic resource region. Maintenance functions are not supported for these dynamic system groups.
System Action:
The request is rejected.
User Action:
None.
Reason:
The Notification Service procedure $BSNS02Z for Broadcast Services failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $BSNS02Z 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:
When actioning a request to notify the user P2 via their preferred method of notification, an unsupported notification mode was encountered. The unsupported mode was P1 .
System Action:
No notification is performed.
User Action:
Replace the invalid notification mode for user P2 with a supported mode.
Reason:
A request to send a notification to user P1 via their preferred method of notification was accepted.
System Action:
None.
User Action:
None
Reason:
When actioning a request to notify the user P2 via their preferred method of notification, an EXIT mode was selected. The EXIT mode specified a procedure that could not be found. The procedure specified was P1 .
System Action:
No notification is performed.
User Action:
Ensure that the exit procedure P1 exists in the commands library concatenation or specify a different exit procedure in the notification details of user P2 .
Reason:
When actioning a request to notify the user P3 via their preferred method of notification, an EXIT mode was selected. The EXIT mode specified the procedure P1 which returned a non-zero return code of P2 . A non-zero return code indicates that an error condition occurred, however the exit procedure did not specify an error message to further describe the error.
System Action:
None.
User Action:
Contact your system administrator specifying the exit procedure name, return code received and the user being notified.
Reason:
A request to notify a user failed because the user's preferred method of notification specified a Domain that is not defined to this system.
System Action:
The request is rejected.
User Action:
Define the Domain to this SOLVE system or change the user's preferred method of notification to specify a different Domain ID.
Reason:
The local system field should contain a Yes to include the local system in the broadcast group or a No to exclude it.
System Action:
The broadcast group is not updated.
User Action:
Correct the value specified in the Local System field to Yes or No.
Reason:
The resource type field is mandatory and must contain one of 'LINK', 'LU' or 'DOMAIN'.
System Action:
The broadcast group is not updated.
User Action:
Correct the value specified in the type field to one of the valid values.
Reason:
The resource name field is mandatory and must contain a valid name. The first character must be an alphabetic or national character and the remaining characters may be alphabetic, numeric, or national ('#','$','@'). The name must be of the correct length for the Resource Type:
APPCLINK - 1 to 12 characters
DOMAIN - 1 to 4 characters
LU - 1 to 8 characters
System Action:
The group is not updated.
User Action:
Correct the resource name to specify a valid name.
Reason:
A resource name was entered that is longer than the maximum allowed for the resource type. An LU name has a maximum length of 8. A domain name has a maximum length of 4. A LINK name has a maximum length of 12.
System Action:
The group is not updated.
User Action:
Correct the resource name to specify a valid name for the resource type.
Reason:
A group name was entered that is not a valid name.
System Action:
The group is not updated.
User Action:
Correct the group name to specify a valid name. The first character must be alphabetic or national character. The remaining characters can be alphabetic, numeric, or national '#', '@', '$'.
Reason:
A resource of the same name and type already exists in the group.
System Action:
The group is not updated.
User Action:
Correct the resource definition to specify a unique resource type and name combination.
Reason:
The group action P1 requires that the ID operand specify the group name.
System Action:
None
User Action:
Correct the $BSCALL invocation to supply an ID keyword that specifies the group name.
Reason:
This message indicates whether a broadcast was sent successfully and if so how many regions in the VTAM Generic Resource group recieved the broadcast.
Review the activity log for each region for details about the number of terminals and users who recieved the broadcast.
P1 indicates the broadcast identifier associated with the request. P2 indicates the number of regions that form the VTAM Generic Resource Group. P3 indicates whether the broadcast was saved in the global vartable. Valid values are : 'TMP STORED' The broadcast has been temporarily stored in a global vartable and will be deleted when all outstanding receivers have viewed the broadcast. 'NOT STORED' The broadcast was not stored in the global vartable. 'RETAINED' The broadcast will be retained in the global vartable until it has been deleted from the active broadcasts selection list. The broadcast will not be retained across SOLVE restarts.
System Action:
None.
User Action:
None.
Reason:
The service procedure name was not provided in the call to the Browse Utility.
System Action:
The call to the Browse Utility is rejected.
User Action:
Specify the service procedure name on the call to the Browse Utility.
Reason:
The specified service procedure was not found in the NCL procedure library.
System Action:
The Browse Utility is terminated.
User Action:
Correct the service procedure name and retry.
Reason:
The Browse Utility did not find any data to display. Either a return code of 14 was returned from the Browse Utility service procedure, or no records were returned from the Browse Utility and the $BUEMPTYEXIT variable was set to 'YES'.
System Action:
The Browse Utility is terminated.
User Action:
None.
Reason:
The function key that was pressed does not perform any function in the panel currently being displayed.
System Action:
The function key request is ignored.
User Action:
Press a valid function key. The function keys which are used in this panel are displayed at the bottom of the screen.
Reason:
A value must be specified in the SCROLL FIELD. Valid values are CSR, HALF, DATA, PAGE, MAX or a number.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Enter a valid value in the scroll field.
Reason:
An invalid scroll amount was specified. Some valid scroll amounts are CSR, MAX, HALF, DATA, PAGE or an amount.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Enter a valid scroll amount.
Reason:
The operand specified with the Find command was invalid. Some valid operands are FIRST, NEXT, PREV and LAST.
System Action:
The Find command is rejected.
User Action:
Correct the parameters on the Find command and retry.
Reason:
An invalid return code was set by a Browse Utility service procedure.
System Action:
None.
User Action:
Contact the System Administrator.
Reason:
The command entered on the command line was not recognized by the Browse Utility.
System Action:
The command is rejected.
User Action:
Enter a valid command and retry.
Reason:
P1 records (P1) were searched for the specified text string but the string was not found.
System Action:
None.
User Action:
Press the FIND key if you wish to continue the search.
Reason:
The character string P1 specified in the FIND command was found.
System Action:
The cursor is placed at the beginning of the character string that was found.
User Action:
None.
Reason:
The locate command was entered, but no record id was specified.
System Action:
The command is rejected.
User Action:
Re-enter the Locate command specifying the full or partial record id which is to be located.
Reason:
The scroll amount that was specified was too large. The scroll amount must be in the range 1 to 99999.
System Action:
The scroll request is rejected.
User Action:
Re-enter the scroll command specifying a valid scroll amount.
Reason:
The bottom of data was reached when trying to find a string specified with the Find command.
System Action:
None.
User Action:
To continue the search press the Find function key. The search will continue from the top of the list.
Reason:
The top of data was reached when trying to find a string specified with the Find command.
System Action:
None.
User Action:
To continue the search press the Find function key. The search will continue from the bottom of the data.
Reason:
An asterisk (*) was entered as a parameter for the Find command, but no previous find command has been entered. When an asterisk is entered as the character string for a find command, the character string from the last find command issued is used. If a literal asterisk is to be found, it should be entered in quotes (ie: '*').
System Action:
The Find command is rejected.
User Action:
Re-enter the Find command specifying a valid character string.
Reason:
A command was entered specifying a label which was more than 8 characters long.
System Action:
The command is rejected.
User Action:
Correct the label name and retry.
Reason:
A dot (.) was entered on the command line without a label name. A label must follow the dot in order to 'name' the current position in the data.
System Action:
The command is rejected.
User Action:
Correct the label name and retry.
Reason:
The requested label has not been defined.
System Action:
The command is rejected.
User Action:
Correct the label name and retry, or enter the command 'locate .?' to display a pick list of the currently defined labels.
Reason:
The label P1 that you specified was found.
System Action:
The data line to which the label was defined is positioned at the top of the window.
User Action:
None.
Reason:
The label name has been stored in memory and associated with the current position in the data.
System Action:
None.
User Action:
None.
Reason:
An unknown calltype of P1 was passed to procedure P2 .
System Action:
The Browse Utility is terminated.
User Action:
Contact the System Administrator.
Reason:
A dump of variables currently in memory have been successfully dumped to your window.
System Action:
None.
User Action:
None.
Reason:
A variable was specified on the DEBUG command but it was greater than 12 characters in length.
System Action:
The command is rejected.
User Action:
Correct the variable name and retry.
Reason:
The output of the DEBUG command was written to the activity log in hexadecimal format. The dumped data is prefixed with the message id BU0036.
System Action:
None.
User Action:
None.
Reason:
The contents of variable P1 have been written to the activity log. The output was prefixed with message id BU0036.
System Action:
None.
User Action:
None.
Reason:
P1 is the contents of a variable in HEX expanded format. The variable name is shown in the message BU00035.
System Action:
None.
User Action:
None.
Reason:
P1 is the contents of a variable. The variable name is shown in the message BU0035.
System Action:
None.
User Action:
None.
Reason:
The Find command could not be actioned because no character string was entered.
System Action:
The command is rejected.
User Action:
Re-enter the Find command specifying a character string to be found.
Reason:
There were no predefined labels found to place in a pick list.
System Action:
The command is rejected.
User Action:
None.
Reason:
The Locate command is not supported on this display.
System Action:
The Locate command is rejected.
User Action:
You must scroll up/down to find the desired record(s).
Reason:
The entered maximum find amount was incorrect. It must be in the range 100 to 9999.
System Action:
The scroll request is rejected.
User Action:
Re-enter the scroll command specifying a valid scroll amount.
| Copyright © 2012 CA. All rights reserved. |
|