Barbara,
It may very well be that SYSLOG has always stopped at either
$PJES2 or the Z EOD command being
issued. I don't remember it that way nor does anyone else in the shop. So
for us, it's something
new and exciting.... We've updated OPERLOG to duplex so that we don't
lose shutdown logs when a coupling
facility may be shutdown or abnormally terminates.
IBM has work to do for SMF or any CF based logstream... Logger
should always harden the SMF
data at shutdown to the archive datasets, currently it does not do so
reliably.
As for
>Date: Fri, 8 May 2009 00:24:50 -0500
>From: Barbara Nitz <nitz-...@gmx.net>
>Subject: Re: SMF LOGGER - Not Ready for Prime Time
>IFA705I HALT SMF PROCESS HAS SYNCHRONIZED THE BUFFERED LOGSTREAM
RECORDS.
>I really like the suggestion in the books for this message <sarcasm off>,
which
>implies to use automation on a 'NOT synchronized' message, even after a z
>eod. Strangely, z eod is only issued in this installation after *all*
address
>spaces are gone (well, those visible on a d a,l). So no automation. I
realize
>that this message is also issued for switch smf commands.
>that we discovered that IBM now stops SYSLOG at two points. When either
>Z EOD is issued or when JES2 is stopped.
The information contained in this message may be CONFIDENTIAL and is for the
intended addressee only. Any unauthorized use, dissemination of the
information, or copying of this message is prohibited. If you are not the
intended addressee, please notify the sender immediately and delete this
message.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
