Invalid pointer errors ERR40, ERR25, ERR43 and ERR24 from TMSPTRS

Document ID : KB000014000
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

TMSPTRS ended with RC12 and reported thousands of errors. The most of them are ERR24 with only 1 DSNB in chain. Additional errors are ERR25, ERR40 and ERR43:

 

TMS REPORT 29 - INVALID POINTERS     OPTIONS: TMC DSNB, NO ENQ                               

ERR43  DSNB 00494592 SHOULD BE END OF UNUSED CHAIN, POINTS TO 00494593                        

ERR40  01000000 DSNBS ALLOCATED, 00494592 DSNBS READ                                         

ERR25  NO END OF CHAIN FOR UNUSED DSNBS                                                       

ERR24  UNUSED DSNB 00494594IS NOT IN CHAIN AND CHAINS THRU DSNB 00494594 0000000ADSNBS IN CHAIN

ERR24  UNUSED DSNB 00494595IS NOT IN CHAIN AND CHAINS THRU DSNB 00494595 0000000ADSNBS IN CHAIN

ERR24  UNUSED DSNB 00494596IS NOT IN CHAIN AND CHAINS THRU DSNB 00494596 0000000ADSNBS IN CHAIN

ERR24  UNUSED DSNB 00494597IS NOT IN CHAIN AND CHAINS THRU DSNB 00494597 0000000ADSNBS IN CHAIN

ERR24  UNUSED DSNB 00494598IS NOT IN CHAIN AND CHAINS THRU DSNB 00494598 0000000ADSNBS IN CHAIN

ERR24  UNUSED DSNB 00494599IS NOT IN CHAIN AND CHAINS THRU DSNB 00494599 0000000ADSNBS IN CHAIN

ERR24  UNUSED DSNB 00494600IS NOT IN CHAIN AND CHAINS THRU DSNB 00494600 0000000ADSNBS IN CHAIN

ERR24  UNUSED DSNB 00494601IS NOT IN CHAIN AND CHAINS THRU DSNB 00494601 0000000ADSNBS IN CHAIN

 

...

 

 

It seems that all of the DSNBs starting at a certain DSNB number received an ERR24.

A rerun of TMSPTRS ended with RC0 and no more errors were found. Also Automatic Pointers Error Correction (APEC) did not find any error. Checking the DSNBs from ERR24 showed, that they are correctly chained and thus the errors are issued incorrectly.

What could have caused these invalid pointer errors in the TMSPTRS report?

 

Answer:

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.

Be sure SYSUT3 does not span multiple volumes. Increase SPACE in the SYSUT3 DD and/or check SMS rules if necessary to prevent this data set from going thru EOV.

 

 

 

 

 

 

Additional Information:

Following Idea has been created to enhance TMSPTRS to ensure SYSUT3 does not span multiple volumes:

https://communities.ca.com/ideas/235735270