Re: SMF Record types to capture

2022-07-06 Thread Bonnie Ordonez
The SMF type/subtype combinatorics is not quite that high. While the SMF record header extended record type field, as well as the subtype field,are each 2 bytes, SMF accepts record types 0-2047 to be recorded, and accepts 32767 subtypes off of a given record type. Bonnie Ordonez

Re: SMF Record types to capture

2022-07-05 Thread Michael Oujesky
compatibility, AND an extended type number (4 digits). Roger W. Suhr suhr...@gmail.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Michael Oujesky Sent: Sunday, July 3, 2022 13:51 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMF Record types to capture The st

Re: SMF Record types to capture

2022-07-05 Thread Bonnie Ordonez
To be precise, as of z/OS 2.1, there are up to 2048 valid record types (0-2047). A value of 126 (decimal) at offset +5 into an SMF record is one (of many) indicators that the record contains an extended header where the actual record type field resides. The chapter titled "SMF record general

Re: SMF Record types to capture

2022-07-04 Thread Michael Oujesky
IBM Mainframe Discussion List On Behalf Of Michael Oujesky Sent: Sunday, July 3, 2022 13:51 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMF Record types to capture The standard header is still a one byte field, so 0:255 captures them all. At each dump/off-load, I segmented our SMF records by category/i

Re: SMF Record types to capture

2022-07-03 Thread Roger W Suhr
lf Of Michael Oujesky Sent: Sunday, July 3, 2022 13:51 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMF Record types to capture The standard header is still a one byte field, so 0:255 captures them all. At each dump/off-load, I segmented our SMF records by category/interest-group and anticipated ret

Re: SMF Record types to capture

2022-07-03 Thread Michael Oujesky
The standard header is still a one byte field, so 0:255 captures them all. At each dump/off-load, I segmented our SMF records by category/interest-group and anticipated retention period to reduce the processing resources and time by not having to process record types that ere superfluous. As

SMF Record types to capture

2022-07-03 Thread Lizette Koehler
I am reviewing our SMF Setup. We are on z/OS V2.3 going to z/OS V2.4 We have not reviewed or updated our SMF record types in decades We only use 0:255 for our archive/collection parms Is there a new range to change to use? If so, what should I use? Any suggestions or is this