I ran a TMSPTRS job and found an invalid DSNB File sequence.
TMS REPORT 29 - INVALID POINTERS OPTIONS: TMC DSNB, NO ENQ
ERR75 CHAINING FROM BASE 112233: VOLUME 112233 DSNB 00648636 HAS INCORRECT FILE SEQUENCE, EXPECTED 00072 CHAIN PROCESSING STOPPED
ERR33 VOL 112233 HAS NO END TO DSNB CHAIN
CA/1 Flexible Storage - All Releases.
Run TMSBINQ report to get the current information for the volume.
VOL=112233,LONG
Run TMSUDSNB first, then run TMSUPDTE.
When fixing your ERR33,
TMSUDSNB
PASSWORD=CA1(TMS) >>>your password could be different, it can be found in your TMOOPTxx member.
DSNB 00648622,NOVER
REP NEXT=HEXZEROS
You will go into the TMSBINQ for the VOLSER and go all the way to the last DSNB in the chain for the VOLSER that is related. For example if the VOLSER is 112233 the attached DSNB's should be 112233. Then you will update the last found DSNB associated to the VOLSER called CURDSNB=00648622 and REP it to HEXZEROS.
Next TMSUPDTE
When fixing your ERR75, count how many DSNB's are in the TMSBINQ for the VOL and subtract 1. This case had 71 total -1 which came out to 70.
VOL 112233,NODSN
REP NUMDSNB=70
REP LSTDSNB=00648622