Maintenance up to APAR PH39324 covers all known problem with USING/DROP, so this is either something new or a weird usage error.
I think you'll need to find out how to raise a support case, as we are not supposed to provide "unofficial" support by email. However, if you can create a tiny test case which you can post on this list then we or others might be able to work out what has gone wrong. Jonathan Scott, HLASM IBM Hursley, UK John writes: > Hi Jonathan > > These are the latest APARs reported by "*PROCESS INFO" and it is on a z/OS > 2.05 system at put 2109. > This is on the CBT LPAR and, as I am not the SYSPROG, I don't know how to > raise a support case. I do have a version of the source with all the MACRO > invocations commented out and replaced with the generated code together with > a listing which I can send to you if that is OK.
