Invalid err24 errors reported in TMSPTRS / SYSUT3 DD Allocation

Products

• CA 1 Flexible Storage

Issue/Introduction

When running TMSPTRS we are getting a large amount of invalid ERR24 messages at the end of the free DSNB chain.  Why?

Resolution

 

TMSPTRS copies the TMC to the work data set referenced by the SYSUT3 DD statement. This TMC copy is used to check for pointer errors. If this work data set spans multiple volumes, then invalid pointer errors are reported. The reason for this is, that TMSPTRS reads the first volume of the SYSUT3 multi-volume data set only and thus TMC records are missing. Typical errors are ERR40, ERR25, ERR43 and ERR24 (for all the DSNBs that are not on the first volume). Other invalid pointer errors might be issued, depending on when EOV of the first volume was reached during the copy process.

 

If the SYSUT3 DD allocation in the TMSPTRS JCL does not meet the following requirements you can get invalid errors.

1.  The allocation must be as large as your TMC.

2.  It must be on one volume.

3.  If you need more than 10,000 CYL you must use the DSNTYPE=LARGE specification in the JCL.

4. Check SMS rules if necessary to prevent this data set from going thru EOV.  Or apply rel 14.0 PTF: SO11360 

CA 1 copies the TMC to the SYSUT3 before doing the processing of the pointers and if we cannot get a complete copy then you may see invalid ERR24 messages.