Salva Carrasco wrote:
>> How did you find it out? Experiencing abends with SMF processing jobs or
>> having problems with Logstreams?
>> Or just simply excellent eye-balling the records?
>>I see you have posted a sample SMF record 80, is that field SMF80USR? (offset
>>19 as per your post)
>No
> How did you find it out? Experiencing abends with SMF processing jobs or
> having problems with Logstreams?
> Or just simply excellent eye-balling the records?
>I see you have posted a sample SMF record 80, is that field SMF80USR? (offset
>19 as per your post)
No abends or errors. An
Salva Carrasco wrote:
>After a long investigation, IBM has found an error when the SMF LogStream
>structure is defined with MAXBUFSIZE < 64K in z/OS 2.2.
>Pending OA51823 APAR.
Many many thanks for helping us SMF oldies. ;-)
Much appreciated.
>SMF record corrupted at offset x16, high order
After a long investigation, IBM has found an error when the SMF LogStream
structure is defined with MAXBUFSIZE < 64K in z/OS 2.2.
Pending OA51823 APAR.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send
Pfewww. Going to 2.2 on production on Sunday, luckily still with MAN datasets.
Kees.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Salva Carrasco
Sent: 16 December, 2016 13:12
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: z/OS 2.2 SMF
Hi all.
SMF record corrupted at offset x16, high order bit zeroed, in (almost) types:
4, 14, 15, 20, 61, 62, 65, 64, 66, 80, 208, 241.
Sample (E7 become 67 at offset 19):
+1+2+
& ยข BCARXPRODPL
1500B10131CCCD2000EDDDCDD
E0060B165F231980507796473
