|
|
|
Reason:
An initialization action has completed successfully. The specific action was started by the EXEC $IACALL P1 P2 command.
System Action:
Initialization continues.
User Action:
None.
Reason:
An initialization action has failed. The specific action was started by the EXEC $IACALL P1 P2 command. Other messages have been logged that indicate the cause of the failure.
System Action:
Initialization continues.
User Action:
Refer to the SOLVE log. The failure messages should immediately precede this message. Refer to those messages to resolve the problem.
Reason:
An initialization action has resulted in a dataset being implicitly allocated. The message indicates which DD name was allocated (P1) and the dataset name (P2). The action to which this relates can be identified in the SOLVE log by either:
SOLVE datasets are normally allocated by either:
This message indicates that neither action has occurred. As the dataset must be allocated before it can be opened, SOLVE has assumed a dataset name based on the relevant shared or local dataset qualifier (as specified in the DSNQSHR and DSNQLCL JCL parms), plus the DD name.
If the assumed dataset name is incorrect, the initialization action will be incomplete.
System Action:
Initialization continues.
User Action:
It is recommended that SOLVE datasets are specifically allocated in the run JCL. Alternatively, the EXEC $IACALL command should include the DSN= operand specifying the full dataset name.
Reason:
An initialization action has failed. The specific action was started by the EXEC $IACALL command where the first parameter is called a primitive. The primitive is either missing or is invalid.
System Action:
Initialization continues but may be incomplete.
User Action:
Correct the command in the initialization procedure. For this to take effect either restart the region or execute the command manually using OCS or Command Entry.
Reason:
An initialization action has failed. The specific action was started by the EXEC $IACALL command where the second parameter is called a qualifier. The qualifier is either missing or is invalid.
System Action:
Initialization continues but may be incomplete.
User Action:
Correct the command in the initialization procedure. For this to take effect either restart the region or execute the command manually using OCS or Command Entry.
Reason:
An initialization action has failed. The specific action was started by the EXEC $IACALL P1 P2 command where the first parameter (P1) is called the primitive and the second parameter (P2) is called the qualifier. The qualifier is a valid qualifier but does not apply to the specific primitive.
System Action:
Initialization continues but may be incomplete.
User Action:
Correct the command in the initialization procedure. For this to take effect either restart the region or execute the command manually using OCS or Command Entry.
Reason:
An initialization action has failed. The specific action was started by the EXEC $IACALL P2 P3 command which requires parameter (P1) but this was not specified.
System Action:
Initialization continues but may be incomplete.
User Action:
Correct the command in the initialization procedure. For this to take effect either restart the region or execute the command manually using OCS or Command Entry.
Reason:
An invalid keyword parameter value was specified for procedure $IAICALL. The keyword is P1 and the invalid value is P2.
System Action:
Procedure terminates.
User Action:
Correct the invalid keyword value and retry the request.
Reason:
An attempt to start an initialization phase failed because the phase was already being processed. The phase was P1.
System Action:
Procedure terminates.
User Action:
If the phase specified was incorrect then retry the request, specifying the correct phase.
Reason:
An attempt to start initialization phase P1 failed because that phase can only be started after its defined predecessor. The current phase is P2. The INIT phase must always be the first phase, then the READY phase can started.
System Action:
Procedure terminates.
User Action:
Specify the correct successor phase for phase P2.
Reason:
An attempt to start initialization failed because it either has already completed or is already in progress. The current initialization status is P1.
System Action:
Procedure terminates.
User Action:
None
Reason:
The P1 initialization phase was successfully started.
System Action:
Initialization processing continues.
User Action:
None.
Reason:
Initialization for the system was completed.
System Action:
None.
User Action:
None.
Reason:
The initialization P1 is entering debug mode. This mode was specified when the start service was requested.
System Action:
None
User Action:
None
Reason:
A set service was requested, but an invalid initialization object was passed to the API. The object must be named $IAINDO and it must be shared to the API. The error occurred assigning component P4, which is of type P3. The MDO return code received was P1 and the feedback code was P2.
System Action:
The request is rejected.
User Action:
Correct the object passed to the API and retry the request.
Reason:
The initialization objects were successfully defined for the initialization wizard P1.
System Action:
None.
User Action:
None.
Reason:
The System Symbols will be made available to the INI file P1. This is a header message and the following messages will show the Symbols used and their values.
System Action:
None.
User Action:
None.
Reason:
This message shows the name and value of a System Symbol.
System Action:
None.
User Action:
None.
Reason:
This message indicates that there are no more system symbols to display.
System Action:
None
User Action:
None
Reason:
An invalid keyword parameter value was specified for procedure $IAIN01U. The keyword is P1 and the invalid value is P2.
System Action:
Procedure terminates.
User Action:
Contact your Systems Administrator.
Reason:
An attempt to invoke the initialization wizard procedure P1 failed. The procedure was not found in the commands library or was in error.
System Action:
Initialization load fails.
User Action:
Contact your Systems Administrator.
Reason:
The initialization wizard P1 has successfully completed its processing to define the system parameters.
System Action:
None
User Action:
None
Reason:
The parameter group P1 is a non-dynamic parameter group. This means that the parameters can be updated at any time but they will only become effective at the NEXT system startup.
System Action:
None
User Action:
None
Reason:
The parameter group could not be started because the lock issued to obtain exclusive control failed, indicating that user P1 was already actioning the parameter group or was updating the parameter group.
System Action:
The request is rejected.
User Action:
Wait until user P1 completes their update and then action the parameter group again, or if the parameter group was already being actioned then wait for this request to complete.
Reason:
The GLBL type parameter of a parameter group was incorrectly named. The parameter cannot be set.
System Action:
Processing for the parameter group fails.
User Action:
Contact your Systems Administrator.
Reason:
The parameter group P1 was not defined to the system because it specified a prerequisite parameter group P2 that did not exist. This may be because your system is not licensed for a feature which defines the parameter group P2.
Parameter group P1 cannot be defined without this prerequisite.
System Action:
Parameter group P1 is bypassed.
User Action:
None
Reason:
The parameter group P2 specified the parameter group P1 as an optional prerequisite and parameter group P1 did not exist. This may be because your system is not licensed for a feature which defines parameter group P1 OR because the prerequisite parameter group was made obsolete by a licensed feature that is currently licensed on this system. The prerequisite is an optional prerequisite and so has been ignored.
System Action:
Prerequisite parameter group P1 is ignored.
User Action:
None
Reason:
The INIT type parameter of a parameter group was incorrectly named. The parameter cannot be set.
System Action:
Processing for the parameter group fails.
User Action:
Contact your Systems Administrator.
Reason:
The parameter group P1 was successfully updated. The parameter settings will be effective for the next system startup.
System Action:
None
User Action:
None
Reason:
The request to update a parameter group was denied because the user P1 is already updating that parameter group.
System Action:
Request denied.
User Action:
Wait until no other user is updating the parameter group.
Reason:
The parameter group P1 was set as requested and the status of the action was P2. If the status was COMPLETED then the values specified for the parameter group will be effective immediately. If the status was FAILED then view the Initialization Log for this parameter group and correct the errors indicated.
System Action:
None
User Action:
If the status was FAILED then view the Initialization Log to determine the cause of the failure. Correct the errors or update the parameter group to correct any parameter values.
Reason:
The initialization monitor process completed all possible processing for initialization phase P1. There are P2 failures outstanding.
System Action:
Processing continues.
User Action:
Correct the errors encountered by any failed parameter groups from the Initialization Monitor list.
Reason:
The keyword P1 was specified with a value. This keyword does not support the specification of a value.
System Action:
Field is set in error.
User Action:
Remove the value specification for the keyword.
Reason:
The DBCS= keyword was specified with an invalid value P1. The only valid values for the UDB command operand keyword DBCS are IBM or FUJITSU.
System Action:
Field is set in error.
User Action:
Correct the value of the DBCS keyword.
Reason:
An error occurred when opening the VFS file for processing by the initialization utilities. The file return code received was P1 .
System Action:
Processing terminates.
User Action:
Contact your Systems Administrator.
Reason:
An error occurred processing the VFS file. The file request was P1, the file return code was P2, the VSAM feedback code was P3, and the key of the record being processed was P4.
System Action:
Processing terminates.
User Action:
Contact your Systems Administrator.
Reason:
A request to clear the VFS file of all parameter groups was successful. There were P1 records deleted.
System Action:
None
User Action:
None
Reason:
The command specified was not recognized as a valid command.
System Action:
Request denied.
User Action:
Enter a valid command for press a valid function key.
Reason:
The request to cancel the previous function was successful.
System Action:
None
User Action:
None
Reason:
During system initialization it was determined that the Customizer had not been used to initialize this system before. This may be because the system has just been installed or it may be because a different VFS file has been used for this system startup.
If a different VFS file has been used, then restart the system with the correct VFS file. Otherwise, you will need to recustomize the system, because the customization parameter settings are stored on the VFS file).
System Action:
None
User Action:
You may wish to restart the system using a different VFS file if this system has been customized.
Reason:
The parameter could not be set because it is only possible to set the parameter during a specific initialization phase. The current initialization phase does not match the parameter's requirement. The parameter name is P1 and the required phase is P2.
System Action:
Parameter is not set.
User Action:
None. The parameter will be set during the next system initialization.
Reason:
An attempt to start the initialization monitor process failed because another process is already running and monitoring initialization.
System Action:
Request denied.
User Action:
None
Reason:
The global variable P1 was set to the value P2 .
System Action:
None
User Action:
None
Reason:
The initialization monitor process has completed its processing because all initialization parameter groups have completed their processing.
System Action:
None
User Action:
None
Reason:
The parameter group P1 has been started by the Customizer and it will begin to process its parameters.
System Action:
None
User Action:
None
Reason:
The system has begun the process of loading parameter groups for the wizard procedure P1 .
System Action:
None
User Action:
None
Reason:
The parameter group P1 was not found in the VFS file.
System Action:
None
User Action:
None
Reason:
The system has completed the process of verifying and resolving parameter group prerequisites and because of required prerequisites not being present, P1 parameter groups were bypassed. This may occur when parameter groups of licensed features are not defined because the feature is not licensed for this system.
System Action:
None
User Action:
Ensure that your system has the correct license.
Reason:
The system has completed the process of loading all of its parameter groups. There were P1 groups loaded.
System Action:
None
User Action:
None
Reason:
The initialization monitor process has been started. This process will start the processing of parameter groups in a controlled fashion until all parameter groups have been set.
System Action:
None
User Action:
None
Reason:
The parameter group P1 was successfully updated. The setting of these parameters for the current execution is either pending the completion of other parameter groups' processing or waiting for the system to schedule it. This occurs because the system has not completed its normal system initialization, when parameter groups are set in an ordered and controlled fashion.
System Action:
None
User Action:
None
Reason:
The parameter group service procedure P1 was invoked to perform a task associated with the parameter group P3. The service procedure returned a failure return code of P2.
System Action:
Processing for the parameter group failed.
User Action:
Check preceding messages to determine the cause of the error.
Reason:
The initialization phase P1 was forced to completion by the initiation of phase P2. All parameter groups from phase P1 will be processed in phase P2.
System Action:
None
User Action:
None
Reason:
A request to set the parameters of parameter group P2 was received from user P1 . The initialization monitor process has accepted this request and will begin the processing of this parameter group.
System Action:
Processing for the parameter group is started.
User Action:
None
Reason:
A request to set the parameters of parameter group P2 was received from user P1. The initialization monitor process has rejected this request because the parameter group's status indicates that it is not eligible to be set.
During system initialization, parameters can be updated and set only if they are in FAILED or COMPLETED status. If the parameter group is in QUEUED or WAITING status, then it will be set when all prerequisite parameter groups have been completed. If the parameter group is in RUNNING status, then it is currently in the process of setting the parameters and cannot be changed until after it has completed or failed.
System Action:
None
User Action:
None
Reason:
A request to ignore the failed status of parameter group P2 was received from user P1. The initialization monitor process has rejected this request because the parameter group's status indicates that it is not eligible to be ignored. Only parameter groups in FAILED status can be ignored.
System Action:
None
User Action:
None
Reason:
A request to ignore the failed status of parameter group P2 was received from user P1. The initialization monitor process has accepted this request and will ignore the failed status.
System Action:
None
User Action:
None
Reason:
A request by user P2 to initiate processing for phase P1 was denied because the phase is invalid.
System Action:
Request is rejected.
User Action:
Specify a valid phase and retry the request.
Reason:
A request by user P2 to initiate processing for phase P1 was ignored because the phase has already been initiated.
System Action:
Request is rejected.
User Action:
None
Reason:
The parameter group service procedure P2 failed. The procedure was invoked to set the parameter P1 and returned a failure return code. The return code was P3.
System Action:
Processing for the parameter group fails.
User Action:
Check related messages for the reason the set failed.
Reason:
The initialization monitor was invoked to display the current status of initialization. However, initialization has already completed and there is nothing to display.
System Action:
None
User Action:
None
Reason:
The initialization monitor process has detected parameter group failures. P1 is the jobname of the system for which the message was issued.
System Action:
None
User Action:
Invoke the initialization monitor and check the reason for the failures.
Reason:
The specified procedure P1 was not found in the target user ID's commands DDNAME. The target user ID is P3 and their commands DDNAME is
P2.
System Action:
Field set in error.
User Action:
Specify a procedure that is valid and exists.
Reason:
The user whose user ID is P1 is not authorized to perform the action requested.
System Action:
Request rejected.
User Action:
None
Reason:
There are one or more parameter groups being updated by one or more other users. INI procedures can be generated only if there are no other users updating parameters.
System Action:
Request rejected.
User Action:
Wait until no other user is updating the parameter groups.
Reason:
There are no parameter groups defined for this system. This condition occurs if the system is never started using the PARMS specifications in the INIT and READY initialization procedures and/or the DEFINE service has never been invoked to define the parameter groups.
System Action:
Request rejected.
User Action:
Start the system using the PARMS specification in the INIT and READY initialization procedures or use the \PARMS DEFINE service.
Reason:
The field P1 is a required field.
System Action:
Field is set in error.
User Action:
Specify a value for P1.
Reason:
The IDCAMS service P1 failed and the return code received was P2.
System Action:
The request terminates.
User Action:
View the activity log for IIIN0150 messages which show the responses from IDCAMS.
Reason:
This is a bracketing message for the IDCAMS messages returned from a previous call.
System Action:
None
User Action:
Determine the error as indicated in the IDCAMS message and retry your request.
Reason:
The file request P1 failed for the file allocated with DDNAME P2 . The file return code was P3 and the VSAM feedback code was P4 .
System Action:
The requested is terminated.
User Action:
Determine the reason for the error and retry the request.
Reason:
An invalid value was specified for field P1 .
System Action:
Field is set in error.
User Action:
Correct the field and retry the request.
Reason:
The target INI file dataset name MUST specify a partitioned dataset.
System Action:
Field is set in error.
User Action:
Specify a partitioned dataset name.
Reason:
The INI procedure was successfully generated and saved as requested.
System Action:
None
User Action:
None
Reason:
The Customizer initialization wizard procedure P1 either was not defined or is invalid.
System Action:
The requested action is terminated.
User Action:
Check that the system was started using the \PARMS invocations in the INIT and READY initialization procedures or that the \PARMS define service has been invoked.
Reason:
The parameter group P1 was updated with the system defaults.
System Action:
None
User Action:
None
Reason:
The target INI file member specified already exists and Replace Member was set to NO.
System Action:
Field is set in error.
User Action:
Either specify a member name that doesn't exist or change the Replace Member field to YES.
Reason:
The supplied INI procedure returned a non-zero return code. This means that there was an error in setting the customized parameter values or that the INI does not support this parameter group. P2 P3 is the Appl ID and Name of the parameter group being defined.
This condition can also occur if a new parameter group has been defined by distributed code that had not be used by this system previously, perhaps because the system was running on a different operating system environment or product maintenance has added a new parameter group.
System Action:
The parameter group is customized using the values set in the VFS file. If this is a new parameter group, then its default values will be used.
User Action:
Check your INI procedure to ensure that it sets customized values for all parameter groups. If the parameter group is new, then regenerate your INI procedure after the system has initialized. If your INI procedure specifically ignores certain parameter groups so that the customization for these parameter groups is taken from the VFS file, then ignore this message.
Reason:
A dataset was specified that is not a key sequenced dataset or that has an invalid key length. The dataset must be a key sequenced dataset (that is, a KSDS/BASE type dataset) and its key length must be P1 .
System Action:
Field is set in error.
User Action:
Specify a dataset with the correct attributes.
Reason:
A requested function is not supported for the Operating System environment P1.
System Action:
Request is rejected.
User Action:
None
Reason:
The specification of a single level dataset name for a parameter is not accepted.
System Action:
Field is set in error.
User Action:
Specify a fully qualified dataset name without quotes and with more than one level.
Reason:
A request to action a parameter group by user P1 failed because the user was not authorized for APPC access to the system user P2 . The specific problem is defined by the error reference P3 , which is either N47J06 or N47J08.
If the reference is N47J06, then it indicates that the APPC access key for user P1 did not match the APPC lock for the system user ID P2 .
If the reference is N47J08, then it indicates that the user could not be signed on to the system user. This could be caused by the system user ID not having a specific user ID definition.
Check the activity log for related APPC messages that will further explain the error condition.
System Action:
The request to action the parameter group is rejected.
User Action:
Contact your systems administrator.
If you are using UAMS, the definition for user P1 must specify a matching key for the lock specified in the system user's definition. The system user must have a user ID definition specifying a lock accessible by other users.
For full SAF security, the user P1 must be defined to the security system.
Reason:
Specification of an NDB was invalid because the NDB was not defined for the current version of P1 system.
System Action:
Field is set in error.
User Action:
Specify a valid NDB for system P1.
Reason:
The START service for Customizer did not detect any activity for initialization for P1 seconds. This occurs if an initialization parameter group's associated actions have not notified the Customizer monitor of their success or failure, but are either still running or waiting for some event to occur.
System Action:
All parameter groups that are QUEUED are reviewed by the Customizer monitor. If any of these parameter groups is waiting for a currently RUNNING parameter group to complete and that dependency is only for the purpose of ordering the execution of the parameter group, then that dependency is removed.
As a result of removing all such soft dependencies on parameter groups, any that become eligible for actioning are started.
If no parameter group can be actioned, then the current initialization phase is terminated and the next phase is initiated. If the current phase is GO, then Customizer will wait until all parameter groups have completed processing. Operator intervention may be required.
User Action:
This condition may occur if external resources are not available to the region and it has been forced, by the operating system, to wait until the resource is available.
The most common such resource is a dataset that is required for allocation to the region and the request is waiting for some external event to occur. If so, then ensure that all required resources are available when the region is started.
This condition may also occur in a system with poor response. In this case the Customizer timeout must be increased to compensate. Within the RMINIT procedure, specify the following NCL statement BEFORE the execution of the $IICALL procedure:
&&000$IIINMXW = 600 -* ICS TIMEOUT IS 10 MINUTES
The default value for this timeout is 300 seconds (5 minutes) and it can be increased to prevent Customizer from assuming that there are problems.
If the system's response is not poor and the default of 300 seconds is considered to be reasonable, then there could be errors in the currently RUNNING parameter group's actions and you may need to contact your Technical Support representative.
Reason:
The phase P1 will be terminated because no activity is occurring in ICS and all parameter groups which should have completed have not done so. This message is accompanied by message IIIN0164 (see the explanation for this message).
System Action:
The phase P1 will be terminated and the next phase will be initiated.
User Action:
See message IIIN0164.
Reason:
Because of a previous ICS timeout, P1 parameter groups were evaluated as eligible for starting. All these parameter groups are started.
System Action:
P1 parameter groups will be actioned.
User Action:
See message IIIN0164.
Reason:
The processing for parameter group P2 failed. The error message for the parameter group follows this message. P1 is the jobname of the system for which the message was issued.
System Action:
Dependent parameter groups will be queued until this parameter group is rerun and completes successfully or is ignored. Parameter groups whose dependency is only for ordering will be started.
User Action:
See following message for more details of the actual error for the parameter group. Correct the error indicated by this message and any other error messages in the failed parameter group's log. If the failed parameter group is PANELLIBS or MODSFILES, then problems may be experienced when logging on to the system.
Reason:
The action requested could not be performed because validation errors were detected for fields that are not present on the current page of the parameter group's display.
System Action:
Request is rejected.
User Action:
Scroll to the other pages for the parameter group and correct the fields in error. Retry the request.
Reason:
Initialization detected one or more errors in processing, but the errors were not severe enough to halt initialization. The errors detected can be found in the initialization log, accessed from the Customization Menu. The errors detected are those colored pink.
System Action:
Processing continues. Problems may be experienced with some components because of the error(s).
User Action:
View the Initialization Log, which can be accessed from the Customization Menu. Review and correct all the errors in pink.
Reason:
This message is related to message IIIN0169 (see the explanation for that message). The message following this one represents the detected error.
System Action:
None
User Action:
See the explanation for message IIIN0169 and for the message following this one. See the Initialization Log, which can be accessed from the Customization Menu.
Reason:
The page number P1 is not a valid number.
System Action:
Page command is rejected.
User Action:
Specify a valid page number.
Reason:
The page number P1 is out of range. It must be a valid number between the values P2 and P3 .
System Action:
Page command is rejected.
User Action:
Specify a valid page number within the indicated range.
Reason:
The dataset specified was not a valid NDB database. The NDB return code received from an NDBOPEN was P1 and the description of that return code is P2 . The description is from the NETINFO database and can be viewed in full by using the $INFO command, under the NDB error codes category.
System Action:
The field is set in error.
User Action:
Specify a valid NDB database dataset name.
Reason:
This message is a header message for the display of the description of an error code contained in another error message. The information shown in subsequent messages is contained within the NETINFO database (this can be accessed by using the $INFO primary command). The information displayed was from the category P1 with error code P2 and the error message that contained the code was P3 .
System Action:
None
User Action:
See message P3 and the description messages that follow this message.
Reason:
This message contains the descriptive text from the NETINFO database. See message IIIN0174 for more details.
System Action:
None
User Action:
For more information view the NETINFO database by using the $INFO primary command.
Reason:
The dataset specified was not a valid, existing dataset. The dynamic allocation reason code (from message N19503) is P1 and the description is P2 . The description is from the NETINFO database and can be viewed in full by using the $INFO command, under the Dynamic Allocation error codes category.
System Action:
The field is set in error.
User Action:
Specify a valid dataset.
Reason:
The system parameter (SYSPARM) with name P1 was already set to the value
P2 and was not set again.
System Action:
None
User Action:
None
Reason:
The parameter group P1 has completed all its processing. The status of its processing is P2 .
System Action:
Any dependent parameter groups will have their dependency on this parameter group removed. These successor parameter groups may be started if this is the last dependency.
User Action:
If the parameter group is in a FAILED status, view the Initialization Log for that parameter group and correct the error.
Reason:
The parameter group P1 was detected as still running and no response has been received for the timeout period. The parameter group may be legitimately waiting for a response from the operating system or there may be errors in the system.
System Action:
None
User Action:
None
Reason:
This message provides an audit trail when a parameter group ( P1 ) is updated or action ( P2 ) and shows the user ID ( P3 ), date ( P4 ) and time ( P5 ) that the activity occurred.
System Action:
None
User Action:
None
Reason:
This message is issued when a parameter group is actioned that resulted in a variable being set. The variable description ( P1 ) and its new value ( P2 ) are shown.
System Action:
None
User Action:
None
Reason:
This message is issued when a parameter group is actioned that resulted in a variable being changed. The variable description ( P1 ) and its old and new values ( P2 and P3 ) are shown.
System Action:
None
User Action:
None
Reason:
A request to set an entire parameter group to its default was rejected. You cannot use the Set Default action for a parameter group during system initialization. Update the group and set the specific parameters required for this system.
System Action:
The request is rejected.
User Action:
Set the individual parameters as required.
Reason:
The parameter group P1 has completed all its processing. The background user id / password has been updated.
System Action:
The update of parameter groups for Scheduler Interface is completed.
User Action:
None
Reason:
A request to ignore a failed status for a parameter group failed because the parameter group was not already in a failed status. The ignore action can only be issued for failed parameter groups.
System Action:
Request rejected.
User Action:
None
Reason:
A request to Action a failed parameter group was accepted. The request was passed to the monitor process. The parameter group for which the action was accepted is P1 . The status of the parameter group will be set by the monitor process dynamically when processing for the group has completed.
System Action:
None
User Action:
None
Reason:
A request to display parameter groups of a particular status(es) was rejected because one or more of the statuses specified was invalid. Valid statuses for the STATUS command are FAILED, RUNNING, COMPLETED, QUEUED, and WAITING.
System Action:
Request rejected.
User Action:
Specify a set of valid statuses separated by commas.
Reason:
A request to action a parameter group was denied because the parameter group was not in FAILED or COMPLETED status. The action request can only be issued for failed or completed parameter groups. This is because the Initialization Monitor process is still actively managing the order of parameter group execution.
System Action:
Request rejected.
User Action:
None
Reason:
A request to restrict the initialization log's view to all messages from a particular initialization phase failed. The initialization phase specified was invalid. Valid initialization phases are:
INITS - Start of initialization (this is an internal phase only)
INIT - The INIT initialization phase that is initiated from the INIT procedure nominated by the startup parameters for the region
READY - The READY initialization phase that is initiated from the READY procedure nominated by the startup parameters for the region
GO - This is an internal phase that represents all initialization that was not scheduled to be performed during the INIT or READY phases. It also includes any initialization that failed during the INIT or READY phases and that was manually actioned during the GO phase.
System Action:
Request is rejected.
User Action:
Specify a valid initialization phase.
Reason:
A request to restrict the Initialization Log's view to all messages for a particular parameter group failed. The application ID specified for the parameter group was invalid. The application ID was P1 .
System Action:
Request rejected.
User Action:
Specify a valid application ID.
Reason:
A request to restrict the Initialization Log's view to all messages for a particular parameter group failed. The parameter group name specified was invalid. The parameter group name was P1 .
System Action:
Request rejected.
User Action:
Specify a valid parameter group name.
Reason:
The user P1 attempted to log on to the region before customization had been performed. The user was the first user to log on; however, they do not have UAMS authority and are thus not eligible to do initial system customization.
System Action:
The request is rejected.
User Action:
Wait until another user performs system customization before logging on.
Reason:
The user P1 attempted to log on to the region before customization had been performed. The user was the first user to log on; however, they are a member of the group P2 that does not have UAMS authority. The group cannot be modified to have UAMS authority. The user is not eligible to do initial system customization.
System Action:
The request is rejected.
User Action:
Wait until another user performs system customization before logging on.
Reason:
The system detected that initialization did not complete and attempted to display a help dialog to that effect; however, there is an error in the help presentation service. The error message returned from the help service is P1.
System Action:
Processing continues.
User Action:
Check the initialization log for initialization errors.
Reason:
An initialization trace could not be selected because the trace table was empty.
System Action:
Request ignored.
User Action:
None
Reason:
The NEXT or PREV command was specified with the parameter P1 and this parameter was not numeric.
System Action:
Request ignored.
User Action:
Specify a valid number.
Reason:
The ALL command was specified with the mnemonic P1 as the parameter. For this particular list, the ALL command does not support this mnemonic.
System Action:
Request ignored.
User Action:
Specify another mnemonic that is supported by the ALL command.
Reason:
The ALL command was requested to delete all the Initialization Traces. There were P1 traces and all were deleted.
System Action:
None
User Action:
None
Reason:
No ICS Debug Traces to display.
System Action:
None
User Action:
None
Reason:
The field P1 is required and must not be blank.
System Action:
Field is set in error.
User Action:
Specify a value for P1.
Reason:
The field P1 is required when the field P2 is specified.
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 value for field P1 must be blank if field P2 is specified.
System Action:
Field set in error.
User Action:
Blank out the value for P1 or the value for P2.
Reason:
The value for field P1 must be blank if the value for field P2 is P3.
System Action:
Field set in error.
User Action:
Blank out the value for P1 or specify a different value for P2.
Reason:
The value for the hi-lighted field must be one of the values in P1.
System Action:
Field set in error.
User Action:
Specify one of the possible values listed in P1.
Reason:
The highlighted field must have a valid dataset name specified.
System Action:
The field is highlighted as an error.
User Action:
Enter a correct value.
Reason:
An internal error occurred because the map P1 was not found in the map dataset.
System Action:
The request is rejected.
User Action:
Contact your system administrator.
Reason:
An internal error occurred. The map P1 experienced the error described by MDORC= P2 and MDOFDBK= P3 .
System Action:
The request is rejected.
User Action:
Contact your system administrator.
Reason:
The dataset specified by P1 was not a sequential dataset.
System Action:
The field containing the dataset name is highlighted as an error.
User Action:
Specify a sequential dataset.
Reason:
A partitioned dataset is specified by P1 but a member name is not specified.
System Action:
The field containing the dataset name is highlighted as an error.
User Action:
Specify the correct dataset or member name.
Reason:
The dataset specified by P1 is not a partitioned dataset.
System Action:
The field containing the dataset name is highlighted as an error.
User Action:
Specify the correct dataset.
Reason:
The dataset specified by P2 does not contain the member P1 .
System Action:
The field containing the dataset name is highlighted as an error.
User Action:
Specify the correct member or dataset name.
Reason:
The dataset specified by P1 cannot be opened for read access.
System Action:
The field containing the dataset name is highlighted as an error.
User Action:
Obtain authority for the SOLVE system to access the dataset.
Reason:
The type of file specified by P1 is not supported. For example it may be a directory name rather than a text file name.
System Action:
The field containing the file name is highlighted as an error.
User Action:
Specify the correct file name.
Reason:
The highlighted field must contain a valid dataset name or a Unix system services file name.
System Action:
The field is highlighted as an error.
User Action:
Enter a correct value.
Reason:
The value for field P1 must be different to the value of field P2.
System Action:
Field set in error.
User Action:
Specify a different value for P1 or P2.
Reason:
A non-VSAM dataset was specified where a VSAM dataset was needed.
System Action:
The field containing the dataset name is highlighted as an error.
User Action:
Specify the correct dataset name.
Reason:
The value for field P1 must be a valid time interval greater than zero.
System Action:
Field set in error.
User Action:
Specify a non-zero time interval for P1.
Reason:
The value for field P1 must be blank if field P2 is also blank.
System Action:
Field set in error.
User Action:
Blank out the value for P1 or specify a value for P2.
Reason:
Columns 1 and 2 of the JCL statement do not contain '//'.
System Action:
Field set in error.
User Action:
Specify '//' in columns 1 and 2.
Reason:
Only a JCL comment or JES3 control statement ('//*' in columns 1 to 3) or a JES2 control statement ('/*' in columns 1 and 2) is allowed.
System Action:
Field set in error.
User Action:
Review the line in error and make any necessary corrections.
Reason:
Only a JCL comment or JES3 control statement ('//*' in columns 1 to 3) or a JES2 control statement ('/*' in columns 1 and 2) is allowed.
System Action:
Field set in error.
User Action:
Review the line in error and make any necessary corrections.
Reason:
A comma was found at the end of the previous line but the next line was not a continuation.
System Action:
Field is set in error.
User Action:
Review the continuation statement and ensure that it begins between columns 4 and 16, or remove the comma from the previous JCL statement.
Reason:
The JCL JOB statement could not be found in the current line.
System Action:
Field is set in error.
User Action:
Review the line in error and ensure that the string 'JOB' appears after the jobname, separated by at least one blank.
Reason:
A jobname must be 1-8 characters in length and can contain only alphanumeric characters or national ($, #, @) characters. The first character must be alphabetic or national.
System Action:
Field is set in error.
User Action:
Correct the line in error.
Reason:
The keyword P1 has been specified more than once.
System Action:
Field is set in error.
User Action:
Correct the line in error.
Reason:
The keyword P1 must contain a single character (A to Z or 0 to 9).
System Action:
Field is set in error.
User Action:
Correct the line in error.
Reason:
The keyword P1 is not allowed.
System Action:
Field is set in error.
User Action:
Correct the line in error.
Reason:
Customizer attempted to process the IIA parameter file for input but the action P1 failed. P2 is additional information about the error.
System Action:
IIA parameters will not be used for this initialization.
User Action:
Correct the error for the next system restart.
Reason:
While processing, the IIA parameter file encountered a record with invalid syntax. The records must specify parm=value, with one parameter per record. The parm must be a valid variable syntax.
System Action:
The record is ignored and processing continues.
User Action:
Correct the error in the parameter file for the next restart of the system.
Reason:
The customizer successfully set the IIA parameter P1 to the value P2.
System Action:
None.
User Action:
None.
Reason:
The value for field P1 must be P2 if field P3 is also P4.
System Action:
Field set in error.
User Action:
Set the value for P1 to P2 or change the value for P3.
Reason:
The value for the field is not a valid HFS path and file name.
System Action:
The value is rejected.
User Action:
Enter a valid fully-qualified Hierarchical File System path and file name.
Reason:
The ddname IIAPARMS is being allocated to the P1 data set.
System Action:
None.
User Action:
None.
Reason:
NO MORE RECORDS FOR THE X25 CATEGORY ON THE FILE
System Action:
No action
User Action:
No action
Reason:
To modify the record overtype all fields which should be changed.
System Action:
None.
User Action:
Overtype existing text to modify the record.
Reason:
A vcbrec code value is necessary to access to a specific record. This value is absent.
System Action:
No action
User Action:
Enter a correct value in the code field and retry.
Reason:
A vcbrec code value is necessary to add the record. This value is absent.
System Action:
No action
User Action:
Enter a correct value in the code field and retry.
Reason:
The F3 key was used to cancel record update.
System Action:
The record remains unchanged.
User Action:
None.
Reason:
When updating a record the key value has changed but a record with this key already exists. Update will overwrite an existing record.
System Action:
None.
User Action:
Press ENTER to proceed, F3 to cancel.
Reason:
A record has been updated successfully.
System Action:
None.
User Action:
None.
Reason:
The record contents were changed before pressing the F11 key to delete the record. This is not allowed.
System Action:
Delete request ignored.
User Action:
Select a record to be deleted and retry.
Reason:
A delete request has been completed successfully.
System Action:
None.
User Action:
None.
Reason:
A record with a code specified was not found.
System Action:
None.
User Action:
Specify a correct code and retry.
Reason:
A VSAM error occured when attempting to delete the record.
System Action:
A record remains unchanged.
User Action:
Refer to the appropriate VSAM manual for the VSAM error code above.
| Copyright © 2012 CA. All rights reserved. |
|