 |
» |
|
|
|
You use the LOG configurator to display information about system and
user logging, print log files, and choose which events the system will record. To enter the LOG configurator | |
You make all system and user logging changes from with the LOG
configurator, which is one of the SYSGEN modules.
To enter the LOG configurator, do as follows: At the MPE prompt, start SYSGEN by entering:
At the SYSGEN prompt (sysgen>), start the LOG configurator by entering:
You will see a list of the commands available to you in the LOG configurator.
(See the example below.) To issue a command, you can either enter
the full name or you can enter the abbreviated version shown in parentheses.
Figure 4-1 Example 4-1. Activating the LOG Configurator
sysgen>LOG
** LOG configurator commands **
show (sh) slog (sl) ulog (ul)
clear (cl)(c) exit (ex)(e) help (he)(h) hold (ho)
oclose (oc) redo
|
To display on-line help | |
Use the HELP command to get information about the commands
available to you in the LOG configurator. To display a complete list of commands and a brief explanation of
each one, at the log> prompt enter: To display information about one of the LOG configurator commands,
at the log> prompt enter HELP followed by the command name.
For example, to get help on the SLOG command, enter:
To show current LOG values | |
Use the LOG configurator's SHOW command to display current
LOG values on the system console or to print them offline.
At the LOG prompt (log>), enter: SHOW has the following parameters: SHOW [[COMMAND =] { SLOG ULOG ALL }] [ [DEST =] OFFLINE ] | Parameter | Definition
|
|---|
| SLOG | Lists the state of the system logging events.
| | ULOG | Lists the number of user logging processes and users per logging process currently configured.
| | ALL | Lists all the information associated with the LOG configurator. This is the default parameter.
| | OFFLINE | Redirects the output of the SHOW command to the SYSGEN listing file, SYSGLIST. Using OFFLINE does not immediately generate a printout. The information is sent to SYSGLIST until you either enter the OCLOSE command or exit the configurator. Exiting SYSGEN or using OCLOSE closes SYSGLIST and prints the file.
|
To see partial logging informationYou can use the SHOW command to see only the values for system logging
or user logging (instead of for both).
For example, to display the current status of user logging processes, enter: The LOG configurator displays the minimum, maximum, current, and default
values for your system. (See the example below.) Figure 4-2 Example 4-2. Showing User Logging Processes
log>SHOW ULOG
configurable item max min current
----------------- ------- ------- -------
# of user logging processes 64 2 64
# users per logging process 1024 1 128
|
To see all logging informationTo display all currently configured values, you can enter: Or, you can enter: The LOG Configurator displays
the minimum, maximum and current value for user log events and
the name, number and status (OFF or ON) of system log events. To print current logging informationInstead of displaying logging information on the console, you can
print it offline. To do so, add the DEST=OFFLINE parameter to
the end of the command line. For example, to print a copy of
system logging data, follow these steps: Send the output of the SHOW command to the file SYSGLIST by
entering:
log>SHOW SLOG DEST=OFFLINE
|
Close the file SYSGLIST and print the information by entering:
Note that you can also exit the LOG Configurator to close and print
SYSGLIST. To log system events | |
System logging keeps a running log of certain resources so that you can
monitor their use by accounts, groups
and users. You can use system logging for billing purposes or simply
to see an overview of system use. To determine which events
are logged, you use the SLOG command to turn them on or off. SLOG has the following parameters: SLOG (SL) [ [ON =] event#,... ] [ [OFF =] event#,... ] | | | |  | NOTE:
You can turn off all events except the following three which are always on:
system up record (event 101), I/O record (event 111), and
diagnostic information record (event 150). | | | | |
Before you change the system logging configuration, enter the SHOW SLOG
command to see which events are currently ON or OFF. Your console
will display something like the example on the next page. Figure 4-3 Example 4-3. Sample Configured Values
log>SHOW SLOG
system log events event # status
----------------- ------- ------
System logging enabled 100 OFF
System up record 101 ON
Job initiation record 102 OFF
Job termination record 103 OFF
Process termination record 104 OFF
NM file close record 105 OFF
System shutdown record 106 ON
Power failure record 107 ON
I/O error record 111 ON
Physical mount/dismount 112 OFF
Logical mount/dismount 113 OFF
Tape labels record 114 OFF
Console log record 115 ON
Program file event 116 ON
NCS spooling log record 120 ON
Architected interface record 130 0N
Password changes 134 ON
System logging configuration 135 ON
Restore logging 136 ON
Printer access failure 137 ON
ACD changes 138 ON
Stream initiation 139 ON
User logging 140 ON
Process creation 141 ON
Chgroup record 143 ON
File open record 144 ON
Maintenance request log 146 OFF
UPS Monitor Event Logging 148 OFF
Diagnostic Information 150 ON
High Priority Machine Check 151 ON
Low Priority Machine Check 152 ON
Directory Open/Close Logging 155 OFF
CM File Close 160 OFF
Chdir 161 OFF
Process Adoption 162 OFF
File Owner Change 163 OFF
log>
|
For any of the system log event are listed as OFF when you issue
the SHOW command, you can quickly enabled them. To do so,
note the number of the event that you want to enable and use the ''SLOG''
command. For example, to enable stream initiation (event 139), at the
log> prompt enter: Or, you can enter: Suppose that you have enabled event 139 (stream initiation), and
a user JOHN in the group DOE of the PAYROLL account logs
on with the session name JREPORT. If he streams the job
file JTEST.TESTGP.TESTACCT that was logged on as #J12,
the system logs the following information:
USER: JOHN GROUP: DOE
ACCOUNT: PAYROLL JSNAME: JREPORT
INPUT LDEV: 21 DEV NAME: TERM
JOB FILE NAME: JTEST.TESTGP.TESTACCT
LOGON J/S TYPE: JOB LOGON J/S NAME: 12
|
To disable an event, you enter the SLOG command with the OFF
parameter, followed by the number of the event you want to disable.
For example, to disable the console log record (event 115), enter: To disable all system loggingTo disable all system logging (except those events always monitored by
MPE, which you cannot turn off), specify event 100. For example: To review one event recorded in the system log fileYou can use the LOGTOOL utility to
review entries in the system log file for a particular event.
To do so, follow these steps: List the names of the log files currently on your system. At the MPE
prompt, enter: Note the number of the last log file in the list (other than LOGDCC).
You will use it in step 5.
Start the system diagnostic utility. At the MPE prompt, enter: Run the LOGTOOL utility. enter: To review the current logfile, use the SWITCHLOG command to close
it and open a new one.
List the information for a specific event in the log file that you
want to review. For example, if the last log file displayed with
the LISTFILE command was LOG00017 and you want information
about event 139, enter:
DUI >LIST LOG=17;TYPE=139
|
Or, if the last log file was LOG00017 and you then issued the SWITCHLOG
command, to see the most recent log file you would enter:
DUI >LIST LOG=18;TYPE=139
|
In a moment, you will see the contents of the system log files for event
139. If event 139 was disabled, you are informed that no messages are found.
To control user logging | |
User logging provides a means for system users and subsystems
to record additions and modifications to databases and other files
that use application programs. As system manager, you determine
the maximum number of logging processes and the maximum number of
users per logging process. Use the ULOG command to configure the user logging process parameters.
ULOG has the following parameters:> ULOG (UL) { [NLOGPROCS =] number processes allowed [USERSPERPROC =] users per logging process} | Parameter | Definition |
|---|
| NLOGPROCS | Controls the user logging ID (LID) table size. The minimum number of processes is 2 and the
maximum is 64. The changes take effect when you perform an UPDATE CONFIG
or an INSTALL with a system load tape that contains the new table size. If
you lower NLOGPROCS, the system will not record any of the current logging
ID information onto the system load tape. If you increase NLOGPROCS or
leave it unchanged, the current information is copied to tape.
| | USERSPERPROC | Controls the maximum number of users assigned to each configured logging process. The minimum number of users per logging process is 1 and the maximum is 1024. |
For example, to set the number of logging processes to 40, enter: Or you can enter: To set the number of users per process to 40, enter: Or, you can enter: To print a log | |
To read and analyze your logs, you must print
your log files. To do this, you use the LOGTOOL utility program
in the following set of steps: At the MPE prompt, enter the SYSDIAG command.
At the diagnostic user interface prompt (DUI>), enter Check the status of all system log files by entering: Choose a file to print and enter the LIST command followed
by the log number and the OUTFILE parameter.
For example, to print log 27 (which appears as LOG00027 in
the list), enter:
LOGTOOL>LIST LOG=27 OUTFILE=LP
|
Exit LOGTOOL by entering EXIT at the LOGTOOL> prompt. Exit the diagnostic user interface by entering EXIT at the DUI>
prompt.
| | | | | NOTE:
If you do not specify the OUTFILE parameter, the log prints on
your terminal screen. Typically this report is very long and ties up
your terminal for quite some time. If this happens, you can enter
CTRL Y to break the process.
Refer to the Online Diagnostic Subsystem Utilities Manual (09740-90021) for more information about LOGTOOL. | | | | |
|
