Re: Question about IEFSSI REQUEST=QUERY
All of these questions are answered in the IEFSSI QUERY description in the MVS Programming: Assembler Services Reference, Volume 2 (IAR-XC manual: WORKAREA=workarea A required parameter that specifies a name (or register containing the address) of a pointer output field that contains the address of the subsystem information returned by the QUERY request. The output area is mapped by the IEFJSQRY macro. The JQRYLEN field contains the length of the output area. ,WORKASP=workasp An optional parameter that specifies a name (or register containing the address) of a one-byte input field that specifies the subpool that the SSI uses to obtain a work area for the returned subsystem information. The caller is responsible for freeing this work area. IBM recommends that you use a job-related or task-related subpool. This allows the system to free the associated storage when the job or task ends, if the caller does not free the returned area. If WORKASP is not specified, the caller's subpool zero is used. Storage for the query information is obtained above 16 megabytes. AMODE 24 callers must switch into AMODE 31 to address this storage. Unauthorized callers may request storage only in the following unauthorized subpools: • 0-127 • 131 • 132 Bonnie Ordonez -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF Record types to capture
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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF Record types to capture
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 information and best practices" contains sections describing the SMF standard and extended headers and record types. https://www-40.ibm.com/servers/resourcelink/svc00100.nsf/pages/zOSV2R5sa380667/$file/ieag200_v2r5.pdf Bonnie Ordonez -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ICSF and Z EOD (and Pervasive Encryption)
Yes, I meant Crypto not compression. Records written to the SMF buffer after Z EOD and prior to system shut down will be lost. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ICSF and Z EOD (and Pervasive Encryption)
If it is configured to do so, SMF will continue to compress data as long as ICSF is active, so if you want end-to-end SMF data compression, shutting down ICSF after Z EOD is the way to go. Regards, Bonnie Ordonez, SMF L3, IBM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF - SIGVALIDATE parameter
SMF signatures include metadata describing both the record contents and the number of records per type and subtype that are written during each interval. Validation processing ensures that neither the record contents nor the counts have changed. Bonnie Ordonez, IBM SMF, Level 3 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Unable to get data from IFAURP roe registered product
On the PROCESSOR statement, the type, model and serial number must match the values that are in the type 89 records. From the record data shown it does not look like the values match. This is discussed where the PROCESSOR statement is described in the IFAURP control statements section of the MVS Product Management manual. Regards, Bonnie Ordonez -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IFAUSAGE REQUEST=FUNCTIONBEGIN nesting
FUNCTIONBEGIN/FUNCTIONEND can be nested for two different products (different PRODQUAL values result in unique product IDs) but if they are both registered under the same task, each of the products will receive the timing values for all work being done under that task. Regards, Bonnie Ordonez, IBM, SMF, Level 3 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Collecting SMF data with Logstreams
Decisions around how long to keep SMF data in the log streams are unique per customer installation. IBM does not make recommendations for that. For your IFASMFDL return code concerns, implementing a post processing job log 'scraper' world be useful to take specific actions based on the messages in the job log that are returned by IFASMFDL. Bonnie Ordonez, IBM, SMF Level 3 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF type and notype
TYPE and NOTYPE cannot coexist on the same statement but TYPE and NOTYPE can be specified on separate statements in the same parmlib member. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF Log Blocks
Hello Stan, SMF log blocks are mapped to include more information than just a single SMF record per block. The structure of the log block is not provided as an IBM external interface. IXGxxx services are programming interfaces, but they are not specifically intended for reading records from SMF log blocks. As you noted, the intended interfaces to retrieve SMF records from log streams are the IEFU8x exits, IFASEXIT, or IFASMFDL. There is also a 'real time' interface, provided via the INMEM SMFPRMxx option. ZEDC compressed data is decompressed by IFASMFDL or IFASEXIT. The IEFU8x exits receive the data in its pre compressed form. Regards, Bonnie Ordonez, SMF Level 3 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMF Log Blocks
You can use either of the following interfaces to extract data from the SMF log stream: IFASMFDL, which is the SMF dump utility IFASEXIT, which is the SMF Logstream Subsystem Exit These are the intended interfaces. They return SMF data in the form of SMF records rather than the entire log block of information. They are documented in the SMF manual. Bonnie Ordonez, IBM, SMF Level 3 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
