Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
IEF352I z/OS MVS System Messages, Vol 8 (IEF-IGD) SA38-0675-02 |
|
IEF352I ADDRESS SPACE UNAVAILABLE ExplanationWhen ending a batch job, started task, or TSO user, the initiator/terminator found that this address space had been used to provide services to other address spaces through space-switching PC routines. In order to maintain system integrity, the address space is ended and is marked as unavailable. This does not necessarily indicate an error in the program or in the initiator. System actionThe system ends the current job, started task, or TSO user normally. The address space is also ended and the address space identifier (ASID) is marked as unavailable. This ASID might be temporarily or permanently unavailable. If a batch job caused this situation to occur, the initiator in this address space will be ended and then automatically restarted in another address space. System programmer responseDetermine which program established the outstanding space switch entries. If it is determined that no error exists, then no action needs to be taken. If an error does exist, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM® Support Center. Note: If batch jobs, started tasks, or TSO users that create
unusable ASIDs end enough times, they will exhaust all available ASIDs
and an IPL will be required. When IPLing is not an acceptable option,
determine which programs caused the problems and fix them. Contact
the IBM Support Center for information about fixing
these programs.
For methods that prevent running out of ASIDs, see z/OS MVS Programming: Extended Addressability Guide. SourceInitiator/terminator ModuleIEFSD166 Routing code2,11 Descriptor code6 |
Copyright IBM Corporation 1990, 2014
|