ENRASW00 utility fails with Message ENCS241I and ABEND S0C3

Products

• Endevor

Issue/Introduction

Utility ENRASW00 fails with message ENCS241I (Invalid SMF record read) and a subsequent ABEND S0C3. This occurs when reporting SMF records written in ESI warning mode.

Cause

The error occurs when the utility reads a record from the input dataset that is shorter than the acceptable minimum length for a standard SMF record.  An SMF record requires a minimum length of 104 bytes.

The SMF records written by Endevor ESI in warning mode are longer than 104 bytes. Therefore the root cause is likely in the process that copied the records from the SMF datasets to the input dataset read by ENRASW00

 

Resolution

Review the creation process of the input SMF datasets to ensure records are not truncated.

If you need to check that the SMF records written by the Endevor ESI are correct, run ENRASW00 using data captured by the EN$SMESI DD with these steps:

1. Run an action in batch that produces at least one message C1E0107I (user restricted)
2. Add EN$SMESI DD to the the JCL defining a sequential dataset with RECFM=VB, LRECL=6114, and BLKSIZE=6118.
3. Execute ENRASW00 using the above dataset as input,
4. Ensure that both the batch action and the report utility use the same C1DEFLTS table so they use the same SMF record number (parameter SMFREC#)

When EN$SMESI DD is present in the JCL, Endevor ESI writes to it a copy of each warning record written to SMF. Therefore, if ENRASW00 does not fail when reading that dataset, it means that the SMF warning records written by ESI are correct.