Trying to follow-up on the stuff that Peter has suggested, I'm still
chasing that elusive '54M' - Who sets it? Where is it set? How can I
override it?
It seems you missed this statement in my first reply in this thread:
IEFUSI will gin control in the BPXAS address space before the UNIX process gets
control. OMVS set REGION to the magic value 54M. This has not meaning and will
later be replaced by the values from the originating batch job. (I don‘t know
why 54M was chosen as the indicator value.)
So, when your IEFUSI sees that value it should leave REGION and MEMLIMIT
alone.
Have tried alternate members from SYS1.IPLPARM, but none of then specify
sufficient paging space.
The 922 indicates that the initiator's ESTAE routine got control because
of another ABEND, a program check, etc. I assume your IEFUSI code has a
bug. It's not a question of paging space (Why do you think that is
related to the problem?)
Have you tried to deactivate the IEFUSI from the console?
SETPROG EXIT,MODIFY,EXITNAME=SYS.IEFUSI,MODNAME=IEFUSI
If you don't know EXITNAME and MODNAME, use
D PROG,EXITS
to get a list of active exits, then
D PROG,EXIT,EXITNAME=
to display MODNAME
--
Peter Hunkeler
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
