> this reminds me of some hanging IMS jobs that could neither be > cancelled nor forced because the routines for memterm could not be > loaded because of memory exhausted. Only BMC Tooling allowed to get > rid of them. > The suggestion in the PMR was to code an IEFUSI to reserve 512k > below to allow memterm to happen in any case. > > Could you please raise another internal discussion why IEFUSI has to > be coded at all in order to allow memterm to happen? > Why can't z/OS just ensure that there is always enough storage > available in the address space for memterm?
Since memterm does not access the storage of the address being terminated, there is no connection between IEFUSI and memterm. There is no requirement for any available storage in the address space being memtermed. Task termination, yes. Memory termination, no. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
