Running job AL2DCC50 to convert CA7 R11.3 DB into Datacom, triggered several successful Logspills.
Then the Logspill job was not able to start to spill logs; See messages below.
S0053124 DATACOM:DB00133I - JOB OPEN LOGSPILL 77963 LOGSPILL S0063928
S0053124 DATACOM:DB00310I - LOG SPILL 104-1, TRACKS 3D1-162, TIMES 2019/05/02 11.37.24-2019/05/02 11.40.17
S0053124 DATACOM:DB00308I - LOG AREA IS 70% FULL, 1176 TRACKS SPILLABLE
S0053124 DATACOM:DB00311I - LOG AREA IS 75% FULL, SPILLING TRACK NONE, OUT OF 1273
S0053124 S LOGSPILL
S0053124 DATACOM:DB00311I - LOG AREA IS 80% FULL, SPILLING TRACK NONE, OUT OF 1393
S0053124 S LOGSPILL
S0053124 IEA602I ADDRESS SPACE CREATE FAILED. A STORAGE SHORTAGE EXISTS
S0053124 IEE328I S COMMAND ABORTED
Extracted from IBM Knowledge Center:
IEA602IADDRESS SPACE CREATE FAILED. text
ADDRESS SPACE CREATE FAILED. text
A request to create a new address space could not be honored because of an error or a resource limitation. In the message text:
One of the following:
- THE GETMAIN FOR THE ASCB FAILED
Storage could not be obtained from SQA for the new address space's ASCB or ASSB.
- MAXUSERS WOULD HAVE BEEN EXCEEDED
The creation of a new address space would exceed the maximum number of allowable address spaces as specified in the MAXUSER, RSVNONR, and RSVSTRT parameters in the IEASYSxx parmlib member.
- ADDRESS SPACE SERVICES FAILED
Address space services suffered an error which prevented the address space creation.
- A STORAGE SHORTAGE EXISTS
There is insufficient SQA, pageable storage, or auxiliary storage available.
- AN UNEXPECTED ERROR OCCURRED
An unexpected error occurred which prevented the address space creation.
--- System action
The system was unable to create the requested new address space. The system continues processing without the new address space.
--- Operator response
Notify the System Programmer.
--- System programmer response
Resolve the resource shortage if the problem is a shortage of SQA, auxiliary storage, or MAXUSERs. For the unexpected error cases, check the logrec data set for an error record or retry the request.
z/os, CA Datacom/AD 14.0 upgrading CA7 to 12.0
Sysprog followed the IBM message below:
Allowing the SPILL job to execute and CA7 12.0 Conversion job to run.
The root cause for us was that we were at Max on page space for our LPAR. This prevented the Logspill from running, both as a STC or batch job. Once we were able to find the heavy users of the storage we brought down the STC's, then Datacom and the Logspill jobs ran successfully.
WMT2 19122 11:42:43.68 00000090 *IRA200E AUXILIARY STORAGE SHORTAGE
WMT2 19122 11:42:43.68 00000090 *IRA206I ZFS ASID 0037 FRAMES 0000040387 SLOTS 0000268110 % OF AUX 5.5
WMT2 19122 11:42:43.69 00000090 *IRA206I MSMTOMC ASID 0129 FRAMES 0000086765 SLOTS 0000138776 % OF AUX 2.8
WMT2 19122 11:42:43.69 00000090 *IRA206I DATACOM ASID 0039 FRAMES 0000295362 SLOTS 0000133902 % OF AUX 2.7
WMT2 19122 11:42:43.69 00000090 *IRA206I *MASTER* ASID 0001 FRAMES 0000008639 SLOTS 0000129209 % OF AUX 2.6
WMT2 19122 11:42:43.69 00000090 *IRA206I CICSJLW ASID 011E FRAMES 0000030898 SLOTS 0000119594 % OF AUX 2.4
WMT2 19122 11:42:43.69 00000090 *IRA203E LOGSPILL ASID 011A SWAPPED OUT FRAMES+SLOTS 00003574 RATE 003289