|
|
|
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:
The command identified by P1 has been issued against a resource which is not a service filter.
System Action:
Field highlighted in error.
User Action:
Change the CLASS of the resource to 'FILTER' and retry the command.
Reason:
The update of the service members list was cancelled.
System Action:
None
User Action:
None
Reason:
A Repeat/Insert of a service member entry has been attempted which would cause the maximum number of entries to be exceeded.
System Action:
Action disallowed
User Action:
None
Reason:
The value P1 is not a valid resource class
System Action:
Field highlighted in error.
User Action:
Enter a valid resource class or '?' for a list of classes.
Reason:
The only valid values for 'weight type' are FIXED or PROPORTIONAL. Values of 'F' or 'P' are acceptable.
System Action:
Field highlighted in error.
User Action:
Enter one of the valid weight type values.
Reason:
The only valid value for 'weight type' is FIXED when applied to a single resource.
System Action:
Field highlighted in error.
User Action:
Change the value to 'FIXED'
Reason:
A combination of SMFId, CLASS and NAME may only appear once within a relationships list.
System Action:
Fields highlighted in error.
User Action:
Change the SMFId, CLASS or NAME to make the relationship unique.
Reason:
A service filter which does not currently exist has been specified in a service's relationships list.
System Action:
Field highlighted in error.
User Action:
The 'L' option may be used to present a list of Service Filters from which the required filter may be added, or enter '?' in the 'Name' field to select an existing Service Filter from a list.
Reason:
The use of the Generic Character * is not supported when Pattern Matching Characters % and/or _ are present. % may be used to indicate generic matching if pattern matching is being performed on the same field.
System Action:
Field highlighted in error.
User Action:
Remove either the Generic Character * or the Pattern Matching Characters
% and/or _. Alternatively % may be used to replace *.
Reason:
The use of the Field Prompt ? is not supported when any of the WildCard Characters, % or _ or * are present.
System Action:
Field highlighted in error.
User Action:
Remove either the Field Prompt or the Wildcard Characters.
Reason:
The only characters allowed in the resource name field are ALPHANUMERIC or the three wildcards,&%&,&_&or&*&.
System Action:
Field highlighted in error.
User Action:
Remove the invalid characters.
Reason:
A list of valid resource names was displayed and no value was selected from it.
System Action:
Field highlighted in error.
User Action:
Enter a different name or select a valid name from the list displayed.
Reason:
A name has been entered which consists of wildcard characters only. This is an invalid situation as the same effect can be achieved by specifying a single % or * .
System Action:
Field highlighted in error.
User Action:
Use % or * to achieve the desired effect.
Reason:
The APPC function was not successfully completed. SYSMSG contains the unexpected message that resulted.
System Action:
Processing is continued.
User Action:
Contact your System Administrator.
Reason:
Procedure $RVCALL was invoked with an invalid parameter. The parameter in question is the KEYWORD identified by P1 whose value is P2.
System Action:
Call is rejected.
User Action:
Correct the parameters and retry.
Reason:
A ZOOM command was attempted on a service which has not yet been modelled by the Service Manager.
System Action:
Call is rejected.
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:
The Link Manager is attempting to start a ServiceView Component for a remote system.
System Action:
None.
User Action:
None.
Reason:
ServiceView Component has ended.
System Action:
None.
User Action:
None.
Reason:
The ALLOCATION of the VARTABLE described by P1, with a NAME and SCOPE of P2 and P3 failed with &ZFDBK of P4.
System Action:
The SERVICE MANAGER will fail to initialize.
User Action:
Try to ascertain the reason for the inability to allocate a vartable, correct it and re-start the Service Manager.
Reason:
Only one Service Manager may be active. This message indicates that a second copy of the Service Manager procedureattempted to start but detected that a previous copy was active and so terminates.
System Action:
The SERVICE MANAGER will fail to initialize.
User Action:
None
Reason:
AN attempt to read the Service Definition, identified by P1, was unsuccessful. The Return Code P2 was returned along with error message P3.
System Action:
Processing continues.
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:
This message is displayed to indicate that the command identified by P1 will not impact any currently active services if confirmed.
System Action:
None
User Action:
Choose to ACTION or CANCEL the nominated command.
Reason:
The resource identified by P1 is not a member of any currently defined service.
System Action:
None.
User Action:
None.
Reason:
The Report Writer external interface procedure $RWCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $RWCALL terminates. Control is returned to the NCL procedure which executed $RWCALL. If $RWCALL was executed from OCS, control is returned to OCS.
User Action:
Correct the NCL procedure which executed $RWCALL. If executed from OCS, check the command entered on the command line and retry.
Reason:
The Report Writer external interface procedure $RWCALL failed during request processing because it received an unknown return code from a procedure. The name of the procedure was P1 and the unknown return code was P2 .
System Action:
The request is rejected and procedure $RWCALL terminates. Control is returned to the NCL procedure which executed $RWCALL.
User Action:
Contact the system administrator.
Reason:
A request to access or generate a public report failed because the report was not defined. The name of the report was P1 .
System Action:
The request is rejected.
User Action:
Correct the report name and retry.
Reason:
A request to access or generate a private report failed because the report was not defined. The name of the report was P1 and the userid of the owner was P2 .
System Action:
The request is rejected.
User Action:
Correct the name of the report and retry.
Reason:
A request to delete a control break header or trailer or data format failed because it was not defined. The resource not defined was P1 .
System Action:
The request is rejected.
User Action:
Correct the sort field number or data format number and retry.
Reason:
A request to delete a control break header or trailer or data format was cancelled.
System Action:
None.
User Action:
None.
Reason:
A control break header or trailer or data format was successfully deleted. The resource deleted was P1 .
System Action:
None.
User Action:
None.
Reason:
The Report Writer external interface procedure $RWCALL failed during request processing because it encountered an error accessing a variable table. The request was P1 , the identifier of the variable table was
P3 , the feedback code was P2 and the value of the key was P4 .
System Action:
The request is rejected and procedure $RWCALL terminates.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A report was requested to be generated in background mode.
System Action:
The report is being generated under the background logger environment.
User Action:
None.
Reason:
A request to generate a report was denied because the report definition was inactive. The name of the report was P1 and it was a public report.
System Action:
The request is rejected.
User Action:
Change the status defined in the report definition to ACTIVE and retry.
Reason:
A request to generate a report was denied because the report definition was inactive. The name of the report was P1 and it was a private report owned by userid P2 .
System Action:
The request is rejected.
User Action:
Change the status defined in the report definition to ACTIVE and retry.
Reason:
The Report Writer external interface procedure $RWCALL failed during request processing because it was invoked with a value set in variable
$RWCRIT1 and a value set in MDO $RWCRIT1. Variable $LHCRIT1 and MDO $RWCRIT1 are mutually exclusive.
System Action:
The request is rejected and procedure $RWCALL terminates.
User Action:
Correct the execution of $RWCALL and retry.
Reason:
Report definitions are saved in a cache when used, the request to reset (clear) the cache was successful.
System Action:
The cache is cleared.
User Action:
None.
Reason:
A value was entered in the P1 field that was less than three in length.
System Action:
The P1 field is set in error.
User Action:
Correct the value in the P1 field and retry.
Reason:
The service procedure $RWPM01M for the Report Writer Primary Menu failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $RWPM01M terminates.
User Action:
Contact the system administrator.
Reason:
A request to access the Report Writer Primary Menu failed because the user was not authorized for the request. The userid of the user was P1 .
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to access the Report Writer Primary Menu failed because the service procedure $RWPM01M for the menu received an unknown return code from procedure $CAUA000. The unknown return code was P1 .
System Action:
The request is rejected and procedure $RWPM01M terminates.
User Action:
Contact the system administrator.
Reason:
The service procedure $RWPM01M for the Report Writer Primary Menu received an unknown return code from a procedure that was executed as the action for an option on the menu. The unknown return code was P1 .
System Action:
Procedure $RWPM01M terminates and the Report Writer Primary Menu is presented.
User Action:
Contact the system administrator.
Reason:
A request to access the Report Writer Table Maintenance facility failed because the user was not authorized for the request. The userid of the user was P1 .
System Action:
The request is rejected.
User Action:
None.
Reason:
The P option was selected from the Report Writer Primary Menu and an invalid value was entered in the Userid field. The value entered was not alphanumeric and/or national characters.
System Action:
The selection of the P option is rejected and the Userid field is set in error.
User Action:
Correct the value in the Userid field and retry.
Reason:
The service procedure $RWRD10M for the Report Definition Menu failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $RWRD10M terminates.
User Action:
Contact the system administrator.
Reason:
A request to access the Report Definition Menu failed because the user was not authorized for the request. The userid of the user was P1 .
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to access the Report Definition Menu failed because the service procedure $RWRD10M for the menu received an unknown return code from procedure $CAUA000. The unknown return code was P1 .
System Action:
The request is rejected and procedure $RWRD10M terminates.
User Action:
Contact the system administrator.
Reason:
The service procedure $RWRD10M for the Report Definition Menu received an unknown return code from a procedure that was executed as the action for an option on the menu. The unknown return code was P1 .
System Action:
Procedure $RWRD10M terminates and the Report Definition Menu is presented.
User Action:
Contact the system administrator.
Reason:
An option was selected from the Report Definition Menu and an invalid value was entered in the P1 field. The value entered was not alphanumeric and/or national characters.
System Action:
The selection of the option is rejected and the P1 field is set in error.
User Action:
Correct the value in the P1 field and retry.
Reason:
An option was selected from the Report Definition Menu and a value was not entered in the P1 field. The option selected was P2 .
System Action:
The selection of the option is rejected and the P1 field is set in error.
User Action:
Enter a value in the P1 field and retry.
Reason:
An option was selected from the Report Definition Menu and an invalid value was entered in the P1 field.
System Action:
The selection of the option is rejected and the P1 field is set in error.
User Action:
Enter 'PUBLIC' or 'PRIVATE' in the P1 field and retry. Only the first two character need to be entered.
Reason:
The L option was selected from the Report Definition Menu and a list of groups was requested to be displayed via a question mark (?) being entered in the Group field but the Report Appl field was omitted. To present a list of groups a report application must be specified as groups belong to specific applications. The first three characters of a report application must be a valid application ID.
System Action:
The selection of the L option is rejected and the Report Appl field is set in error.
User Action:
Enter a report application in the Report Appl field and retry. A question mark (?) can be entered in the Report Appl field to present a list from which a selection can be made.
Reason:
An option was selected from the Report Definition Menu and a value was entered in the Report Appl field that was less than three characters in length.
System Action:
The selection of the option is rejected and the Report Appl field is set in error.
User Action:
Correct the value in the Report Appl field and retry.
Reason:
A request to add, delete or copy a report definition, or browse or update the report description failed because procedure $RWRD11P received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $RWRD11P terminates.
User Action:
Contact the system administrator.
Reason:
A request to add, delete or copy a report definition, or browse or update the report description failed because the user was not authorized for the request. The function requested was P2 and the userid of the user was P1 . P3 is set to 'YOUR OWN PRIVATE' if the report to be accessed was their own or set to 'OTHER USERS PRIVATE' if another user's report was to be accessed.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to add, delete or copy a report definition, or browse or update the report description failed because procedure $RWRD11P received an unknown return code from procedure $CAUA000. The unknown return code was P1 .
System Action:
The request is rejected and procedure $RWRD11P terminates.
User Action:
Contact the system administrator.
Reason:
An invalid command was entered in the Command field on the Report Description panel.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
A request to delete or copy a report definition, or browse or update the report description failed because the report definition was not defined. The name of the report was P1 and it was a public report.
System Action:
The request is rejected.
User Action:
Specify a report name previously defined and retry.
Reason:
A request to delete or copy a report definition, or browse or update the report description failed because the report definition was not defined. The name of the report was P1 and it was a private report owned by userid P2 .
System Action:
The request is rejected.
User Action:
Specify a report name previously defined and retry.
Reason:
An add, delete or copy report definition or update report description request was cancelled. The request cancelled was P1 .
System Action:
None.
User Action:
None.
Reason:
A report definition was successfully added or deleted, or the report description was successfully updated. The name of the report definition was P1 and it was a public report. The action successfully performed was P2 .
System Action:
None.
User Action:
None.
Reason:
A report definition was successfully added or deleted, or the report description was successfully updated. The name of the report definition was P1 and it was a private report owned by userid P2 . The action successfully performed was P3 .
System Action:
None.
User Action:
None.
Reason:
A request to add a report definition failed because the report definition was already defined. The name of the report was P1 and it was a public report.
System Action:
The request is rejected.
User Action:
Specify a report name not previously defined and retry.
Reason:
A request to add a report definition failed because the report definition was already defined. The name of the report was P1 and it was a private report owned by userid P2 .
System Action:
The request is rejected.
User Action:
Specify a report name not previously defined and retry.
Reason:
The description for a report definition was successfully updated. The name of the report definition was P1 and it was a public report.
System Action:
None.
User Action:
None.
Reason:
The description for a report definition was successfully updated. The name of the report definition was P1 and it was a private report owned by userid P2 .
System Action:
None.
User Action:
None.
Reason:
The Report Description panel was displayed requesting the user to confirm the deletion of the report definition presented.
System Action:
None.
User Action:
Press the ENTER key to allow the report definition to be deleted, or press the CANCEL key to cancel the delete request.
Reason:
Function key P1 was pressed on the Report Description panel and the command assigned to it was invalid.
System Action:
The command is rejected.
User Action:
Correct the setting of the function key and retry.
Reason:
The validation exit $RWRD12X for the Report Definition panel received an unknown field name from procedure $CAGP000. The name of the field was P1 .
System Action:
Procedure $RWRD12X terminates.
User Action:
Contact the system administrator.
Reason:
An invalid value was entered in the P1 field on the Report Definition panel.
System Action:
The Report Definition panel is displayed with the P1 field set in error.
User Action:
Enter 'PUBLIC' or 'PRIVATE' in the P1 field and retry. Only the first two characters need to be entered.
Reason:
A report name was entered in the Report Name field on the Report Description panel that was previously defined. The report name entered was P1 and it was a public report.
System Action:
The Report Description panel is displayed with the Report Name field set in error.
User Action:
Enter a report name not previously defined and retry.
Reason:
A report name was entered in the Report Name field on the Report Description panel that was previously defined. The report name entered was P1 and it was a private report owned by userid P2 .
System Action:
The Report Description panel is displayed with the Report Name field set in error.
User Action:
Enter a report name not previously defined and retry.
Reason:
P3 was entered in the P2 field on the Report Definition panel and a value was entered in the P1 field.
System Action:
The Report Definition panel is displayed with the P1 field set in error.
User Action:
Clear the P1 field or change the value of the P2 field and retry.
Reason:
P3 was entered in the P2 field on the Report Description panel and a value was not entered in the P1 field.
System Action:
The Report Description panel is displayed with the P1 field set in error.
User Action:
Enter a value in the P1 field or change the value of the P2 field and retry.
Reason:
A value was not entered in the P2 field on the Report Description panel and a value was entered in the P1 field.
System Action:
The Report Description panel is displayed with the P1 field set in error.
User Action:
Clear the P1 field or enter a value in the P2 field and retry.
Reason:
An invalid value was entered in the P1 field on the Report Description panel.
System Action:
The Report Description panel is displayed with the P1 field set in error.
User Action:
Enter 'PUBLIC', 'PRIVATE' or 'FREEFORM' in the P1 field and retry. Only the first character needs to be entered if the required value is 'FREEFORM', else the first two characters need to be entered.
Reason:
An invalid value was entered in the P1 field on the Report Description panel.
System Action:
The Report Description panel is displayed with the P1 field set in error.
User Action:
Enter 'ACTIVE' or 'INACTIVE' in the P1 field and retry. Only the first character needs to be entered.
Reason:
'FREEFORM' was entered in the P1 field on the Report Description panel and a value was also entered in the P2 field.
System Action:
The Report Description panel is displayed with the P1 field set in error.
User Action:
Change the value of the P1 field or clear the P2 field and retry.
Reason:
A value was entered in the Report Appl field on the Report Description panel that was less than three in length.
System Action:
The Report Description panel is displayed with the Report Appl field set in error.
User Action:
Correct the value in the Report Appl field and retry.
Reason:
The service procedure $RWRD13L for the Report Definition List failed because it received an unknown call type in variable &$SLCALLTYPE from procedure $CASL000. The unknown call type was P1 .
System Action:
Procedure $RWRD13L terminates.
User Action:
Contact the system administrator.
Reason:
A request to present a Report Definition List with public reports listed failed because the user was not authorized for the request. The userid of the user was P1 .
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to present a Report Definition List or delete a report definition failed because the service procedure $RWRD13L for the Report Definition List received an unknown return code from procedure $CAUA000. The unknown return code was P1 .
System Action:
The request is rejected and procedure $RWRD13L terminates.
User Action:
Contact the system administrator.
Reason:
A request to present a Report Definition List failed because there were no reports defined.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to present a Report Definition List failed because there were no reports defined within the range specified.
System Action:
The request is rejected.
User Action:
None.
Reason:
The selection of a report definition from the Report Definition List failed because the report was deleted by another user since the list was presented. The name of the report definition selected was P1 .
System Action:
The selection of the report definition is rejected.
User Action:
None.
Reason:
A request to present a Report Definition List with private reports listed failed because the user was not authorized for the request. The userid of the user was P1 . P2 is set to 'YOUR OWN PRIVATE' if the reports to be listed were their own or set to 'OTHER USERS PRIVATE' if other user's reports were to be listed.
System Action:
The request is rejected.
User Action:
None.
Reason:
The service procedure $RWRM14M for the Report Definition Component Menu failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $RWRM14M terminates.
User Action:
Contact the system administrator.
Reason:
A request to browse or update a report definition failed because the user was not authorized for the request. The function requested was P2 and the userid of the user was P1 . P3 is set to 'YOUR OWN PRIVATE' if the report to be accessed was their own or set to 'OTHER USERS PRIVATE' if another user's report was to be accessed.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to browse or update a report definition failed because procedure $RWRM14M received an unknown return code from procedure $CAUA000. The unknown return code was P1 .
System Action:
The request is rejected and procedure $RWRM14M terminates.
User Action:
Contact the system administrator.
Reason:
The service procedure $RWRM14M for the Report Definition Component Menu received an unknown return code from a procedure that was executed as the action for an option on the menu. The unknown return code was P1 .
System Action:
Procedure $RWRM14M terminates and the Report Definition Component Menu is presented.
User Action:
Contact the system administrator.
Reason:
A request to browse or edit a report header, page header, control break header, data format, control break trailer, page trailer or report trailer failed because procedure $RWFI15P received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $RWFI15P terminates.
User Action:
Contact the system administrator.
Reason:
Procedure $RWFI15P encountered an error authorizing an edit request or getting or saving a user's scroll amount. It received an unknown return code from procedure $CAUA000. The unknown return code was P1 .
System Action:
This error message is displayed on the last panel displayed or procedure $RWFI15P terminates.
User Action:
Contact the system administrator.
Reason:
Procedure $RWFI15P encountered an error allocating or resetting a variable table. The request was P1 , the identifier of the variable table was P3 and the feedback code was P2 .
System Action:
This error message is displayed on the last panel displayed or procedure $RWFI15P terminates.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
Procedure $RWFI15P encountered an error accessing a variable table. The request was P1 , the identifier of the variable table was P3 , the feedback code was P2 and the key value used was P4 .
System Action:
This error message is displayed on the last panel displayed or procedure $RWFI15P terminates.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to add a control break header or trailer or data format failed because it was already defined. The component was P1 and the sort field number or data format number was P2 .
System Action:
The request is rejected.
User Action:
Specify a sort field number or data format number not previously defined and retry.
Reason:
A request to browse, update or copy a control break header or trailer or data format failed because it was not defined. The component was P1 and the sort field number or data format number was P2 .
System Action:
The request is rejected.
User Action:
Specify a sort field number or data format number previously defined and retry.
Reason:
A report header, page header, page trailer or report trailer was successfully updated. The component was P1 and the action successfully performed was P2 .
System Action:
None.
User Action:
None.
Reason:
A control break header or trailer or data format was successfully added or updated. The component was P1 and the sort field number or data format number was P2 . The action successfully performed was P3 .
System Action:
None.
User Action:
None.
Reason:
An invalid command was entered in the Command field.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
An edit report header, page header, page trailer, or report trailer request, or add or update control break header, data format or control break trailer request was cancelled. The request cancelled was P1 .
System Action:
None.
User Action:
None.
Reason:
A command was entered in the Command field that was a valid command, however, it was not allowed to be specified on that panel.
System Action:
The command is rejected.
User Action:
Clear the Command field.
Reason:
A value was not entered in the P1 field.
System Action:
The panel is displayed with the P1 field set in error.
User Action:
Enter a value in the P1 field and retry.
Reason:
P was entered in a Fmt field and text was entered in the corresponding Layout Line.
System Action:
The panel is displayed with the Layout Line set in error.
User Action:
Clear the Layout Line or change the value of the Fmt field and retry.
Reason:
P1 and P2 were entered in a Fmt field.
System Action:
The panel is displayed with the Fmt field set in error.
User Action:
Change the value of the Fmt field by deleting P1 or P2 and retry.
Reason:
An invalid value was entered in a Fmt field.
System Action:
The panel is displayed with the Fmt field set in error.
User Action:
Enter 'P', 'Pn' or a combination of 'B', 'O', 'X' and 'L', 'R' or 'C' in the Fmt field and retry. 'n' must be in the range 0 to 9999.
Reason:
An invalid value was entered in a Fmt field.
System Action:
The panel is displayed with the Fmt field set in error.
User Action:
Enter 'P', 'Pn' or a combination of 'H', 'B', 'O', 'X' and 'L', 'R' or 'C' in the Fmt field and retry. 'n' must be in the range 0 to 9999.
Reason:
O was entered in the Fmt field that corresponds to layout line 1.
System Action:
The panel is displayed with the layout line set in error.
User Action:
Delete O from the Fmt field that corresponds to layout line 1 and retry.
Reason:
H was entered in a Fmt field for a Report Header, Page Header, Control Break Header or Trailer, Page Trailer or Report Trailer. The component being edited was P1 .
System Action:
The panel is displayed with the Fmt field set in error.
User Action:
Delete H from the Fmt field and retry.
Reason:
An invalid Data Field name was entered in a Layout Line starting at column P1 . The Data Field name entered was not 1 to 12 alphanumeric and/or national characters.
System Action:
The panel is displayed with the layout line set in error.
User Action:
Change the name of the Data Field to be 1 to 12 alphanumeric and/or national characters and retry. An ampersand ( ) followed by a question mark (?) can be entered in the layout line to present a list of Data Fields from which a selection can be made.
Reason:
An invalid Data Field name was entered in a layout line starting at column P2 . The Data Field name entered was a reserved NCL keyword. The name of the Data Field was P1 .
System Action:
The panel is displayed with the layout line set in error.
User Action:
Change the name of the Data Field to a name that is not a reserved NCL keyword and retry. An ampersand ( ) followed by a question mark (?) can be entered in the layout line to present a list of Data Fields from which a selection can be made.
Reason:
An invalid System Field name was entered in a layout line starting at column P1 . The System Field name entered was not defined in the System Field table.
System Action:
The panel is displayed with the layout line set in error.
User Action:
Change the name of the System Field to the name of a field defined in the System Field table and retry. An exclamation mark (!) followed by a question mark (?) can be entered in the layout line to present a list of System Fields from which a selection can be made.
Reason:
An invalid System Field name was entered in a Real Field field. The field name entered was not defined in the System Field table.
System Action:
The panel is displayed with the Real Field field set in error.
User Action:
Change the name of the System Field in the Real Field field to the name of a field defined in the System Field table and retry. An exclamation mark (!) followed by a question mark (?) can be entered in the Real Field to present a list of System Fields from which a selection can be made.
Reason:
An invalid value was entered in a Real Field field. The value entered was not a Data Field or System Field.
System Action:
The panel is displayed with the Real Field field set in error.
User Action:
Change the value in the Real Field field to the name of a Data Field or System Field and retry. A question mark (?) can be entered in the Real Field to present a list of Data Fields from which a selection can be made. An exclamation mark (!) followed by a question mark (?) can be entered in the Real Field to present a list of System Fields from which a selection can be made.
Reason:
An invalid Data Field name was entered in a Real Field field. The Data Field name entered was a reserved NCL keyword. The name of the Data Field was P1 .
System Action:
The panel is displayed with the Real Field field set in error.
User Action:
Change the name of the Data Field in the Real Field field to a name that is not a reserved NCL keyword and retry. A question mark (?) can be entered in the Real Field to present a list of Data Fields from which a selection can be made.
Reason:
An invalid value was entered in a Format field.
System Action:
The panel is displayed with the Format field set in error.
User Action:
Correct the value in the Format field and retry. Refer to the help information by issuing the help command for the valid values that may be entered in the Format field.
Reason:
An invalid line command was entered in a sequence number field.
System Action:
The command is rejected.
User Action:
Correct the line command and retry.
Reason:
A number of mutually exclusive line commands were entered in sequence number fields.
System Action:
The line commands are not processed.
User Action:
Correct the line commands and retry.
Reason:
A number of line commands were entered in sequence number fields and some or all were followed by a number which caused them to be mutually exclusive.
System Action:
The line commands are not processed.
User Action:
Correct the line commands and retry.
Reason:
A block line command was partially specified. That is, either the start line or end line was specified but not both.
System Action:
The block command remains pending.
User Action:
Specify the start line and end line.
Reason:
A move or copy line command was specified but the position the lines were to be moved/copied before/after was not specified. The line command specified was P1 .
System Action:
The move/copy command remains pending.
User Action:
Specify the position the lines are to be moved/copied to by entering an 'A' or 'B' line command in a sequence number field.
Reason:
A line command was entered in a Sequence Number field that was a valid line command, however, it was not allowed to be specified for that line.
System Action:
The line command is rejected.
User Action:
Correct the line command and retry.
Reason:
A command was entered in the Command field that was a valid command, however, the command parameter was invalid.
System Action:
The command is rejected.
User Action:
Correct the command parameter and retry.
Reason:
A repeating field was entered in a layout line or a Real Field field for a Page Trailer. The component being edited was P1 . A repeating field is a Data Field that is terminated by an asterisk (*).
System Action:
The panel is displayed with the layout line or Real Field field set in error.
User Action:
Change the Data Field so that it is not a repeating field and retry.
Reason:
Validation of the Real Field field failed because Table Services encountered an error during the validation of the field. The number of the message returned by Table Services was P1 .
System Action:
Message P1 is written to the activity log.
User Action:
Refer to message P1 on the activity log for more information.
Reason:
A request to present a Data Field List failed because Table Services encountered an error during the generation of the List. The number of the message returned by Table Services was P1 .
System Action:
Message P1 is written to the activity log.
User Action:
Refer to message P1 on the activity log for more information.
Reason:
A request to browse or edit a report header, page header, control break header, data format, control break trailer, page trailer or report trailer failed because the user was not authorized for the request. The function requested was P2 and the userid of the user was P1 . P3 is set to 'YOUR OWN PRIVATE' if the report to be accessed was their own or set to 'OTHER USERS PRIVATE' if another user's report was to be accessed.
System Action:
The request is rejected.
User Action:
None.
Reason:
Function key P1 was pressed and the command assigned to it was invalid.
System Action:
The command is rejected.
User Action:
Correct the setting of the function key and retry.
Reason:
The Page Number system field (!P) was entered in an item which is not a Page Header or Page Trailer.
System Action:
The layout line containing the Page Header system variable is highlighted.
User Action:
Delete the Page Header system variable from the item.
Reason:
A request to browse or edit the sort fields for a report definition failed because procedure $RWSF16P received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $RWSF16P terminates.
User Action:
Contact the system administrator.
Reason:
Function key P1 was pressed on the Sort Fields panel and the command assigned to it was invalid.
System Action:
The command is rejected.
User Action:
Correct the setting of the function key and retry.
Reason:
An invalid command was entered in the Command field on the Sort Fields panel.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
A request to browse the sort fields for a public report failed because there were no sort fields defined. The name of the report was P1 .
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to browse the sort fields for a private report failed because there were no sort fields defined. The name of the report was P1 and it was owned by userid P2 .
System Action:
The request is rejected.
User Action:
None.
Reason:
An edit sort fields request was cancelled. The request cancelled was P1 .
System Action:
None.
User Action:
None.
Reason:
The sort fields for a report definition were successfully updated. The name of the report definition was P1 and it was a public report. The action successfully performed was P2 .
System Action:
None.
User Action:
None.
Reason:
The sort fields for a report definition were successfully updated. The name of the report definition was P1 and it was a private report owned by userid P2 . The action successfully performed was P3 .
System Action:
None.
User Action:
None.
Reason:
A request to edit the sort fields for a report definition failed because the report appl in which the report was defined did not support record sorting. The report appl was P1 .
System Action:
The request is rejected.
User Action:
None.
Reason:
The validation exit $RWSF17X for the Sort Fields panel received an unknown field name from procedure $CAGP000. The name of the field was
P1 .
System Action:
Procedure $RWSF17X terminates.
User Action:
Contact the system administrator.
Reason:
A value was entered in the Start Offset field on the Sort Fields panel and a value was not entered in the Field Name field. P1 was set to Start Offset and P2 was set to Field Name.
System Action:
The Sort Fields panel is displayed with the Start Offset field set in error.
User Action:
Clear the Start Offset field or enter a field name in the Field Name field and retry.
Reason:
A value was entered in the End Offset field on the Sort Fields panel and a value was not entered in the Field Name field. P1 was set to End Offset and P2 was set to Field Name.
System Action:
The Sort Fields panel is displayed with the End Offset field set in error.
User Action:
Clear the End Offset field or enter a field name in the Field Name field and retry.
Reason:
A value was entered in the End Offset field on the Sort Fields panel that was less than the value entered in the Start Offset field. P1 was set to End Offset and P2 was set to Start Offset.
System Action:
The Sort Fields panel is displayed with the End Offset field set in error.
User Action:
Change the value of the Start Offset or End Offset field so that the End Offset is greater than or equal to the Start Offset and retry.
Reason:
A value was entered in the Order field on the Sort Fields panel and a value was not entered in the Field Name field. P1 was set to Order and P2 was set to Field Name.
System Action:
The Sort Fields panel is displayed with the Order field set in error.
User Action:
Clear the Order field or enter a field name in the Field Name field and retry.
Reason:
An invalid value was entered in the Order field on the Sort Fields panel. P1 was set to Order.
System Action:
The Sort Fields panel is displayed with the Order field set in error.
User Action:
Enter 'A' for ascending or 'D' for descending in the Order field and retry.
Reason:
A value was entered in the Start Offset or End Offset field on the Sort Fields panel, however, the application in which the report was defined did not support sort field offsets. The field in which the offset was entered was P1 and the application ID was P2 .
System Action:
The Sort Fields panel is displayed with the P1 field set in error.
User Action:
Clear the P1 field and retry.
Reason:
A value was entered in the Order field on the Sort Fields panel that was not equal to P2 . The application in which the report was defined only supported the Order field being set to P2 . The application ID was P2 and P1 was set to Order.
System Action:
The Sort Fields panel is displayed with the Order field set in error.
User Action:
Enter P2 in the Order field and retry.
Reason:
A combination of A's (ascending) and D's (descending) were entered in the Order fields on the Sort Fields panel, however, the application in which the report was defined did not support mixed sort orders. The application ID was P2 and P1 was set to Order.
System Action:
The Sort Fields panel is displayed with the Order field set in error.
User Action:
Change the value of the Order fields so they are all set to A or D and retry.
Reason:
The number of sort fields that were entered on the Sort Fields panel exceeded the maximum supported by the application in which the report was defined. The application ID was P1 and the maximum number of sort fields supported by the application was P2 .
System Action:
The Sort Fields panel is displayed with the Field Name field set in error.
User Action:
Specify fewer sort fields.
Reason:
The service procedure $RWVL18L for the View Report Layout failed because it received an unknown call type in variable &$SLCALLTYPE from procedure $CABU000. The unknown call type was P1 .
System Action:
Procedure $RWVL18L terminates.
User Action:
Contact the system administrator.
Reason:
Procedure $RWVL18L encountered an error accessing a variable table. The request was P1 , the identifier of the variable table was P3 and the feedback code was P2 .
System Action:
Procedure $RWVL18L terminates.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to view the layout for a report definition failed because the user was not authorized for the request. The userid of the user was P1 and the report type was P2 .
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to view the layout for a report definition failed because the report definition was not defined. The report type was P1 and the name of the report was P2 .
System Action:
The request is rejected.
User Action:
Specify a report name previously defined and retry.
Reason:
The LOCATE command was entered in the Command field on the View Report Layout panel, however, it was not allowed to be entered on that panel.
System Action:
The command is rejected.
User Action:
Clear the Command field.
Reason:
A request to view the layout for a report definition failed because there were no format items defined for the specified report.
System Action:
The request is rejected.
User Action:
None.
Reason:
The service procedure $RWRD19L for the Report List failed because it received an unknown call type in variable $SLCALLTYPE from procedure $CASL000. The unknown call type was P1 .
System Action:
Procedure $RWRD19L terminates.
User Action:
Contact the system administrator.
Reason:
A request to present a Report List failed because an error was encountered allocating a variable table. The request was P1 , the identifier of the variable table was P3 and the feedback code was P2 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to present a Report List failed because an error was encountered accessing a variable table. The request was P1 , the identifier of the variable table was P3 , the feedback code was P2 and the key value used was P4 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to present a Report List failed because there were no reports defined within the range specified.
System Action:
The request is rejected.
User Action:
None.
Reason:
The selection of a report from the Report List failed because the report was deleted by another user since the Report List was displayed. The name of the report selected was P1 .
System Action:
The selection of the report is rejected.
User Action:
None.
Reason:
The service procedure $RWFI20M for the Control Break Header Menu, Data Format Menu or Control Break Trailer Menu failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $RWFI20M terminates.
User Action:
Contact the system administrator.
Reason:
A request to access the Control Break Header Menu, Data Format Menu or Control Break Trailer Menu failed because the user was not authorized for the request. The userid of the user was P1 and the requested request was P2 . P3 is set to 'YOUR OWN PRIVATE' if the report to be accessed was their own or set to 'OTHER USERS PRIVATE' if another user's report was to be accessed.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to access the Control Break Header Menu, Data Format Menu or Control Break Trailer Menu failed because the service procedure $RWFI20M for the menu received an unknown return code from procedure $CAUA000. The unknown return code was P1 .
System Action:
The request is rejected and procedure $RWFI20M terminates.
User Action:
Contact the system administrator.
Reason:
The service procedure $RWFI20M for the Control Break Header Menu, Data Format Menu or Control Break Trailer Menu received an unknown return code from a procedure that was executed as the action for an option on the menu. The unknown return code was P1 .
System Action:
Procedure $RWFI20M terminates and the Control Break Header Menu, Data Format Menu or Control Break Trailer Menu is presented.
User Action:
Contact the system administrator.
Reason:
An option was selected from the Control Break Header Menu, Data Format Menu or Control Break Trailer Menu and a value was not entered in the P1 field. The option selected was P2 .
System Action:
The selection of the option is rejected and the P1 field is set in error.
User Action:
Enter a value in the P1 field and retry.
Reason:
An option was selected from the Control Break Header Menu, Data Format Menu or Control Break Trailer Menu and an invalid value was entered in the P1 field. The value entered was not numeric.
System Action:
The selection of the option is rejected and the P1 field is set in error.
User Action:
Correct the value in the P1 field and retry.
Reason:
The service procedure $RWFD21L for the Control Break Header List, Data Format List, Control Break Trailer List or Report Definition Component List failed because it received an unknown call type in variable &$SLCALLTYPE from procedure $CASL000. The unknown call type was P1 .
System Action:
Procedure $RWFD21L terminates.
User Action:
Contact the system administrator.
Reason:
A request to present a Control Break Header List, Data Format List or Control Break Trailer List failed because there were no P1 defined.
System Action:
The request is rejected.
User Action:
None.
Reason:
The selection of a P1 from the Control Break Header List, Data Format List, Control Break Trailer List or Report Definition Component List failed because it was deleted by another user since the list was presented. The component selected was P1 and if the component was a control break header or trailer or data format P2 was the sort field number or data format number.
System Action:
The selection of the P1 is rejected.
User Action:
None.
Reason:
A P2 was selected from the Report Definition Component List, however, the function request was not valid for the record selected. The function requested was P1 .
System Action:
The selection of the P2 is rejected.
User Action:
None.
Reason:
A request to present a Control Break Header List, Data Format List, Control Break Trailer List or Report Definition Component List failed because the user was not authorized for the request. The userid of the user was P1 . P2 is set to 'YOUR OWN PRIVATE' if the report to be accessed was their own or set to 'OTHER USERS PRIVATE' if another user's report was to be accessed.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to present a Control Break Header List, Data Format List, Control Break Trailer List or Report Definition Component List for a public report failed because the report was not defined. The name of the report was P1 .
System Action:
The request is rejected.
User Action:
Correct the name of the report and retry.
Reason:
A request to present a Control Break Header List, Data Format List, Control Break Trailer List or Report Definition Component List for a private report failed because the report was not defined. The name of the report was P1 .
System Action:
The request is rejected.
User Action:
Correct the name of the report and retry.
Reason:
A request display report information failed because procedure $RWRI22P received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $RWRI22P terminates.
User Action:
Contact the system administrator.
Reason:
An invalid command was entered in the Command field on the Report Information panel.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
A request to display report information failed because the report definition was not defined. The name of the report was P1 and it was a public report.
System Action:
The request is rejected.
User Action:
Specify a report name previously defined and retry.
Reason:
A request to display report information failed because the report definition was not defined. The name of the report was P1 and it was a private report owned by userid P2 .
System Action:
The request is rejected.
User Action:
Specify a report name previously defined and retry.
Reason:
A request to display report information failed because the criteria defined in the report definition was not defined. The name of the criteria was P1 and it was a public criteria.
System Action:
The request is rejected.
User Action:
Update the report definition to contain a criteria previously defined and retry.
Reason:
A request to display report information failed because the criteria defined in the report definition was not defined. The name of the criteria was P1 and it was a private criteria owned by userid P2 .
System Action:
The request is rejected.
User Action:
Update the report definition to contain a criteria previously defined and retry.
Reason:
Function key P1 was pressed on the Report Information panel and the command assigned to it was invalid.
System Action:
The command is rejected.
User Action:
Correct the setting of the function key and retry.
Reason:
The service procedure $RWSD30M for the Schedule Definition Menu failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $RWSD30M terminates.
User Action:
Contact the system administrator.
Reason:
A request to access the Schedule Definition Menu or start or stop schedule processing failed because the user was not authorized for the request. The userid of the user was P1 and if the menu was to be accessed P2 was set to 'MAINTAIN' or if schedule processing was to be started or stopped P2 was set to 'START/STOP'.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to access the Schedule Definition Menu failed because the service procedure $RWSD30M for the menu received an unknown return code from procedure $CAUA000. The unknown return code was P1 .
System Action:
The request is rejected and procedure $RWSD30M terminates.
User Action:
Contact the system administrator.
Reason:
An option was selected from the Schedule Definition Menu and an invalid value was entered in the P1 field. The value entered was not alphanumeric and/or national characters.
System Action:
The selection of the option is rejected and the P1 field is set in error.
User Action:
Correct the value in the P1 field and retry.
Reason:
A request to add, browse, update, delete or copy a schedule definition failed because procedure $RWSD31P received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $RWSD31P terminates.
User Action:
Contact the system administrator.
Reason:
An invalid command was entered in the Command field on the Schedule Definition panel.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
A request to browse, update, delete or copy a schedule definition failed because the schedule definition was not defined. The name of the schedule was P1 .
System Action:
The request is rejected.
User Action:
Specify a schedule name previously defined and retry.
Reason:
An add, browse, update or delete schedule definition request was cancelled. The request cancelled was P1 .
System Action:
None.
User Action:
None.
Reason:
A schedule definition was successfully added, updated or deleted. The name of the schedule definition was P1 and the action successfully performed was P2 .
System Action:
None.
User Action:
None.
Reason:
A request to add a schedule definition failed because the schedule definition was already defined. The name of the schedule was P1 .
System Action:
The request is rejected.
User Action:
Specify a schedule name not previously defined and retry.
Reason:
A command was entered in the Command field on the Schedule Definition panel that was a valid command, however, it was not allowed to be specified on that panel.
System Action:
The command is rejected.
User Action:
Clear the Command field.
Reason:
A request to update or delete a schedule definition failed because the schedule definition was being updated or deleted by another user. The name of the schedule was P1 .
System Action:
The request is rejected.
User Action:
Update or delete the schedule when it is not being updated or deleted by another user.
Reason:
A request to add, browse, update, delete or copy a schedule definition failed because the user was not authorized for the request. The function requested was P2 and the userid of the user was P1 .
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to add, browse, update, delete or copy a schedule definition failed because procedure $RWSD31P received an unknown return code from procedure $CAUA000. The unknown return code was P1 .
System Action:
The request is rejected and procedure $RWSD31P terminates.
User Action:
Contact the system administrator.
Reason:
The Schedule Definition panel was displayed requesting the user to confirm the deletion of the schedule definition presented.
System Action:
None.
User Action:
Press the ENTER key to allow the schedule definition to be deleted, or press the CANCEL key to cancel the delete request.
Reason:
The validation exit $RWSD32X for the Schedule Definition panel received an unknown field name from procedure $CAGP000. The name of the field was P1 .
System Action:
Procedure $RWSD32X terminates.
User Action:
Contact the system administrator.
Reason:
A schedule name was entered in the Schedule Name field on the Schedule Definition panel that was previously defined. The schedule name entered was P1 .
System Action:
The Setup Definition panel is displayed with the Schedule Name field set in error.
User Action:
Enter a schedule name not previously defined and retry.
Reason:
An invalid value was entered in the P1 field on the Schedule Definition panel.
System Action:
The Schedule Definition panel is displayed with the P1 field set in error.
User Action:
Enter 'TIME', 'DAYS' or 'MONTHS' in the P1 field and retry. Only the first character needs to be entered.
Reason:
A date was entered in the Expiry Date field on the Schedule Definition panel that was less than or equal to the date entered in the Start Date field. P1 was set to Expiry Date.
System Action:
The Schedule Definition panel is displayed with the Expiry Date field set in error.
User Action:
Change the date in the Start Date or Expiry Date field so that the Expiry Date is greater than the Start Date and retry.
Reason:
An invalid day was entered in the P1 field on the Schedule Definition panel.
System Action:
The Schedule Definition panel is displayed with the P1 field set in error.
User Action:
Enter a list of valid days separated by commas in the P1 field or clear the field and retry.
Reason:
An invalid value was entered in the P1 field on the Schedule Definition panel.
System Action:
The Schedule Definition panel is displayed with the P1 field set in error.
User Action:
Enter 'ACTIVE' or 'INACTIVE' in the P1 field and retry. Only the first character needs to be entered.
Reason:
An invalid value was entered in the P1 field on the Schedule Definition panel.
System Action:
The Schedule Definition panel is displayed with the P1 field set in error.
User Action:
Enter 'MON', 'LOG', 'SYS' or '*' in the P1 field and retry.
Reason:
An invalid value was entered in the P1 field on the Schedule Definition panel.
System Action:
The Schedule Definition panel is displayed with the P1 field set in error.
User Action:
Enter 'MON', 'LOG' or 'SYS' in the P1 field and retry. Only the first character needs to be entered.
Reason:
A time was entered in the End Time field on the Schedule Definition panel that was less than or equal to the time entered in the Start Time field. P1 was set to End Time.
System Action:
The Schedule Definition panel is displayed with the End Time field set in error.
User Action:
Change the time in the Start Time or End Time field so that the End Time is greater than the Start Time and retry.
Reason:
If specified, the Valid Days list must contain the day, P2 for compatibility with a Start Date which falls on that day when the Frequency Type is DAYS and the Frequency is a multiple of 7.
System Action:
The Schedule Definition panel is displayed with the Valid Days field set in error.
User Action:
Change the Valid Days field to P2 or clear it and retry. Changing the value of the Start Date and/or Frequency fields will also correct the incompatibility error.
Reason:
The service procedure $RWSD33L for the Schedule Definition List failed because it received an unknown call type in variable &$SLCALLTYPE from procedure $CASL000. The unknown call type was P1 .
System Action:
Procedure $RWSD33L terminates.
User Action:
Contact the system administrator.
Reason:
A request to present a Schedule Definition List failed because there were no schedules defined.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to present a Schedule Definition List failed because there were no schedules defined with names starting with the characters ' P1 '.
System Action:
The request is rejected.
User Action:
None.
Reason:
A schedule definition was successfully deleted. The name of the schedule definition successfully deleted was P1 .
System Action:
None.
User Action:
None.
Reason:
The selection of a schedule definition from the Schedule Definition List failed because the schedule was deleted by another user since the list was presented. The name of the schedule definition selected was P1 .
System Action:
The selection of the schedule definition is rejected.
User Action:
None.
Reason:
A request to delete a schedule definition failed because the schedule definition was being updated or deleted by another user. The name of the schedule was P1 .
System Action:
The request is rejected.
User Action:
Delete the schedule when it is not being updated or deleted by another user.
Reason:
A request to delete a schedule definition failed because the user was not authorized for the request. The userid of the user was P1 .
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to delete a schedule definition failed because the service procedure $RWSD33L for the Schedule Definition List received an unknown return code from procedure $CAUA000. The unknown return code was P1 .
System Action:
The request is rejected and procedure $RWSD33L terminates.
User Action:
Contact the system administrator.
Reason:
A request to generate a report failed because the user was not authorized for the request. The userid of the user was P1 .
System Action:
The request is rejected.
User Action:
None.
Reason:
A report was requested to be generated in foreground mode. This message is displayed on the Generate a Report panel while the report is being generated by the system.
System Action:
The report specified on the Generate a Report panel is being generated.
User Action:
None.
Reason:
A report was requested to be generated in background mode.
System Action:
The report specified on the Generate a Report panel is being generated under the background logger environment.
User Action:
None.
Reason:
An invalid command was entered in the Command field on the Generate a Report panel.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Function key P1 was pressed on the Generate a Report panel and the command assigned to it was invalid.
System Action:
The command is rejected.
User Action:
Correct the setting of the function key and retry.
Reason:
A request to generate a report failed because the report exit or service procedure for the report was not found on the procedure library. The type of procedure not found was P1 and the name of the procedure was P2 .
System Action:
The request is rejected.
User Action:
Correct the report exit or service procedure name, or create the procedure and retry.
Reason:
A request to generate a report failed because the report exit or service procedure set an unknown return code in variable RETCODE. The type of procedure which set the unknown return code was P1 , the name of the procedure was P2 and the unknown return code was P3 .
System Action:
The report generator terminates.
User Action:
Correct the setting of the return code by the P1 procedure and retry.
Reason:
A request to generate a report failed because a control break header or trailer was defined for a sort field number that was not defined. The sort field number was P1 .
System Action:
The report generator terminates.
User Action:
Correct the report definition by defining a sort field for sort field number P1 and retry.
Reason:
A request to generate a report failed because the report was not defined. The type of report was P1 and the name of the report was P2 .
System Action:
The request is rejected.
User Action:
Specify a report name previously defined and retry.
Reason:
A report was successfully generated.
System Action:
None.
User Action:
None.
Reason:
A request to generate a report completed successfully, however, no data was received from the service procedure to be used to produce the report.
System Action:
None.
User Action:
None.
Reason:
A request to generate a report failed because procedure $RWGR41Z was unable to obtain a lock. The primary name of the lock was P1 , the return code was P2 and the feedback code was P3 .
System Action:
The request is rejected and procedure $PSGR41Z terminates.
User Action:
Interpret the feedback code using the NCL Reference. The SHOW LOCKS command can be issued from an OCS window to determine the procedure and userid that is holding the lock.
Reason:
A request to generate a report failed because the user was not authorized for the request. The userid of the user was P1 and the type of report was P2 .
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to generate a report failed because the number of lines in the report format was greater than the Lines per Page field in the form definition that was defined for the printer on which the report was to be printed.
System Action:
The request is rejected.
User Action:
Change the name of the printer or form on which the report is to be printed or reduce the number of lines in the page header or trailer in the report definition and retry.
Reason:
The generation of a report failed or was incomplete because the report generator procedure encountered an error.
System Action:
This message and other messages indicating the report name and reason for the error are printed.
User Action:
Refer to the other messages printed for more information.
Reason:
The generation of a report failed or was incomplete because the report generator procedure encountered an error. This message is issued after message RW4113 to indicate the name of the report in error. The application ID in which the report was defined was P1 , the report type was P2 , the userid of the owner if the type was private was P3 and the name of the report was P4 . The owner of the report output was P5 .
System Action:
This message is printed.
User Action:
Refer to the other messages printed for more information.
Reason:
The generation of a report was cancelled by request from a user. The userid of the user was P1 .
System Action:
None.
User Action:
None.
Reason:
The generation of a report has commenced. The application ID in which the report was defined was P1 , the report type was P2 , the userid of the owner if the type was private was P3 and the name of the report was P4 . The owner of the report output was P5 .
System Action:
None.
User Action:
None.
Reason:
The generation of a report has completed. The application ID in which the report was defined was P1 , the report type was P2 , the userid of the owner if the type was private was P3 and the name of the report was P4 . The owner of the report output was P5 .
System Action:
None.
User Action:
None.
Reason:
Report generation was unable to proceed because the report definition is incomplete. It contains no format items.
System Action:
Report generation fails.
User Action:
Update the report definition to include data fields and other components as required to define the report layout.
Reason:
The validation exit $RWGR42X for the Generate a Report panel received an unknown field name from procedure $CAGP000. The name of the field was
P1 .
System Action:
Procedure $RWGR42X terminates.
User Action:
Contact the system administrator.
Reason:
An invalid value was entered in the P1 field on the Generate a Report panel.
System Action:
The Generate a Report panel is displayed with the P1 field set in error.
User Action:
Correct the value in the P1 field and retry.
Reason:
An invalid value was entered in the P1 field on the Generate a Report panel.
System Action:
The Generate a Report panel is displayed with the P1 field set in error.
User Action:
Enter 'PUBLIC' or 'PRIVATE' in the P1 field and retry. Only the first two characters need to be entered.
Reason:
P3 was entered in the P2 field on the Generate a Report panel and a value was entered in the P1 field.
System Action:
The Generate a Report panel is displayed with the P1 field set in error.
User Action:
Clear the P1 field or change the value of the P2 field and retry.
Reason:
A value was entered in the Report Appl field on the Generate a Report panel that was less than three in length.
System Action:
The Generate a Report panel is displayed with the Report Appl field set in error.
User Action:
Correct the value in the Report Appl field and retry.
Reason:
A request to present a Report List failed because there were no reports defined for the application specified.
System Action:
The request is rejected.
User Action:
None.
Reason:
The service procedure $RWRP43L for the Report in Progress failed because it received an unknown call type in variable &$SLCALLTYPE from procedure $CASL000. The unknown call type was P1 .
System Action:
Procedure $RWRP13L terminates.
User Action:
Contact the system administrator.
Reason:
A request to present the Reports in Progress failed because the user was not authorized for the request. The userid of the user was P1 . A user must be authorized to access the Report Writer Primary Menu to be able to present the Reports in Progress
System Action:
The request is rejected.
User Action:
None.
Reason:
A cancel or purge command was requested from the Reports in Progress panel. The command requested was P1 .
System Action:
The report is flagged for purging or cancellation and the request will be processed when the status table is next updated.
User Action:
None.
Reason:
A request to cancel or purge a report failed because the user was not authorized for the request. The userid of the user was P1 . P2 is set to 'YOUR OWN PRIVATE' if the report to be cancelled or purged was their own or set to 'OTHER USERS PRIVATE' if another user's report was to be cancelled or purged.
System Action:
The request is rejected.
User Action:
None.
Reason:
The service procedure $RWRL60L for the Report List failed because it received an unknown call type in variable &$SLCALLTYPE from procedure $CASL000. The unknown call type was P1 .
System Action:
Procedure $RWRL60L terminates.
User Action:
Contact the system administrator.
Reason:
A request to present a Report List failed because there were no reports defined.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to present a Report List failed because there were no reports defined within the range specified.
System Action:
The request is rejected.
User Action:
None.
Reason:
A Report List was presented and a report was not selected.
System Action:
None.
User Action:
None.
Reason:
The service procedure $RWRL61L for the Report List failed because it received an unknown call type in variable $SLCALLTYPE from procedure $CASL000. The unknown call type was P1 .
System Action:
Procedure $RWRL61L terminates.
User Action:
Contact the system administrator.
Reason:
A request to present a Report List failed because an error was encountered allocating a variable table. The request was P1 , the identifier of the variable table was P3 and the feedback code was P2 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to present a Report List failed because an error was encountered accessing a variable table. The request was P1 , the identifier of the variable table was P3 , the feedback code was P2 and the key value used was P4 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to present a Report List failed because there were no reports defined.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to present a Report List failed because there were no reports defined within the range specified.
System Action:
The request is rejected.
User Action:
None.
Reason:
A Report List was presented and a report was not selected.
System Action:
None.
User Action:
None.
Reason:
A value was not entered in the P1 field on the CAS Table Entry Definition panel.
System Action:
The Table Entry panel is displayed with the P1 field set in error.
User Action:
Enter a value in the P1 field and retry.
Reason:
An invalid value was entered in the Sort Order Support field on the CAS Table Entry Definition panel. P1 was set to Sort Order Support.
System Action:
The Table Entry panel is displayed with the Sort Order Support field set in error.
User Action:
Enter one of the following values in the Sort Order Support field and retry. A - Only ascending order is supported. D - Only descending order is supported. BOTH - Ascending and descending both supported, but all fields must be sorted in the same order. MIXED - Ascending and descending both supported and fields may be sorted in either order.
Reason:
An invalid value ( P1 ) was entered in the Full Value field on the CAS Table Entry Definition panel. All entries in the $RWAPPL table for application ID ( P2 ) must begin with that application ID.
System Action:
The Table Entry panel is displayed with the Full Value field set in error.
User Action:
Correct the entry and retry.
Reason:
The Report Writer Report Application Table (Application $RW, Table Name APPL) either does not exist, or has no entries. There are no Report Applications to be converted.
System Action:
The Report Writer Report Application Conversion Utility terminates normally.
User Action:
None.
Reason:
Application ID P1 is not defined in the Application Register. Therefore no $RWAPPL table is defined for that application and hence, there is no table to add the report application P2 to.
System Action:
The Report Writer Report Application Conversion Utility ignores this report application and continues.
User Action:
Add the Application ID using MODS. Then add the $RWAPPL table definition using CAS Table Services using the following attributes:
Edit type = TABLE Validation exit = $RWVM70X
Sequence numbers = NO
Load Table = YES
Max abbreviation length = blank
Max full value = 8
Max description length = 38
Note: It may be easier to copy an existing $RWAPPL table definition for another application, for example application $RW.
Reason:
The Report Writer Report Application Conversion Utility has created a $RWAPPL table for application P1. This message will be followed by one or more RW7204 messages showing the Report Application entries that have been copied to this new table.
System Action:
The Report Writer Report Application Conversion Utility continues processing the $RW.APPL table.
User Action:
None.
Reason:
The P1 Report Application entry has been copied from the $RW.APPL table to the $RWAPPL table for application P2.
System Action:
The Report Writer Report Application Conversion Utility continues processing the $RW.APPL table.
User Action:
None.
Reason:
The P1 Report Application entry has not been copied to the application's $RWAPPL table because it already exists.
System Action:
The Report Writer Report Application Conversion Utility continues processing the $RW.APPL table.
User Action:
None.
Reason:
An unexpected error has occured accessing the CAS Tables Database. Diagnostic information is provided as follows:
P1 is an action code
P2 is key information
P3 is the Database Manager return code
P4 is the Database Manager feedback code
Note: This message is normally preceded by another message (DBnnnn) which contains additional information.
System Action:
The Report Writer Report Application Conversion Utility ends.
User Action:
Note the diagnostic information and contact your product supplier with this information.
Reason:
The Report Writer Report Application Conversion Utility has ended. In the message, P1 is the completion code, P2 the number of new $RWAPPL tables added (and messages RW7203 issued), and P3 the total number of report application entries copied (and messages RW7204 issued).
If the completion code ( P1 ) is non zero, the results are incomplete and previous messages will indicate why.
System Action:
The Report Writer Report Application Conversion Utility ends.
User Action:
If the completion code is non-zero establish the cause of error from prior messages, correct, and rerun.
Reason:
There are no Report Writer tables whose names are at least 7 characters, the last 4 being DATA or SORT, and the first 3 are not $RW. Thus there are no tables to be converted.
System Action:
The Report Writer Report Table Conversion Utility terminates normally.
User Action:
None.
Reason:
Application ID P1 is not defined in the Application Register. Therefore no tables may be defined for that application and hence it is not possible to copy report table P2 under that application ID.
System Action:
The Report Writer Table Conversion Utility ignores this table and continues.
User Action:
Add the Application ID using MODS and rerun the utility.
Reason:
The P1 Report Table has been copied from application ID $RW to application ID P2.
System Action:
The Report Writer Table Conversion Utility continues with the next table.
User Action:
None.
Reason:
The P1 Report Table has not been copied because it already exists in the new application ID (the first three characters of the table name).
System Action:
The Report Writer Table Conversion Utility continues with the next table.
User Action:
None.
Reason:
The Report Writer Tables Conversion Utility has ended. In the message,
P1 is the completion code and P2 the number of tables copied (and messages RW7303 issued).
If the completion code ( P1 ) is non zero, the results are incomplete and previous messages will indicate why.
System Action:
The Report Writer Tables Conversion Utility ends.
User Action:
If the completion code is non-zero establish the cause of error from prior messages, correct, and rerun.
Reason:
An unexpected error has occured accessing the CAS Tables Database. Diagnostic information is provided as follows:
P1 is an action code
P2 is key information
P3 is the Database Manager return code
P4 is the Database Manager feedback code
Note: This message is normally preceded by another message (DBnnnn) which contains additional information.
System Action:
The Report Writer Table Conversion Utility ends.
User Action:
Note the diagnostic information and contact your product supplier with this information.
Reason:
An error occurred attempting to read a Report Writer definition. In the message:
P1 is the file ID.
P3 is the file return code (&FILERC).
P4 is the file feedback code (&VSAMFDBK).
P4 is the file key.
System Action:
The procedure terminates.
User Action:
For return code and feedback values, see the &FILE GET verb description in the NCL Reference.
Reason:
An error occurred attempting to write a Report Writer definition. In the message:
P1 is the file ID.
P3 is the file return code (&FILERC).
P4 is the file feedback code (&VSAMFDBK).
P4 is the file key.
System Action:
The procedure terminates.
User Action:
For return code and feedback values, see the &FILE GET verb description in the NCL Reference.
Reason:
An error occurred attempting to delete a Report Writer definition. In the message:
P1 is the file ID.
P3 is the file return code (&FILERC).
P4 is the file feedback code (&VSAMFDBK).
P4 is the file key.
System Action:
The procedure terminates.
User Action:
For return code and feedback values, see the &FILE GET verb description in the NCL Reference.
Reason:
A REXX emulation error has occurred. P1 is a message of a group of messages that traps the related error details.
System Action:
The current REXX request is terminated.
User Action:
Contact Technical Support.
Reason:
REXX NetMaster emulation detected a command which is invalid or not supported at the moment.
P1 is the command name.
P2 is the REXX procedure name.
P3 is the NetMaster process number (NCLID) executing the REXX proc.
System Action:
None.
User Action:
Verify and correct the command specification.
Reason:
REXX NetMaster emulation detected a function which is invalid or not supported at the moment.
P1 is the function name.
P2 is the REXX procedure name.
P3 is the NetMaster process number (NCLID) executing the REXX proc.
System Action:
None.
User Action:
Verify and correct the function specification.
Reason:
REXX NetMaster emulation detected that the keyword argument was incorrectly specified.
P1 is the command name.
P2 is the original error message.
P3 is the REXX procedure name.
P4 is the NetMaster process number (NCLID) executing the REXX proc.
System Action:
None.
User Action:
Verify the syntax and correct the arguments.
Reason:
NetMaster REXX command failed while using an OML function or verb.
P1 is the NetMaster REXX command/function name.
P2 is the error code indicated by the OML language executor.
P3 is the REXX procedure name.
P4 is the NetMaster process number (NCLID) executing the REXX proc.
System Action:
None.
User Action:
Verify the specification of the arguments for the emulated command or function and fix them according to the specification. If you cannot fix the arguments, Contact Technical Support and provide them with diagnostic data.
Reason:
This message logs the fact that the function was called in either a NETVIEW or NETVASIS environment.
P1 is the function name.
P2 is the calling pocedure name.
P3 is the REXXHELP process identifier.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the external NetView/NetVASIS Rexx function although defined in function table is not defined in the emulation functions table. It indicates mismatch between both definitions.
P1 is the function name.
P2 is the calling pocedure name.
P3 is the REXXHELP process identifier.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The message displays a REXX EXECIO trace record.
P1 is the NCLID, P2 is the trace ID, P3 is the DDNAME and P4 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The REXX EXECIO emulator procedure has encountered an internal system error. P1 is the reason for the failure.
System Action:
Processing terminates,
User Action:
Contact Technical Support.
Reason:
The REXX EXECIO emulator procedure requires input from the data stack. The data stack is empty, the procedure now reads from the terminal. P1 is the NCLID.
System Action:
Waits for terminal input.
User Action:
Reply "GO ID= P1 --data--" to resume.
Reason:
The REXX EXECIO emulator procedure does not currently support DISKRU (open data set for update).
System Action:
EXECIO terminates.
User Action:
You may want to write the updated data to a work file and copy it back to the source file.
Reason:
The REXX EXECIO emulator procedure has exceeded the maximum amount of virtual storage available for a REXX process.
System Action:
EXECIO terminates.
User Action:
Review the SYSPARMS RXMSTG setting by issuing the following command:
SHOW SYSPARMS=RXMSTG . RXMSTG sets the maximum amount of storage that a given REXX process can use at any time. Its value ranges from 10 KB to 4096 KB (default is 1024 KB).
Alternatively, you can override this value for a given procedure at execution time by including the following REXX OPTIONS statement:
OPTIONS "MAXSTOR=nK"
where the value of nK ranges from 32 KB to 100000 KB.
Reason:
The exec tried to write to the specified file, but the function is not allowed. The indicated file is not open for output. P1 is the file DDNAME.
System Action:
The WRITE function is not performed.
User Action:
If the indicated file is currently opened for READ, close it and reopen for output or update.
Reason:
The exec tried to read from the specified file, but the function is not allowed. The indicated file is not open for input. P1 is the file DDNAME.
System Action:
The READ function is not performed.
User Action:
If the indicated file is currently opened for WRITE, close it and reopen for input or update.
Reason:
No positional parameters were found for the EXECIO command. However, you must specify at least three positional parameters.
System Action:
EXECIO terminates.
User Action:
Specify a number or * as the first positional parameter to indicate the the number of lines to process. Specify DISKR, or DISKW (the operation) as the second positional parameter. Specify the ddname (to which or from which I/O is to be performed) as the third positional parameter.
Reason:
The second positional parameter on the EXECIO command is missing. It must be a valid operation identifier (DISKR or DISKW).
System Action:
EXECIO terminates.
User Action:
Specify DISKR (input) to read a file or DISKW (output) to write a file.
Reason:
The third positional parameter on the EXECIO command is missing. This parameter is required.
System Action:
EXECIO terminates.
User Action:
Specify a 1 to 8 character ddname to which or from which I/O is to be performed. The ddname should be allocated to a sequential data set, or to a single member of a partitioned data set.
Reason:
An unknown positional parameter was specified.
System Action:
EXECIO terminates.
User Action:
You may specify a maximum of four positional parameters. Remove any extra parameters. If you wish to specify EXECIO options, they should follow the positional parameters, and should be delimited from the positional parameters by a left parenthesis ' ( '.
Reason:
The first EXECIO positional parameter must specify the number of lines to be processed by EXECIO.
System Action:
EXECIO terminates.
User Action:
Specify * or a number : An * means that end-of-file terminates the EXECIO DISKR operation and a null line or an uninitialized STEM variable terminates an EXECIO DISKW operation. A number indicates an exact number of lines to process before EXECIO terminates.
Reason:
The second positional parameter on the EXECIO command is not valid.
System Action:
EXECIO terminates.
User Action:
Specify DISKR or DISKW .
Reason:
The third positional parameter on the EXECIO command is not a valid ddname.
System Action:
EXECIO terminates.
User Action:
Specify a 1 to 8 character ddname to which or from which I/O is to be performed. The ddname should be allocated to a sequential data set, or to a single member of a partitioned data set.
Reason:
The EXECIO linenum parameter was specified with the DISKW operation. However, "linenum" cannot be specified with DISKW.
System Action:
EXECIO terminates.
User Action:
Remove the linenum parameter.
Reason:
The fourth positional parameter on the EXECIO command is optional. However, if specified it must be a valid number. This parameter represents the record number at which reading is to begin for a DISKR operation. This parameter is not valid when DISKW is specified.
System Action:
EXECIO terminates.
User Action:
Specify a valid number, or specify nothing.
Reason:
An unknown or ambiguous EXECIO keyword option was found on the EXECIO command. The valid options are: - FIFO, LIFO, STEM, SKIP, FINIS and OPEN.
System Action:
EXECIO terminates.
User Action:
Specify a valid option.
Reason:
The EXECIO STEM option can only be specified once on the EXECIO command.
System Action:
EXECIO terminates.
User Action:
Remove one of the STEM option.
Reason:
No STEM variable name was specified after the EXECIO STEM option.
System Action:
EXECIO terminates.
User Action:
Specify the name of the STEM variable after the STEM option of the EXECIO command. A STEM variable name may be from 1 to 240 characters in length.
Reason:
The specified EXECIO STEM name is too long.
System Action:
EXECIO terminates.
User Action:
Specify a valid REXX variable name after the EXECIO STEM option. Valid names are 1 to 240 characters in length, and must be valid REXX variable names.
Reason:
The specified EXECIO STEM name is not a valid REXX variable name.
System Action:
EXECIO terminates.
User Action:
Specify a valid REXX variable name after the EXECIO STEM option. Valid names are 1 to 240 characters in length, and must be valid REXX variable names.
Reason:
The EXECIO FIFO or LIFO option was specified with the DISKW operation. However, FIFO and LIFO cannot be specified with DISKW.
System Action:
EXECIO terminates.
User Action:
Remove the FIFO or LIFO option.
Reason:
The EXECIO SKIP option was specified with the DISKW operation. However, SKIP cannot be specified with DISKW.
System Action:
EXECIO terminates.
User Action:
Remove the SKIP option.
Reason:
The EXECIO FIFO or LIFO option was specified with the STEM option. However, FIFO and LIFO cannot be specified with the STEM option.
System Action:
EXECIO terminates.
User Action:
Remove the FIFO or LIFO option.
Reason:
The EXECIO procedure failed to open the file specified by DDNAME P1 as P2. P3 is the associated error message.
System Action:
EXECIO terminates.
User Action:
Review message P3 for additional information.
Reason:
The EXECIO procedure failed to read a record from the file specified by DDNAME P1. P2 is the associated error message.
System Action:
EXECIO terminates.
User Action:
Review message P3 for additional information.
Reason:
The EXECIO procedure failed to write a record to the file specified by DDNAME P1. P2 is the associated error message.
System Action:
EXECIO terminates.
User Action:
Review message P3 for additional information.
Reason:
The EXECIO procedure failed to close the file specified by DDNAME P1.
P3 is the associated error message.
System Action:
EXECIO terminates.
User Action:
Review message P3 for additional information.
Reason:
A request to UPDATE a record on file: P1 has been rejected because no record has been read for UPDATE. Update only allows the re-writing (in-place) of the last record read.
P1 is the file DDNAME.
System Action:
The WRITE function is terminated.
User Action:
Ensure that at least one record has been read for update.
Reason:
Member P1 in PDS allocated for output via DDNAME P3 is in use by another user. The ENQUEUE return code is P2.
System Action:
EXECIO terminates.
User Action:
Try later.
Reason:
A REXX data set has a non-valid record format. I/O is supported only to non-spanned fixed or variable record format. Spanned, track overflow, and undefined record formats are not supported.
P1 is the file DDNAME.
System Action:
EXECIO terminates.
User Action:
Check the record format of the data set specified by DDNAME P1 .
Reason:
A REXX data set was opened for UPDATE (DISKRU). However, its size (in records) is larger than the supported maximum.
P1 is the file size limit (in records).
System Action:
EXECIO terminates.
User Action:
You may want to write the updated data to a work file and copy it back to the source file.
Reason:
An error occurred in storing a REXX variable from the EXECIO procedure. The variable value was not set successfully.
P1 is the variable name.
P2 is the EXECIO procedure emulation verb that failed.
P3 is the emulation verb return code.
P4 is the emulation verb feed back code.
System Action:
EXECIO terminates.
User Action:
Contact Technical Support.
Reason:
An error occurred in the EXECIO procedure when fetching a REXX variable. The variable value was not obtained successfully.
P1 is the variable name.
P2 is the EXECIO procedure emulation verb that failed.
P3 is the emulation verb return code.
P4 is the emulation verb feed back code.
System Action:
EXECIO terminates.
User Action:
Contact Technical Support.
Reason:
The stack error has occurred while trying to add an element to the data stack.
P1 is the EXECIO procedure emulation verb that failed.
P2 is the emulation verb return code.
P3 is the emulation verb feed back code.
System Action:
EXECIO terminates.
User Action:
Try to correct the error condition, or contact Technical Support.
Reason:
The stack error has occurred while trying to get an element to the data stack.
P1 is the EXECIO procedure emulation verb that failed.
P2 is the emulation verb return code.
P3 is the emulation verb feed back code.
System Action:
EXECIO terminates.
User Action:
Try to correct the error condition, or contact Technical Support.
Reason:
REXX NetMaster emulation detected that the command specified is written in unsupported language.
P1 is the command/procedure name
P2 is the language detected
System Action:
None.
User Action:
Verify the the spelling of the call and the language of called command, if source available.
Reason:
REXX NetMaster emulation detected that the positional argument P1 is invalid.
P2 describes the reason:
Action - action specified is invalid to the command emulated.
GLBL - text variable(name) does not start with 'GLBL'.
Length - text variable(name) is longer than allowed for its type:
- max 8 characters for NCL/OML procedure name.
- max 12 characters for global variable name.
- max 12 characters for vartable name.
- max 256 characters for NCL variable name.
Text - invalid text variable.
Txtype - text variable(name) contains characters invalid for its type.
List - list variable invalid, missing ending bracket.
System Action:
None.
User Action:
Verify the syntax and add correct arguments.
Reason:
REXX NetMaster emulation detected that the key argument specified is invalid.
P1 is the detailed message.
System Action:
None.
User Action:
Verify the syntax and correct arguments.
Reason:
REXX NetMaster emulation detected that the value of the key argument specified is invalid.
P1 - keyword value in error
P2 - describes the reason (see RXNM001 for explanations).
System Action:
None.
User Action:
Verify the syntax and correct arguments.
Reason:
REXX NetMaster emulation detected that the text specified starts with one type of the quote but does not end with it.
P1 - Name of the keyword in error
P2 - Text in error
System Action:
None.
User Action:
Verify the syntax and correct the arguments.
Reason:
REXX NetMaster emulation detected that the number of arguemts specified is less than required.
System Action:
None.
User Action:
Verify the syntax and add required arguments.
Reason:
REXX NetMaster emulation detected that the required positional argument was not specified
P1 is the name of missing keyword argument.
System Action:
None.
User Action:
Verify the syntax and add required arguments.
Reason:
REXX NetMaster emulation detected that the required keyword argument was not specified.
P1 is the name of missing keyword argument.
System Action:
None.
User Action:
Verify the syntax and add required arguments.
Reason:
REXX NetMaster emulation detected that the c-requisite positional argument was not specified.
P1 is the name of missing argument
System Action:
None.
User Action:
Verify the syntax and add required arguments.
Reason:
REXX NetMaster emulation detected that the c-requisite keyword argument was not specified. P1 is the name of missing argument.
System Action:
None.
User Action:
Verify the syntax and add required arguments.
Reason:
REXX NetMaster emulation detected that the co-requisite keyword argument value was not specified or the specification is shorter than expected.
P1 is the keyword list name.
System Action:
None.
User Action:
Verify the syntax and specify required values.
Reason:
REXX NetMaster emulation detected that the text provided as REXX variable name is not a valid REXX variable name.
P1 is the variable name.
System Action:
None.
User Action:
Verify the syntax and correct the arguments specification.
Reason:
REXX NetMaster emulation detected that the conflict in positional arguments.
P1 is the first argument.
P2 is the second argument.
System Action:
None.
User Action:
Verify the syntax and correct the arguments specification.
Reason:
REXX NetMaster emulation detected that the conflict in key arguments.
P1 is the first argument.
P2 is the second argument.
System Action:
None.
User Action:
Verify the syntax and correct the arguments specification.
Reason:
REXX NetMaster emulation detected that the keyword argument was specified which is excessive for the action selected.
P1 is the name of the argument.
System Action:
None.
User Action:
Verify the syntax and correct the arguments specification.
Reason:
REXX NetMaster emulation detected that the specified argument value(s) is incompatible with its meaning or two arguments specified are not compatible.
P1 is the first or only argument.
P2 is the second argument.
System Action:
None.
User Action:
Verify the syntax and correct the arguments specification.
Reason:
REXX NetMaster emulation VARTABLE trace is active. This message displays a REXX NM VARTABLE trace record.
P1 is the trace ID.
P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
An error occurred in the NetMaster Command emulation while calling Internal NetMaster Service.
P1 is the Service name.
P2 is the Service function name.
P3 is the Service Return Code.
P4 is the Service Feedback Code.
P5 is the Service SYSMSG.
System Action:
NetMaster command execution terminates.
User Action:
Verify your syntax for erros, correct and rerun, if necessary. If the situation persists, contact Technical Support.
Reason:
This is a continuation of msg RXNM201 providing further details:
P1 - Error text
System Action:
None.
User Action:
As per msg RXEM110401.
Reason:
NetMaster procedure P1 called by REXX program ended with Return Code P2.
System Action:
None.
User Action:
None.
Reason:
This is a continuation of RXNM301 providing additional information on the completion results of called procedure.
P1 - RETCODE
P2 - FDBK
P3 - SYSMSG
System Action:
None.
User Action:
If the information returned by the called NetMaster procedure indicates error or abnormal situation, resolve the situation and execute the REXX program again.
Reason:
Procedure P1 called by REXX program failed compilation stage.
P2 identifies the language the procedure is written in, NCL or OML.
P3 displays the error code indicated by the language compiler.
System Action:
None.
User Action:
If the procedure is in-house, run a direct compile, analyse errors, and fix the code.
It the procedure is a part of product distribution, contact Technical Support with the diagnostic data provided.
Reason:
This is a continuation of msg RXNM401 providing further details:
P1 - Error text
System Action:
None.
User Action:
As per msg RXNM401.
Reason:
This is a continuation of message RXNM401, providing more details:
P1 - File/member name containing the failed procedure.
P2 - Source line number in the file.
P3 - Failed statement name.
P4 - If present, failed keyword name.
System Action:
None.
User Action:
See message RXNM401.
Reason:
REXX Analysis Complete.
System Action:
None.
User Action:
None.
Reason:
$RXSA000 has been invoked with an invalid value.
System Action:
Analysis processing terminates in error.
User Action:
Refer to the comments in $RXSA000 for detail of valid values.
Reason:
P1 provides error condition detail.
System Action:
Analysis processing terminates in error.
User Action:
Try to resolve the issue. If the issue persists, contact Technical Support.
Reason:
Analysis Input Data Set DSORG is not Partitioned.
P1 specifies the invalid DSORG.
System Action:
Analysis processing terminates in error.
User Action:
Ensure your input data set has the following allocation details:
- RECFM = PO
- DSORG = FB or VB
- LRECL = Greater than or equal to 80 and less than or equal to 255
Reason:
Analysis Input Data Set RECFM is not Fixed or Variable Block.
P1 specifies the invalid RECFM.
System Action:
Analysis processing terminates in error.
User Action:
Ensure your input data set has the following allocation details:
- RECFM = PO
- DSORG = FB or VB
- LRECL = Greater than or equal to 80 and less than or equal to 255
Reason:
Analysis Input Data Set RECLEN is less than 80 or greater than 255.
P1 specifies the invalid RECLEN.
System Action:
Analysis processing terminates in error.
User Action:
Ensure your input data set has the following allocation details:
- RECFM = PO
- DSORG = FB or VB
- LRECL = Greater than or equal to 80 and less than or equal to 255
Reason:
Analysis Output Data Set DSORG is not Partitioned.
P1 specifies the invalid DSORG.
System Action:
Analysis processing terminates in error.
User Action:
Use the pre-allocated data set or allocate a valid data set.
If you allocate your own data set, ensure the allocation details are as follows: - DSORG = PO
- RECFM = VB
- LRECL = 1028
- BLKSIZE = 6240
- SPACE = CYL(30,2,50)
Reason:
Analysis Output Data Set RECFM is not Variable Block.
P1 specifies the invalid RECFM.
System Action:
Analysis processing terminates in error.
User Action:
Use the pre-allocated data set or allocate a valid data set.
If you allocate your own data set, ensure the allocation details are as follows: - DSORG = PO
- RECFM = VB
- LRECL = 1028
- BLKSIZE = 6240
- SPACE = CYL(30,2,50)
Reason:
Analysis Input Data Set RECLEN is less than 1024.
P1 specifies the invalid RECLEN.
System Action:
Analysis processing terminates in error.
User Action:
Use the pre-allocated data set or allocate a valid data set.
If you allocate your own data set, ensure the allocation details are as follows: - DSORG = PO
- RECFM = VB
- LRECL = 1028
- BLKSIZE = 6240
- SPACE = CYL(30,2,50)
Reason:
Analysis Output Data Set has an invalid member name.
P1 specifies the invalid member name.
System Action:
Analysis processing terminates in error.
User Action:
Delete the invalid member from the data set.
Reason:
Analysis Output Data Set has used all possible member names.
System Action:
Analysis processing terminates in error.
User Action:
Allocate a new Analysis Output Data Set or delete some members starting at A0000000.
Reason:
The output member being generated in the output analysis data set for this run is specified in P1 .
System Action:
Analysis processing continues.
User Action:
None.
Reason:
Specifies the number of members in Analysis input data set.
P1 specifies the number of members.
System Action:
Analysis processing continues.
User Action:
None.
Reason:
P1 specifies the number of members selected for inclusion.
System Action:
Analysis processing continues.
User Action:
None.
Reason:
P1 specifies the number of members rejected by exclusion.
System Action:
Analysis processing continues.
User Action:
None.
Reason:
P1 specifies the number of members passing inclusion and exclusion processing.
System Action:
Analysis processing continues.
User Action:
None.
Reason:
P1 specifies the number of members examined by scan.
System Action:
Analysis processing continues.
User Action:
None.
Reason:
P1 specifies the number of members rejected by scan.
System Action:
Analysis processing continues.
User Action:
None.
Reason:
P1 specifies the number of members selected by scan.
System Action:
Analysis processing continues.
User Action:
None.
Reason:
The was a mismatch between the number of records to be scanned and the number of records that were scanned.
P1 specifies the number of records that were scanned.
P2 specifies the number of records that were to be scanned.
System Action:
Analysis processing terminates.
User Action:
Run REXX Analysis processing again. If the problem persists, contact Technical Support.
Reason:
Analysis processing is starting and P1 specifies the total number of members to be analyzed.
System Action:
Analysis processing continues.
User Action:
None.
Reason:
Analysis processing is complete.
System Action:
Analysis processing ends.
User Action:
None.
Reason:
A member specified in P1 has passed scan processing and is starting to be analyzed.
System Action:
Analysis processing continues.
User Action:
None.
Reason:
Analysis processing for the member specified in P1 is complete.
System Action:
Analysis processing continues until all members have been analyzed.
User Action:
None.
Reason:
Analysis processing found an invalid character within the member:
P1 - Character within the member.
P2 - Line number within the member.
P3 - Column number within the member.
System Action:
Analysis processing continues until all members have been analyzed.
User Action:
Ensure the member is not corrupted and try running the Analyzer again. If the problem persists, contact Technical Support.
Reason:
Analysis processing failed because an attempt was made to read a new line after End Of File was processed.
System Action:
Analysis processing continues until all members have been analyzed.
User Action:
Ensure the member is not corrupted and try running the Analyzer again. If the problem persists, contact Technical Support.
Reason:
An error was experienced when attempting to write the trailer record to the Analysis output member.
System Action:
Analysis processing terminates.
User Action:
Review the Activity Log for additional information regarding this error. If the problem persists, contact Technical Support.
Reason:
P1 specifies the number of members that have been processed.
System Action:
Processing continues.
User Action:
None.
Reason:
P1 specifies the action being performed at the time of the data set processing failure.
P2 specifies the Return Code of the data set processing failure.
P3 specifies the Feedback Code of the data set processing failure.
System Action:
Analysis processing terminates.
User Action:
Review the displayed message and the Activity Log (/LOG) to determine the cause of the error. Ensure the data set is allocated correctly and this region has the required read or write access to this data set. See the chapter on Dataset Services Interface in the Network Control Language Reference for additional information about Return and Feedback codes.
If the problem persists, contact Technical Support.
Reason:
P1 specifies the REXX procedure name.
P2 specifies the type of record being processed at the time of failure.
System Action:
Analysis processing terminates.
User Action:
Review the message RXSA0029 for return code and feedback information. Ensure the dataset is allocated correctly and this region has the required read or write access to this dataset. See the chapter on Dataset Services in the NCL Control Language Reference for additional information about Return and Feedback codes.
If the problem persists contact Technical Support.
Reason:
P1 specifies the REXX procedure name.
P2 specifies the type of record being processed at the time of failure.
P3 specifies the failure reason.
System Action:
Analysis processing terminates.
User Action:
This condition can occur if the number of entities being processed within the REXX procedure exceeds the maximum record length of 1024. Detail of each record type is written to one line in the output member.
Check to see whether this member requires additional changes that have not been reported by the REXX analyzer.
Reason:
P1 specifies the number of records that were truncated during analysis. Details of each record type are written to one line in the output member.
This condition occurs if the number of entities being processed in the REXX procedure exceeds the maximum record length of 1024. This usually occurs when there are large single pipe stages, for example, LOCATE or PICK.
System Action:
None.
User Action:
Review the displayed messages in the Activity Log (/LOG) to determine which members were affected by the record truncation. Check to see whether this member requires additional changes that have not been reported by the REXX analyzer.
Reason:
P1 provides error condition detail.
System Action:
Report Generation processing terminates in error.
User Action:
Try to resolve the issue. If the issue persists, contact Technical Support.
Reason:
P1 specifies the version of the REXX Analyzer that is running.
System Action:
Report Generation processing continues.
User Action:
None.
Reason:
$RXSR000 has been invoked with an invalid value.
System Action:
Report generation processing terminates in error.
User Action:
Refer to the comments in $RXSR000 for detailed information about valid values.
Reason:
Report Input Data Set DSORG is not Partitioned.
P1 specifies the invalid DSORG.
System Action:
Report generation processing terminates in error.
User Action:
Ensure that the input data set is an output data set from the analysis run and has the following allocation details: - DSORG = PO - RECFM = VB - LRECL = 1028 - BLKSIZE = 6240 - SPACE = CYL(30,2,50)
Reason:
Report Input Data Set RECFM is not Variable Block.
P1 specifies the invalid RECFM.
System Action:
Report generation processing terminates in error.
User Action:
Ensure that the input data set is an output data set from the analysis run and has the following allocation details:
- DSORG = PO
- RECFM = VB
- LRECL = 1028
- BLKSIZE = 6240
- SPACE = CYL(30,2,50)
Reason:
Report Input Data Set RECLEN is less than 1024.
P1 specifies the invalid RECLEN.
System Action:
Report generation processing terminates in error.
User Action:
Ensure that the input data set is an output data set from the analysis run and has the following allocation details: - DSORG = PO - RECFM = VB - LRECL = 1028 - BLKSIZE = 6240 - SPACE = CYL(30,2,50)
Reason:
Output mode is invalid:
P1 specifies the output mode.
Internal Valid Values are:
- ONLINE
- SYSOUT
- DD
- TERM
Exteranally valid values are:
- ONLINE
- DSN
System Action:
Report generation processing terminates in error.
User Action:
Ensure that a valid output mode is specified. If calling $RXSR000 from a procedure, use the valid internal values above. If generating a report from the REXX Analyzer user interface, then specify either DSN or ONLINE.
Reason:
Report Output Data Set DSORG is not Physical Sequential.
P1 specifies the invalid DSORG.
System Action:
Report generation processing terminates in error.
User Action:
Ensure your output data set has the following allocation details: - RECFM = PS - BLKSIZE = 0 - LRECL = 137 - DSORG = VBA - SPACE = CYL(10,5)
Reason:
Report Output Data Set RECLEN is less than 137.
P1 specifies the invalid RECLEN.
System Action:
Report generation processing terminates in error.
User Action:
Ensure your output data set has the following allocation details:
- RECFM = PS
- BLKSIZE = 0
- LRECL = 137
- DSORG = VBA
- SPACE = CYL(10,5)
Reason:
The Report input data set does not contain any analysis members required for report generation.
P1 specified the Member Selection value specified during report generation.
System Action:
Report generiation processing terminates in error.
User Action:
Ensure the input data set used for report generation is the output data set of an analysis run.
Reason:
Report generation processing failed because and attempt was made to read the PDS after EOF.
System Action:
Report generation terminates.
User Action:
Ensure the input data set used for report generation is the output data set of an analysis run. If the problem persists, contact Technical Support.
Reason:
Report generation processing failed because an invalid member name was found in the input data set.
P1 specifies the name of the erroneous member.
System Action:
Report generation terminates.
User Action:
Ensure the input data set used for report generation is the output data set of an analysis run. A member name must start with 'A' and the remainder of the member name must be numeric.
Reason:
Report generation processing failed because an invalid member record was found.
P1 specifies the name of the erroneous member.
P2 specifies the erroneous data.
System Action:
Report generation terminates.
User Action:
Ensure the input data set used for report generation is the output data set of an analysis run. If the problem persists, contact Technical Support.
Reason:
Report generation processing failed because of a Vartable update failure.
P1 specifies the feedback code.
P2 specifies the Vartable ID.
P3 specifies the Key.
System Action:
Report generation terminates.
User Action:
Report the error to Technical Support providing the ID, Fdbk code, and key.
Reason:
Report generation processing failed because of a Vartable add failure.
P1 specifies the feedback code.
P2 specifies the Vartable ID.
P3 specifies the Key.
System Action:
Report generation terminates.
User Action:
Report the error to Technical Support providing the ID, Fdbk code, and key.
Reason:
Report Generation is processing an input member.
P1 specifies the member name.
P2 specifies the data the member was updated.
P3 specifies the owning data set.
System Action:
Report generation continues.
User Action:
None.
Reason:
The input member is invalid.
P1 specifies the error.
System Action:
Report terminates.
User Action:
Ensure the input data set used for report generation is the output data set of an analysis run. Review the Activity Log for additional information. If the problem persists, contact Technical Support.
Reason:
The input member is invalid.
P1 specifies the member name.
P2 specifies the error.
System Action:
Report terminates.
User Action:
Ensure the input data set used for report generation is the output data set of an analysis run. If the problem persists, contact Technical Support.
Reason:
Report Generation member processing for the member specified in P1 is complete.
System Action:
Report generation continues.
User Action:
None.
Reason:
$RXSR20W was invoked with an invalid argument and the procedure failed.
P1 specifies the invalid argument.
System Action:
Processing terminates.
User Action:
Review the comments and initialization of $RXSR20W, specify valid arguments, and re- run the procedure.
Reason:
Report generation has completed successfully.
System Action:
None.
User Action:
None.
Reason:
Report generation processing failed because of a Vartable allocation failure.
P1 specifies the feedback code.
P2 specifies the Vartable ID.
P3 specifies the Key.
System Action:
Report generation terminates.
User Action:
Report the error to Technical Support providing the ID, Fdbk code, and key.
Reason:
P1 specifies the action being performed at the time of the dataset processing failure.
P2 specifies the Return Code of the dataset processing failure.
P3 specifies the Feedback Code of the dataset processing failure.
System Action:
Report generation processing terminates.
User Action:
Review the displayed message and the Activity Log (/LOG) to determine the cause of the error. Ensure the dataset is allocated correctly and this region has the required read or write access to this dataset. See the chapter on Dataset Services in the NCL Control Language Reference for additional information about Return and Feedback codes. If the problem persists contact Technical Support.
Reason:
$RXSR000 has invoked $RXSU05E with an invalid stem count.
System Action:
Summary report processing ends.
User Action:
Contact Technical Support.
Reason:
The allocation of the Report output data set failed.
P1 is the dynamic allocation error information.
P2 is the dynamic allocation failure return code.
P3 is the dynamic allocation failure feedback code.
System Action:
Report Generation process stops.
User Action:
Review the allocation return and feedback code to help resolve the issue.
Reason:
A report is currently being generated by the user specified in P1 . Data set contention may occur when two users try to update the report output data set at the same time.
System Action:
Report Generation process stops.
User Action:
Try running the report at a later time.
Reason:
The specified ID in P1 is invalid.
System Action:
Report Generation process stops.
User Action:
Specify a syntactically valid PDS member name as in the ID field and re-run the report.
Reason:
The specified Member value in P1 is invalid.
System Action:
Report Generation process stops.
User Action:
Do one of the following and then re-run the report: - Specify a valid value in the Member Selection field. Member name must be in the format: Annnnnnn where nnnnnnn is the number assigned to the member during analysis. - Enter S in the Member Selection field to display a list of valid members. - Specify LAST to generate the report from the last written analysis member in the input data set.
Reason:
The specified List Analysis Members Value P1 is invalid. Valid values are:
SHORT
Data set summary information as well as procedure name are included in the report.
NO
Data set summary information is included in the report.
FULL
Data set summary information, as well as procedure names and all members in the input data set, are included in the report.
System Action:
Report Generation process stops.
User Action:
Specify a valid value and re-run the report.
Reason:
The specified Print Control Value P1 is invalid. Valid values are:
ASA
(ANSI) standard where each record is prefixed with a blank and the new page is set by writing number 1.
FF
Form Feed, this option should be used if the output data set is to be transmitted to a PC and sent to a printing device. The new page value written is EBCDIC 'FF'.
NONE
If displaying the report online, then specify NONE.
System Action:
Report Generation process stops.
User Action:
Specify a valid value and re-run the report.
Reason:
The specified Line Count value P1 is invalid. The Line Count value must be numeric and greater than 39 and less than 10000.
System Action:
Report Generation process stops.
User Action:
Specify a valid value and re-run the report.
Reason:
The specified Output Type value P1 is invalid. Valid values are:
ONLINE - displays the report online.
DSN - writes the report to an output data set.
System Action:
Report Generation process stops.
User Action:
Specify a valid value and re-run the report.
Reason:
A Print Control value other than NONE has been specified with an Output Type of ONLINE.
No Print Control value other than NONE should be specified with the Output Type set to ONLINE.
Print Control of ASA or FF should only be specified with an Output Type of DSN.
System Action:
Report Generation process stops.
User Action:
Specify a valid value and re-run the report.
Reason:
An Output Data Set value has been specified with an Output Type of ONLINE.
No Output Data Set value should be specified with the Output Type set to ONLINE.
The output Data Set should only be specified with an Output Type of DSN.
System Action:
Report Generation process stops.
User Action:
Specify a valid value and re-run the report.
Reason:
An Output Data Set value has not been specified with an Output Type of DSN.
An Output Data Set value should be specified with the Output Type set to DSN.
System Action:
Report Generation process stops.
User Action:
Specify a valid value and re-run the report.
Reason:
The specified Environment Type value P1 is invalid.
Valid values are:
NETVIEW aids in NETVIEW REXX specific analysis.
ISPF aids in ISPF REXX specified analysis.
System Action:
Analysis processing stops.
User Action:
Specify a valid value and re-run analysis.
Reason:
The specified Scan Type value P1 is invalid.
Valid values are:
REXXONLY analyze members where line 1 includes /* REXX */ .
REXXCMT analyze members where line 1 starts with /* .
YES preanalysis is performed to attempt to ignore any non-REXX.
NO no preanalysis scan is performed and all members are processed.
System Action:
Analysis processing stops.
User Action:
Specify a valid value and re-run the analysis.
Reason:
The specified value P2 in field P1 is invalid.
You must specify a member name or a list of comma delimited member names.
You can also use a search pattern of * for many characters and ? for one character.
System Action:
Analysis processing stops.
User Action:
Specify a valid value and re-run analysis.
Reason:
The specified value in P1 is invalid.
Valid values are:
YES - If specified, then the $$$SPACE member will be ignored during analysis processing and will not be displayed in the output.
NO - If NO is specified, then it is assumed that if a member called $$$SPACE exists, it is not a CA-PDSMAN member and will be included in the report.
System Action:
Analysis processing stops.
User Action:
Enter YES or NO in this field and re-run Analysis.
Reason:
The specified System Name in P1 is invalid.
System Action:
Analysis processing stops.
User Action:
Specify a syntactically valid PDS member name as in the System Name field and re-run analysis.
Reason:
The specified STC Name in P1 is invalid.
System Action:
Report Generation process stops.
User Action:
Specify a syntactically valid PDS member name as in the STC Name field and re-run analysis.
Reason:
P1 is a required field but was not specified.
System Action:
Analysis processing stops.
User Action:
Specify a valid value in P1 and re-run analysis.
Reason:
The REXX Analyzer Print Services procedure was invoked with variable $RXLine0 set to an invalid value.
Variable $RXLine* variables must be shared and $RXLine0 must be set to 0.
P1 specifies the passed value. If a null value was passed, then P1 specifies "NONE".
System Action:
Print processing terminates.
User Action:
Ensure this stem is set with a count greater than 0.
Reason:
Print processing has completed successfully.
System Action:
None.
User Action:
None.
Reason:
A request to recall the specified criteria definition ( P1 ) has failed because it was not found.
System Action:
None.
User Action:
None.
Reason:
A request to list analysis members has failed. There are no analysis members in the Analysis output data set.
System Action:
None.
User Action:
None.
Reason:
Analysis is being peformed by the user specified in P1 .
Data set contention may occur when two users try to update the same analysis output data set at the same time.
System Action:
Analysis processing terminates.
User Action:
Try running the analysis process at a later time.
Reason:
The field must conform to the dataset name rules. The full dataset name must be entered without quotes. Member name specification is not allowed.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
P1 specifies the action being performed at the time of the dataset processing failure.
P2 specifies the Return Code of the dataset processing failure.
P3 specifies the Feedback Code of the dataset processing failure.
System Action:
Report Generation processing terminates.
User Action:
Review the displayed message and the Activity Log (/LOG) to determine the cause of the error. Ensure the dataset is allocated correctly and this region has the required read or write access to this dataset. See the chapter on Dataset Services in the NCL Control Language Reference for additional information about Return and Feedback codes.
If the problem persists contact Technical Support.
Reason:
P1 specifies the number of lines built for the report. Online reporting cannot process lines in excess of 32000.
System Action:
Report Generation processing terminates.
User Action:
Use the Run Report and Save to File reporting option, or change the reporting and/or analysis criteria and re-run analysis and/or report generation.
Reason:
The Report Type specified in P1 is invalid.
System Action:
The Report Generation process stops.
User Action:
Specify Summary or Detailed. For more information about these options, see the online help.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |