|
|
|
Reason:
The NCL Debug API procedure $SDCALL failed because it was invoked with an invalid keyword value specified. The keyword was P1 and the value was P2.
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The NCL Debug selection list service procedure $SDDB14L failed because it received a call type that is not supported by the service procedure. The call type was P1.
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The INCLUDE or EXCLUDE command was entered but no procedure masks were specified.
System Action:
The command is rejected.
User Action:
Specify a list of procedure masks seperated by blanks. The mask character is *.
Reason:
An error occurred accessing the AOM Global Database. The action being attempted was P1 and the feed back code returned was P2 . The feed back code means P3 . The option (if relevent) was P5 and the key being used was P4 .
System Action:
The action is aborted and processing continues.
User Action:
For user correlator missmatches retry the request. The not found condition may be because of other system components having deleted the entry, similarly for the already exists condition. For other errors see the System Administrator.
Reason:
The maximum number of global variables is P1. The browse and update actions are only supported for indexes less than P1 .
System Action:
Request is rejected.
User Action:
If you wish to change the value of global flags then use the ON and OFF actions.
Reason:
The NCL Debug Static Call Analysis procedure $SDDB19Z failed because it was invoked with an invalid keyword value specified. The keyword was P1 and the value was P2 .
System Action:
The procedure terminates.
User Action:
Contact your Systems Administrator.
Reason:
The NCL Static Call Analysis procedure $SDDB19Z failed because it receive an invalid feedback code from a vartable operation. The table was P1 , the operation or action perfromed was P2 and the returned feedback code was P3 .
System Action:
The procedure terminates.
User Action:
Contact your Systems Administrator.
Reason:
The NCL Static Call Analysis request to print the report was cancelled.
System Action:
The report is not printed and the procedure completes.
User Action:
None.
Reason:
The NCL Static Call Analysis request failed to analyse a procedure because the procedure's listing caused an overflow in the internal dependent response queue for the analysis procedure.
System Action:
The procedure terminates.
User Action:
Consider dividing the procedure into smaller procedures.
Reason:
The NCL Static Call Analysis request was successfully completed.
System Action:
None.
User Action:
None.
Reason:
The NCL Static Call Analysis request was submitted to the background system region for execution. A notification will be sent when it has completed.
System Action:
None.
User Action:
None.
Reason:
The NCL Static Call Analysis request was printed using PSM. The PSM request number for the print is P1.
System Action:
None.
User Action:
None.
Reason:
The NCL Debug Session Server procedure $SDDB20Z failed because it was invoked with an invalid keyword value specified. The keyword was P1 and the value was P2 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The NCL Debug Session Server was attempting to start a background debug session, but another process is already using that server ID.
System Action:
Procedure $SDDB20Z terminates.
User Action:
Use a different server ID or wait for the existing process to complete.
Reason:
The NCL Debug Session Server was started and was unable to establish contact with the server owner. The owner's NCL ID was P1 .
System Action:
Procedure $SDDB20Z terminates.
User Action:
Check why the owner terminated.
Reason:
The NCL Debug Session Server was attempting to write a message to the servers owner process and the write failed with a return code P2 . The owner's NCL ID was P1 .
System Action:
Procedure $SDDB20Z terminates.
User Action:
Check why the owner terminated.
Reason:
The NCL Debug server's owner was attempting to write a message to the server process and the write failed with a return code P2 . The server's server ID was P1 .
System Action:
Procedure $SDDB20Z terminates.
User Action:
Check why the NCL Debug Session Server terminated.
Reason:
The NCL Debug Server procedure $SDDB20Z received an unexpected feedback code from a vartable action. The action was P1 , the feedback code was P2 and the table name was P3 .
System Action:
Processing continues.
User Action:
Contact the system administrator.
Reason:
The request P1 was attempting to read the response messages from an internal server but the read timed out.
System Action:
The command terminates in error.
User Action:
The cause may be slow system response, if not then contact the systems administrator.
Reason:
The request P1 was attempting to read the response messages from an internal server and the internal queue overflowed.
System Action:
The request terminates in error.
User Action:
Contact the Systems Administrator.
Reason:
The NCL Debug selection list service procedure $SDDB21L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The NCL Debug selection list of debug processes could not display a list because there are no precesses under debug control.
System Action:
None.
User Action:
None.
Reason:
The NCL Debug selection list of debug processes could not complete its processing because the dependent environment's message queue overflowed and the list would be inaccurate.
System Action:
None.
User Action:
Retry the list.
Reason:
The action selected cannot be performed against the item selected.
System Action:
The action is rejected.
User Action:
None.
Reason:
The NCL Debug selection list service procedure $SDDB22L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The action selected cannot be performed against the item selected.
System Action:
The action is rejected.
User Action:
None.
Reason:
The NCL Debug selection list of user regions could not display a list because there were no regions that satisified the criteria.
System Action:
None.
User Action:
None.
Reason:
The NCL Debug start selection was made for a disconnected region, which is invalid.
System Action:
Selection is rejected.
User Action:
Select the user ID as the target for debug.
Reason:
A request to cancel a system User ID or Region was ignored. You cannot cancel system users and/or regions from the Active Users list.
System Action:
Selection is rejected.
User Action:
None.
Reason:
The NCL Debug selection list service procedure $SDDB23L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The action selected cannot be performed against the item selected.
System Action:
The action is rejected.
User Action:
None.
Reason:
The NCL Debug selection list of NCL processes could not display a list because there were no precesses that matched the criteria.
System Action:
None.
User Action:
None.
Reason:
The NCL Debug Command processor procedure $SDDB24Z failed because it was invoked with an invalid keyword value specified. The keyword was P1 and the value was P2 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The command P1 is not a valid command for the NCL Debug Command processor.
System Action:
The command is rejected.
User Action:
Enter a valid command.
Reason:
An invalid command parameter value was specified. The command was P3 . the parameter was P1 and the invalid value was P2 .
System Action:
The command is rejected.
User Action:
Reenter the command with a valid value for parameter P1 .
Reason:
The command P1 was attempting to read the response messages from an internal command but the read timed out.
System Action:
The command terminates in error.
User Action:
Contact the Systems Administrator.
Reason:
The command P1 was attempting to read the response messages from an internal command and the internal queue overflowed.
System Action:
The command terminates in error.
User Action:
Contact the Systems Administrator.
Reason:
The trace log was cleared for the process with NCL ID P1 .
System Action:
None.
User Action:
None.
Reason:
The P1 tracing option was set to P2 .
System Action:
None.
User Action:
None.
Reason:
The NCL tracing option was set to P1 for the process whose NCL ID is P2
System Action:
None.
User Action:
None.
Reason:
The field set in error did not contain a valid numeric value.
System Action:
Field is set in error.
User Action:
Specify a valid procedure name.
Reason:
The field set in error did not contain a valid procedure name.
System Action:
Field is set in error.
User Action:
Specify a numeric value.
Reason:
The fields set in error conflict with previous breakpoint operands.
System Action:
Fields are set in error.
User Action:
Specify a only one operand.
Reason:
No breakpoint operands were specified. One breakpoint operand must be entered.
System Action:
Fields are set in error.
User Action:
Specify a breakpoint operand.
Reason:
For an execution breakpoint you can only specify ENTRY, EXIT or BOTH.
System Action:
Field is set in error.
User Action:
Specify a valid execution breakpoint value.
Reason:
Valid statement numbers are of the form nnnnnnnn or LNEnnnnn, where n is a decimal digit.
System Action:
Field is set in error.
User Action:
Specify a valid statement number.
Reason:
The specified verb is invalid.
System Action:
Field is set in error.
User Action:
Specify a valid NCL verb.
Reason:
Valid variable specifications are either prefix*, varname, or a list of variable names seperated by commas and enclosed in parenthesis with no imbeded blanks.
System Action:
Field is set in error.
User Action:
Specify valid valiables.
Reason:
A "Y" indicates that the variable breakpoint is to be set on the ARGS.
System Action:
Field is set in error.
User Action:
Specify either "Y" or blank out the field.
Reason:
Specify both the range operands or leave both blank.
System Action:
Field is set in error.
User Action:
Specify a both or none of the range operands.
Reason:
The range values must specify an ascending numeric range.
System Action:
Fields are set in error.
User Action:
Specify a larger to range or smaller from range.
Reason:
The NCL ID field was omitted. The NCL ID field is a required field and must be set to a valid NCL ID.
System Action:
Field is set in error.
User Action:
Specify a valid NCL ID.
Reason:
An invalid queue type was specified, valid types are RESP and REQ.
System Action:
Field is set in error.
User Action:
Specify a valid queue type.
Reason:
Either the Data field must be specified or the Message ID field.
System Action:
Fields are set in error.
User Action:
Specify a either the Data field or a Message ID.
Reason:
The message was queued to the process with NCL ID P1 .
System Action:
None.
User Action:
None.
Reason:
The server process that was loading a vartable for the procedure display could not add a record to the vartable. P1 is the name of the vartable and P2 is the feed back code received.
System Action:
The procedure display is terminated.
User Action:
Contact the Systems Administrator.
Reason:
Two keyword parameters were specified for a command and only one or the other (but not both) of the parameters are valid at one time. The command was P3 the first operand was P1 and the second operand was P2 .
System Action:
The command is rejected.
User Action:
Specify either P1 or P2 but not both.
Reason:
An invalid command parameter was specified. The command was P2 and the invalid value was P1 .
System Action:
The command is rejected.
User Action:
Reenter the command with a valid value for the positional parameter.
Reason:
Parameters P1 are invalid for command P2 .
System Action:
The command is rejected.
User Action:
Reenter the command omitting the parameters P1 .
Reason:
The NCL Debug Command processor procedure $SDDB24Z failed because it was attempting to add a breakpoint to the breakpoint action table and received an error. The table name is P1 and the feed back code is P2 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
A statement breakpoint was specified however the procedure name was blank. A statement breakpoint must also specify a procedure name.
System Action:
Field is set in error.
User Action:
Specify a procedure name.
Reason:
The request was cancelled as requested by the user.
System Action:
None.
User Action:
None.
Reason:
The breakpoint action was altered as specified in the Action field.
System Action:
None.
User Action:
None.
Reason:
The trace print could not continue because the NCL ID specified did not have any trace records to print. The NCL ID is P1 .
System Action:
Print request is terminated.
User Action:
None.
Reason:
The trace log was printed for the NCL ID P1 and the print request ID is
P2 .
System Action:
None.
User Action:
None.
Reason:
An attempt to free a region level vartable failed because the table existed in another region. The table name was P1 .
System Action:
None.
User Action:
None.
Reason:
An action against a vartable failed because the table did not exist in the indicated scope.
p1 is the name of the table.
p2 is the scope.
System Action:
None.
User Action:
None.
Reason:
The vartable P2 in scope P3 was successfully processed by P1 .
System Action:
None.
User Action:
None.
Reason:
The current trace filter has been reset to the default.
System Action:
None.
User Action:
None.
Reason:
The current trace filter has been updated with the changes requested.
System Action:
None.
User Action:
None.
Reason:
The keyword P1 is required if the keyword P2 has the value P3.
System Action:
Field is set in error.
User Action:
Specify a value for P1.
Reason:
An error occurred mapping an MDO to the map P1 . The MDORC and MDOFDBK are P2.
System Action:
The action is rejected.
User Action:
Specify a valid map for the selected MDO component.
Reason:
An invalid name has been specified for a data set, a member, or both. The names must be valid data set and member names.
System Action:
The action is rejected.
User Action:
Correct the invalid data set and member names.
Reason:
An invalid data set was specified. The data set must be a partitioned data set with a logical record length of 80 or more bytes.
System Action:
The action is rejected.
User Action:
Specify a valid data set.
Reason:
A vartable was exported successfully.
p1 is scope of the table.
p2 is the name of the table.
p3 (if the table is exported to a data set) is the name of the data set member.
System Action:
None.
User Action:
None.
Reason:
The NCL Debug browse service procedure $SDDB26L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
There are no trace records for process with NCL ID P1 .
System Action:
None.
User Action:
None.
Reason:
A NEXT or PREV command was entered and an invalid number of trace procedures was specified. P1 is the invalid value specified.
System Action:
Action is rejected.
User Action:
Specify a valid number of trace procedures to skip.
Reason:
An invalid value was specified as a parameter for the OMLEXPR command. The only valid values are ON or YES to view OML expression trace records or OFF or NO to exclude OML ecpression trace records.
System Action:
Action is rejected.
User Action:
Specify ON or YES to view the expression trace records or specify OFF or NO to exclude the records.
Reason:
An invalid value was specified as a parameter for the VIEWFLTR command. The only valid values are ON or YES to apply the current view filter or OFF or NO to ignore the current view filter.
System Action:
Action is rejected.
User Action:
Specify ON or YES to have the current view filter applied to trace records or specify OFF or NO to ignore the current view filter. The current view filter can be maintained using the TRACE VIEWFLTR LIST command or TVFL for short.
Reason:
The current setting for the P1 option is P2.
System Action:
None.
User Action:
None.
Reason:
The NCL Debug selection list service procedure $SDDB26L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
There are no call trace records for process with NCL ID P1 .
System Action:
None.
User Action:
None.
Reason:
The NCL Debug selection list service procedure $SDDB27L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
There are no NCL trace logs for this debug session.
System Action:
None.
User Action:
None.
Reason:
The action selected cannot be performed against the item selected.
System Action:
The action is rejected.
User Action:
None.
Reason:
The NCL Debug selection list service procedure $SDDB28L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
A statement breakpoint was set as requested but was not applied to the currently executing copys of the procedure. This occurs because the procedure is not privately loaded. The breakpoint will be applied when the procedure is next invoked, since the debugger will automatically load the procedure privately and apply the breakpoint. The Breakpoint ID is P1 and the procedure for which the breakpoint was not applied is P2 .
System Action:
The breakpoint is set but not applied to currently executing copies of the procedure P2 .
User Action:
Re-invoke the procedure to ensure that it is privately loaded and that the breakpoint is applied.
Reason:
The NCL Debug selection list service procedure $SDDB29L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The MDO selected has been deleted by the debugged process.
System Action:
The action is rejected.
User Action:
None.
Reason:
There are no MDO's for the selected NCL process and procedure.
System Action:
None.
User Action:
None.
Reason:
An error occurred mapping an MDO to the map P1 . The MDORC and MDOFDBK are P2 which mean P3 .
System Action:
The action is rejected.
User Action:
Specify a valid map for the selected MDO.
Reason:
The NCL Debug selection list service procedure $SDDB30L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
There are no NCL variables to display for the process with NCL ID P1 and procedure P2 .
System Action:
None.
User Action:
None.
Reason:
The variable was being edited in hex mode, however invalid hex data was found on line P1 .
System Action:
The editor is reinvoked.
User Action:
Correct the error.
Reason:
The variable no longer exists in the debugged procedure.
System Action:
None.
User Action:
None.
Reason:
The variable P1 was updated.
System Action:
None.
User Action:
None.
Reason:
The action selected cannot be performed against system variables.
System Action:
The action is rejected.
User Action:
None.
Reason:
The attribute for variable P1 was altered.
System Action:
None.
User Action:
None.
Reason:
The variable P1 was deleted.
System Action:
None.
User Action:
None.
Reason:
The total number of list lines for the variable list display exceeded the maximum allowable.
System Action:
The list is terminated.
User Action:
Specify a prefix or fewer variable types to reduce the size of the list.
Reason:
The variable was being edited in hex mode, however invalid hex data was found on line P1 . The length of the line was found to be an odd number and for hex data the length must be even. Each line must be of even length even though the lines are concatenated together.
System Action:
The editor is reinvoked.
User Action:
Correct the error.
Reason:
A variable list was being generated but the terminating message was not received or the wait time was exceeded. This may be caused by the queue overflowing in the presentation process or in the debug server process. If the server's queue overflowed then the terminating message was probably not delivered to the presentation process and hence a timeout would occur, thus is indicated by a FDBK of 4. If the presentations queue overflowed then the FDBK would be 8. P1 is the feed back code.
System Action:
The section of the variables list being processes is incomplete and the system continues listing other variable types.
User Action:
Increase system queue limits or narrow the scope of the variable display by using the PREFIX or TYPE parameters on the VARS command.
Reason:
The NCL Debug selection list service procedure $SDDB31L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
There are no NCL global variables with the specified prefix, or there are no globla variables at all (if no prefix was specified).
System Action:
None.
User Action:
None.
Reason:
The variable was being edited in hex mode, however invalid hex data was found on line P1 .
System Action:
The editor is reinvoked.
User Action:
Correct the error.
Reason:
The global variable with suffix P1 was updated.
System Action:
None.
User Action:
None.
Reason:
The global variable with suffix P1 was deleted.
System Action:
None.
User Action:
None.
Reason:
The variable was being edited in hex mode, however invalid hex data was found on line P1 . The length of the line was found to be an odd number and for hex data the length must be even. Each line must be of even length even though the lines are concatenated together.
System Action:
The editor is reinvoked.
User Action:
Correct the error.
Reason:
No value was selected from the displayed selection list.
System Action:
None.
User Action:
None.
Reason:
No suspended debug session to select from.
System Action:
None.
User Action:
None.
Reason:
The NCL Debug selection list service procedure $SDDB33L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The NCL Debug selection list service procedure $SDDB34L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
A statement breakpoint was set as requested but was not applied to the currently executing copy of the procedure. This occurs because the procedure is not privately loaded. The breakpoint will be applied when the procedure is next invoked, since the debugger will automatically load the procedure privately and apply the breakpoint. The Breakpoint ID is P1 and the procedure for which the breakpoint was not applied is P2 .
System Action:
The breakpoint is set but not applied to currently executing copies of the procedure P2 .
User Action:
Re-invoke the procedure to ensure that it is privately loaded and that the breakpoint is applied.
Reason:
The NCL Debug selection list service procedure $SDDB35L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The NCL Debug selection list of vartables could not display a list because there were no vartables that satisified the criteria.
System Action:
None.
User Action:
None.
Reason:
The NCL Debug selection list of vartables could not display a list because there were no vartables of scope PROCESS for the NCL process ID
P1.
System Action:
None.
User Action:
None.
Reason:
The NCL Debug selection list service procedure $SDDB36L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The vartable display utility was invoked with an invalid keyword value passed. P1 is the keyword name and P2 is the invalid value.
System Action:
Request is rejected.
User Action:
Specify a valid value for keyword P1.
Reason:
The vartable specified to be displayed did not exist in the specified scope. The table could have been freed by another user. P1 is the name of the table and P2 is the scope.
System Action:
None.
User Action:
None.
Reason:
The vartable entry did not exist or was deleted by another user. P1 is the key of the entry that didn't exist.
System Action:
None.
User Action:
None.
Reason:
The vartable entry could not be updated because the mapped entry was not mapped by the $NCL map.
System Action:
None.
User Action:
None.
Reason:
The vartable entry could not be updated because the correlator used to retrieve the entry changed when the entry was saved. This condition indicates that at least one other update was made to the entry by another user.
System Action:
None.
User Action:
None.
Reason:
The vartable entry was successfully updated.
System Action:
None.
User Action:
None.
Reason:
The vartable entry was successfully added and because the limit was exceeded for the table, the most eligible entry of the table was deleted.
System Action:
None.
User Action:
None.
Reason:
The vartable entry was successfully added.
System Action:
None.
User Action:
None.
Reason:
The vartable add could not be performed because the key specified was invalid for the vartable's requirements.
System Action:
The action is rejected.
User Action:
Specify a valid key value.
Reason:
The vartable add could not be performed because the table already has the maximum number of entries allowed as specified on the vartable ALLOC used to define the table.
System Action:
The action is rejected.
User Action:
None.
Reason:
The vartable entry was successfully deleted.
System Action:
None.
User Action:
None.
Reason:
A vartable entry was being added and the key for the new entry was a duplicate. The key must be unique within the table.
System Action:
None.
User Action:
Enter a unique key value.
Reason:
A vartable entry was being edited in hex mode and the data entered on line P1 was not valid hex. All lines must be valid hex characters and have an even length.
System Action:
None.
User Action:
Specify valid hex data.
Reason:
A vartable entry was being edited in hex mode and the data entered on line P1 was not valid hex. All lines must be valid hex characters and have an even length.
System Action:
None.
User Action:
Specify valid hex data.
Reason:
A vartable entry was being edited in hex mode and the data entered for the key (part P1 ) was not valid hex. All parts of the key must be valid hex characters and have an even length.
System Action:
None.
User Action:
Specify valid hex data.
Reason:
A vartable entry was being edited in hex mode and the data entered for the key (part P1 ) was not valid hex. All parts of the key must be valid hex characters and have an even length.
System Action:
None.
User Action:
Specify valid hex data.
Reason:
A vartable entry was being modified and the value specified for the AOM attribute was invalid. The invalid value starts at position P1 within the value specified.
System Action:
Save or file request is rejected.
User Action:
Specify valid AOM attribute data.
Reason:
The vartable action P2 was performed and the feedback returned was P1 .
System Action:
None.
User Action:
Check the NCL reference for an explanation of the feedback.
Reason:
The NCL Debug selection list service procedure $SDDB37L failed because it received a call type that is not supported by the service procedure. The call type was P1 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The MDO component P1 was successfully set to a null value.
System Action:
None.
User Action:
None.
Reason:
The MDO component P1 was successfully deleted from the object.
System Action:
None.
User Action:
None.
Reason:
The MDO component P1 was successfully set a null value.
System Action:
None.
User Action:
None.
Reason:
The MDO component P was successfully deleted from the object.
System Action:
None.
User Action:
None.
Reason:
The MDO component P1 was successfully updated, however the data value was truncated.
System Action:
None.
User Action:
None.
Reason:
The MDO component P1 was not updated because of a type error. The basic type of the component is P2 .
System Action:
None.
User Action:
None.
Reason:
The MDO component P1 was not updated because of a data error. The data is structurally invalid. Acommon cause could be data size.
System Action:
None.
User Action:
None.
Reason:
The MDO component P1 does not exist in the map P2 .
System Action:
None.
User Action:
None.
Reason:
The MDO component P1 had an invalid index position.
System Action:
None.
User Action:
None.
Reason:
The MDO component could not be updated because the map associated with the object did not exist. The map associated with the object is
P1 .
System Action:
None.
User Action:
None.
Reason:
The MDO component could not be updated because the map associated with the object contained errors and it could not be loaded. The map was P1 .
System Action:
None.
User Action:
None.
Reason:
The MDO component could not be updated because the map associated with the object contained errors. The map was P1 .
System Action:
None.
User Action:
None.
Reason:
The MDO component P1 was successfully updated.
System Action:
None.
User Action:
None.
Reason:
The MDO component was being updated in hex mode and invalid hex data was specified on line P1 .
System Action:
None.
User Action:
None.
Reason:
The MDO was successfully modified.
System Action:
None.
User Action:
None.
Reason:
The MDO component was being updated in hex mode and invalid hex data was specified on line P1 . The error was an odd data length, hex data must be of an even length.
System Action:
None.
User Action:
None.
Reason:
The MDO component was being updated and the cancel request was issued. The changes to the mdo will not be saved.
System Action:
None.
User Action:
None.
Reason:
The value specified for the SHOWKEY command is invalid. It must be a number between 1 and the length of the key, P1.
System Action:
Command rejected.
User Action:
Specify a valid number in the correct range.
Reason:
There are no eligible UDB files to view. Files to view must already be allocated and opened using the UDBCTL OPEN command. NDB files cannot be viewed using this utility.
System Action:
Request rejected.
User Action:
Allocate and open a UDB file and then invoke the viewer.
Reason:
No file was selected for viewing.
System Action:
Request rejected.
User Action:
Select a file from the prompt list or specify a file DD name and retry.
Reason:
The specified DD name P1 is not allocated or is not a VSAM file.
System Action:
Request rejected.
User Action:
Ensure that the DD name specified is allocated to a VSAM file and that the file is opened using the UDBCTL OPEN command.
Reason:
The specified action cannot be performed because the record does not exist.
System Action:
Request rejected.
User Action:
None.
Reason:
The selected record was deleted.
System Action:
None.
User Action:
None.
Reason:
The selected record has a key only and there is no data present.
System Action:
None.
User Action:
None.
Reason:
The vartable specified does not exist in the specified scope. The table may have been freed by another user. P1 is the name of the table and P2 is the scope.
System Action:
None.
User Action:
None.
Reason:
The data was saved in the repository.
System Action:
None.
User Action:
None.
Reason:
The data to edit contains non-displayable hexadecimal characters. The editor automatically switches into hexadecimal editing mode.
System Action:
None.
User Action:
None.
Reason:
The hexadecimal editing area contains invalid characters. The area must contain characters 0-9 or A-F.
System Action:
The cursor is placed on the first invalid hexadecimal character.
User Action:
Change the invalid character to a valid hexadecimaL character 0-9 or A-F.
Reason:
The vartable entry no longer exists. The entry was deleted by another user or by a system process.
System Action:
Command is rejected.
User Action:
Refresh the list to view the latest vartable entries.
Reason:
The vartable no longer exists. The table has been freed by another user or by a system process.
System Action:
Processing terminates.
User Action:
None.
Reason:
The vartable action P1 failed with feedback code P2.
System Action:
Processing continues.
User Action:
None.
Reason:
The $NCL MDO component specified is invalid. It must be of the form: DATALIST{n} where n is a number from 1 to 32767.
System Action:
Field is set in error.
User Action:
Correct the Component field.
Reason:
The command is not valid on the line on which it was placed. Some line commands apply to certain lines only.
System Action:
Field is set in error.
User Action:
Change the line command or blank out the field.
Reason:
The command conflicts with a previous line command.
System Action:
The field is set in error.
User Action:
Change the line command or blank out the field.
Reason:
A previous block command does not have a matching command on another line.
System Action:
The field is set in error.
User Action:
Enter a matching command on another line or blank out the pending line command.
Reason:
The line command entered is not recognized as a valid line command.
System Action:
The field is set in error.
User Action:
Enter a valid line command or blank out the field.
Reason:
The vartable entry was successfully deleted from the table.
System Action:
None.
User Action:
None.
Reason:
The vartable entry was successfully updated.
System Action:
None.
User Action:
None.
Reason:
The MDO component specified already exists. A unique component name must be specified.
System Action:
The field is set in error.
User Action:
Correct the Component field.
Reason:
The vartable entry already exists in the table.
System Action:
The field is set in error.
User Action:
You must specify a unique key for the vartable entry.
Reason:
The vartable entry was successfully added.
System Action:
None.
User Action:
None.
Reason:
The data being set for the MDO component is of an invalid data type. For example, if the component is an enumerated type, the value must be one of the valid enumerations. If the type is declared as INTEGER, the data must be a valid integer, and so on.
System Action:
The data is not saved in the MDO.
User Action:
Correct the data and retry the request.
Reason:
The data being set for the MDO component is structurally invalid. For example, the data may be too long or too short.
System Action:
The data is not saved in the MDO.
User Action:
Correct the data and retry the request.
Reason:
The data being set for the MDO component will cause the MDO to exceed its maximum length.
System Action:
The data is not saved in the MDO.
User Action:
Correct the data and retry the request.
Reason:
The Map Name field is incorrectly specified. The map name must be $NCL.DATALIST for a standard list of value, $NCL.VARSLIST for a standard list of varaible suffixes and values, or a name (that is only using alphanumeric and national characters, with the first character not a number).
System Action:
The field is set in error.
User Action:
Enter a valid map name or one of the standard $NCL forms.
Reason:
The Map Name field was invalid. P1 indicates the reason that the map is invalid.
System Action:
The field is set in error.
User Action:
Enter a valid map name that exists or one of the standard $NCL forms (that is $NCL.DATALIST or $NCL.VARSLIST).
Reason:
The data entered exceeds the maximum length of P1.
System Action:
The field is set in error.
User Action:
Reduce the size of the field value to P1 or less.
Reason:
The $NCL MDO component specified is invalid. It must be of the form: VARSLIST.TOKEN{n}.NAME or VARSLIST.TOKEN{n}.DATA where n is a number from 1 to 32767.
System Action:
The field is set in error.
User Action:
Correct the Component field.
Reason:
The data on line P1 is invalid hexadecimal data. The characters allowed are 0 to 9, A to F, and blanks. There must be an even number of non-blank characters. P2 provides more information about the error.
System Action:
The data is rejected and the editor invoked.
User Action:
Correct the data.
Reason:
Record not added or updated because a duplicate alternate key exists.
System Action:
Request rejected.
User Action:
None.
Reason:
The record was successfully updated.
System Action:
None.
User Action:
None.
Reason:
The record was successfully added.
System Action:
None.
User Action:
None.
Reason:
There are no eligible NDB files to view. To view NDBs, they must be allocated, opened, and started.
System Action:
Request rejected.
User Action:
Allocate, open, and start an NDB, and then invoke the viewer.
Reason:
No NDB was selected for viewing.
System Action:
Request rejected.
User Action:
Select an NDB from the prompt list or specify an NDB name and retry.
Reason:
The specified NDB name P1 is not started as an NDB.
System Action:
Request rejected.
User Action:
Ensure that the NDB name specified is allocated, opened, and started as an NDB.
Reason:
The field P1 is invalid. P2 provides the reason.
System Action:
Field set in error.
User Action:
Correct the error and retry.
Reason:
The NDB scan returned P1 records.
System Action:
Records are presented starting with the first in the sequence.
User Action:
None.
Reason:
The parameter to the LENGTH command is invalid. You must specify + or - followed by a number to increment or decrement the total length of the data. You can specify an absolute length by entering = followed by the data length required. If you specify * , the length of the data is variable and when saved, trailing blanks are stripped.
System Action:
Command rejected.
User Action:
Enter a valid parameter to the LENGTH command.
Reason:
The global variable was successfully deleted.
System Action:
None.
User Action:
None.
Reason:
The Var Name field is invalid. The name must begin with GLBL and follow the OML rule for variable names.
System Action:
The field is set in error.
User Action:
Enter a valid variable name.
Reason:
NCL process P1 is not holding any NCL locks, so there is nothing to display.
System Action:
Request rejected.
User Action:
None.
Reason:
An invalid sort options was specified. Valid sort options are:
NCLID - sort based on the NCL process ID
NAME - sort on the lock resource name
PROC - sort on the NCL procedure name that issued the lock
USER - sort on user ID
TEXT - sort on the lock text
You can only specify ONE sort option.
System Action:
Request rejected.
User Action:
Specify a valid sort option.
Reason:
An invalid boolean expression filter was specified. The expression must be of the BOOLEXPR format and can use the following variables:
&NCLID - NCL ID of process holding lock
&PROC - Procedure name that issued lock
&USER - User ID
&TYPE - Type of lock (EXCL or SHR)
&ID - Unique lock ID
&LEVEL - Level of resource specification, PRIMARY name only or MINOR and primary name specified.
&TEXT - Lock text
&NAME - Resource name of lock. This is the primary and minor names joined together (with a period as the seperator)
The following examples illustrate the use of the filter command:
1) To show only locks for procedure PROC1 specify:
FILTER &proc = 'proc1'
2) To show only locks for procedure PROC1 with resource name starting with RES:
FILTER &proc = 'proc1' and &name like 'res%'
System Action:
Request rejected.
User Action:
Specify a valid filter expression.
Reason:
The list of global variables excludes the OML global variables because the current environment is being debugged by another user. To display the OML global variables, the debugger is required and the current environment must not be debugged by another user or process.
System Action:
OML global variables are excluded from the display.
User Action:
None.
If you want to see the OML global variables, stop the debug session on this user or environment, and retry the request. Alternatively, request the display from another user that is not being debugged.
Reason:
The list of global variables excludes some global variables because there are too many to display.
System Action:
Some global variables are excluded from the display.
User Action:
Use the Name Like filter field to display only those variables that match the specified pattern, reducing the number of variables to display.
Reason:
You have requested a display record type P1, but no records of this type exist. The record count is 0.
System Action:
None.
User Action:
None.
Reason:
The packet analyzer record display facility supports a maximum of 9999 records. More than 9999 records were found. Only the first 9999 records have been listed.
System Action:
None.
User Action:
If multiple stacks run on this system and you are viewing records from all stacks, you can reduce the size of the list by viewing records from a single stack. Use PKTANAL STACK=name.
Reason:
The TDF record has been successfully reasigned to this region.
System Action:
None.
User Action:
None.
Reason:
A reassign request was issued, but failed because the record is already owned by this region.
System Action:
None.
User Action:
None.
Reason:
The web page unload action failed attempting to do p1. The error message received was P2.
System Action:
Web page is not unloaded.
User Action:
If a UDB OPEN was in error, you must manually re-open the UDB file with the correct options for that file.
Reason:
The web page unload p1 was successfully unloaded.
System Action:
None.
User Action:
None.
Reason:
An invalid value ( P2 ) has been specified for the P1 parameter. (The paramater name is valid, the operand value is invalid).
System Action:
No diagnostics are performed.
User Action:
Check the operand value and retry.
Reason:
$SDDIAGN attempted to obtain diagnostic information for the NCL process
P1 but was unsuccessful.
System Action:
None.
User Action:
Check log for errors. Also check the authority of the user that $SDDIAGN is running under that they are authorized for the DEBUG command. Also check that someone isn't already using the DEBUG command to debug this NCL process.
Reason:
The $SDDIAGN diagnostic facility was called by an application that has encountered an error or an unexpected condition to log some diagnostic information for the NCL process P1 .
This message indicates the start of diagnostic information. The end of of the diagnostic information is indicated by the message SDDG004.
System Action:
None.
User Action:
Send the diagnostic information to your local support representative with a detailed description on how the problem can be repeated.
If you are getting too much diagnostic information written to the log the diagnostic facility can be diabled by issuing the following command:
$SDDIAGN OPT=DISABLE
The diagnostic facility can be later enabled by the command:
$SDDIAGN OPT=ENABLE
Reason:
The $SDDIAGN diagnostic facility was called by an application that has encountered an error or an unexpected condition to log some diagnostic information for the NCL process P1 .
This message indicates the end of diagnostic information. The start of the diagnostic information is indicated by the message SDDG003.
System Action:
None.
User Action:
Send the diagnostic information to your local support representative with a detailed description on how the problem can be repeated.
If you are getting too much diagnostic information written to the log the diagnostic facility can be diabled by issuing the following command:
$SDDIAGN OPT=DISABLE
The diagnostic facility can be later enabled by the command:
$SDDIAGN OPT=ENABLE
Reason:
The $SDDIAGN diagnostic facility has been enabled or disabled ( P1 ).
System Action:
None.
User Action:
Only disable the diagnostic facility if it is interfering with normal system operation. The purpose of this facility is to aid problem diagnosis.
Reason:
The $SDDIAGN diagnostic facility was called by an application that has encountered an error or an unexpected condition to log some diagnostic information. The $SDDIAGN diagnostic procedure was unable to obtain diagnostic information because the NCL/DEBUG component is not included in this system.
System Action:
None.
User Action:
Refer to your system administrator. The NCL/DEBUG component may not be included for the following reasons:
- The NCL/DEBUG component is not licensed. The NCL/DEBUG component is licensable and must be included in the configuration licence member that is issued by your product supplier. Check that the licence member includes NCL/DEBUG and contact your product supplier if it is not present.
- The NCL/DEBUG component has been specifically excluded. The SOLVE run JCL allows licensable components to be excluded. Check the run JCL to see if the EXC= parameter has been specified and NCL/DEBUG is amongst the components to be excluded.
- The NCL/DEBUG component has not been specifically included. The SOLVE run JCL allows licensable components to be specifically included. Check the run JCL to see if the INC= parameter has been specified but the NCL/DEBUG was omitted from the components to be included.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |