Troubles when SYSLOG or WTO buffers are full

Contents

Bottom

1. SYSLOG or WTO buffers are full

          1.1. WTO buffers full

          1.2. SYSLOG buffers full

2. Save SYSLOG on tape

3. Save SYSLOG to PC

When SYSLOG or WTO buffers are full and SYSLOG file need to be saved on tape or transfered to PC, some action described below have to be performed.

When WTO/R or SYSLOG buffers reached their limits or are full, it is necessary to investigate the buffer limits with the TSO/ISPF sd.log command ‘D C,HC’ and compare them with  the limits in the normal system status. Go to item 1 of the Contents.

To save the current SYSLOG data on tape a procedure is used for daily/monthly processing of SYSLOG on a production system , minimizing the size of the SYSLOG. Go to item 2 of the Contents.

To save the current SYSLOG STC**** to PC for later investigating and analysis, z/OS file is created that contains all SYSLOG current data and it is sent to PC with MF-PC text file transfer. Go to item 3 of the Contents.

           1. SYSLOG or WTO buffers are full

If by any reason WTO/R or SYSLOG buffers reached their limits or are full the warning messages will appear and the following command shoul be issued:

D C,HC – display SYSLOG and WTO buffers

IEE889I 14.20.22 CONSOLE DISPLAY 182

MSG: CURR=4 LIM=3000 RPLY:CURR=1 LIM=100 SYS=BC2A PFK=NONE

CONSOLE/ALT                              ID ————— SPECIFICATIONS —————

SYSLOG                 COND=H      AUTH=CMDS         NBUF=0    UD=N
                                  ROUTCDE=ALL

LOG BUFFERS IN USE: 0 LOG BUFFER LIMIT: 1000

                    1.1. WTO buffers full

The system stops delivering informational messages to a console when there is a WTO buffer shortage and/or when the console has a backlog of more than four screens of messages or 150 messages (whichever is greater).

When the z/OS console operator message area occurs to be 100 % full (because of too much WTO error messages generated by some system or application program) and the generation of messages (WTO, WTOR) from the system is stopped, the following message appears:

IEA404A SEVERE WTO BUFFER SHORTAGE – 100% FULL

, The system is not usable, need urgent system actions and the following should be done:

– Enter k q or k q,r=hc – to delete all WTO/WTOR messages /the most effective from CPU console!!!/

If the WTO buffer limit is 80% reached the following message will appear:

IEA405E WTO BUFFER SHORTAGE – 80% FULL – WTO current = 2400 is 80% of 3000 (the limit value specified in the MLIM parameter of a CONSOL00 sys1.parmlib member to change before IPL):

INIT PFK(NONE) MPF(CI) RLIM(100) MLIM(3000) UEXIT(N) CMDDELIM(“)

CNGRP(1B) APPLID(SMCS&SYSCLONE)

In WTO/R display: MSG: CURR=2400 LIM=3000 RPLY:CURR=1 LIM=100 SYS=BC2A PFK=NONE

WTO limit=3000 (current=2400), WTOR limit=100 (current=1)

The following should be done:

– Enter the k q command to purge the messages.

– Enter the k (CONTROL) S command to delete a specified number of messages.

– Enter the k (CONTROL) M,MLIM or M,RLIM command to increase the value of the WTO or WTOR buffer limit (k m,mlim=4000).

– Put the display CPU console in roll mode to let a specified number of messages roll off the screen at a specified time interval. Consoles that are currently in HOLD mode and have messages waiting are taken out of HOLD (IEE163I MODE= RD).

If the buffers of WTO console messages written on hardcopy are full (LIM is reached) the WTO messages has to be deleted by command ‘k q,f=hc’ from the master system console. This is described in the article ZOS_WTO_WTOR_MSG_delete

                    1.2. SYSLOG buffers full

Logging provides a permanent record of saving system messages and, optionally, commands and command responses, by using the system log (SYSLOG) called the hardcopy medium. The system log (SYSLOG) is a direct access data set that stores messages and commands. It resides in the primary JES (job entry subsystem’s) spool space.The SYSLOG spool file is managed by JES and can be displayed using TSO/ISPF log command:

