We have encountered two abends today, following the upgrade from TPX 5.0 to TPX V5.2 SP00 overnight. TPX has recovered, without any intervention.
Here is an extract from the TPX task log:
*TPX990E ABEND U0351 - MODULE=SCREENSV, TASK=RTEPROG TPX ABEND PSW 070C2000 99A6DDA8 0002000D 00000000 TPX R0 - R3 E3FA176C 0000015F 1E272868 1BFC8B80 TPX R4 - R7 1E238140 203DE000 1C05E894 00000056 TPX R8 - R11 19A6EA7F 19A6FA7E 1E33BEB0 0001D038 TPX R12 - R15 99A6DA80 00717A18 99A6F852 99A22130 TPX991I SDUMP IN PROGRESS TPX992I RECOVERY WILL BE ATTEMPTED IEA794I SVC DUMP HAS CAPTURED: 828 DUMPID=002 REQUESTED BY JOB (TPX ) DUMP TITLE=TPX990E ABEND U0351 - MODULE=SCREENSV, TASK=RTEP TPX990E ABEND S0C4 - MODULE=SCREEN , TASK=RTEPROG TPX ABEND PSW 070C1000 99A6596E 00040004 00000000 TPX R0 - R3 00000000 2010F000 1E3FB4A8 1C005400 TPX R4 - R7 1E45F7C8 00000000 2014F634 00000000 TPX R8 - R11 19A652F8 19A64DA7 1E293418 0001D038 TPX R12 - R15 99A63DA8 00717508 00000001 00000BB9 TPX991I SDUMP IN PROGRESS *TPX990E ABEND U0351 - MODULE=SCREENSV, TASK=RTEPROG TPX ABEND PSW 070C2000 99A6DDA8 0002000D 00000000 TPX R0 - R3 DF28DFEC 0000015F 1E2A4BC0 1BFD8B00 TPX R4 - R7 1E378258 1E2A4C4C 20D72014 00000BE0 TPX R8 - R11 19A6EA7F 19A6FA7E 1E513D68 0001D038 TPX R12 - R15 99A6DA80 00718AF8 99A6F852 99A22130 TPX991I SDUMP IN PROGRESS TPX993E SDUMP FAILED, RC...8..11 TPX991I SNAP IN PROGRESS, ID=001 TPX992I RECOVERY WILL BE ATTEMPTED IEA995I SYMPTOM DUMP OUTPUT 020 USER COMPLETION CODE=0351 TIME=14.38.10 SEQ=00839 CPU=0000 ASID=0022 PSW AT TIME OF ERROR 070C2000 99A6DDA8 ILC 2 INTC 0D ACTIVE LOAD MODULE ADDRESS=19A6DA40 OFFSET=00000368 NAME=TPXSCRNV DATA AT PSW 19A6DDA2 - 4110015F 0A0D47F0 C1AE50E0 AR/GR 0: 00000000/DF28DFEC 1: 00000002/0000015F 2: 00000000/1E2A4BC0 3: 00000000/1BFD8B00 4: 00000000/1E378258 5: 00000000/1E2A4C4C 6: 00000000/20D72014 7: 00000000/00000BE0 8: 00000000/19A6EA7F 9: 00000000/19A6FA7E A: 00000000/1E513D68 B: 00000000/0001D038 C: 00000000/99A6DA80 D: 00000000/00718AF8 E: 00000000/99A6F852 F: 00000000/99A22130 END OF SYMPTOM DUMP
Exit TPXUCMND SAMPLIB changed at some point since TPX 5.0 to include a buffer size calculation so that this type of error can be avoided.
In the above instance, the customer had an older version of the exit that they had previously customized. For the upgrade, they simply reassembled their old exit with the new release libraries. This did not include the new buffer calculation code.
When upgrading to a new release, you need to compare these libraries:
For example, with SAMPLIB, compare original vendor SAMPLIB to new vendor SAMPLIB.
You need to do this for all custom code that you have including JCL and PROCs.