On 8 March 2016 at 12:03, ESHEL Jonathan <[email protected]> wrote: > Thank you John and apologies for not doing it earlier. We did use GROUPEXTEND > initially so OA44222 was in > the package already. We also tried today to apply it specifically, but no > joy. UA71619 is preq'ed by UA72148 (the > fix of OA44222) and it does not apply due to the ISFJREAD compile failure. > The thing is that this compile error is quite strange, It is around this CALL > macro: > > CALL > (15),((R14),WORRSUM,=A(L'RECSNO),=A(1),=X'00',=X'00',=X'00',=X'00',=A(0),WORERRMG),LINKINST=BASR,PLIST4=,PLIST8=YES,MF=(E,WORCALL) > > This call looks "heavy" but there is actually nothing wrong with it. I tried > to code it in a small program and it > compiles without a problem. In the IBM source, for some reason it takes > everything from the second parameter > (WORRSUM) on as one long parameter instead of 9, so obviously the resulting > LA instruction gets an error.
I'm betting that your SMP/E is for some reason configured to pass in the COMPAT(SYSLIST) option to HLASM. The default is NOCOMPAT. The options list at the top of the HLASM listing will tell you the settings and where they came from. > If we are the only ones having this problem, we must be doing something very > weird ... If I'm right, then what's weird is where this option came from. Some other APAR that required it? But it's rare that NOCOMPAT causes problems. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
