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 © 2014 CA.
All rights reserved.
|
|