Hi,

We have an RDT Mainframe server which we recently IPLed because the SPOOL became full. After doing a warm/cold start, we encountered the following errors:

1. "$HASP003 SPOOLDEF VOLUME - DATA IS TOO LONG"
2. This was followed by "$HASP469 REPLY STATEMENT , CANCEL, OR END". The reply given for this was "CANCEL"
3. Then we encountered "$HASP428 CORRECT THE ABOVE PROBLEMS AND RESTART" followed by "$HASP085 JES2 TERMINATION COMPLETE"
4. This was followed by another error "*BPXP007E STARTING PHYSICAL FILE SYSTEM ZFS IN ADDRESS SPACE ZFS"
5. Finally "$HASP358 NO ACTIVE SPOOL VOLUMES" error is repeating over and over again in about 30 secs interval. 

Our RDT is hosted on a linux machine and we have tried restarting the linux machine as well with no success. Please refer to the attached snapshots of the log. It would be really helpful if anybody can provide some pointers on what might be going wrong. 

Thanks & regards,

Niranjan

Hi Niranjan,

It looks like the VOLUME value for the SPOOLDEF is bad.  Try responding to the message VOLUME=HDSYS which is the default value that was shipped with the ADCD.  If that allows your system to IPL then the JES2PARM member must be updated in order to correct the problem.  On 1.13 systems the default member is found in ADCD.Z113H.PARMLIB(JES2PARM).  For future reference the VOLUME parameter field is limited to 4 to 5 characters and that's why the error is occurring because your current value is 6 characters long.  Also if needed here are instructions on bringing up a single stand-alone system so that you are able to correct errors that prevent system IPL:

1.  Get the device address of SARES1 in the devmap. Below, I assume it is 0ACA
2.  Do not use runzpdt. Issue "awsstart devmap" where devmap is your devmap
3.  Enter "x3270 -port 3270 mstcon@localhost &" where mstcon is the name of the 3270 session in your devmap. This brings up the MVS console
4.  ipl 0ACA parm 0ACASA    (SA is the parm for the backup resident volume)
5.  After logging on to TSO and changing parms, issue S SHUTSA to shut down all systems
6.  After systems shutdown, enter $PJES2 to end jes
7.  Issue awsstop from linux terminal where you did awsstart

Let us know if this corrects the problem.

Regards,

Rick

Hi Rick,

Thank you so much for the reply.

We tried to respond using "R 01,VOLUME=HDSYS" but it did not accept the command (incorrect syntax). Please let us know how to send the response.

We followed the instructions for bringing up a single stand-alone system. We were able to execute instructions 1 - 3 but are stuck at 4th because, our device address for SARES1 is "0a94". We are not able to find the SA parm. Please let us know where we can find this value. We have tried "ipl 0a94 parm0a9401" and "ipl 0a94 parm0a9443" but we got an Informational message "AWSEMI307I Warning! Disabled Wait CPU 0 = 00020000 00000000 00000000 00000000".

Our team has no experience on the administration side and so I am asking the above questions. Please let us know.

Thanks & regards,

Niranjan

Hello Niranjan,

Have you tried to reset your spooldef using $T SPOOLDEF command https://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.hasa200/sjes2se.htm and then $S SPOOL to start it again https://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.hasa200/ssv.htm

I assume you can enter these commands when you get the $HASP003 error.

Hope that helps,

Olivier

Hi Olivier,

We have tried "$T SPOOLDEF,VOLUME=nnnn" command but we do not know the "4-character prefix assigned to JES2 spool volumes". Is there any way we can find out this value without logging into TSO region. The TSO region is down.

Regards,

Niranjan

I had more thought you would use $T SPOOLDEF,VOLUME=HDSYS as Rick suggested. Have you tried that as well?

VOLUME=(volume | *)

If no generic characters are specified, volume specifies a 4 or 5-character prefix to be assigned to JES2 spool volumes; volume must be the first 4 or 5 characters of the existing prefix.

Hi Olivier,

We did try "$T SPOOLDEF,VOLUME=HDSYS" but we got an error message.

Currently we are trying with the standalone IPL suggested by Rick and awaiting his reply.

Please let us know if you know what parms need to be modified.

Regards,

Niranjan

Hi Niranjan,

When bringing up the standalone system the ADCD datasets that make up your normal system are not catalogued.  However you can still access them by viewing the volume that they reside on.  So when on the backup system look at the HDRES1 volume.  From here you can modify your PARMLIB members.

Regards,

Rick

Hi Rick,

Thank you so much for your support.

We followed your instructions, got the stand alone system and updated the SPOOLDEF volume from HDSYS1 to HDSYS in ADCD.Z113H.PARMLIB(JES2PARM). 

We have now performed a succesful IPL and the users are able to access the system.

Thank you again for the solution :) 

Regards,

Niranjan

Hi Rick,

After following instructions 1-4, we were able to login to stand alone TSO.

But we can't find the dataset "ADCD.Z113H.PARMLIB". We have another dataset "ADCD.ADCDSA.PARMLIB" which has the member JES2PARM with SPOOLDEF VOLUME=SARES.

Please let us know what parms we have to change in this member as we cannot find any instance of "HDSYS" or HDSYS1" in this member.

Regards,

Niranjan