|
|
|
Reason:
Invalid parameters were passed to Procedure $RMIC01D.
System Action:
The Procedure terminates.
User Action:
Contact your support representative.
Reason:
The panel, P1, you have chosen to be displayed as a graphical monitor is currently being updated by the user identified by P2.
System Action:
Request rejected.
User Action:
Use another panel or wait until the user currently updating the panel is finished with it.
Reason:
The Resource Group you have elected to Zoom to does not contain any resources.
System Action:
The Zoom request is rejected.
User Action:
Check that the Resource Group definition is correct, and that all links between Service/View Regions are up.
Reason:
The panel name P1 is not a valid panel name.
System Action:
Request rejected.
User Action:
Specify a valid panel name.
Reason:
The command identified by P1, issued against the Icon identified by P2 was not a valid Icon command.
System Action:
Request rejected.
User Action:
Enter a valid Icon command
Reason:
The command P1 is not allowed to be issued against resource group P2 because it appears in the list of restricted commands contained in GLOBAL variable $RM$GCBL.
System Action:
Command is rejected.
User Action:
If it is required to be able to issue this command then remove it from the GLOBAL variable $RM$GCBL in the system startup parameters.
Reason:
The requested command(s) were successfully submitted.
System Action:
None.
User Action:
None.
Reason:
There was en error encountered Zooming to a Resource Group panel.
P1 is the resource group being ZOOMed to and P2 is the error message returned.
System Action:
The Zoom is terminated.
User Action:
Check to see if the Zoomed Panel or Resource Group are invalid.
Reason:
The specified Command is Invalid.
System Action:
None.
User Action:
Enter a "?" in the field to get a list of Valid Commands.
Reason:
Resource commands cannot be issued against an icon which contains a resource group which points to another icon panel. You must first Zoom the lower level panel and issue resoure commands at that level, if possible.
System Action:
Command is rejected.
User Action:
Zoom on the icon to reveal the panel below. If the icons on this subsequent panel point directly to resources then commands may be issued against them.
Reason:
An error occurred while displaying the indicated panel. The panel may have changed since it was last displayed. The activity log contains more information about the panel error.
System Action:
The displaying operation is terminated.
User Action:
See the activity log for more information about the panel error.
Reason:
The specified command has been issued.
System Action:
The command will be processed.
User Action:
None
Reason:
An invalid keyword value was passed to the Graphical Resource Monitor service procedure. The keyword was P1 and the invalid value was P2.
System Action:
Request is rejected.
User Action:
Correct the keywords value and retry the request.
Reason:
The command specified was invalid.
System Action:
Command field is set in error.
User Action:
Enter a valid command.
Reason:
A request to execute a command against all the resources represented by an Icon was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
Allocation for the vartable named P3 with scope P4 of type P2 was unsuccessful. FDBK P1 was returned.
System Action:
The Icon Manager terminates.
User Action:
Resolve the reason for the vartable allocation failure. This may be that the region is short of storage and it may be necessary to restart the region with more storage.
Reason:
A panel path has been invoked in which the ICON (Resource Group) known as P1 points to the PANEL P2 which has either been referenced earlier in the path or which contains the ICON (Resource Group) identified by P1
System Action:
Entry to the Graphical Monitor is denied as this sort of recursive path leads to excessive CPU usage and degradation of performance.
User Action:
Locate where the recursion occurs in the path and correct the situation and retry.
Reason:
You invoked the Icon Manager Service procedure with invalid parameters identified by P1.
System Action:
The Icon Manager Service procedure terminates.
User Action:
These are internal calls and should not provide invalid parameters. Contact Technical Support.
Reason:
You invoked the Icon Manager Service procedure to resolve the icons in an icon panel, but the name of the panel, identified by P1, is not a valid panel name.
System Action:
The Icon Manager Service procedure terminates.
User Action:
Correct the source of the invalid panel name. It may be stored in a user's profile.
Reason:
You invoked the Icon Manager Service procedure to resolve the icons in the icon panel identified by P1 but the panel cannot be read from the panel library identified by P2.
System Action:
The Icon Manager Service procedure terminates.
User Action:
Ensure that the region has initialized without errors. The most likely cause of this error is that the ICOPANL data set is not allocated.
Reason:
The System Image P1 of version P2 is being loaded as the current system.
System Action:
None.
User Action:
None.
Reason:
The registration table used to support multiple systems was successfully allocated.
System Action:
None.
User Action:
None.
Reason:
The status table was successfully loaded.
System Action:
None.
User Action:
None.
Reason:
The loading of the status table failed. See associated message(s) for the reason.
System Action:
System load terminates.
User Action:
See the associated messages and correct the error indicated by these messages.
Reason:
The processes that manage APPC communication sessions with this system are being started and initialized.
System Action:
None.
User Action:
None.
Reason:
The various SSO long running processes which manage message traffic and event flows are being started and initialized.
System Action:
None.
User Action:
None.
Reason:
The long running background process P1 failed to initialize.
System Action:
Load of the system fails.
User Action:
See the associated messages for the reason that the process failed.
Reason:
The long running background process P1 successfully initialized.
System Action:
None.
User Action:
None.
Reason:
The action of starting and initializing all the required long running background process failed.
System Action:
System load fails.
User Action:
See the associated messages.
Reason:
The Availibility Statistics Monitor is being started in the background.
System Action:
None.
User Action:
None.
Reason:
The process responsible for Starting all the resources of the current System Image is being started.
System Action:
None.
User Action:
None.
Reason:
Initialization of Console Consolidation processing failed.
System Action:
System load fails.
User Action:
See the associated messages for the reason.
Reason:
The Console Consolidation ISR link manager process is being started.
System Action:
None.
User Action:
None.
Reason:
An invalid command was entered.
System Action:
The command is rejected.
User Action:
Specify a valid command.
Reason:
The system image load has completed.
System Action:
None.
User Action:
None.
Reason:
An request to load a new system image was rejected because there is already a system load in progress. The currently running load was started at P1.
System Action:
Request rejected.
User Action:
None.
Reason:
The system load process detected that the monitor process was already running. This is normal, the process will not be restarted.
System Action:
None.
User Action:
None.
Reason:
The system load process had previously been unsuccessful with the initialization of some components which are not critical but which resulted in a load status of WARNING. This message indicates that a user has initiated a Retry request in order to initialize these components.
System Action:
None.
User Action:
None.
Reason:
A request to retry the initialization of non-critical components was issued.
System Action:
None.
User Action:
Wait for subsequent messages, which indicate the results of the request.
Reason:
An attempt to initialize non-critical components failed.
System Action:
Initialization remains in the warning state.
User Action:
Determine the reason for the errors and retry the request.
Reason:
An attempt to initialize non-critical components completed successfully and the components are now initialized.
System Action:
None.
User Action:
None.
Reason:
The load of System Image P1 with Version P2 has completed.
System Action:
None.
User Action:
None.
Reason:
The long running background process P1 failed to initialize. The reason is P2. If the reason is ended then the process prematurally ended before notifying the loader.
System Action:
Load of the system fails.
User Action:
See the associated messages (also in the activity log) for the reason that the process failed.
Reason:
A system image load was requested but the supplied system image name was not found in the database.
System Action:
A dummy system image is loaded.
User Action:
Load a valid system image.
Reason:
A system image load was requested but the supplied system image name is the active system image on a linked region.
System Action:
A dummy system image is loaded.
User Action:
Load a different system image on this region or the linked region, or unlink the regions and retry.
Reason:
The indicated Template System Image Version does not exist in the RAMDB. System load cannot proceed without a valid Template System Image Version.
System Action:
System load fails.
User Action:
Update ICS parameter member OPSYSIDS with a valid Template System Image Version.
Reason:
The monitors defined to the Data Sampling Framework are being started in the background.
System Action:
None.
User Action:
None.
Reason:
The service procedure identified by P1 was invoked with an invalid value for the keyword identified by P2 of P3.
System Action:
Request rejected
User Action:
Correct the keyword value and re-try
Reason:
There were no records in the log.
System Action:
None
User Action:
None
Reason:
There were more tha 9999 log records.
System Action:
The first 9999 log records will be displayed.
User Action:
None
Reason:
The feature or features P1 are either excluded or not licensed for this CPU.
System Action:
Function is terminated.
User Action:
Contact your Systems Administrator.
Reason:
The field P1 is required and must not be null.
System Action:
Field is set in error.
User Action:
Specify a value for P1.
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 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 blank out the value for P2 .
Reason:
An invalid job entry subsystem was specified. The only valid job entry subsystems are:
- For MVS: JES2 or JES3 - For MSP: JES - For VOS3: JSS3 or JSS4
System Action:
Field is set in error.
User Action:
Specify a valid value.
Reason:
The specified character, P1 , is invalid. Specify one of the characters in P2 .
System Action:
The field in error is highlighted.
User Action:
Specify a valid character.
Reason:
The field P1 must have a different value to the field P2 .
System Action:
Field is set in error.
User Action:
Specify different values for P1 and P2 .
Reason:
The P1 type specified was invalid. The only valid values are GLOBAL or LOCAL. P1 will be either JES3 or JSS4.
System Action:
Field is set in error.
User Action:
Specify either GLOBAL or LOCAL.
Reason:
The field must have the value NO if the field P1 is NO.
System Action:
Field is set in error.
User Action:
Specify NO for the field or specify YES for P1 .
Reason:
This region is configured with the NetMaster Automation product that requires the $RSPPOPR PPO procedure.
System Action:
The parameter group fails.
User Action:
Either specify the correct PPO procedure name, or clear the field for it to default to the required value.
Reason:
The field contains an invalid value. The only valid values are ACTIVE or INACTIVE.
System Action:
Field is set in error.
User Action:
Specify either ACTIVE or INACTIVE.
Reason:
The field contains an invalid value. The field must be in the format n-m, where n and m are both numeric and in the range 1 to 128. Also n must be less than or equal to m. For example 17-128.
System Action:
Field is set in error.
User Action:
Specify a valid range.
Reason:
The field contains an invalid value. The field must be in the format n,n,n:m where n and m are numeric and in the range 1 to 128. For example 1,2,8:12,29,36:123
System Action:
Field is set in error.
User Action:
Specify a valid series of route codes.
Reason:
The field contains an invalid value. The only valid values are SMFID or NMDID.
System Action:
Field is set in error.
User Action:
Specify either SMFID or NMDID.
Reason:
The AOMPROC was started and did not return an indication that it had successfully initialized within the time allowed.
System Action:
The parameter group fails.
User Action:
Determine the reason the AOMPROC failed or did not issue a notification.
Reason:
The parameter P1 could not be changed because AOM is currently in a status which does not allow the altering of this parameter. The current status of AOM is P2 . AOM must be inactive to action this parameter. P1 gives the name of the parameter and in parentheses the current value.
System Action:
Parameter is not set.
User Action:
Save the parameters value and it will become effective at next startup or stop AOM, set the parameter and then restart AOM.
Warning: Stopping AOM will affect the functioning of the system. No messages will be received, no automation will be taken and the resource status changes will be lost. You will need to reload the system image.
Reason:
The field contains an invalid value. The only valid values are AUTOMATED or MANUAL.
System Action:
Field is set in error.
User Action:
Specify either AUTOMATED or MANUAL.
Reason:
The field contains an invalid value. The only valid values are 0 or a number between 128 and 255.
System Action:
Field is set in error.
User Action:
Specify either 0 or a number between 128 and 255.
Reason:
The field contains an invalid value. The field must be greater than or equal to 10 minutes (00.10) and less than 24 hours (ie less than or equal to 23.59).
System Action:
Field is set in error.
User Action:
Specify a time interval between 00.10 and 23.59.
Reason:
The AOM global number variable P1 was set to the value P2.
System Action:
None.
User Action:
None.
Reason:
This is an informational message which describes an NDB error code.
System Action:
None.
User Action:
See related messages.
Reason:
The NDB specified was invalid because the NDB was not defined for the current version.
System Action:
The RAMDB is not allocated.
User Action:
Specify a valid RAMDB.
Reason:
The value for field P1 must be greater than the value specified for field P2.
System Action:
Field is set in error.
User Action:
Specify a higher value for P1 or a lower value for P2.
Reason:
The value for field P1 must be a valid IP address in numeric form. AAA.BBB.CCC.DDD where AAA,BBB,CCC,DDD are numbers less than 256.
System Action:
Field is set in error.
User Action:
Specify a proper numeric format IP address for P1.
Reason:
The value for field P1 was specified as NO, and thus no further WSPEER parameters were processed.
System Action:
None.
User Action:
If you wish to use a Workstation peer system, then change the setting of the field to YES, and specify all of the other parameters correctly. Otherwise this message can be ignored.
Reason:
The selected System Image cannot be loaded on this region because it is active on a linked region.
System Action:
Field is set in error.
User Action:
Select another System Image.
Reason:
The value for the IP address in the WSPEER customization parms was found to be null.
System Action:
WSPEER parameter processing is terminated.
User Action:
Specify a proper numeric format IP address in the WSPEER customization parameters. If WSPEER processing is not required, set the 'Workstation peer in use' field to NO.
Reason:
The Template System Image Version specified is not valid for the JES identified by P2.
System Action:
The field is highlighted and a message is displayed to the user.
User Action:
Correct the Template System Image Version entered in the field.
Reason:
The field contains an invalid value. The only valid values are YES or NO.
System Action:
Field is set in error.
User Action:
Specify either YES or NO.
Reason:
The PPOPROC was started and did not return an indication that it had successfully initialized within the time allowed.
System Action:
The parameter group fails.
User Action:
Determine the reason the PPOPROC failed. Use the $LOG command to access the activity log. Look for any messages that indicate that the procedure has ended, either normally or as a result of an abend.
Reason:
There is insufficient storage to load all the console consolidation message profiles.
System Action:
Console consolidation profiles are unloaded and the screening table activation is reattempted.
User Action:
Reduce the amount of storage needed by the console consolidation profiles by: - inactivating unused profiles
- reducing the size (complexity) of the profiles Reactivate the profiles from the customization parameter for console consolidation (CCONSOLIDATN).
Reason:
Background user IDs must be defined to execute the procedure that operates the product. If they are not defined, the product may not operate correctly.
System Action:
Processing continues.
User Action:
From a session with UAMS authority, run procedure $NMUAINI with no arguments to generate the background user IDs. Then go to /BCAST.L and delete this broadcast message or it will be retained until the region is stopped.
Reason:
See message RMINWI37.
System Action:
See message RMINWI37.
User Action:
See message RMINWI37.
Reason:
See message RMINWI37.
System Action:
See message RMINWI37.
User Action:
See message RMINWI37.
Reason:
See message RMINWI37.
System Action:
See message RMINWI37.
User Action:
See message RMINWI37.
Reason:
To activate the use of the Workstation Peer, the Workstation Peer User ID must be defined in this system. P1 is the Workstation Peer User ID and it does not exist. The system wanted to create it automatically for you but you are not authorized for UAMS maintenance access and hence the request was not attempted.
System Action:
Validation for this parameter group fails.
User Action:
Either obtain the required authority to perform user maintenance or ask a suitably authorized user to update this parameter group. You can also ask a suitably authorized user to run the following procedure to automatically define the required user ID. Run this procedure from OCS:
$RMUAINI ACTION=DEFINE NAME=WSPU
Reason:
There is insufficient storage to load all the event simulation code.
System Action:
Event simulation is disabled, and the screening table activation is retried.
User Action:
If event simulation is not required, disable it permanently through the MSGAWARENESS parameter group. In future, no attempt to enable its code will be made. This improves the performance of system initialization.
If event simulation is required, reduce the amount of storage used by console consolidation and/or NetMaster Automation. This can be done in the following ways:
Note: If console consolidation profiles are modified, reactivate the profiles by selecting option A - Activate Message Profiles from the System Console Consolidation menu. Then action the MSGAWARENESS parameter group to enable event simulation.
Reason:
The P1 component of Message Awareness was set to P2.
Message Awareness consists of the following components:
This facility lets you simulate message traffic through your environment and report any EventView rules or ResourceView definitions affected.
This facility notifies you about possible critical system messages that your EventView and ResourceView environment is not set up to deal with. The messages and the alerting method are controlled through the MSGAWARENESS parameter group.
System Action:
None.
User Action:
None.
Reason:
The global variable P1 was set to the value P2 .
System Action:
None.
User Action:
None.
Reason:
The screening table has exceeded its storage limit while loading code dynamically generated by the Unmatched Message Alerting facility, and that facility has been disabled.
System Action:
Unmatched Message Alerting is disabled, and the screening table activation is retried.
User Action:
If Unmatched Message Alerting is not required, disable it permanently through the MSGAWARENESS parameter group. In future, no attempt to enable its code will be made. This improves the performance of system initialization.
Reason:
The AOM global flag variable P1 was set to the value P2.
System Action:
None.
User Action:
None.
Reason:
The AOM SSI Command String Prefix contains an invalid character. The supported characters are:
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 @ $ # ' , . / ( ) * & + - › < | ! ; % _ > ? : "
System Action:
Field is set in error.
User Action:
Correct the AOM SSI Command String Prefix or leave the input field blank if no Command String Prefix is required.
Reason:
The dataset specified does not have the correct dataset organization.
P1 is dataset organization of the dataset. Valid values are PO or PS.
System Action:
Field is set in error.
User Action:
Specify a partitioned (PO) dataset with a member name or a physical sequential (PS) dataset.
Reason:
The dataset specified was a partitioned dataset however a member name was not specified. A member name must be specified if the dataset is partitioned.
System Action:
Field is set in error.
User Action:
Specify a partitioned (PO) dataset with a member name or a physical sequential (PS) dataset.
Reason:
An error was encountered when attempting to access a file. P1 is the operation being performed, P2 is the ID of the file, P3 is the return code, and P4 is the message set by the FILE verb.
System Action:
Processing terminates.
User Action:
Contact your local support representative.
Reason:
The link record indicated by P1 has been successfully processed. P2 indicates if the record was CREATED, REPLACED or SKIPPED. The record is SKIPPED if there is an existing multisystem link record with the key P1 that has been customized.
System Action:
None.
User Action:
None.
Reason:
Ruleset name given must be a valid defined rulest under File Transfer Ruleset definition.
System Action:
Validation for this parameter fails.
User Action:
Enter a valid defined Ruleset name.
Reason:
The set of communication access methods you have selected is not valid at this time. The set has no access method in common with linked region P1 and would render P1 uncontactable.
System Action:
Fields required to access P1 are highlighted.
User Action:
Set one of the highlighted fields to YES. Alternatively, unlink region P1.
Reason:
You must enable at least one of the communication access methods.
System Action:
The fields that cause the error are highlighted.
User Action:
Specify YES to at least one access method.
Reason:
The TCP/IP? field cannot be set to YES because the interface to TCP/IP has not been enabled on this system.
System Action:
The TCP/IP? field is highlighted.
User Action:
If you want to use TCP/IP, update the SOCKETS parameter group and set the TCP/IP Software Type field to a value other than NONE.
Reason:
You cannot specify YES in the EPS? field because the interface to the SSI has not been defined.
System Action:
The field in error, EPS?, is highlighted.
User Action:
If you want to use EPS, specify an SSI in the SSI parameter group to provide the EPS service.
Reason:
You cannot specify YES in the EPS? field because this is not an MVS system. EPS is available on MVS only.
System Action:
The field in error, EPS?, is highlighted.
User Action:
Specify NO in the EPS? field.
Reason:
The value in the P1 field cannot be greater than the value in the P2 field.
System Action:
The field in error is highlighted.
User Action:
Specify a lower value in the P1 field or a higher value in the P2 field.
Reason:
This region requires the console support level of Management Services 3.7 (plus APARs).
System Action:
Initialization cannot complete.
User Action:
Contact Technical Support.
Reason:
The highlighted field contains an invalid value. The only valid value is PRIMARY or ALTERNATE, indicating which set of resource relationships will be used when the SHUTSYS or SHUTFORCE command is used to shut down a system image.
System Action:
The field in error is highlighted.
User Action:
Specify either PRIMARY or ALTERNATE.
Reason:
During region startup, no records were found in the knowledge base (RAMDB) that match the primary (ACB) name of this region. However, other records exist matching other primary names. This is an abnormal situation, usually indicating that the PRI JCL parameter of the region has changed. The change means that remote regions become inaccessible. As a consequence, the region is unlinked automatically from other regions.
System Action:
The region is unlinked, and the message is broadcasted to all users.
User Action:
If new multisystem links are required, the administrator will need to relink the region by using the Link Region and Synchronize Database option on the Multi-System Support Menu (=/MADMIN.SD).
Reason:
The value specified for the NSM Agent Instance name contains special characters such as '@#$-'. Only alphabetic or numeric characters are valid in the instance name and should start with an alphabetic character.
System Action:
The field in error is highlighted.
User Action:
Specify a valid value.
Reason:
The P1 system image was not loaded because of reason P2 .
System Action:
The P1 image is not loaded. A default image, $&ZNMDID Version NONE, is loaded instead. &ZNMDID contains the domain identifier of the region.
User Action:
Enter the /PARMS shortcut to display the list of parameter groups, and enter U beside the AUTOIDS group. Specify a system image that is appropriate for the region. If no appropriate images exist, define one and specify it in the AUTOIDS group.
Reason:
The VTAM Application ID specified in the Terminal Prefix field does not exist.
System Action:
Field is set in error.
User Action:
Specify a valid VTAM Application ID that is currently defined to VTAM. The ID can be for a pool of Application IDs with the same prefix and numeric suffixes starting from 001 and up to 999. Alternatively the Application ID can be a generic prefix.
Reason:
The NetMaster for TCP/IP agent does not support filtering.
System Action:
Field is set in error.
User Action:
Specify NONE as the filter value.
Reason:
An absolute directory path is required.
System Action:
Field in error is highlighted.
User Action:
Provide an absolute path directory.
Reason:
The P1 file is empty.
System Action:
Field is set in error and the agent is not started.
User Action:
Specify a valid P1 dataset.
Reason:
The contents of P2 is displayed after this message.
System Action:
None.
User Action:
None.
Reason:
An attempt to OPEN the P1 file failed and the system could not read its contents.
System Action:
Initialization continues.
User Action:
None.
Reason:
The value provided is not in the valid range of 5-60.
System Action:
Field is set in error.
User Action:
Specify a number within the valid range.
Reason:
The CA-7 User ID field contains an invalid value.
System Action:
Field is set in error.
User Action:
Specify other values.
Reason:
The CA-7 User Password field contains an invalid value.
System Action:
Field is set in error.
User Action:
Specify other values.
Reason:
The CA-7 SSID field contains an invalid value.
System Action:
Field is set in error.
User Action:
Specify other values.
Reason:
The option is set to NO because the security exit is not installed.
System Action:
Message displayed. Processing continues.
User Action:
Install the security exit, if required.
Reason:
The automatic password option of the SCHEDAPI parameter group requires the CA-7 user to be defined to UAMS. If the option is set to YES, the system attempts to automatically add the user to the UAMS file. If the attempt is unsuccessful, this message is displayed. P1 is the message returned by the SECCALL ADD function.
System Action:
Message displayed. Processing continues.
User Action:
Determine why the ADD failed. The user may already be defined. Correct the problem and add the user manually.
Reason:
The value provided is not a valid host with port specification. A valid IP address or host name, optionally followed by a port number (:nnnnn), is required.
If a host name is specified, special characters, including @ and #, are not permitted.
If an IPv6 address is specified with a port number, the address must be enclosed in square brackets.
Examples:
192.10.23.24
my.host.com
los-angeles.ARN24
192.10.23.128:1080
[fd00:7a06:a20:100::1]:1080
my.host.com:31076
System Action:
The field is highlighted in error.
User Action:
Specify an alphanumeric IP host name or address.
Reason:
The specified AOM Message Suppression Character is invalid. The supported characters are:
@ # , . / & + - › < | ! ; % _ > ? : ^
System Action:
Field is set in error.
User Action:
Specify a valid character.
Reason:
The system parameter (SYSPARM) with name P1 is already set to the value P2.
System Action:
None.
User Action:
None.
Reason:
The default size must have a value less than or equal to the value specified for the maximum size.
System Action:
None.
User Action:
Correct the field value, and retry.
Reason:
An Alert Severity field must contain 1, 2, 3, 4, or be blank.
System Action:
None.
User Action:
Correct the value, and retry.
Reason:
An IPv6 address has been entered in the Web Address 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 Web Address Override field. Alternatively, check the SOCKETS parameter group (/PARMS). For IPv6 support, the TCP/IP Software Type must specify IBMV6.
Reason:
The valid Hardware Interface Service API security environments are REGION, SERVER, or USER.
System Action:
The field is set in error.
User Action:
Specify a correct value.
Reason:
An invalid value was entered in the P1 field of the SYSLOGD parameter group. The fields have the following valid values:
Specifies a valid UNIX file system file name that either does not exist or exists as a named pipe. The file name must be an absolute reference, beginning with a forward slash.
Specifies one of the following values:
Specifies a valid user ID, optionally ending in an * to signify generic.
Specifies a valid job name, optionally ending in an * to signify generic.
System Action:
The field is set in error.
User Action:
Specify a valid value in the P1 field.
Reason:
The file specified in the P1 field of the SYSLOGD parameter group exists, but it is not a named pipe. The SYSLOGD message receiver requires a named pipe.
System Action:
Actioning of the SYSLOGD parameter group ceases.
User Action:
Specify a valid named pipe in the SYSLOGD parameter group, and press F6 (Action).
Reason:
A value must be provided in the P1 field if a value is set in the P2 field.
SYSLOGD message filters must be in one of the following formats:
System Action:
The field is set in error.
User Action:
Specify a value in the P1 field.
Reason:
An attempt to create or delete the named pipe failed.
P1 is the action.
P2 identifies the named pipe.
P3 is the return code.
System Action:
If the attempted action was CREATE, then actioning of the SYSLOGD parameter group ceases.
User Action:
Ensure that your UNIX file system has enough space for the creation of the named pipe.
Reason:
This informational message provides some information about the actioning of the SYSLOGD parameter group.
System Action:
Actioning of the SYSLOGD parameter group continues.
User Action:
None.
Reason:
The SYSLOGD parameter group must restart the syslog daemon whenever it updates the configuration file or whenever it starts the pipe receiver. The attempt to restart the daemon has failed.
System Action:
Actioning of the SYSLOGD parameter group ceases.
User Action:
Restart the syslog daemon manually. When the daemon has restarted, re-action the SYSLOGD parameter group, making no new changes.
Reason:
CA NetMaster NM for TCP/IP r11.6 SP1 deprecated some monitoring attributes and replaced them with new ones. When the region starts, the RAMDB is scanned and if the deprecated attributes are found, defined EE resources are checked and if they are using the deprecated attributes, they are replaced with the new attributes. When all defined EE resources are updated, the deprecated attributes are deleted.
The deprecated attributes are:
LowPriorityData
HighPriorityData
MediumPriorityData
NetworkPriorityDat
SignalTraffic
The replacement attributes are:
EEBytesPriLow
EEBytesPriHigh
EEBytesPriMedium
EEBytesPriNetwork
EEBytesPriSignal
This message is issued at the start and end of this processing, as identified by P1 . Messages issued in between detail any action taken.
System Action:
Deprecated attributes in resource monitoring defintions are replaced and the deprecated attributes deleted.
User Action:
None.
Reason:
The Telnet, FTP or Connection 'Workload' option was selected but no host samples exist for this option.
System Action:
None.
User Action:
None.
Reason:
The selected STACK resource is not registered internally.
System Action:
The command is rejected.
User Action:
This message may occur transiently following a system image load or when remote stack resources are accessed. Try the command again later.
If the situation persists, there may be a mismatch in the information provided about the stack. Check the stack name, type and SSID (if applicable) are correct in the following places:
- The stack resource definition (A.R.R)
- SOCKETS parameter group (/PARMS)
Reason:
A display query for P1 has no matching data in Workload Manager (WLM).
System Action:
None.
User Action:
None.
Reason:
The definition of the selected resource does not include the associated TCP/IP stack job name.
System Action:
The request is rejected.
User Action:
Update the resource definition to include the associated stack job name.
Reason:
The Telnet option was selected but no samples exist for this option.
System Action:
None.
User Action:
None.
Reason:
The command P1 is not valid against the selected resource. The command requires P2 (OSA/SF or SNMP) and the OSA resource definition specifies that P2 is not used.
System Action:
The command is rejected.
User Action:
None.
Reason:
The command request identified by P1 has been canceled.
System Action:
None
User Action:
None
Reason:
The command request identified by P1 has been canceled because CA NetSpy is not configured.
System Action:
None.
User Action:
None.
Reason:
You tried to file or save a definition that has not been changed. The requested action is not performed.
System Action:
The definition is not saved again.
User Action:
None.
Reason:
The associated STACK jobname P1 for the selected resource is not registered internally.
System Action:
The command is rejected.
User Action:
This message may occur transiently following a system image load or when remote stack resources are accessed. Try the command again later.
If the situation persists, there may be a mismatch in the information provided about the associated stack jobname. Check the stack jobname, type and SSID (if applicable) are correct in the following places:
- The Associated STACK Jobname field definition for the selected resource (A.R.R)
- The stack's own resource definition (A.R.R)
- SOCKETS parameter group (/PARMS)
Reason:
Another user is updating this definition.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
The IP Resource Monitor IU command (List IP UDP Connections) is no longer supported. You can list UDP end points using the Connection List function.
System Action:
None.
User Action:
To display current UDP end points and their total traffic counts, use a Connection List /CONNC (not /CONNCF) with the criteria Connection Status EQ UDP.
Reason:
The entered command is not valid against the selected resource. The stack associated with this resource is type TCPaccess. The command is not supported for TCPaccess stacks.
System Action:
The command is rejected.
User Action:
None.
Reason:
The link name identified by p1 is not currently active.
System Action:
The request is rejected.
User Action:
Investigate the cause of the link failure, and retry the operation.
Reason:
The requested command is not supported by the remote region, p1. The link is in Migration Mode. This type of linkage is used during the migration of the remote region to a new release level.
System Action:
Processing of the command terminates.
User Action:
This command will be available in the remote region when you have upgraded the remote region to the same release level as this region.
Reason:
The TWL option is not supported by IBM for z/OS V1R11.0 or later.
System Action:
The request is rejected.
User Action:
None.
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:
System image load processing has started and will be requesting confirmation of the system image name and version, the automation mode, and whether a cold or a warm load is to be performed. The system ID is
P1 .
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue the load process.
Reason:
The region is initializing and will be requesting confirmation of the system image and version to use. The system ID is P1 , and the currently nominated system image name is P2 .
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue initialization.
Reason:
The region is initializing, and will be requesting confirmation of the system image and version to use. The system ID is P1 , and the currently nominated system image version is P2 .
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue initialization.
Reason:
The region is initializing, and will be requesting confirmation of the system image and version to use. The system ID is P1 , and the currently nominated automation mode is P2 .
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue initialization.
Reason:
The region is initializing, and is requesting confirmation of the system image name and version, automation mode, and cold load setting to use for the region. The system ID is P1 , and the currently nominated system image name is P2 , the version is P3 , the automation mode is
P4 , and cold load is P5 .
System Action:
The system waits for a reply.
User Action:
Reply to the message, or allow it to time out to continue initialization.
Reason:
The region is starting system image load or network discovery, and is requesting override or confirmation of the parameters listed in the previous messages (RMIWTOnn). The messages display the current setting of parameter values. See AUTOIDS or AUTOSNACNTL for further details of the parameters in the group. P1 is the system ID of the region.
System Action:
The system will wait for a reply, or will use the values shown when the timeout value expires. The timeout value is determined by the Confirm via WTOR at Startup? field in the parameter group. The default is 120 seconds.
User Action:
Check that the parameter values are correct.
If they are correct, reply as follows: R n,U
If a value is not correct, reply with the parameter name and its correct value in the format, PARM=VALUE. The following example changes the system image to be loaded:
R n,SYSTEM=SOLVPROD,VERSION=0002,MODE=AUTOMATED
Reason:
The region is initializing, and will be requesting confirmation of the system image and version to use. The system ID is P1 , and P2 indicates if there will be a cold start of checkpointing.
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue initialization.
Reason:
The region is starting its network discovery processing, and will be requesting confirmation of the discovery rate (number of commands per time frame) and whether a cold start is required. The system ID is P1 .
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue network discovery.
Reason:
The region is starting network discovery and will be prompting for confirmation of the discovery parameters. P1 is the system ID, and P2 indicates whether a cold start will be done. P2 can be changed in response to a subsequent WTOR message by replying COLD=YES or COLD=NO.
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue network discovery.
Reason:
The region is starting network discovery and will be prompting for confirmation of the discovery parameters. P1 is the system ID, and P2 indicates the maximum number of commands that can be issued within the time frame displayed in a subsequent message. P2 can be changed in response to a subsequent WTOR message by replying CMDS=n, where n is the new number of commands per time frame.
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue network discovery.
Reason:
The region is starting network discovery and will be prompting for confirmation of the discovery parameters. P1 is the system ID, and P2 indicates the time frame within which the specified maximum number of commands can be issued (see previous message). P2 can be changed in response to a subsequent WTOR message by replying TIME=n, where n is the new value for the time frame in seconds.
System Action:
This message is followed by a RMIWTO06 message requesting a reply.
User Action:
Reply to the RMIWTO06 message, or allow it to time out to continue network discovery.
Reason:
The region is starting network discovery and is requesting confirmation of the Cold Start, Commands per Time Frame, and Time Frame in Seconds discovery control parameters. The system ID is P1 and the current value for Cold Start is P2 , Commands per Time Frame is P3 , and Time Frame in Seconds is P4 .
System Action:
None.
User Action:
Check that the Cold Start, Commands per Time Frame, and Time Frame in Seconds are correct, and if so, reply "U".
Reason:
A reply received to confirm System Image Load or Network Discovery specified an invalid value for the keyword parameter P2. This parameter must be P3. The system's ID is P1.
System Action:
None.
User Action:
Reply to the subsequent WTOR the correct value for the keyword P1.
Reason:
A reply to change the System Image name and/or Version was rejected because the specified system and version combination could not be found in the database. P1 is the system's ID, P2 is the system image name and version, P3 is the database return code and P4 is the message returned from the database manager.
System Action:
None.
User Action:
Reply to the subsequent WTOR with a valid system name and version that exist.
Reason:
No reply to change the parameter for the P2 process was received within 2 minutes. The current values will be accepted as confirmed. The system's ID is P1.
System Action:
None.
User Action:
None.
Reason:
Confirmation of the parameter for the P2 process was acknowledged. The system's ID is P1.
System Action:
None.
User Action:
None.
Reason:
Indicates the reply that was received to the last request for parameter confirmation. P1 is the system's ID and P2 is the reply received.
System Action:
None.
User Action:
None.
Reason:
The reply received for confirmation of parameters was invalid. It was not in valid keyword format. P1 is the system's ID and P2 is the error message received.
System Action:
None.
User Action:
None.
Reason:
The parameters for the P2 process were reset to their initial values. The system's ID is P1.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
An non-numeric value was entered into the field identified by P1 .
System Action:
The field is highlighted and an error message is displayed to the user.
User Action:
Correct the value entered and retry.
Reason:
The command P1 is invalid.
System Action:
Command field is set in error.
User Action:
Enter a valid command.
Reason:
The number of Defined Initiators has been changed to P1 .
System Action:
None
User Action:
The message is informational only.
Reason:
The Group identified by P1 is does not exist on the system specified.
System Action:
The modify command fails.
User Action:
Check the Group is named correctly and that it is defined to JES3.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
No scheduler jobs found.
System Action:
None
User Action:
None
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The dataset which contains the required JCL member could not be allocated. P1 contains the error message received.
System Action:
The procedure terminates in error.
User Action:
Contact your system administrator.
Reason:
The JCL for this job has been successfully submitted to JES.
System Action:
None.
User Action:
None.
Reason:
The JCL for this job has not be submitted successfully to JES.
System Action:
Job is placed in automation failed state.
User Action:
Investigate.
Reason:
The List of the JCL member has failed.
System Action:
Procedure terminates in error.
User Action:
Contact your system administrator.
Reason:
JES2 termination has been requested however the resource P2 of type
P1 is still active.
System Action:
The system waits for a reply to the WTOR.
User Action:
Reply P if the active resource is to be terminated with a JES2 PURGE command. Replay C if the active resource is to be terminated with a CANCEL or N for IGNORE if the resource has been terminated already using operator intervention.
Reason:
The JES type has been determined.
System Action:
None
User Action:
None
Reason:
The JES type has not been determined. JES Default assumed.
System Action:
None
User Action:
None
Reason:
The JES type has not been determined. JES Default assumed.
System Action:
None
User Action:
None
Reason:
The JES3 type has been determined.
System Action:
None
User Action:
None
Reason:
Default of JES3 LOCAL assumed.
System Action:
None
User Action:
None
Reason:
Default of JES3 LOCAL assumed.
System Action:
None
User Action:
None
Reason:
Unexpected response received.
System Action:
None
User Action:
Contact your System Administrator.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
The keyword P1 was deleted.
System Action:
None.
User Action:
None.
Reason:
The keyword P1 cannot be updated because it is already being updated by user P2.
System Action:
Request is rejected.
User Action:
Try later.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
The selected record is already being updated by user P1.
System Action:
Request rejected.
User Action:
Try later.
Reason:
One or more required fields were not entered.
System Action:
Field(s) set in error.
User Action:
Enter values for the omitted field(s).
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
All system keywords are reserved and cannot have actions applied against them.
System Action:
The request is rejected.
User Action:
None.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
An invalid keyword value was passed. The keyword is P1 and the invalid value is P2.
System Action:
The request is rejected.
User Action:
Correct the invalid value and retry the request.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The activity log will be swapped.
System Action:
The next available activity log will be emptied and will then become the active log.
User Action:
None.
Reason:
A log browse request has been received, but no log can be found for the requested starting date and time.
System Action:
Request is rejected.
User Action:
None.
Reason:
The user cancelled the log swap request.
System Action:
The log is not swapped.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
No log file are available.
System Action:
Logproc will terminate.
User Action:
Contact your system administrator.
Reason:
No log file are available.
System Action:
Logproc will terminate.
User Action:
Contact your system administrator.
Reason:
The executing NCL process with the specified NCLID has been flushed to enable a Log Swap to take place.
System Action:
None.
User Action:
None.
Reason:
The specified User was has been cancelled to enable a Log Swap to take place.
System Action:
None.
User Action:
None.
Reason:
This region is licensed as a SOLVE:Operations for IT/Operations or OpenView agent only and cannot be run in automated mode.
System Action:
The request is rejected.
User Action:
If a full license is required, contact Technical Support.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
$RMLINK has been called with parameters which are not consistent with Keyword format (ie. KEYWORD=<value>).
System Action:
Procedure completed in error.
User Action:
Correct the calling procedure and rerun exec.
Reason:
$RMLINK has not be supplied with all required details. The list provides the keywords that are needed.
System Action:
Request is rejected.
User Action:
Correct command and retry.
Reason:
The link request made is not valid.
System Action:
Request is rejected.
User Action:
None.
Reason:
The link request has completed successfully.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
The link manager is attempting to start the component specified in P1 for connected region P2 .
System Action:
None.
User Action:
None.
Reason:
An attempt was made to dynamically define a component, but it has failed. P1 contains the name of the failed component, while P2 and P3 contain the return code and failure message respectively.
System Action:
Processing continues.
User Action:
None.
Reason:
The region specified in P1 has been unlinked.
System Action:
None.
User Action:
None.
Reason:
The local or remote database is blocked against link access.
System Action:
The traffic manager terminates.
User Action:
Synchronize the databases if you require contact between the regions.
Reason:
The Database does not have a Database Information Record defined. Therefore no correlator ID checking can be performed.
System Action:
The traffic manager terminates.
User Action:
The database has not been initialized correctly. Contact your Systems Administrator.
Reason:
An error was encountered when trying to retrieve a record from the database.
System Action:
Traffic is not received from the linked system until the Link Manager is restarted.
User Action:
Contact your System Administrator.
Reason:
A Traffic Manager attempted the APPC verb P1 which resulted in the error.
System Action:
The conversation is terminated and will be retried later.
User Action:
Determine whether the remote system is still available. Contact your System Administrator.
Reason:
The database correlator does not match the database correlator on the connected region. This indicates that the connected region has been unlinked.
System Action:
The traffic manager will terminate.
User Action:
None.
Reason:
The database at the remote end of the link could not be accessed.
System Action:
The traffic manager will terminate.
User Action:
See the remote log for the cause of the error.
Reason:
An Unlink request has been received from the indicated region.
System Action:
The traffic manager will terminate and the indicated region will be unlinked.
User Action:
None.
Reason:
An Unlink was performed on the local region, P1. This resulted in P2 connected regions being unlinked from this region.
System Action:
All connected regions where unlinked from the local region.
User Action:
None.
Reason:
Either the current region or the linked region was Unlinked and therefore the Traffic Manager is no longer required and has been shut down.
System Action:
None.
User Action:
None.
Reason:
The link manager is stopping the traffic manager specified in P1 for the connected region P2 because the connected region does not have the required license.
System Action:
The traffic manager stops and the internal resource that represents it is deleted.
User Action:
If the remote region should be licensed for the specified type of traffic, stop the region, update it to include the licence, and then restart it.
Reason:
The Linked Regions list service procedure was called with keyword P2 set to a value ( P1 ) which the procedure does not support.
System Action:
The request is rejected.
User Action:
Check the defined allowed values for the keyword P2 and retry.
Reason:
No records found to be displayed in the selection list.
System Action:
None.
User Action:
None.
Reason:
The P1 region has been unlinked.
System Action:
None.
User Action:
None.
Reason:
An Unlink was performed on the home region, P1. This resulted in P2 remote region(s) being unlinked from this region.
System Action:
None.
User Action:
None.
Reason:
An error occurred while performing function P1 on vartable P2. The FDBK code returned was P3 and P4 the key of the record being processed.
System Action:
Request rejected.
User Action:
Contact your Systems Administrator.
Reason:
The Unlink option was selected for an ACB other than the current ACB. This option is only supported for the current region.
System Action:
The request is rejected.
User Action:
Log on to the region that you wish to Unlink and select the Unlink (D) option from the Linked Regions list on that region.
Reason:
A vartable error occurred while performing function(P1) on vartable(P2). The FDBK was P3 and the entry key was P4.
System Action:
Request rejected.
User Action:
Contact your Systems Administrator.
Reason:
The database correlator does not match with the database correlator on a connected region. This indicates that the connected region has been unlinked.
System Action:
The traffic manager will terminate.
User Action:
None.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
The local database is blocked against link access.
System Action:
The traffic manager terminates.
User Action:
Synchronize the databases if you require contact between the regions.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
The Database does not have a Database Information Record defined. Therefore no correlator ID checking can be performed.
System Action:
The traffic manager terminates.
User Action:
The database has not been initialized correctly. Contact your Systems Administrator.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
An error was encountered when trying to retrieve a record from the database.
System Action:
Traffic is not sent to the linked system until the Link Manager is restarted.
User Action:
Contact your Systems Administrator.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
A Traffic Manager attempted the APPC verb P1 which resulted in the error.
System Action:
The conversation is terminated and will be retried later.
User Action:
Determine whether the remote system is still available. Contact your Systems Administrator.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
A region attempted to commence communications with another region, but the former region had been Unlinked while it was not active. A signal will be returned to that region to permanently terminate the connection.
System Action:
None.
User Action:
None.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
A region attempted to commence communications with another region, but the two regions had the same active System Image and could not be connected. P3 identifies the type of connection being attempted.
System Action:
The regions are not connected. Events and database updates are not transmitted between the regions but are held in staging files until the regions are connected.
User Action:
Two connected regions should not have the same active System Image. Load a different System Image in one of the regions, and the regions will be connected automatically.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
A link manager from a connected region attempted to start communication with the current region but could not because database synchronization was in progress on the current region.
System Action:
The request is rejected and will be re-attempted when database synchronization has completed.
User Action:
None.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
A link manager from a connected region attempted to start communication with the current region but the connecting region has been Unlinked by user request at some earlier time.
System Action:
The link manager is terminated and the connected region will be permanently disconnected.
User Action:
None.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
A region attempted to commence communications with another region, but the two regions had the same Domain ID and could not be connected. P3 identifies the type of connection being attempted, and P4 is the region to which the connection was being attempted.
System Action:
The regions are not connected. Resource status events are not transmitted between the regions. Database updates are held in staging files until the regions are connected.
User Action:
Two connected regions must not have the same domain ID. Restart one of the regions with a different Domain ID, and the regions will be connected automatically.
The status of the Link Managers can be checked at any time by issuing
FILTER INTNL from within the Status Monitor.
Reason:
The Link Record definition panel display service procedure was called with keyword P2 set to a value ( P1 ) which the procedure does not support.
System Action:
The request is rejected.
User Action:
Check the defined allowed values for the keyword P2 and retry.
Reason:
Validation found no entry specified on mandatory field/s.
System Action:
The request is rejected.
User Action:
Specify entry on field/s in error.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The Object ID was not found and can not be created because there is not enough information passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact your System Administrator.
Reason:
An Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
An error occurred while performing function P1 on vartable P2. The FDBK code returned was P3 and P4 the key of the record being processed.
System Action:
Request rejected.
User Action:
Contact your Systems Administrator.
Reason:
The Link Name assigned to a link definition is already assigned to another link definition.
System Action:
The Link Name field is highlighted as in error.
User Action:
Change the value in the Link Name field.
Reason:
An invalid parameter value was passed to the Link Resource activation/inactivation process ($RMLK05P).
System Action:
The link resource process terminates.
User Action:
Contact Technical Support.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Function key P1 was pressed but the command assigned to it was invalid.
System Action:
The command is rejected.
User Action:
Contact System Administrator.
Reason:
An invalid class specified.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Both System name and Version are mandatory field.
System Action:
The request is rejected.
User Action:
Specify System name and Version or use '?' to display available System name and Version to the system.
Reason:
Sysname and Version specified is unknown to the system.
System Action:
The request is rejected.
User Action:
Use '?' to list a selection list of Sysname and Version known to system.
Reason:
Template definition is a special definition which must be access only from Customisation Menu option "T".
System Action:
The request is rejected.
User Action:
Access Template definition from Customisation menu option "T".
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
An invalid format was received for an unsolicited event data.
System Action:
The event data is not processd; however, the text of the event message is written to the activity log.
User Action:
Contact your local support representative and provide the details of the event message.
Reason:
The profile was requested to be reset, but no profile was in effect.
System Action:
The request is rejected.
User Action:
None.
Reason:
A restart of the transient log handler completed without errors.
System Action:
None.
User Action:
None.
Reason:
The transient log handler terminated because a restart of the handler was requested.
System Action:
None.
User Action:
None.
Reason:
You attempted to start the transient log handler; however, it is already running.
The transient log handler is always restarted during a system image load and should never be stopped while the region is active.
System Action:
None.
User Action:
None.
Reason:
No Log records exist.
System Action:
No further processing.
User Action:
None.
Reason:
The command which was entered is not supported on this screen.
System Action:
Command is rejected.
User Action:
None.
Reason:
Function key P1 was pressed and the command assigned to it was invalid
System Action:
Command is rejected.
User Action:
Contact System Administrator.
Reason:
You attempted to view transient log records; however, logging is disabled for this resource.
Logging is disabled by one of the following methods:
System Action:
None.
User Action:
None.
Reason:
A PROFILE EDS command, issued internally by Resource Learning, failed with message P1.
System Action:
Resource Learning fails.
User Action:
Contact your local support representative.
Reason:
Resource Learning is listening for any messages concerned with the resource that is being created. These will be displayed on the list automatically as soon as they are detected.
System Action:
None.
User Action:
None.
Reason:
The profile command entered is invalid.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun the executable.
Reason:
The profile is reset.
System Action:
None.
User Action:
None.
Reason:
The profile was modified successfully.
System Action:
None.
User Action:
None.
Reason:
The profile command was not successful.
System Action:
None.
User Action:
Correct and retry.
Reason:
The transient log size for the current resource is P1 (increased or decreased) from P2 to P3 for one of the following reasons, P4:
Indicates that the transient log size for this resource has been updated.
Indicates that the default value specified in the AUTOTABLES parameter group has been updated.
Indicates that the maximum value specified in the AUTOTABLES parameter group has been updated.
Indicates that the maximum value specified in the AUTOTABLES parameter group has been updated and the current value specified for this resource exceeds this maximum.
System Action:
None.
User Action:
None.
Reason:
The current view of the transient log browser ended because the log is being resized.
System Action:
None.
User Action:
Retry the L command to restart the transient log browser.
Reason:
The indicated number, P1, of messages in the transient log are deleted according to the retention period specified in the AUTOTABLES parameter group.
System Action:
None.
User Action:
None.
Reason:
A message was received by the logger procedure for a resource that has the 'Log to Activity Log' flag set to YES.
P1 is the class of the resource.
P2 is the resource name.
P3 is the severity level of the message.
P4 is the ID of the NCL process that raised the message.
P5 is the name of the NCL procedure that raised the message.
P6 is the actual message received by the logger procedure.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Please contact your local support representative.
Reason:
As this resource exists in a remote region, an APPC conversation is required to process this log request. APPC function P1 has ended in error. P2 contains the return code, P3 the feedback code, and P4 the message describing the failure.
System Action:
Processing terminated in error.
User Action:
Determine whether the remote system is still available. Contact your systems administrator.
Reason:
The profile command entered was invalid.
System Action:
The request is rejected.
User Action:
Respecify the profile with the correct keywords.
Reason:
The profile was requested to be reset, but no profile was in effect.
System Action:
The request is rejected.
User Action:
None.
Reason:
The profile has been reset.
System Action:
None.
User Action:
None.
Reason:
The profile has been modified successfully.
System Action:
None.
User Action:
None.
Reason:
The profile command was not successful.
System Action:
None.
User Action:
Correct and retry.
Reason:
The command which was entered is not supported on this screen.
System Action:
Command is rejected.
User Action:
None.
Reason:
Function key P1 was pressed and the command assigned to it was invalid
System Action:
Command is rejected.
User Action:
Contact System Administrator.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Please contact your local support representative.
Reason:
As this resource exists in a remote region, an APPC conversation is required to process this log request. APPC function P1 has ended in error. P2 contains the return code, P3 the feedback code, and P4 the message describing the failure.
System Action:
Processing terminated in error.
User Action:
Determine whether the remote system is still available. Contact your systems administrator.
Reason:
No Log records exist.
System Action:
No further processing.
User Action:
None.
Reason:
Procedure in unexpected APPC "What Received" State.
System Action:
None.
User Action:
Contact System Administrator.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Please contact your local support representative.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Please contact your local support representative.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Please contact your local support representative.
Reason:
The PROFILE command entered was invalid.
System Action:
The request is rejected.
User Action:
Respecify the PROFILE command with the correct keywords.
Reason:
The profile was requested to be reset, but no profile was in effect.
System Action:
The request is rejected.
User Action:
None.
Reason:
The profile has been reset.
System Action:
None.
User Action:
None.
Reason:
The profile has been modified successfully.
System Action:
None.
User Action:
None.
Reason:
The user cancelled the profile command.
System Action:
None.
User Action:
None.
Reason:
No Log records exist.
System Action:
No further processing.
User Action:
None.
Reason:
The command which was entered is not supported on this screen.
System Action:
Command is rejected.
User Action:
None.
Reason:
Function key P1 was pressed and the command assigned to it was invalid
System Action:
Command is rejected.
User Action:
Contact System Administrator.
Reason:
No Log records exist.
System Action:
No further processing.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Please contact your local support representative.
Reason:
You have selected a service or an owner resource. No resource records were found to match the service or ownership criteria for the resource. The type is identified by P1, and the name of the service or owner is identified by P2.
System Action:
None.
User Action:
The message is informational only.
Reason:
An error occurred while attempting to build a resource list for the entity identified by P1 .
System Action:
None.
User Action:
Contact your local support representative.
Reason:
An error occurred while getting the first record in the vartable.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
An error occurred while adding a record to the vartable.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
An error occurred while getting a record from the vartable.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
An error occurred while getting a record from the $RM$$LOGOBJ vartable.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
Procedure $RMLOAD was invoked with an invlaid value of P2 for keyword P1.
System Action:
Request rejected.
User Action:
Correct call and retry.
Reason:
Self Explanatory
System Action:
Request rejected.
User Action:
Specify one of the correct values
Reason:
The entity identified by P1 has been shut down due to a request for a system image load made by the user identified by P2.
System Action:
Informational only.
User Action:
None.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
This message indicates an action being performed by the system image load procedure.
System Action:
None.
User Action:
None.
Reason:
A System Image load request was rejected because the System Image is loaded on a linked region.
System Action:
None.
User Action:
None.
Reason:
A System Image load request was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
The System Image name supplied in a load command is not the name of an active System Image.
System Action:
The load request is rejected.
User Action:
Correct the System Image name and retry.
Reason:
This region is licensed as a SOLVE:Operations for IT/Operations or OpenView agent only and cannot be run in automated mode.
System Action:
The request is rejected.
User Action:
If a full license is required, contact Technical Support.
Reason:
The valid values for P1 are 'YES' or 'NO'.
System Action:
Request rejected.
User Action:
Specify one of the correct values either 'YES' or 'NO'.
Reason:
Cannot Warm Start as Checkpoint Restart is not active.
System Action:
Value changed to 'YES', error message displayed to user.
User Action:
None.
Reason:
A request to load a new system image was rejected because there is already a system load in progress. The current load was started at P1.
System Action:
Request rejected.
User Action:
None.
| Copyright © 2012 CA. All rights reserved. |
|