SMF records missing in Report 42 after LPAR migration - Endevor

Products

• Endevor

Issue/Introduction

After migrating Endevor to a new LPAR, SMF reports (such as Report #42) may stop reflecting new activity even if the C1DEFLTS table remains unchanged and action recording is enabled.

Environment

All supported versions

Cause

The issue is typically environmental. While Endevor continues to write records to the system, those records are either not being captured by the new LPAR's SMF settings or are not being extracted into the history files processed by the report.

Resolution

If Endevor was previously recording SMF data correctly and the C1DEFLTS table has not changed, follow these steps to identify why records are missing on the new LPAR:

1. Verify System SMF Collection: Ensure the new z/OS LPAR is configured to collect the specific record type assigned to Endevor.

• Check the SMFREC# value in the C1DEFLTS table (e.g., 231).
• Issue the following z/OS operator command: D SMF,OPTIONS
• Verify that the record type (e.g., 231) is listed under the TYPE parameter. If it is missing, the system programmer must update SYS1.PARMLIB(SMFPRMxx).

2. Validate the Extraction:  Utility Endevor reports do not read directly from the system SMF inventory; they read from a sequential file populated by an extraction job.

• Identify the job that runs the SMF dump utility (e.g., IFASMFDP).
• Ensure this job is updated to pull records from the current LPAR's SMF inventory into the sequential dataset used by the Endevor reporting JCL.

3. Perform a Direct Trace Test:  To confirm Endevor is successfully passing records to the operating system, add a trace DD statement to any Endevor action job (such as a Generate or Move):

• Add the following DD statement to the JCL:

//EN$TRSMF DD DISP=(MOD,CATLG),DSN=####.SMF.TRACE,
//            RECFM=VB,LRECL=27994,BLKSIZE=27998


• If this dataset is populated after the action, Endevor is functioning correctly, and the issue exists within the system extraction or reporting workflow.  Work with your systems provider to ensure the SMF dump utility includes the correct record types for the new LPAR.

 

Additional Information

For guidance on verifying the initial SMF configuration within Endevor, see KB article #244432 Checking if SMF recording is enabled.

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.