Had a recent report of an APK460S on z/OS, loading from a PC to the mainframe.
APK460S
TRIGGERS SATISFIED, BUT INDEXES WERE INCOMPLETE AT END-OF-FILE.
The TRIGGERn parameters specified in the parameter file were met, but the end of the file was reached before the INDEXn parameters were located.
In that case that means that while this trigger was found
TRIGGER1=*,1,X'31',(TYPE=GROUP)
But then based on that trigger the index was not found.
FIELD1=2,17,30,(TRIGGER=1,BASE=0)
INDEX1=X'53454354494F4E4944',FIELD1,(TYPE=GROUP,BREAK=YES)
Cause and resolution:
The mainframe would double-space before printing the change details line.
Windows still does the double-space when the report prints, but indexing was thrown off by 1.
After updating the FIELD1 line to look down 1 line instead of 2 all is well.