Each MVS system has a System Log (SYSLOG) where various messages are kept. Sysplex systems optionally have an operator log (OPERLOG) which combines log data from all systems in the sysplex. When OPERLOG is active on the sysplex, the installation also may choose to run SYSLOG on one or more of the MVS systems that make up the sysplex. Or, they may elect to disable SYSLOG entirely.
The option, L, on the IOF Option Menu is used to request access to the log. If your installation is running OPERLOG and has selected that it be displayed by default, the combined OPERLOG will be displayed. Otherwise, the SYSLOG will be displayed.
The L command has several options that can be entered as parms. If both SYSLOG and OPERLOG are active on your system, you can request access to the type of log you prefer. You also can request access to the log for a single system id. If your installation uses IOF to manage old logs, you can request access to old or archived logs.
Syntax
L [ Operlog / Syslog / sysid / OLD / ARCH ]
O or OPER. Displays the Operlog.
S or SYSLOG. Displays the System Log.
sysid. Displays a specified system id.
OLD. Displays a menu of old logs if your installation makes memo copies of old logs.
ARCH. Displays a menu of archived logs if your installation uses IOF procedures to archive old logs.
Examples
L O Displays Operlog
L IPO9 Displays log for sysid IPO9
L ARCH Displays menu of archived logs
L S SYS8 Displays syslog for SYS8
The Log Option Menu is a full-screen panel that can be used to specify log options. To access the panel enter L? on the IOF Option Menu or enter /L? from any IOF panel.
|
Once you have invoked IOF browse of the log with the L option, you can go directly to any time of day with the LOCATE command.
L 1245 Positions to 12:45 PM
L 0715 Positions to 07:15 AM
The SNAPTIME command snaps parts of the log to an IOF snap target data set. After defining the target data set with the SS or SD command, enter
SNAPTIME 0945 1015
to snap the system log between the times of 09:45 and 10:15. The SNAPTIME command is not available under IOF/CICS.
Many important system events are continuously monitored and indexed by the IOF Indexing Task. Each event is classified into a particular category and then added to the index for that type of event. After invoking IOF Browse for the log with the L option, enter INDEX to display a menu of the types of events that have been indexed.
|
This menu quickly shows you that you have had 23 device errors today, 12 enqueued data sets, and 39 miscellaneous errors. One minute (23:59) was indexed yesterday (Monday), and 956 minutes have been indexed today (Tuesday). You can position to 12:43 this afternoon by entering L 1243.
Indices can be selected for display from the IOF Data Indices menu. One or more specific indices can be displayed by entering S in the action area(s) or by entering the menu number(s) in the command area. The miscellaneous index from the display above can be selected by entering 6 in the command area.
|
Part of the miscellaneous data index is shown above. It points directly to several conditions that may need to be investigated. An index entry may be selected to cause direct entry into browse at the point where the exception condition occurred by entering S in the action area, or by entering the item's menu number in the command area.
Remember that the Log Index is read when the L command is entered and is not read again until you enter another L command. To get to the bottom of the log after being in browse for a few minutes, it is better to enter another /L command than to enter DOWN MAX. To update the log display continuously, enter E5 D M (every 5 seconds refresh the screen and go down max). Press ATTENTION to break out of automatic update mode. Note that the EVERY command is not available when running IOF from CICS.
Your installation may choose to keep one or more days of log data online for easy access. If so, the old logs can be accessed by entering /L? on any IOF panel and following the directions for access. You also can jump directly to an old log display by entering /L OLD.
If your installation runs operlog, optionally you can skip to the menu of old logs and access directly a specific old operlog. The command L O-1 requests access to yesterday's operlog. Similarly, L O-2 requests access to the operlog that is two days old.
Your installation may choose to archive old log data. If so, these can be accessed by entering /L ARCH on any IOF panel and selecting an old log for browse from the menu.
The SYSID command can be used to save your default syslog system id in the profile.
Syntax
SYSID sid
sid. The system id of the syslog you normally wish to review.
Enter the DR command from any IOF screen to display the current list of system messages which are awaiting a response from the system operator.
Syntax
DR [n1,n2,...] [ALL/MVS/USER] [EVENTUAL]
n1,n2,... List of route codes for which messages are to be displayed.
ALL.Show messages with route codes 1 through 28.
MVS. Show messages with route codes 1 through 12.
USER. Show messages with route codes 13 through 28.
EVENTUAL Also show eventual action messages.
Enter the SR command from any IOF panel to display outstanding
System Requests, including action messages and WTORs. Action
messages can be deleted, and replies to WTORs can be entered as
line commands directly on the displayed panel.
Entering MVS and JES2 Commands
Authorized users can enter MVS and JES2 commands from any IOF panel. The JES2 command character is a dollar sign ( $ ). The MVS command character is a number sign ( # ) on most IOF systems, but may be a slash ( / ) if your IOF system is installed in SDSF compatibility mode.
To issue a JES2 command, enter $ followed by the JES2 command. To issue an MVS command, enter # (or / if your IOF is installed in SDSF compatibility mode) followed by the MVS command. For example:
$DSPOOL,ALL
#D T
/D T (in compatibility mode)
The < command is a special way to issue MVS commands and see the response in the system log. The MVS command following < is issued, then found in the system log so you can easily see its output. You would normally use the MCS Extended Console to enter commands, but you alternately can enter the < command. This command is not available under IOF/CICS.
The MVS command with no parms, or # or < with no parms, displays a
special command assist panel that permits entering long MVS and JES2
commands. The last 32 commands issued can be re-selected from the old
command display at the bottom of this display.
Extended MCS Console
IOF provides full-screen support for the extended MCS console feature. Proper authority is required to use the extended console feature and to issue MVS and JES2 commands.
The IOF Extended MCS Console is a special browse panel that captures and displays commands and messages from a private extended MCS console. Commands that have been issued from a console panel in the current IOF session, and responses to those commands, are displayed by default. Standard browse features are available to the extended console. For example, FIND, SNAP and scrolling work as in any IOF browse session. The END command exits to the IOF panel from which the extended console was invoked.
MVS commands can be entered with no prefix character on the extended console panel.
There are a few ambiguous commands which could be valid both as panel commands and MVS commands. For example, D M is the MVS DISPLAY MACHINE command and the panel DOWN MAX command. This problem is solved by requiring that DOWN not be abbreviated. The MVS command character can also be used to eliminate ambiguities.
Entering an MVS or JES2 command on any IOF panel automatically initializes an extended MCS console and displays the IOF console panel. The CONSOLE command can also be used from any IOF panel to explicitly initialize an extended MCS console.
Syntax
CONSOLE/CN [NAME(cons_name)]
cons_name. The name of the extended console if you wish to explicitly name it. The default console name is your userid followed by one or more digits.
Examples
CONSOLE
CN NAME(SPGMR)
or enter a MVS or JES2 command
The AUTOCON command can be entered from any IOF panel to disable automatic invocation of the extended console when an MVS or JES2 command is issued. The automatic console status is saved in your profile and remains set until changed by another AUTOCON command. When AUTOCON OFF is in effect, the CONSOLE command must be used to invoke the extended console.
Syntax
AUTOCON [ON/OFF]
ON. Enable automatic console invocation.
OFF. Disable automatic console invocation.
The AUTOROUT command can be entered from any IOF panel to specify that all explicit MVS and JES2 commands entered by the user from IOF be routed to a designated system in the sysplex. The sysid is saved in the profile, but is not validated by IOF. AUTOROUT reverts to the OFF status when the IOF session is terminated.
Syntax
AUTOROUT [ON/OFF] [sysid]
ON. Enable automatic routing. ON is the default if neither ON nor OFF is specified.
OFF. Disable automatic routing.
sysid. System id of the system to which commands will be automatically routed.
Examples
AUTOROUT IPO9 (Enable autorout to system IPO9)
AUTOROUT OFF (Disable autorout)
AUTOROUT ON (Re-enable autorout)
Note that AUTOROUT is not required to send commands to a specific MVS system. The MVS ROUTE command can also be used. For example, the following command will issue a JES2 command on system IPO9 to display the SPOOL:
#RO IPO9,$DSPOOL,ALL
The format of messages displayed on the extended console can be controlled with the MFORM command. The MFORM status is saved in the profile. MFORM with no parms resets to the default format.
Syntax
MFORM [ T ] [ S ] [ J ] [ M ]
T. Display time stamp on all messages
S. Display the system id on all messages
J. Display the job name on applicable messages
M. Display message text only
Examples
MFORM T
MFORM JTS
MFORM
Extended consoles normally display only messages that are explicitly routed to them. The ROUTCDE command can be used to have specific MVS route codes automatically displayed at the currently active extended console. MVS route codes revert to the default value for the console when the current extended console is terminated. The MCS extended console is normally terminated when the console panel is terminated but can be kept active with the CNSKEEP command.
Syntax
ROUTcde [NONE/ALL] [ADD] [DEL] [codes]
NONE. Revert to no route codes. This is the default if no parms are entered.
ALL. Enable all route codes.
ADD. Add the codes listed in the codes parm.
DEL. Delete the codes listed in the codes parm.
CODES. One or more MVS route code numbers or range of numbers. The codes will be added if the ADD parm is present, deleted if the DEL parm is present, or set if neither is present.
Examples
ROUTDCE ALL
ROUT 1,3,7-10
ROUT ADD 2,5
ROUT NONE
Use the CNSCROLL command to control automatic scrolling when a command is entered on the MVS extended console.
Syntax
CNSCROLL [ON/OFF]
The extended MCS console is normally terminated when you leave the console panel. To leave the console active enter the CNSKEEP command before exiting the console panel.
Syntax
CNSKEEP
The DC command can be issued from the extended console panel to display the status of the extended console.
Syntax
DC
The CLEAR command can be issued from the extended console panel to clear all existing commands and messages. An automatic clear command is done each time IOF is terminated.
Syntax
CLear
The LONG command can be issued from the extended console to display an ISPF panel that allows entering very long MVS or JES2 commands. The ISPF panel is particularly useful when entering long SLIP commands.
Syntax
LONG
A maximum of nine commands can be saved in the profile to be automatically executed every time the IOF extended console is initialized. Extended console commands, IOF browse commands, MVS commands or JES2 commands can be saved.
Syntax
CNSICMD nbr command [DELETE]
nbr. The command number (1 to 9) to be defined.
command. The IOF, MVS, or JES2 command to be issued.
DELETE. Delete all 9 previously saved initialization commands.
Examples
CNSICMD DELETE
CNSICMD 1 ROUTCDE 1,3,5-9
CNSICM 2 $DSPOOL,ALL
CNSIDD 3 EVERY 5 DOWN MAX