There was a problem with NOTE/POINT for large UNIX files in SYSLIB which was fixed by access method APAR OA59500 in 2020: https://www.ibm.com/support/pages/apar/OA59500
There were also earlier unrelated problems with UNIX files in SYSLIB such as an abend S112 which was triggered by access method security changes for APAR OA56487 and fixed by APAR OA58404. gil writes: > If SYSLIB contains UNIX directories and my program contains > nested COPY instructions, does HLASM use NOTE and POINT > to return to the point of the outer copy member? > > I know it took a couple APARs to get this finally working. > Was the fix ini BPAM, or did HLASM resort to ftell() and > fseek()? Or did it resort to an enormous buffer making > POINT unnecessary? Jonathan Scott, HLASM IBM Hursley, UK