/D CONSOLES,HARDCOPY (D C,HC) – display information about the Log buffers in use and the Log limit:

LOG BUFFERS IN USE: 0 LOG BUFFER LIMIT: 1000

If the system log task (SYSLOG) is active but 100% of its buffers (LOG BUFFER LIMIT: 1000) are full, Write-to-log (WTL) processing ceases to allocate WTL queue elements and the following message appears:

IEE767A SEVERE BUFFER SHORTAGE FOR SYSTEM LOG – 100% FULL

To reanimate SYSLOG, it is necessary to increase the number of WTL buffers available to the system by entering the ‘k M,LOGLIM=2000’ command or to increase permanently the value of LOGLIM in the CONSOL00 member of sys1.parmlib before a new IPL.

If a VARY SYSLOG,HARDCPY,OFF,UNCOND command has previously been issued, z/os has saved SYSLOG messages in SYSLOG buffers to be hardcopied later.

After some time of work the number of syslog buffers are increasing (less than 1000) and the contents of buffers with the saved SYSLOG messages after the last command in SYSLOG is as follows:

HARDCOPY SUSPENDED ON THIS SYSTEM

LOG BUFFERS IN USE: 24 LOG BUFFER LIMIT: 1000

When SYSLOG buffers are full (limit of 1000 is reached) and no longer is possible to save system messages on hardcopy, the following message appears:

IEE012A NO LONGER SAVING MESSAGES FOR HARDCOPY, LOGLIM REACHED

Either activate a hardcopy medium , or increase the value of LOGLIM (1000) with the CONTROL M,LOGLIM command.

In this case it is necessary first to increase the limit of 1000 with the “k M,LOGLIM=2000” command and then to issue a command ‘ /v syslog,hardcpy’ to activate a hardcopy medium.

/V SYSLOG,HARDCPY – SYSLOG data set is assigned again as Hardcopy medium for system messages. After this command all log buffers/messages following the last log command VARY SYSLOG,HARDCPY,OFF,UNCOND are restored/added in SYSLOG.

          2. Save SYSLOG on tape

To save the current SYSLOG data on tape, a Writelog command is used by an external writer ‘SYSWRT’ to write class L syslog to a disk data set, accumulated on weekly file and cleared for the next ‘SYSWRT’ use. When the weekly file is full, it is backed up on GDG tape for long time saving to be restored and analyzed when needed. The operator is asked to mount labeled scratched or work tape where weekly syslog data set are copied and then the accumulation weekly file is empted for next summary use.

In the item 2 ‘SYSLOG prossessing of production system’ of article ZOS_SYSLOG  a procedure is described for daily/monthly processing of SYSLOG of production system , so that after this procedure the size of the SYSLOG to be minimized (checking in TSO/ISPF – sd.log).

          3. Save SYSLOG to PC

To the current SYSLOG to PC for investigating and analysis of some special situations , first write the command ‘xdc’ on the SYSLOG line af the main TSO/ISPF – sd.st menu as follows:

xdc SYSLOG STC06608 +MASTER+ 15 EXECUTION BC2A BC2A

Use the following next screen menu to create ‘BCA1MGP.SYSLOG’ file that contains all SYSLOG data – viewed in TSO/ISPF – p.3.4 – and send file the ‘BCA1MGP.SYSLOG’ to PC with MF-PC text file transfer. Go to article JES2_ job_ processing  where these operations are described at item 2.3. ‘xdc (save to MVS file)’.

End

Leave A Reply

Comments

No comments yet, be the first to add one!

Places

 

Clef two-factor authentication

woolrich outlet woolrich outlet online tiffany milano tiffany outlet tiffany outlet tiffany outlet tiffany outlet tiffany milano tiffany outlet peuterey outlet peuterey uomo hogan outlet hogan rebel hogan outlet hogan rebel hogan outlet hogan rebel hogan outlet hogan rebel hogan outlet hogan rebel hogan outlet hogan rebel roshe run pas cher roshe run parajumpers pas cher parajumpers soldes parajumpers pas cher parajumpers soldes parajumpers pas cher parajumpers soldes louboutin pas cher louboutin pas cher louboutin pas cher nike tn pas cher nike tn pas cher