Just an FYI, but SYS1.SAMPLIB(IEAMDBLG) can be
modifies to increase the record length of the
SYSLOG formatted extract of OPERLOG from 132 to
255 and thereby eliminate split ("s") records.
Michael
At 09:21 AM 8/6/2022, Feller, Paul wrote:
Content-Transfer-Encoding: base64This is from
the
And SDSF should limit itself to pointing out that latter manual. As
previously mentioned, documenting program behavior that is not under your
control leads to mistakes and confusion, not to mention useless redundancy,
even if correct for a time.
sas
On Sat, Aug 6, 2022 at 10:05 AM Colin Paice
This is from the z/OS 2.4 "z/OS MVS Planning: Operations" manual. I do find it
interesting that similar information is found in different manuals.
Each SYSLOG record is prefaced by a two-character record type field.
Valid first characters are:
N - single-line message
W - single-line message
See MVS System messages ABA.. eg SA38-0668-04
https://www.ibm.com/docs/en/zos/2.3.0?topic=format-message-body
and
https://www.ibm.com/docs/en/zos/2.3.0?topic=format-messages-sent-hardcopy-log-in-jes2-system
On Sat, 6 Aug 2022 at 14:24, Pierre Fichaud wrote:
> In SDSF, I type in the LOG
In SDSF, I type in the LOG command.
I get lines like :
X 000 S0W1 22060 18:01:25.24 SYSLOG IEE042I SYSTEM LOG
DATA SET INITIALIZED
NC000 S0W1 22060 18:00:18.73 INTERNAL 0290 CONTROL M,UEXIT=Y
IEAVN701 - INTERNALLY ISSUED K M
NR000 S0W1 22060
You may like this then -
https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/yu-mei-dai/2022/08/04/dsfs-introduction
- KB
--- Original Message ---
On Saturday, August 6th, 2022 at 1:35 AM, Paul Gilmartin
<042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:
> On the
