The problem is with the ACC11VSMI, which is a PDSE.
An attempt to ACCEPT properly applied PTFs (by Chorus Software Manager) fails when accessing ACC11VSMI, which is a PDSE.
SMP shows 27 PTFs with "accepted in error".
Job shows these SMP/E errors
GIM21802I SYSMOD ENTRY LU03447 WAS STORED IN THE CAID81 ZONE.
GIM44002S ** SYSTEM ABEND 002 OCCURRED WITH A REASON CODE OF '000000AC'X AFTER SMP/E CALLED
THE GIMDRS UTILITY TO PROCESS THE AC11VSMI LIBRARY.
GIM40800I ACCEPT PROCESSING FAILED FOR SYSMOD LU03447. SMP/E PROCESSING FAILED FOR AN ELEMENT
IN LU03447.
GIM30223E ** ACCEPT PROCESSING FAILED FOR SYSMOD LU03425. PROCESSING FAILED FOR SYSMOD LU03447,
WHICH WAS SPECIFIED ON THE ++IF REQ OPERAND.
GIM30223E ** ACCEPT PROCESSING FAILED FOR SYSMOD LU03343. PROCESSING FAILED FOR SYSMOD LU03447,
WHICH WAS SPECIFIED ON THE ++IF REQ OPERAND.
And this abend.
IEC036I 002-AC,IGC0005E,PSYACCP,SMPACCP,AC11VSMI,BF22,SYSM07, 221
NMSTR.SMP.NMC2.AC11VSMI
IEA995I SYMPTOM DUMP OUTPUT 226
SYSTEM COMPLETION CODE=002 REASON CODE=000000AC
TIME=17.40.04 SEQ=00239 CPU=0000 ASID=00B6
PSW AT TIME OF ERROR 075C1000 80E38B62 ILC 2 INTC 0D
ACTIVE MODULE ADDRESS=00000000_00E36000 OFFSET=00002B
NAME=IFG0199B
DATA AT PSW 00E38B5C - 4100303C 0A0DB20A 00509808
AR/GR 0: 009BF7A0/00E38DCC 1: 00000000/A4002000
2: 00000000/0032D24C 3: 00000000/00E38D90
4: 00000000/009BA218 5: 00000000/009FF7C8
6: 00000000/009BA4BC 7: 00000000/FFFFFF74
8: 00000000/009BA4DC 9: 00000000/009BAEC0
A: 00000000/00ECAAF0 B: 00000000/00E387EE
C: 00000000/89851A20 D: 00000000/7F49ECE8
E: 00000000/00E387EE F: 00000000/000000AC
END OF SYMPTOM DUMP
Release : 12.2
Component : NetMaster Suite
Problem with PDSE processing
The problem is with the ACC11VSMI, which is a PDSE.
Because this is an attempted ACCEPT, there is no option to back-out or remove and re-process PTFs.
There are multiple potential solutions.
1. Create new PDS and use IEBCOPY to move the members from the old PDSE to the new PDS.
Rename the files and try the ACCEPT with the PDS.
NOTE: file format of the members is converted when going from PDS to PDSE or vice versa so retain the original
dataset until you are sure everything is working.
See also IBM doc on CONVERTING PDSE'S TO PDS AND BACK
Other options that may also work
2. Re-run the job in at a later time
3. Create a new PDSE and use TSO 3.4 or IEBCOPY to move content to the new PDSE.
Rename the files to use the new one in your SMP job and try the ACCEPT again
If the product was installed with CSM, files are generated as PDSE, while the NetMaster Install utility will generate a PDS.
Both are acceptable.
Changing a library from PDSE to PDS does not negatively impact further processing in either CSM or when running batchjobs, but ensuring the PDS is sized large enough and has ample directory blocks is important.
If you are having a problem with APPLY processing see also KB 194052.