|
|
|
Reason:
The Language Services external interface procedure $CALD000 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 $CALD000 terminates.
User Action:
Contact the system administrator.
Reason:
Language Services failed during request processing because an error was encountered accessing a variable table. The action being used to access the table was P1, the identifier of the 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 add, browse or update a language definition failed because procedure $CALD01P received an invalid keyword value. The keyword was
P1 and the invalid value was P2 .
System Action:
The request is rejected.
User Action:
Contact the system administrator.
Reason:
An invalid command was entered in the Command field on the Language Description panel.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Function key P1 was pressed on the Language 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:
A command was entered in the Command field on the Language Description panel that was a valid command, however, it was not allowed to be specified on that panel. The command was P1 .
System Action:
The command is rejected.
User Action:
Clear the Command field.
Reason:
A request to browse or update a language definition failed because the language definition was not defined. The code of the language definition was P1 .
System Action:
The request is rejected.
User Action:
Specify a language code previously defined and retry.
Reason:
An add language definition request was cancelled.
System Action:
None.
User Action:
None.
Reason:
An update language definition request was cancelled.
System Action:
None.
User Action:
None.
Reason:
A language definition was successfully added. The code of the language definition was P1 .
System Action:
None.
User Action:
None.
Reason:
A language definition was successfully updated. The code of the language definition was P1 .
System Action:
None.
User Action:
None.
Reason:
A value was not entered in the P1 field on the Language Description panel.
System Action:
The Language Description panel is displayed with the P1 field set in error.
User Action:
Enter a value in the P1 field and retry.
Reason:
A request to add a language definition failed because the language definition was already defined. The code of the language definition was P1 .
System Action:
The request is rejected.
User Action:
Specify a new language code and retry.
Reason:
A Panel Library List was presented but you did not select a panel library.
System Action:
None.
User Action:
Enter a panel library name, or select one from the list.
Reason:
A library name was entered in the Panel Library field on the Language Description panel that was not in the user's current panel path.
System Action:
The Language Description panel is displayed with the Panel Library field set in error.
User Action:
Enter a library name in the Panel Library field that is in your current panel path and retry. A question mark (?) can be entered in the Panel Library field to present a list of library names that are in your current panel path from which a selection can be made.
Reason:
A library name was entered in the Panel Library field on the Language Description panel that was defined as non editable.
System Action:
The Language Description panel is displayed with the Panel Library field set in error.
User Action:
Enter a library name in the Panel Library field that is defined as editable and retry. A question mark (?) can be entered in the Panel Library field to present a list of library names that are in your current panel path from which a selection can be made. For each library in the list it shows whether or not it is editable.
Reason:
A request to access a language definition was denied because the user ID
P1 was not authorized. System Support Services authority is required to be able to access language definitions.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to present a list failed because the Data Source field in the list definition was null.
System Action:
The request is rejected.
User Action:
Contact the system administrator.
Reason:
A request to present a list failed because the Data Source field in the list definition was set to an invalid value.
System Action:
The request is rejected.
User Action:
Contact the system administrator.
Reason:
A request to apply an action to an entry on the Help List failed because the action was not valid for the selected entry. The only valid action for the selected entry is F (Functions).
System Action:
The request is rejected.
User Action:
Change the action to F and retry.
Reason:
A request to present a list of primary commands for an application failed because an error was encountered allocating a variable table. The identifier of the variable table was P2 and the feedback code was P1 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to present a list of primary commands for an application failed because an error was encountered accessing a variable table. The action being used to access the table was P1 , the identifier of the 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 access the Language Definition List was denied because the user ID P1 was not authorized. System Support Services authority is required to be able to access the Language Definition List.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to add or rebuild the components for a language failed because procedure $CALD04Z received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $CALD04Z terminates.
User Action:
Contact the system administrator.
Reason:
The application components for a language were successfully rebuilt.
System Action:
None.
User Action:
None.
Reason:
A request to browse or update Common Services presentation elements failed because procedure $CALD05P received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $CALD05P terminates.
User Action:
Contact the system administrator.
Reason:
An invalid command was entered in the Command field on one of the Common Services presentation elements panels.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Function key P1 was pressed on one of the Common Services presentation elements panels 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 valid command was entered in the Command field on one of the Common Services presentation elements panels. However the command is not allowed to be specified on this panel. The command was P1 .
System Action:
The command is rejected.
User Action:
Clear the Command field.
Reason:
A request to browse or update the common services presentation elements for a language failed because the presentation elements record for common services was not defined on the database. The language code of the presentation elements to be accessed was P1 .
System Action:
The request is rejected.
User Action:
Contact the system administrator.
Reason:
An update common services presentation elements request was cancelled.
System Action:
None.
User Action:
None.
Reason:
The common services presentation elements for a language were successfully updated.
System Action:
None.
User Action:
None.
Reason:
A value was not entered in the P1 field on one of the Common Services presentation elements panels.
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:
The same value was entered in the YES and NO fields on the the Common Services General Elements panel.
System Action:
The Common Services General Elements panel is displayed with the YES and NO fields set in error.
User Action:
Change the value of either the YES or NO field and retry. The YES and NO fields must have different values.
Reason:
A request to browse or update MAI presentation elements failed because procedure $CALD06P received an invalid keyword value. The keyword was
P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $CALD06P terminates.
User Action:
Contact the system administrator.
Reason:
An invalid command was entered in the Command field on one of the MAI presentation elements panels.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Function key P1 was pressed on one of the MAI presentation elements panels 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 valid command was entered in the Command field on one of the MAI presentation elements panels. However it is not allowed to be specified on this panel. The command was P1 .
System Action:
The command is rejected.
User Action:
Clear the Command field.
Reason:
A request to browse or update the MAI presentation elements for a language failed because the presentation elements record for MAI was not defined on the database. The language code of the presentation elements to be accessed was P1 .
System Action:
The request is rejected.
User Action:
Contact the system administrator.
Reason:
An update MAI presentation elements request was cancelled.
System Action:
None.
User Action:
None.
Reason:
The MAI presentation elements for a language were successfully updated.
System Action:
None.
User Action:
None.
Reason:
A value was not entered in the P1 field on one of the MAI presentation elements panels.
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:
A request to browse or update an MAI line command definition failed because procedure $CALD07P received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $CALD07P terminates.
User Action:
Contact the system administrator.
Reason:
An invalid command was entered in the Command field on the MAI Line Command Definition panel.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Function key P1 was pressed on the MAI Line Command Definition 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 browse or update an MAI line command failed because the string definition record for the command was not defined on the database. The internal ID of the string definition was P1 .
System Action:
The request is rejected.
User Action:
Contact the system administrator.
Reason:
An update MAI line command request was cancelled.
System Action:
None.
User Action:
None.
Reason:
An MAI line command was successfully updated. The ID of the command was
P1 .
System Action:
None.
User Action:
None.
Reason:
A value was not entered in the User Description field on the MAI Line Command Definition panel.
System Action:
The MAI Line Command Definition panel is displayed with the User Description field set in error.
User Action:
Enter a value in the User Description field and retry.
Reason:
A request to add, browse, update or delete a primary command definition failed because procedure $CALD08P received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $CALD08P terminates.
User Action:
Contact the system administrator.
Reason:
An invalid command was entered in the Command field on the Primary Command Definition panel.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Function key P1 was pressed on the Primary Command Definition 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 copy, browse, update or delete a primary command failed because the string definition record for the command was not defined on the database. The internal ID of the string definition was P1 .
System Action:
The request is rejected.
User Action:
Contact the system administrator.
Reason:
An add primary command request was cancelled.
System Action:
None.
User Action:
None.
Reason:
An update primary command request was cancelled.
System Action:
None.
User Action:
None.
Reason:
A primary command was successfully added. The ID of the command was P1 .
System Action:
None.
User Action:
None.
Reason:
A primary command was successfully updated. The ID of the command was
P1 .
System Action:
None.
User Action:
None.
Reason:
A primary command was successfully deleted. The ID of the command was
P1 .
System Action:
None.
User Action:
None.
Reason:
A value was not entered in the P1 field on the Primary Command Definition panel.
System Action:
The Primary Command Definition panel is displayed with the P1 field set in error.
User Action:
Enter a value in the P1 field and retry.
Reason:
A request to delete a primary command failed because it was not eligible for deletion. The ID of the command was P1 . For a primary command to be eligible for deletion it must be an an abbreviation of another command. For example, the H command can be deleted because it is an abbreviation of the HIDE command, where as the HIDE command cannot be deleted as it is not an abbreviation of another command.
System Action:
The delete request is rejected.
User Action:
None.
Reason:
A primary command was entered in the Command ID field on the Primary Command Definition panel that was already defined. The command ID entered was P1 .
System Action:
The Primary Command Definition panel is displayed with the Command ID field set in error.
User Action:
Enter a primary command in the Command ID field that is not already defined and retry.
Reason:
An error was encountered accessing a variable table while processing an add, browse, update or delete primary command definition request. The action being used to access the table was P1 , the identifier of the table was P3 , the feedback code was P2 and the key value used was P4 .
System Action:
This error message is displayed.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
An internal ID was entered in the Internal ID field on the Primary Command Definition panel that was not previously defined. The internal ID entered was P1 .
System Action:
The Primary Command Definition panel is displayed with the Internal ID field set in error.
User Action:
Enter an internal ID previously defined and retry. A question mark (?) can be entered in the Internal ID field to present a list of previously defined internal IDs from which a selection can be made.
Reason:
Language Services procedure $CALD09Z failed during request processing because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $CALD09Z terminates.
User Action:
Contact the system administrator.
Reason:
The application P1 was successfully activated for the language code P2 .
System Action:
The application is made available in the specified language to users with a corresponding language code. Each time Language Services is initialised it will make the application available in this language.
User Action:
None.
Reason:
The application P1 was successfully inactivated for the language code
P2 . Inactive applications are not made available in the specified language when Language Services is being initialized.
System Action:
The application is disabled for the specified language.
User Action:
None.
Reason:
The application P1 was successfully initialized for the language code
P2 .
System Action:
The application is made available in the specified language to users with a corresponding language code.
User Action:
None.
Reason:
The application P1 was successfully terminated for the language code P2.
System Action:
The application is disabled for the specified language.
User Action:
None.
Reason:
A request to initialize an application for a language failed because an error was encountered allocating a variable table. The identifier of the table was P2 and the feedback code was P1 .
System Action:
The request is rejected.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to initialize or terminate an application for a language failed because an error was encountered accessing a variable table. The action being used to access the table was P1 , the identifier of the 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:
The initialization of all active applications completed with P1 errors occurring during processing.
System Action:
Errors that occurred during processing are written to the activity log.
User Action:
If errors occurred during processing refer to the activity log for further details.
Reason:
The termination of all active applications completed with P1 errors occurring during processing.
System Action:
Errors that occurred during processing are written to the activity log.
User Action:
If errors occurred during processing refer to the activity log for further details.
Reason:
A request to initialize application P1 for language code P2 failed because the application was already initialized for that language code.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to activate application P1 for language code P2 failed because the application was already active for that language code.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to inactivate application P1 for language code P2 failed because the application was already inactive for that language code.
System Action:
The request is rejected.
User Action:
None.
Reason:
Language Services procedure $CALD10D failed during request processing because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $CALD10D terminates.
User Action:
Contact the system administrator.
Reason:
A request to access a language status record failed because procedure $CALD10D was unable to open the VFS File. The return code from the &FILE statement was P1 .
System Action:
The request is rejected and procedure $CALD10D terminates.
User Action:
Interpret the feedback code using the NCL Reference.
Reason:
A request to access a language status record failed because procedure $CALD10D encountered an error accessing the VFS file. The file request that failed was P1 , the file return code was P2 , the VSAM feedback code was P3 and the key of the record was P4 .
System Action:
The request is rejected and procedure $CALD10D terminates.
User Action:
Interpret the file return code using the NCL Reference and the the feedback code using the VSAM Programmer's Guide or the VSAM Administration: Macro Instruction Reference for installations with DFP.
Reason:
A request to browse a string definition failed because procedure $CALD13P received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $CALD13P terminates.
User Action:
Contact the system administrator.
Reason:
An invalid command was entered in the Command field on the String Definition panel.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Function key P1 was pressed on the String Definition 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 browse a string definition failed because the definition was not defined on the database. The application ID of the definition was P1 , the class was P2 , the internal ID was P3 and the sequence number was P4 .
System Action:
The request is rejected.
User Action:
Specify a string definition previously defined and retry.
Reason:
A request to access the Language List was denied because the user ID
P1 was not authorized. System Support Services authority is required to be able to access the Language List.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to activate language code P1 failed because the language was already active.
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to inactivate language code P1 failed because the language was already inactive.
System Action:
The request is rejected.
User Action:
None.
Reason:
A language was successfully activated. The code of the language was P1 .
System Action:
None.
User Action:
None.
Reason:
A language was successfully inactivated. The code of the language was
P1 .
System Action:
None.
User Action:
None.
Reason:
List Handler 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 List Handler terminates.
User Action:
Contact your System Administrator.
Reason:
A request to get or display a list failed because the list definition was not defined or the information in the list cache was incorrect. The information in the list cache can become incorrect when list definitions are added to the MODS file using the Definition Utility move or copy functions. The Definition Utility does not update the list cache when it moves or copies list definitions. The list to access belongs to application ID P1 , its type is P2 , its owner's user ID if private is
P3 ,and its name is P4 .
System Action:
The request is rejected.
User Action:
If the list is defined on the MODS file, reset the list cache (option R on the CAS : List Definition Menu) and retry the request; otherwise, specify a list previously defined and retry.
Reason:
A question mark (?) was entered in the P1 field and was preceded by an invalid value. The value preceding the ? contained characters other than alphabetics (A - Z), numerics (0-9) and nationals (@, # and $).
System Action:
The panel is displayed with the P1 field set in error.
User Action:
Correct the value in the P1 field and retry.
Reason:
A request to display a list was denied because the list definition was inactive. The list to display belongs to appl ID P1 , with type
P2 , and owner's user ID (if private) of P3 ,and named P4 .
System Action:
The request is rejected.
User Action:
Change the status defined in the list definition to ACTIVE and retry.
Reason:
A request to get lists failed because there are no lists defined in the range specified.
System Action:
The request is rejected.
User Action:
None.
Reason:
List 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 request to display a list failed because the format list specified in the list definition refers to a format list. A format list must contain the list formatting information - it cannot refer to another format list. The name of the list referring to another format list is P1 . The list to display belongs to appl ID P2 , its type is P3 , its owner's user ID if private is P4 ,and its name was P5 .
System Action:
The request is rejected.
User Action:
Change the format list to contain the formatting information and retry.
Reason:
A request to display a list failed because the format list specified in the list definition is not defined. The name of the list not defined is P1 . The list to display belongs to application ID P2 , its type is P3 , its owner's user ID if private is P4 ,and its name is P5 .
System Action:
The request is rejected.
User Action:
Change the format list in the list definition to a previously defined list and retry.
Reason:
A command was entered in the Command field on the List Description or List Criteria 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:
Function key P1 was pressed on the List Description or List Criteria panel and the command assigned to it is invalid.
System Action:
The command is rejected.
User Action:
Correct the setting of the function key and retry.
Reason:
A request to file or save a list definition was rejected because a format was not entered on the List Format panel or the name of a list definition was not entered in the Format List fields on the List Criteria panel.
System Action:
The file or save request is rejected.
User Action:
Enter a format on the List Format panel or the name of a list definition in the Format List fields on the List Criteria panel, and then retry.
Reason:
A request to file or save a list definition was rejected because a format was entered on the List Format panel and the name of a list definition was entered in the Format List fields on the List Criteria panel.
System Action:
The file or save request is rejected.
User Action:
Clear the format on the List Format panel or the Format List fields on the List Criteria panel, and then retry.
Reason:
A request to file or save a list definition was rejected because the list definition entered in the Format List fields on the List Criteria panel is not defined. The list not defined belongs to application ID P1 , its type is P2 , its owner's user ID (if private) is P3 , and its name is P4 .
System Action:
The file or save request is rejected.
User Action:
Specify a list previously defined in the Format List fields on the List Criteria panel and retry.
Reason:
A request to file or save a list definition was rejected because data was entered on the List Entry Line Presentation Attributes panel and the name of a list definition was entered in the Format List fields on the List Criteria panel.
System Action:
The file or save request is rejected.
User Action:
Clear the fields on the List Entry Line Presentation Attributes panel or the Format List fields on the List Criteria panel and retry.
Reason:
The validation exit $CALH12X for the List Description and List Criteria panel received an unknown field name from procedure $CAGP000. The name of the field is P1 .
System Action:
Procedure $CALH12X terminates.
User Action:
Contact your System Administrator.
Reason:
An invalid value was entered in the P1 field on the List Description or List Criteria panel.
System Action:
The panel is displayed with the P1 field set in error.
User Action:
Enter PUBLIC or PRIVATE in the P1 field and retry. The first two characters need to be entered only.
Reason:
P3 was entered in the P2 field on the List Description or List Criteria panel and a value was entered in the P1 field.
System Action:
The 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 list name was entered in the List Name field on the List Description or List Criteria panel that was previously defined. The list name entered is P1 and it is a public list.
System Action:
The panel is displayed with the List Name field set in error.
User Action:
Enter a list name not previously defined and retry.
Reason:
A list name was entered in the List Name field on the List Description List Criteria panel that was previously defined. The list name entered is P1 and it is a private list owned by user ID P2 .
System Action:
The panel is displayed with the List Name field set in error.
User Action:
Enter a list name not previously defined and retry.
Reason:
An invalid value was entered in the P1 field on the List Description panel.
System Action:
The List Description panel is displayed with the P1 field set in error.
User Action:
Enter a value in the range 1 to P2 in the P1 field and retry.
Reason:
P3 was entered in the P2 field on the List Criteria panel and a value was not entered in the P1 field.
System Action:
The List Criteria 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 List Criteria panel and a value was entered in the P1 field.
System Action:
The List Criteria 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 List Description panel.
System Action:
The List Description panel is displayed with the P1 field set in error.
User Action:
Enter ACTIVE or INACTIVE in the P1 field and retry. The first character needs to be entered only.
Reason:
FREEFORM was entered in the P1 field on the List Criteria panel and a value was also entered in the P2 field.
System Action:
The List Criteria 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 not entered in the P2 field on the List Entry Line Presentation Attributes panel and a value was entered in the P1 field.
System Action:
The List Entry Line Presentation Attributes panel is displayed with the P1 field set in error.
User Action:
Enter a value in the P2 field or clear the P1 field and retry.
Reason:
P3 was entered in the P2 field on the List Entry Line Presentation Attributes panel and a value was not entered in the P1 field.
System Action:
The List Entry Line Presentation Attributes panel is displayed with the P1 field set in error.
User Action:
Enter a value in the P1 field or clear the P2 field and retry.
Reason:
A list definition was successfully added, updated, or deleted. The name of the list definition is P1 and it is a public list. The action successfully performed was P2 .
System Action:
None.
User Action:
None.
Reason:
A list definition was successfully added, updated, or deleted. The name of the list definition is P1 and it is a private list owned by user ID
P2 . The action successfully performed was P3 .
System Action:
None.
User Action:
None.
Reason:
A request to add a list definition failed because the list definition is already defined. The name of the list is P1 and it is a public list.
System Action:
The request is rejected.
User Action:
Specify a list name not previously defined and retry.
Reason:
A request to add a list definition failed because the list definition is already defined. The name of the list is P1 and it is a private list owned by user ID P2 .
System Action:
The request is rejected.
User Action:
Specify a list name not previously defined and retry.
Reason:
A request to browse, update, delete, or copy a list definition failed because the list definition is not defined. The name of the list is P1 and it is a public list.
System Action:
The request is rejected.
User Action:
Specify a list name previously defined and retry.
Reason:
A request to browse, update, delete, or copy a list definition failed because the list definition is not defined. The name of the list is
P1 and it is a private list owned by user ID P2 .
System Action:
The request is rejected.
User Action:
Specify a list name previously defined and retry.
Reason:
A comment line was entered in format line P1 that was already specified. The invalid comment line was for a P2 list.
System Action:
The List Format panel is redisplayed.
User Action:
Change line P1 so that it is not a comment line for a P2 list and retry.
Reason:
A heading was entered that consisted of more than 10 lines. The first line of the heading is line P1 of the format.
System Action:
The List Format panel is redisplayed.
User Action:
Change the heading to be from 1- to 10-lines and retry.
Reason:
An invalid Entry Line Field name was entered in format line P2 starting at column P1 . The Entry Line Field name entered was not 1- to 12- alphabetic (A - Z), numeric (0-9) and/or national (@, # and $) characters starting with an alphabetic or national character.
System Action:
The List Format panel is redisplayed.
User Action:
Change the name of the Entry Line Field to be 1- to 12- alphanumeric and/or national characters starting with an alphabetic or national character and retry.
Reason:
An invalid Entry Line Field name was entered in format line P3 starting at column P2 . The Entry Line Field name entered is a reserved NCL keyword. The name of the Entry Line Field is P1 .
System Action:
The List Format panel is redisplayed.
User Action:
Change the name of the Entry Line Field to a name that is not a reserved NCL keyword and retry.
Reason:
The format for a list definition was entered that consists of more than 10 screen formats.
System Action:
The List Format panel is redisplayed.
User Action:
Change the format to consist of 1- to 10- screen formats and retry.
Reason:
A request to save a list definition was rejected because a format was entered on the List Format panel or the name of a list definition was entered in the Format List fields on the List Criteria panel.
System Action:
The save request is rejected.
User Action:
Enter a format on the List Format panel or the name of a list definition in the Format List fields on the List Criteria panel, and then retry.
Reason:
A request to save a list definition was rejected because a format was entered on the List Format panel and the name of a list definition was entered in the Format List fields on the List Criteria panel.
System Action:
The save request is rejected.
User Action:
Clear the format on the List Format panel or the Format List fields on the List Criteria panel, and then retry.
Reason:
A screen format was entered that did not contain at least one heading line. The number of the screen format is P1 and the format line before which the the heading must be inserted is P2 .
System Action:
The List Format panel is redisplayed.
User Action:
Change screen format P1 to include at least one heading line by inserting a heading before format line P2 and retry.
Reason:
A screen format was entered that did not contain an entry line. The number of the screen format is P1 and the format line that did not contain an entry line is P2 .
System Action:
The List Format panel is redisplayed.
User Action:
Change screen format P1 to include an entry line at format line P2 and retry.
Reason:
The format for a list definition was entered that consisted of a comment line and no screen format. At least one screen format must be entered when a comment line is entered.
System Action:
The List Format panel is redisplayed.
User Action:
Change the format to include at least one screen format and retry.
Reason:
A request to file or save a list definition was rejected because data was entered on the List Entry Line Presentation Attributes panel and the name of a list definition was entered in the Format List fields on the List Criteria panel.
System Action:
The file or save request is rejected.
User Action:
Clear the fields on the List Entry Line Presentation Attributes panel or the Format List fields on the List Criteria panel, and then retry.
Reason:
A command was entered in the Command field on the List Entry Line Fields 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:
An invalid attribute ID was entered in an Attribute ID field on the List Entry Line Fields panel. The attribute ID entered was a reserved NCL keyword. The ID of the attribute is P1 .
System Action:
The List Entry Line Fields panel is displayed with the Attribute ID field set in error.
User Action:
Change the ID of the attribute to an ID that is not a reserved NCL keyword and retry.
Reason:
An invalid attribute ID was entered in an Attribute ID field on the List Entry Line Fields panel. The attribute ID entered was not 1- to 12- alphabetic (A - Z), numeric (0-9) and/or national (@, # and $) characters starting with an alphabetic or national character.
System Action:
The List Entry Line Fields panel is displayed with the Attribute ID field set in error.
User Action:
Change the ID of the attribute to be 1 to 12 alphanumeric and/or national characters starting with an alphabetic or national character and retry.
Reason:
Function key P1 was pressed on the List Entry Line Fields panel and the command assigned to it is invalid.
System Action:
The command is rejected.
User Action:
Correct the setting of the function key and retry.
Reason:
A request to save a list definition was rejected because a format was entered on the List Format panel or the name of a list definition was entered in the Format List fields on the List Criteria panel.
System Action:
The save request is rejected.
User Action:
Enter a format on the List Format panel or the name of a list definition in the Format List fields on the List Criteria panel, and then retry.
Reason:
A request to save a list definition was rejected because a format was entered on the List Format panel and the name of a list definition was entered in the Format List fields on the List Criteria panel.
System Action:
The save request is rejected.
User Action:
Clear the format on the List Format panel or the Format List fields on the List Criteria panel, and then retry.
Reason:
A request to file or save a list definition was rejected because data was entered on the List Entry Line Presentation Attributes panel and the name of a list definition was entered in the Format List fields on the List Criteria panel.
System Action:
The file or save request is rejected.
User Action:
Clear the fields on the List Entry Line Presentation Attributes panel or the Format List fields on the List Criteria panel, and then retry.
Reason:
A request to present a List list failed because there are no lists defined in the range specified.
System Action:
The request is rejected.
User Action:
None.
Reason:
The selection of a list from the List list failed because the list was deleted by another user since the List list was displayed. The name of the list selected is P1 .
System Action:
The selection of the list is rejected.
User Action:
None.
Reason:
A request to display a list failed because procedure $CALH20L received an unknown call type in variable &$SLCALLTYPE from procedure $CASL000. The unknown call type is P1 .
System Action:
Procedure $CALH20L terminates and the request is rejected
User Action:
Contact your System Administrator.
Reason:
A request to display a list failed because the list exit or service procedure for the list was not found in the procedure library. The type of procedure not found is P1 and the name of the procedure is P2 .
System Action:
The request is rejected.
User Action:
Correct the list exit or service procedure name in the list definition or create the procedure, and then retry.
Reason:
A request to display a list failed because the list exit or service procedure returned an invalid return code. The type of procedure is
P1 , the name of the procedure is P2 , and the invalid return code is
P3 .
System Action:
The request is rejected.
User Action:
Correct the setting of the return code by the list exit or service procedure and retry.
Reason:
A request to display a list failed because the list exit or service procedure returned a return code that was not valid for the option set in variable &$LHOPT. The type of procedure is P1 , the value of variable &$LHOPT is P2 , and the name of the procedure is P3 .
System Action:
The request is rejected.
User Action:
Correct the setting of the return code by the list exit or service procedure and retry.
Reason:
A request to display a list failed because there were no entries to display.
System Action:
None.
User Action:
None.
Reason:
A list was displayed and an entry was not selected.
System Action:
None.
User Action:
None.
Reason:
A command was entered in the Command field that is a valid command; however, the command parameter is invalid.
System Action:
The command is rejected.
User Action:
Correct the command parameter and retry.
Reason:
List Handler called the service procedure for list to process an option; however, the option is not supported by the service procedure. The option to process is P1 .
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to display a list failed because the service procedure did not set variable &$LHACTIONS to the available actions. The name of the service procedure is P1 .
System Action:
The request is rejected.
User Action:
If the list is to be presented as an action list, modify the service procedure to set variable &$LHACTIONS and retry.
Reason:
During a request to display a list, the service procedure or list exit set returned code 8 and did not set variable &SYSMSG to an error message. The type of procedure is P1 and the name of the procedure is P2 .
System Action:
None.
User Action:
Correct the list exit or service procedure to set &SYSMSG to an error message and retry.
Reason:
An APPC receive error starting the conversation that sends events to the workstation event manager.
System Action:
SOLVE:Operations OV/NV event flow terminates.
User Action:
Check installation details for SOLVE:Operations OV/NV client on the workstation and also on the product region server.
Reason:
An APPC SEND error occurred while sending events to the workstation event manager.
System Action:
SOLVE:OPS OV/NV event flow terminates.
User Action:
Check that workstation is active. Check that link is still active. Check Installation of SOLVE:Ops OV/NV on workstation and on the SOLVE server region.
Reason:
An error occurred while BER encoding a SOLVE:Ops OV/NV event into an SNMP trap for sending to the workstation event manager.
System Action:
Skips this event without sending it and waits for the next.
User Action:
Contact systems programmer. Check installation, including ASN1 maps are compiled on this version of Management Services.
Reason:
An error occured when a procedure in SOLVE:Ops OV/NV tried to profile itself for a certain event type.
System Action:
SOLVE:Ops OV/NV server terminates.
User Action:
Check SOLVE:Ops OV/NV userid Event Distribution Services (EDS) authority. Contact technical support.
Reason:
The SOLVE:Ops OV/NV SNMP trap flow is terminating because it received a termination event, probably as the result of a terminate command.
System Action:
SOLVE:Ops OV/NV server terminates completely.
User Action:
Re-start SOLVE:Ops OV/NV from workstation if required.
Reason:
The SOLVE:Operatins OV/NV process that receives events and sends them as traps to the workstation has reached its queue limit, and events received are discarded.
The NMIQLIM parameter controls the maximum size of the event queue. The default for this is 32767.
System Action:
Events are discarded until queue size drops.
User Action:
Investigate why so many events are queued.
Reason:
An error occurred trying to BER encode an event in to an SNMP trap.
P1 is the ZMDORC value,
P2 is the ZMDOFDBK value.
System Action:
SOLVE:Ops OV/NV processing terminates.
User Action:
Contact technical support.
Reason:
An error occurred trying to start the link monitor in SOLVE:Ops OV/NV.
P1 is the return code from the start.
P2 is any error message returned from the start.
System Action:
SOLVE:Ops OV/NV processing terminates.
User Action:
Contact technical support.
Reason:
SOLVE:Ops OV/NV has been started from the workstation, and the SNMP trap sender has been activated.
P1 is the host name of the workstation to which the events are sent.
System Action:
SOLVE:Ops OV/NV should receive events as they arise.
User Action:
None. (Informational)
Reason:
A workstation peer system running SOLVE:Ops OV/NV attempted to open an SNMP trap flow from this SOLVE:Operations region, however this region is not configured to use SOLVE:Ops OV/NV, so the connection was rejected. SOLVE:Ops OV/NV is configured by setting the SOLVE:Operations $RM WSPEER Customisation parameter group.
System Action:
The SOLVE:Operations component of SOLVE:Ops OV/NV is not started.
User Action:
To configure SOLVE:Operations to connect to a SOLVE:Ops OV/NV system, update the $RM WSPEER Customisation parameter group in SOLVE:Operations.
Reason:
A Socket error occurred while trying to start the flow of SNMP traps from SOLVE:Operations to SOLVE:Ops OV/NV running on a workstation.
System Action:
The SOLVE:Operations component of SOLVE:Ops OV/NV is not started.
User Action:
Check that the $RM WSPEER parameter group in SOLVE:Operations has been configured correctly. Check that the TCP/IP port numbers are not in use by any other applications.
Reason:
An error occured when the alert monitor was invoked to create an agent to receive alerts that are to be sent to SOLVE:Operations for OpenView and NetView. P1 contains more details of the error.
System Action:
The SOLVE:Operations for OpenView and NetView server terminates.
User Action:
Contact your support representative.
Reason:
The SOLVE:Link event monitor terminated because it received an invalid startup parameter from the workstation P1 is the workstation host name (if known) P2 is the parameter that was in error P3 is the invalid parameter value that was supplied
System Action:
The SOLVE:Link event monitor process terminates.
User Action:
Make sure the version of SOLVE:Link on the workstation is compatible with the version of Management Services.
Reason:
A failed connection to a workstation has resulted in P2 messages being lost. The workstation's sysid is P1.
System Action:
Message pooling continues.
User Action:
Check the log for additional messages that indicate the reason that the link to the workstation failed and correct the problem.
Reason:
An attempt to recover a link to a workstation failed. The initialization string could not be queued to the existing server. The return code was P1 and the system ID of the workstation was P2.
System Action:
Connection terminates.
User Action:
Check the log for additional messages that may indicate a reason for the error.
Reason:
This is a general trace message. P1 contains variable information used to debug problems.
System Action:
None.
User Action:
Send all of these messages to you support representative.
Reason:
While waiting for a workstation to reconnect P1 messages that were being pooled were lost due to pool table overflow. The connection failure was between the times stated by P2 and P3.
System Action:
Processing continues.
User Action:
None.
Reason:
This message is written to the MVS console in response to a LOGMSG request from a SOLVE:Link workstation.
System Action:
None.
User Action:
None.
Reason:
Unexpected data was received on the SOLVE:Link host command APPC transaction.
P1 is what was received.
P2 is what was expected to be received.
System Action:
The host command transaction ends.
User Action:
Contact your local support representative.
Reason:
An APPC error occurred when sending data to a SOLVE:Link workstation. P1 is the RETCODE value after the APPC SEND. P2 is the ZFDBK value after the APPC SEND.
System Action:
The host command transaction ends.
User Action:
Retry. Check that all SOLVE:Link links, PU's and LU's are active.
Reason:
No response was received within the expected period for a command submitted from a SOLVE:Link workstation.
System Action:
The transaction ends. The command may not have completed.
User Action:
Retry the command. The timeout may have been caused by slow system response times. Check that the command is intended to be a short running command. This command facility is not useful for starting long running background procedures, or commands that display panels. If the problem recurs, increase the timeout period specified in the &&000$RMCMDWS and/or &&000$RMCMDWR system variables. If the region is licensed for SOLVE:Operations, these values should be changed in the WSPEER parameter group. Otherwise, set them in the region's initialization procedure.
Reason:
The SOLVE:Link Data Request listener (which accepts requests from SOLVE:Link workstations to initiate event flow) either could not be initialized, or failed. It will automatically attempt to restart in the specified number of seconds. P1 is the return code from the &SOCKET verb P2 is the feedback code from the &SOCKET verb P3 is the &SOCKET verb that failed
System Action:
The Data Request listener will not accept data flow connection requests from SOLVE:Link workstations. It will automatically initialize when the problem has been rectified.
User Action:
Determine the cause of the error (it may be that the TCP/IP stack has been stopped) and take corrective action. Once the problem has been rectified the Data Request listener will automatically restart.
Reason:
The SOLVE:Link Data Request listener (which accepts requests from SOLVE:Link workstations to initiate event flow) could not be initialized because the TCP/IP stack is not active.
System Action:
The Data Request listener will not accept data flow connection requests from SOLVE:Link workstations. It will automatically initialize when the TCP/IP stack is started.
User Action:
Start the TCP/IP stack.
Reason:
The SOLVE:Link Data Request listener (which accepts requests from SOLVE:Link workstations to initiate event flow) is now active.
System Action:
Requests from SOLVE:Link workstations to initiate data flow will now be processed.
User Action:
None.
Reason:
The SOLVE:Link Data Request listener (which accepts requests from SOLVE:Link workstations to initiate event flow) either could not be initialized, or failed. It will automatically attempt to restart in the specified number of seconds.
System Action:
The Data Request listener will automatically attempt to restart in the specified number of seconds.
User Action:
Review the preceding error message (which has a prefix of LI15) to determine why the error occured and take appropriate action.
Reason:
The SOLVE:Link Data Request listener (which accepts requests from SOLVE:Link workstations to initiate event flow) could not be initialized because the nominated port is already in use by another procedure or application.
System Action:
The system will not accept data flow connection requests from SOLVE:Link workstations until the problem is corrected.
User Action:
Find the procedure or application that is using the port and free it, or change the data port number used by the SOLVE:Link agent.
Reason:
A command from a SOLVE:Link workstation could not be processed because a TCP/IP error occurred.
System Action:
The command is not processed.
User Action:
Check that the TCP/IP stack is active using the SHOW TCPIP command. Determine the cause of the error from the return and feedback codes.
Reason:
No response was returned from the command processor when a command from a SOLVE:Link workstation was submitted. This probably indicates that the command processor failed.
System Action:
The command may not have been processed.
User Action:
Check the SOLVE activity log for error messages, particularly from process $LITP09Z OR $LISG19T.
Reason:
A command request from a SOLVE:Link workstation was rejected because the userid was not defined in the security database.
System Action:
The command is not processed.
User Action:
Resubmit the command with a valid userid.
Reason:
A command request from a SOLVE:Link workstation was rejected because the supplied password or new password was longer than the maximum allowed length.
System Action:
The command is not processed.
User Action:
Resubmit the command, supplying valid password(s).
Reason:
NO RESPONSE AFTER SOCKET SELECT
System Action:
System will work on next available socket
User Action:
no
Reason:
A logon request from a SOVLE:Link workstation was refused. P1 is the reason for not allowing the logon.
System Action:
The command is not processed.
User Action:
Determine the cause of the problem from the error message, correct and retry.
Reason:
A command request from a SOLVE:Link workstation was rejected because the user's password has expired.
System Action:
The command is not processed.
User Action:
Either resubmit the request supplying a new password, or directly log on to the SOLVE region and follow the prompts to change the password.
Reason:
A command request from a SOLVE:Link workstation was rejected because the user is logging on for the first time and did not supplu a new password.
System Action:
The command is not processed.
User Action:
Either resubmit the command supplying a new password, or directly log on to the SOLVE region and follow the prompts to change the password.
Reason:
A command from a SOLVE:Link workstation was not processed because an invalid password was supplied.
System Action:
The command is rejected.
User Action:
Resubmit the command with the correct password.
Reason:
A command request from a SOLVE:Link workstation was rejected because the userid was not defined in the security database.
System Action:
The command is not processed.
User Action:
Resubmit the command with a valid userid.
Reason:
A command request from a SOLVE:Link workstation was rejected because user verification failed.
System Action:
The command is not processed.
User Action:
Contact the system administrator. Their may be a problem with the security system.
Reason:
A command request from a SOLVE:Link workstation was rejected because the external security system rejected the request.
System Action:
The command is not processed.
User Action:
Contact your systems administrator.
Reason:
A logon request from a SOLVE:Link or SOLVE:Operations for OV/NV/ITO workstation workstation could not be processed because the security level used is not supported on this system.
System Action:
The command is not processed.
User Action:
Either change the security level used on the SOLVE:Link or SOLVE:Operations for OV/NV/ITO workstation, or apply patches (if available) to the current region so that it supports the security level that is being used.
Reason:
A logon request from a SOLVE:Link or SOLVE:Operations for OV/NV/ITO workstation was flagged as an encrypted string, but was not in the expected format.
System Action:
The command is not processed.
User Action:
Contact your local support representative.
Reason:
An invalid keyword parameter value was passed. The keyword was P1 and the invalid value was P2.
System Action:
Processing terminates.
User Action:
Specify a valid value.
Reason:
In order to activate the SOLVE:Link agent procedures, the Workstation Peer User ID must be defined. P1 is the Workstation Peer User ID and it does not exist. It could not be defined automatically because you are not authorized for UAMS maintenance access.
System Action:
Processing terminates.
User Action:
From a userid that has UAMS Maintenance authority, invoke the following procedure:
$LICALL ACTION=DEFUSER
Reason:
An attempt to add a user or group definition to the UAMS database failed. P1 is the ID of the user and P2 is the message set by the &SECCALL verb.
System Action:
The UAMS record is not added and processing terminates.
User Action:
Determine the cause of the error from the &SECCALL message, correct, and retry the request.
Reason:
The request action P1 successfully completed.
System Action:
None.
User Action:
None.
Reason:
The agent process which accepts command or event flow requests from a SOLVE:Link workstation has been started. P1 is the type of listener (DATA or CONTROL) P2 is the port number used by the listener
System Action:
None.
User Action:
None.
Reason:
During initialization of the SOLVE:Link agent, an APPC command failed.
P1 is the APPC verb that failed.
P2 is the error message returned from the APPC command.
P3 is the name of the host for which the link was being defined.
System Action:
An APPC link is not established for the host. Processing continues.
User Action:
Determine the cause of the error from the APPC error message, correct and retry.
Reason:
APPC links were successfully defined for communication with the SOLVE:Link workstation P1 is the name of the SOLVE:Link workstation
P2 is the control (command) LU P3 is the data (event flow) LU
System Action:
None.
User Action:
None.
Reason:
An invalid parameter set was passed for a SOLVE:Link APPC connection. If one of HOST, CNTLLU and DATALU is supplied, the other two must also be supplied.
System Action:
Processing terminates.
User Action:
Correct the command and retry.
Reason:
An attempt by the Log Browse utility to access the file P1 failed.
System Action:
Log Browse terminates.
User Action:
Ensure the file id is correctly specified. If necessary issue a SHOW UDB command to determine the file id's that are available.
Reason:
The Log Browse utility attempted to access a log file. The data was not in the expected format. P1 is the identifier of the file being accessed.
System Action:
Log Browse terminates.
User Action:
Check that the file accessed has been used as a log file.
Reason:
A command entered on the Log Browse panel is not recognized.
System Action:
None.
User Action:
Check the spelling of the command. If necessary use the Help command, or press F1, to view the application help.
Reason:
A / command was entered without any operands.
System Action:
None.
User Action:
Reenter the / command with a SOLVE command as the operand.
Reason:
A SOLVE command has been processed.
System Action:
None.
User Action:
None.
Reason:
A request to access a specific date failed because the format of the data does not match one of the following: YY.DDD DD/MM/YY or MM/DD/YY (if US language code) YY/MM/DD YYMMDD
System Action:
None.
User Action:
Correct the date entered to match one of the supported formats.
Reason:
A label command has specified an invalid label name. A label must be 1 to 8 characters.
System Action:
None.
User Action:
Correct the label entered to be 1 to 8 characters.
Reason:
A SCANMAX command has specified an invalid value. The limit must be a number in the range 1 to 5000.
System Action:
None.
User Action:
Correct the limit entered to be a number in the range 1 to 5000.
Reason:
A SCANMAX command has been accepted. P1 is now the limit on the number of log records that will be searched for a Find request.
System Action:
None.
User Action:
None.
Reason:
An ATTR command has been used to activate message level coloring and highlighting.
System Action:
Log messages with color and highlighting will be displayed with those attributes.
User Action:
Use the ATTR command again to reset message level attributes.
Reason:
An ATTR command has been used to deactivate message level coloring and highlighting.
System Action:
Log messages are displayed without color and highlighting.
User Action:
Use the ATTR command again to set message level attributes.
Reason:
A scroll value entered is not supported.
System Action:
None.
User Action:
Correct the scroll amount entered.
Reason:
A request to access a specific time failed because the format of the data does not match one of the following: HH HH.MM HH.MM.SS
System Action:
None.
User Action:
Correct the time entered to match one of the supported formats.
Reason:
A LABEL command has not specified a label name.
System Action:
None.
User Action:
Correct the label command to specify a label name. For example '.HERE' or 'LABEL HERE'.
Reason:
A FORMAT command has specified an unknown format name.
System Action:
The format is unchanged.
User Action:
Correct the Format command to specify one of NORMAL, SHORT, LONG, or SOURCE.
Reason:
A FIND command has not specified a search argument.
System Action:
None.
User Action:
Correct the Find command to specify a search argument.
Reason:
A LOCATE command has not specified a label name.
System Action:
None.
User Action:
Correct the LOCATE command to specify a label name. For example, 'LOCATE THERE'.
Reason:
A Locate command has specified a label name that is not defined.
System Action:
None.
User Action:
Check that the label name is spelt correctly and matches a defined label.
Reason:
A Label has been defined for the line indicated by the cursor or the line displayed at the top of the screen.
System Action:
None.
User Action:
Use the Locate P1 command to reposition to this line.
Reason:
A Label has been defined for the line indicated by the cursor or the line displayed at the top of the screen. This definition replaces an earlier position for the label.
System Action:
None.
User Action:
Use the Locate P1 command to reposition to this line.
Reason:
A request to display a remote Activity Log has failed because the domain ID specified ( P1 ) is unknown. The value must represent either a SOLVE Domain ID or an INMC Link Name that is known to this SOLVE region.
System Action:
Log Browse terminates.
User Action:
Ensure the domain ID is correctly specified. If necessary issue a SHOW DOMAINS or SHOW LINKS command to verify IDs that are available.
Reason:
A request to display a remote Activity Log has failed because the domain ID specified ( P1 ) does not support remote log browse. Only SOLVE systems running Management Services V3.3 and above provide this facility.
System Action:
Log Browse terminates.
User Action:
None.
Reason:
A request to display a remote Activity Log has failed because the domain ID specified ( P1 ) is not contactable due to one of the following reasons:
- the INMC link is not active
- the APPC link is not defined
System Action:
Log Browse terminates.
User Action:
Check the status of the INMC link by using the SHOW LINKS TYPE=INMC command. If the requested domain is not active, activate it. If it is active, check that APPC links have been defined on the remote system. Log on to the remote system and issue the SHOW LINKS TYPE=APPC command and verify that there is a link name defined, perhaps using a generic LUMASK, that supports a link from the local SOLVE System.
Reason:
No domain name was selected from the list of domains presented.
System Action:
Log Browse terminates.
User Action:
If a display was required, ensure that you select one of the domains in the list. To select the local log select the first item.
Reason:
The Logging procedure is not running. The reason why it is not running is given in P1 . The following reasons are possible:
FILE_OPEN_ERROR - Logproc experienced an error while trying to open the log file.
FILE_ADD_ERROR - Logproc experienced an error while trying to add a record to the log file. The log file may be full.
WRONG_FILE_FORMAT - Logproc determined that the contents of the log file are not in the correct format for log records.
NONE_GIVEN - No reason is available for why Logproc is not running. It may never have been started or it may have been deliberately flushed.
System Action:
Log Browse continues if possible but no new log records will be written.
User Action:
If you require Logproc to be running. Ensure that the logging file is is of the correct format and available for use. Then start Logproc by issuing the 'SYSPARM LOGPROC=your_logproc_name' command.
Reason:
You entered a number to increment/decrement the current date. The resulting date is out of the date processor's range.
System Action:
Date request is ignored.
User Action:
Use a smaller number to increment/decrement the current date.
Reason:
You entered $LOG in a processing environment that does not have an associated real terminal window (for example, the system background environment, LU 1 Telnet, or ROF session).
System Action:
The command cannot be serviced.
User Action:
Issue the $LOG command in an environment with a terminal window.
Reason:
An invalid search limit was specified. The value must be a numeric value in the range of 500 to 9999.
System Action:
Log search processing terminates.
User Action:
Correct the limit entered to be a number in the range 500 to 9999.
Reason:
An invalid scroll amount was specified. The value must be a numeric value in the range of 1 to 999.
System Action:
Log search processing terminates.
User Action:
Correct the amount entered to be a number in the range 1 to 999.
Reason:
You attempted to browse the Activity Log from an environment that does not have an associated real terminal window (for example, the system background environment, LU 1 Telnet, or ROF session).
System Action:
The request cannot be processed.
User Action:
Issue the $LOG command in an environment with a terminal window.
Reason:
A command entered on the Log Browse panel is not recognized. Valid commands from the Activity Log display include: Specific log browse commands such as find. date, time, print and so on CAS commands and menu shortcuts Any NetMaster command
System Action:
None.
User Action:
Check the spelling of the command. See the log browse online help for a description of log browse commands.
Reason:
The data requested by a log browse DATE or TIME command is outside the range of data stored in all activity log files.
System Action:
None.
User Action:
The command 'DATE ?' or 'D ?' will display the range of dates/times contained in the allocated activity log files.
Reason:
The parameter entered for the Log Browse DATE command was not recognized. Valid DATE command parameters are as follows:
D D ? D absolute date D +N D -N
System Action:
None.
User Action:
Correct the parameter and retry the command.
Reason:
The parameter entered for the Log Browse TIME command was either omitted or invalid. A parameter is mandatory for the TIME command. Valid TIME command parameters are as follows:
T HH T HH.MM T HH.MM.SS T HH.MM.SS.hh
T +HH T +HH.MM or T+.MM T +HH.MM.SS or T+.MM.SS or T+..SS T +HH.MM.SS.hh or T+.MM.SS.hh or T+...hh
T -HH T -HH.MM or T-.MM T -HH.MM.SS or T-.MM.SS or T-..SS T -HH.MM.SS.hh or T- .MM.SS.hh or T-...hh
System Action:
None.
User Action:
Correct the parameter and retry the command.
Reason:
This message appears when the Activity Log lines displayed on this panel include lines that occurred after a backwards local time offset change on this LPAR.
Activity Log lines always appear with their local system time. When a backward time change occurs, such as for Daylight Saving, the local system time moves back; however, log records are already written for this time interval.
To distinguish the log records that occurred during the second time through the same local time interval, a + is displayed after the local system time.
Example
02.50.06 Message ...
Records written during the second 2:00 a.m. to 3:00 a.m. period after the backwards time change display with a + character, for example,
02.50.06+Message ...
System Action:
None.
User Action:
None.
To see when local time offset changes were detected on this LPAR, look for log messages N02H10 to N02H13.
Reason:
This message reports the status of a Label-related Log Browse command.
Labels must have a valid name, from 1 through 12 characters long. The first character of the name must be alphabetic, or one of the characters @, #, or $.
Label names are not case sensitive. If a Label Name already exists, it is replaced,
Label names are valid only for the current Log Browse instance - they are not retained once you exit Log Browse.
System Action:
None.
User Action:
If necessary, correct the invalid label name and retry the operation.
Reason:
A scroll attempt was made, but there is either no or no more applicable log data for the displayed date.
If a Region, Origin or Text filter is active, this message indicates that no (more) log data matching the filter exists for this date. There may be more non-matching lines of log data beyond the times shown.
System Action:
None.
User Action:
None.
Reason:
A Region/Origin/Text/Color command has an invalid filter criteria, or an hlRegion/hlOrigin/hlText command has an invalid highlight criteria.
The correct command format is:
REGION <region name>
region name is a valid user ID
ORIGIN <origin name>
origin name is a valid terminal ID
TEXT <text string>
text string contains no blank characters
COLOR <color initial>
1st letter of color name: r p y g b t w
r(ed) p(ink) y(ellow) g(reen) b(lue) t(urquoise) w(hite) For example, color r displays all red lines.
HLREGION <region name>
region name is a valid user ID
HLORIGIN <origin name>
origin name is a valid terminal ID
HLTEXT <text string>
text string contains no blank characters
You can enter the commands without parameters to remove all filtering or highlighting on that Criteria. Any two or all three attributes can be filtered or highlighted at once - this is cumulative (that is, matches region AND origin AND text).
System Action:
None.
User Action:
None.
Reason:
An ATTR command has been used to enable or disable message level coloring and highlighting.
System Action:
When enabled, log messages with special display attributes are shown as colored and/or highlighted. When disabled, all log messages are shown in low intensity monocolour.
User Action:
Use the ATTR command again to reverse the message level attributes.
Reason:
A NetMaster command has been issued on domain P1
System Action:
None.
User Action:
None.
Reason:
A log browse 'Find' command has been attempted but the parameters were omitted or invalid. Valid command formats are:
Find repeats any last Find command Find * repeats any last Find command
Find xxx yyy zzz find next occurrence of xxx yyy zzz
Find a a º b b º c c find next line containing aaa or bbb or ccc Find a a + b b + c c find next line containing aaa and bbb and ccc
º and + cannot be mixed in the same operation.
arguments are case-insensitive & space-sensitive
By default, scanning starts forward from the current cursor position. The keywords Prev, First or Last may be added to the command.
Prev causes search to be performed backwards First finds first occurrence of the string for the displayed date Last finds last occurrence of the string for the displayed date
All find operations are performed only within the displayed date. To search another day for the same thing, use the D command then the repeat Find command.
The Findmax limit controls the number of lines that are searched. Find terminates when the Findmax limit is reached, or the day changes. Use the Findmax or Scanmax commands to change the search line limit.
If Text, Region or Origin filters are active, only lines that pass the filter condition(s) will go on to be searched for the search string(s).
System Action:
None.
User Action:
None.
Reason:
A log browse 'Find' command was requested but could not be performed because of the error condition indicated. These are usually file errors on the activity log VSAM files.
System Action:
None.
User Action:
Check the log for any additional messages describing the error. For file errors, correct the condition and retry the find request.
Reason:
This message indicates the results of a completed FIND command.
System Action:
None.
User Action:
None.
Reason:
This message indicates the results of a SCANMAX or FINDMAX command.
SCANMAX (or FINDMAX or MAX) sets the number of lines to be searched by a Find command. The limit can be between 500 and 10,000 inclusive. The default value is set at startup by your System Administrator.
Note: If text, region or origin filtering is active, SCANMAX continues to control the number of lines read from the log file(s), filtered, and searched. In other words, SCANMAX 600 does not mean that 600 lines matching the filters are searched - it means that 600 lines are filtered and searched.
System Action:
None.
User Action:
None.
Reason:
A Reset command has been completed.
The following Log Browse settings are restored to their default values:
Format/Mode = NORMAL, column offset 1
Repeat Find parameters reset to none
All Label definitions reset
PF12 Command Stack reset
Text/Region/Origin filters reset to none and data refreshed
Highlight Text/Region/Origin reset to HLREGION=&USERID
Message Attribute Display = ON
Scanmax/Findmax reset to default
System Action:
None.
User Action:
None.
Reason:
An invalid horizontal or vertical scroll amount was entered on the command line or in the scroll field.
Valid vertical scroll values are:
MAX or M—to the start or end of the displayed day
PAGE—one page
HALF—half a page
CSR—at cursor line position
D—to next or previous day (D is valid only on the command line, not the scroll field)
nnn—nnn lines, 1–xxxx (xxxx being a number between 1 and the number specified in /PARMS, $NM LOGFILES for "Log View FIND Line Limit")
Valid horizontal scroll values are:
MAX or M—left to column 1 or right to column 256
PAGE—one page
HALF—half a page
CSR—at cursor column position
nnn—nnn columns, 1–256
System Action:
None.
User Action:
None.
Reason:
A Log Browse Print command was attempted with invalid parameters. Valid command format is:
Prints all lines on the display.
Prints next nnnn lines (from and including the top line).
nnnn = 1 to PrMax (see note below)
Prints next mmmm minutes (from and including the top line).
mmmm = 1 to 1439
Print Screen, Print nnnn lines and Print mmmm minutes are self-contained print commands that will be executed immediately.
Alternatively, a print range may be specified using a combination of the Print Start, Print End, and Print commands, as follows:
Defines the top line as the start of the print range.
Defines the top line as the end of the print range.
Prints all lines in the print range, inclusive of the start and end line. The print range is then reset. (The end line time may be before the start line time.)
Resets any specified print range.
Displays the currently specified print range.
Print Start, Print End, and Print must be entered in that order, but do not need to be consecutive commands - other non-Print commands may be issued in between.
Note: The default maximum print lines is 9999. Maximum can be changed with $GLBL $loPrMax nnnn, where nnnn is in the range 100 to 500000.
System Action:
None.
User Action:
None.
Reason:
This message provides information about the current print line range.
A print line range may be specified via a combination of the Print Start, Print End, and Print commands, as follows:
Defines the currently displayed top line as the start.
Defines the currently displayed top line as the end.
Prints all lines in the print range, inclusive of the start and end line. The print range is then reset. (The end line time may be before the start line time.)
Resets any specified print range.
Displays the currently specified print range.
Print Start, Print End, and Print must be entered in that order, but do not need to be consecutive commands - other non-Print commands may be issued in between.
Alternatively, instead of specifying a print range, one of the following commands may be used.
Prints all lines on the display.
Prints next nnnn lines (from and including the top line).
nnnn = 1 to PrMax (see note below)
Prints next mmmm minutes (from and including the top line).
mmmm = 1 to 1439
Print Screen, Print nnnn lines and Print mmmm minutes are self-contained print commands that will be executed immediately.
Note: The default maximum print lines is 9999. Maximum can be changed with $GLBL $loPrMax nnnn, where nnnn is in the range 100 to 500000.
System Action:
None.
User Action:
None.
Reason:
This message displays the completion status of a print request.
A successful print request should now be visible on the /PSM request queue.
System Action:
None.
User Action:
None.
Reason:
This message displays information about Print command syntax.
Valid command format is:
Prints all lines on the display.
Prints next nnnn lines (from and including the top line).
nnnn = 1 to PrMax (see note below)
Prints next mmmm minutes (from and including the top line).
mmmm = 1 to 1439
Print Screen, Print nnnn lines and Print mmmm minutes are self-contained print commands that will be executed immediately.
Alternatively, a print range may be specified via a combination of the Print Start, Print End, and Print commands, as follows:
Defines the top line as the start of the print range.
Defines the top line as the end of the print range.
Prints all lines in the print range, inclusive of the start and end line. The print range is then reset. (The end line time may be before the start line time.)
Resets any specified print range.
Displays the currently specified print range.
Print Start, Print End, and Print must be entered in that order, but do not need to be consecutive commands - other non-Print commands may be issued in between.
Print may be abbreviated as Prt, Pr or P.
The RESET command resets, among many other things, the print range settings.
Note: The default maximum print lines is 9999. Maximum can be changed with $GLBL $loPrMax nnnn, where nnnn is in the range 100 to 500000.
System Action:
None.
User Action:
None.
Reason:
A print request has failed, due to the indicated error.
If this is a PSM (Print Services Manager) error, consult the PSM documentation.
System Action:
None.
User Action:
None.
Reason:
A request to display a remote Activity Log has failed because the domain ID specified ( P1 ) is unknown. The value must represent either a NetMaster Domain ID or an INMC Link Name that is known to this NetMaster region.
System Action:
Log Browse terminates.
User Action:
Ensure the domain ID is correctly specified. If necessary issue a SHOW DOMAINS or SHOW LINKS command to verify IDs that are available.
Reason:
A request to display a remote Activity Log has failed because the domain ID specified ( P1 ) does not support remote log browse. Only NetMaster systems running Management Services V3.3 and above provide this facility.
System Action:
Log Browse terminates.
User Action:
None.
Reason:
A request to display a remote Activity Log has failed because the domain ID specified ( P1 ) is not contactable due to one of the following reasons:
- The INMC link is not active.
- The APPC link is not defined.
System Action:
None
User Action:
Check the status of the INMC link by using the SHOW LINKS TYPE=INMC command. If the requested domain is not active, activate it. If it is active, check that APPC links have been defined on the remote system. Log on to the remote system and issue the SHOW LINKS TYPE=APPC command and verify that there is a link name defined, perhaps using a generic LUMASK, that supports a link from the local system.
Reason:
The domain of the displayed Activity Log data has changed as indicated, as the result of a DOMAIN command.
Valid command format is:
DOMAIN Displays a selection list of formally linked domains.
DOMAIN domainId/linkName Switches the current display to the requested remote NetMaster region. The browsing environment is retained, and the time set as close as possible to the previous display.
Note: domainID/linkName, when explicitly specified, are not restricted to those on the selection list. Any dynamically linked domain may be specified.
System Action:
None
User Action:
None
Reason:
An invalid shortcut was entered from the Activity Log Browse display.
Navigating to the function you want from the Activity Log can be done in any of these ways:
- Entering a shortcut (/levels or =/levels)
- Entering a combined shortcut and menu option (/bcast.s or =/bcast.s)
- Entering a panel path (=H.I.P)
System Action:
None.
User Action:
Correct the shortcut or panel path, and retry.
SHORTCUTS
Enter a shortcut name, preceded by a slash, at the ===> prompt (for example, /levels or /info or /ipmon). This will take you directly to the function.
To see a list of all shortcuts and their associated functions, enter a single slash (/) at the ===> prompt. Select the desired shortcut from the list by entering 'S' beside it.
If a shortcut exists for a menu option, it is displayed in turquoise, to the right of the option description.
Shortcuts may also be combined with menu options (for example, /bcast.s or =/bcast.s).
Shortcuts can be invoked in two ways: 1. A 'nested' shortcut 2. A shortcut skip
To retain and nest the current screen level, use a nested shortcut:
/shortcut_name Exit will bring you back to the last nested screen in this window. Screens may be nested to a maximum of 64 levels.
To close all currently nested screen levels, use a shortcut skip:
=/shortcut_name
Exit will take you back to the Primary Menu. If you no longer need any nested screens, a shortcut skips saves storage and resources.
(If you are currently at the Primary Menu, a nested shortcut and a shortcut skip behave the same.)
PANEL PATH
Like shortcuts, panel paths move directly to a function without having to access each submenu between it and the current menu. A panel path consists of multiple menu options separated by periods (for example =U.M).
Also like shortcuts, the = sign functions as a skip character, closing all nested screens and effectively entering the path from the primary menu. (If you are currently at the Primary Menu, the skip character is not required.)
Frequently used panel paths have associated shortcuts. If you don't remember a shortcut, enter / at the ===> prompt for a list. Select one from the list, or enter it at the ===> prompt.
There is no difference between accessing a function using a panel path skip or a shortcut skip, although the shortcut should be easier to remember. Both close the current screens and go straight to the function.
Entering == at the ===> prompt from any panel closes all nested screens and returns you to the Primary Menu.
Reason:
This informational message issued by the Activity Log Browser indicates that new log entries have been posted that are not in the current
System Action:
User Action:
To view the most recent log entry, press F6=Latest to reposition the
Reason:
A log browse 'Find' command was requested but could not be performed because of the error condition indicated. These are usually file errors on the activity log VSAM files.
System Action:
None.
User Action:
Check the log for any additional messages describing the error. For file errors, correct the condition and retry the find request.
Reason:
An attempt was made to browse the Activity Logs or perform Log Administration, but no VSAM log data files are available.
By default, three Activity Log VSAM files are defined at NetMaster installation time, and allocated and opened at region startup.
Activity Logs are VSAM datasets named ?dsnqual.NMLOG01, NMLOG02, NMLOG03 They should be allocated to the region as DD's NMLOG01, NMLOG02, NMLOG03 and a UDBCTL OPEN performed with the same names as the FILEIDs.
Up to 7 files, NMLOG01 - NMLOG07, may be used.
System Action:
Activity Log browse or administration functions are not available.
User Action:
Ensure that at least one activity log VSAM file is correctly allocated and opened.
Use SH VSAM=NMLOG* to check that correctly defined VSAM datasets are allocated as DDNAMEs NMLOG01 and so on.
A UDBCTL OPEN.. should have been performed for each file - recommended parameters are DEFER, LSR, SIS
Once the files are allocated and opened, use the SYSPARMS LOGPROC=$LOPROC command to start activity logging.
Reason:
An attempt was made to browse Activity Log VSAM Fileid P1 , but this file cannot be browsed. It may not have been correctly allocated and opened, or it may have been flagged in error by the LOGPROC procedure (possibly after an unsuccessful swap attempt).
System Action:
None.
User Action:
Retry the Log Browse activity without specifying a specific fileid. The latest available log data will be displayed.
System Administrators: Ensure that the VSAM file has been correctly defined, allocated and opened. Check the $LOGFILES ICS Parameter group for errors. Check the hardcopy log for any log swap failures. After fixing any errors, flush and restart the LOGPROC to make this file available for use.
Reason:
An APPC error was encountered while trying to get activity log data or details from remotely connected system P1
The APPC error details are written to the activity log.
(An APPC verb specified the parameter aaaa with invalid value bbbb)
If the parameter is LINK, a likely cause of the error is that the underlying INMC/APPC link between this system and the remote system
P1 has gone down. Check the status of the link, on both systems, and restart it if necessary.
If the parameter is LUNAME, a probable cause of the error is having no DEFLINK TYPE=APPC ... definition covering this LUNAME.
If the parameter is LUNAME, do a SH DEFLINK TYPE=APPC command and ensure that there is an LUMASK that matches this LUNAME. If not, use REPLINK to correct the definition.
System Action:
None. Activity Log display may revert to the local system.
User Action:
Check the log for any additional messages describing the link error. SH LINK TYPE=APPC and SH DOMAINS will display the remote links and domains available. Fix the link between the two systems, and try the operation again.
Reason:
Incorrect parameters were passed to the Activity Log Interface. This is an internal programming error.
System Action:
None.
User Action:
Retry the action - if the message recurs, contact support.
Reason:
An attempt was made to browse the Activity Log, but the current activity log P1 contains no data.
The file status P2 is one of:
RESET The file has been reset and is ready to receive log record data, but no records have been written to it yet. This should be a temporary condition.
NODATA The file is in the process of being closed so that it can be reset. This should be a temporary condition.
ERROR This status has a variety of causes:
- The file could not be closed.
- The file could not be opened.
- The file is marked unusable because of a VSAM error condition.
- The region could not write to the file.
System Action:
None.
User Action:
Wait for a short time, then try to browse the activity log again.
If the problem recurs, investigate the following for additional details on the exact VSAM log file error:
- JCL message and SYSPRINT output for this NetMaster region
- SYSLOG LOGxx DD output for this NetMaster region
- this contains all log messages, including those that could not be written to VSAM Log files
- OCS SHOW VSAM and SHOW UDB commands
Reason:
No log data was found for the date specified.
System Action:
None.
User Action:
Specify a date that has log data for it. For a list of dates that contain log data, enter the DATE command without specifying a date.
Reason:
A delete request for the named log file P3 failed with an unexpected return code of P1 . P2 is the VSAM feedback.
System Action:
If available the system message from the FILE Verb is logged.
User Action:
Refer to the VSAM Programming manual for an explanation of error codes.
Reason:
A delete request for the named log file P3 was rejected. No records for the request date P1 were found on the file P2 .
System Action:
None.
User Action:
None.
Reason:
Details of the system being accessed.
System Action:
None.
User Action:
None.
Reason:
A request to access a specific date failed because the format of the data does not match one of the following: YY.DDD DD/MM/YY or MM/DD/YY (if US language code) YY/MM/DD YYMMDD
System Action:
None.
User Action:
Correct the date entered to match one of the supported formats.
Reason:
A request to delete log data has specified the current day. This is not supported.
System Action:
None.
User Action:
None.
Reason:
An attempt to access the named log file failed.
System Action:
None.
User Action:
Determine why the file is unavailable (by using SH ALLOC and SH UDB commands). Correct and retry.
Reason:
A request to process log resources requires the System Support authority which the current user region does not have.
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator. System Support authority may be granted through the update user function of UAMS maintenance.
Reason:
A request to access Log functions has failed because a required operand is not specified.
System Action:
Request is terminated.
User Action:
Correct the request to specify the required operand.
Reason:
The value P1 is not a valid value for the field identified by the field label P2 .
System Action:
The user cannot proceed until a valid value is entered.
User Action:
Enter a valid value before proceeding.
Reason:
The value P1 has been located in the Log file. The log record number for the day is P2 . The data was found in the field P3 at offset P3 .
System Action:
None.
User Action:
None.
Reason:
A Log search has failed to locate the requested search argument. P1 lines were read in the time range indicated by P2 to P3 .
System Action:
None.
User Action:
If necessary retry the Find operation.
Reason:
A Log search has failed to locate the requested search argument. The top of data was reached for the current day.
System Action:
None.
User Action:
If necessary retry the Find operation.
Reason:
A Log search has failed to locate the requested search argument. The bottom of data was reached for the current day.
System Action:
None.
User Action:
If necessary retry the Find operation.
Reason:
A parsing error occurred processing the parameters in the procedure P1 .
System Action:
The SETVARS system message is logged.
User Action:
Refer to the log and report the error to your product support representative.
Reason:
The VSAM file selected for browsing is either empty or in error. Only files with a status of 'DATA' can be browsed.
System Action:
None.
User Action:
None.
Reason:
Activity Logging Services Procedure P1 received an error on a P2 operation for log file P3 . The File System Error Number was P5 . The associated file key was P7
System Action:
Additional messages may describe the specific error action taken by the calling procedure. In general, file errors while writing to a file cause the logging procedure to swap to the next available file. File errors on reading cause the termination of log browsing procedures.
User Action:
Contact your system administrator.
Reason:
Activity Logging Services Procedure P1 received an error on a P2 operation for Vartable P3 . The FDBK code was P4 . The associated file key was P5
System Action:
Additional messages may describe the specific error action taken by the calling procedure. In general, vartable errors cause log writing or browsing operations to terminate.
User Action:
Contact your system administrator.
Reason:
The active LOGPROC procedure has terminated because of a fatal condition detected by Activity Log Services procedure P1 in routine/function P2
System Action:
Activity Logging reverts to the default processing - messages are logged to SYSOUT, but are not written to any VSAM Log files. Log browsing may continue, but log records from this point onwards are not available. There may be additional SYSOUT messages related to the error condition.
User Action:
Contact your system administrator. Correct the error condition and issue the SYSPARMS LOGPROC= ... command to restart VSAM Activity Logging.
Reason:
No LOGPROC procedure is currently active. The procedure may have terminated in error, or may have been manually stopped with the SYSPARMS LOGPROC=FLUSH command.
System Action:
Activity Logging is using the default processing - messages are logged to SYSOUT, but are not written to any VSAM Log files. Log browsing may continue, but no records since the LOGPROC termination will be available Log File and Date displays may be inaccurate.
User Action:
Contact your system administrator. Check the SYSOUT LOG files for error messages. Correct the error condition and issue the SYSPARMS LOGPROC=$LOPROC command to resume activity logging.
Reason:
The executing NCL process with the specified NCLID has been flushed to enable a Log Swap to take place.
System Action:
Log Swap processing continues.
User Action:
None.
Reason:
The specified userid has been cancelled in order to free the target log file and enable a Log Swap to take place.
System Action:
Log Swap processing continues.
User Action:
None.
Reason:
The LOG procedure P1 has started processing activity log records.
System Action:
None.
User Action:
None.
Reason:
A VSAM error was received writing to the activity log file P1 . P2 is the FILERC value. P3 is the VSAM feedback code indicating the error.
P4 is the procedure name of the log processor detecting the error.
System Action:
Log processing terminates.
User Action:
Refer to the hardcopy log for further messages. Use the feedback code to determine the nature of the error. If necessary allocate a new VSAM log file. Issue SYSPARMS LOGPROC= P4 to restart the log processor.
Reason:
The process P1 started by the log procedure to handle trace records has terminated. The recording of Session Replay Facility traces stops.
System Action:
Logging continues with SRF.
User Action:
Determine why the $TRPROC process terminated. If necessary stop and restart the log procedure to reactivate SRF tracing.
Reason:
An &FILE error was received opening the activity log file P1 . P2 is the &FILERC value. P3 is the procedure name of the log processor detecting the error.
System Action:
Log processing terminates.
User Action:
Use the &FILERC value to determine the cause of the error. Check that the file indicated is allocated and that the fileid has been made available to NCL by means of UDBCTL OPEN. Issue SYSPARMS LOGPROC= P3 to restart the log processor.
Reason:
The log file P1 contains records that are not in the expected key format. P2 is the unexpected data. The file key should be in the format 'yyyymmddnnnnnn'. P3 is the procedure name of the log processor detecting the error.
System Action:
Log processing terminates.
User Action:
If the file key is in the format 'yy/mm/ddnnnnnn' then the file has not been converted from an earlier release. Refer to the product installation instructions for conversion procedures. If the existing data is not required then use the RESET option on UDBCTL OPEN to delete the old data.
Issue SYSPARMS LOGPROC= P3 to restart the log processor.
Reason:
The Activity Log Services Logging Procedure is commencing a VSAM Log Swap operation. This message group indicates the status of the log swap.
System Action:
The log swap processing proceeds. Log swaps of VSAM Log Files are done in response to user request, and on full or file error conditions.
User Action:
None.
Reason:
This message provides information about the status of the log exit procedure.
System Action:
If an error is detected in a log exit procedure or it does not exist, calls to the exit are disabled until the next SYSPARMS LOGPROC restart. If the exit sets the log text to the string NOLOG, that record will be ignored by the LOGPROC procedure.
User Action:
The log exit name is set in the $NMLGXIT global variable. To implement or correct a log exit, LOGPROC must be flushed and restarted with the SYSPARMS LOGPROC command.
The log exit is passed the variable &#lo$record and the MDO &$LOG. &$LOG. is mapped by the distributed ASN.1 map $MSG.
Reason:
The process P1 started by the log procedure to handle trace records has terminated. The recording of Session Replay Facility traces stops.
System Action:
Logging continues with SRF.
User Action:
Determine why the $TRPROC process terminated. If necessary stop and restart the log procedure to reactivate SRF tracing.
Reason:
A backwards local time offset change was detected.
The offset amount was p1 (sHHMM) and the change was made at P2 P3.
System Action:
None.
User Action:
None.
To see when local time offset changes were detected on this LPAR, look for log messages N02H10 to N02H13.
Note: When you browse the Activity Log for a period affected by a backwards time change, log records that occur during the second time through the same local time interval are marked with the character +.
| Copyright © 2012 CA. All rights reserved. |
|