APAR status
Closed as canceled.
Error description
This APAR is meant to help debug when customers are missing SMF type 74.4 records (Coupling Facility RMF records). It also contains a second section of steps to verify if any RMF SMF record is missing (SMF type 70-79 records). Part 1. RMFGAT (Monitor III) gathers for record types 74.4 (CF), 74.2 (XCF) and 74.3 (OMVS). If you are missing these records, the first thing to verify is that you have RMFGAT started. Part 2. -If you are missing any RMF type record, the first thing to check is if you have asked RMF to monitor for it. Check the MON I parmlib member to make sure CACHE is specified (and not NOCACHE) for example if you are trying to generate Cache reports. The MON I parmlib member is ERBRMF00. Also, check the SMF parmlib member SMFPRMxx for TYPE and NOTYPE parameters to see if SMF is suppressing any record types. -Sort records prior to running the postprocessor. We have seen unpredictable results with unsorted records including missing records messages -If you are running RMF 2.4, you can run a program called ERBSCAN against the dumped RMF records data set (you can never use the MANX data set with the postprocessor). This will show what records are contained in the data set. Use this tool to verify that you indeed have missing records. Otherwise, use the IFASMFDP program to dump the record type and subtype you are interested in. This will also verify if the records are truly missing. Syncsort users should reference APAR OW31343 Please see the RMF User's Guide and Report Analysis Manual for further information.
Local fix
ADDITIONAL KEYWORDS: TYPE74 SUBTYPE4 TYPE74.4 SMF74 SMFtype74 subtype2 subtype3 st2 st3 st4
Problem summary
Problem conclusion
Temporary fix
Comments
Info APAR only.
APAR Information
APAR number
II11486
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1998-10-22
Closed date
2001-05-29
Last modified date
2001-05-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"001"}]
Document Information
Modified date:
09 September 2020