After reading the $TSPL command it shows you the HASP 893 shows more detail. Did you get additional 893 messages? A sample from the $TSPL command shows:
$HASP893 VOLUME(SPOOL6) $HASP893 VOLUME(SPOOL6) STATUS=ACTIVE,AWAITING(EXTEND), $HASP893 COMMAND=(EXTEND),PERCENT=0 $HASP646 30 PERCENT SPOOL UTILIZATION $HASP630 VOLUME SPOOL6 ACTIVE 0 PERCENT UTILIZATION $HASP740 Volume SPOOL6 Extend successful. Those could be helpful. I suspect that when you do this JES may need to invoke the migration process to move data around so it can expand the HASPACE on the volume. Additional messages that could be produced (Did you see any of these?) according to the $TSPL command The $HASP003 message indicates a syntax error. The $HASP443 message indicates that specified spool volume has not been allocated. The $HASP646 message displays the percentage of total spool space in the MAS that is in use. The $HASP740 message indicates successful completion of the extension. The $HASP741 message indicates an unsuccessful extend, and returns an error code. The $HASP742 message indicates the data set could not be extended because the SPOOL volume is inactive. The $HASP743 message indicates the data set could not be extended because the SPOOL volume is a MAPPED volume. The $HASP744 message indicates the data set could not be extended because the SPOOL volume is in the wrong format. The $HASP745 message indicates the data set could not be extended due to an internal error, and indicates a diagnostic code. The $HASP893 message indicates that the command was accepted. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Lizette Koehler > Sent: Tuesday, December 09, 2014 6:00 AM > To: [email protected] > Subject: Re: What is JES2 waitning for after $TSPL(volser),SPACE=MAX? > > I would probably open an SR. The message says AWAITING is for Lists any spool > volumes whose unavailability is preventing this spool volume from draining, > most > likely because jobs which have space on that volume cannot purge. > > This may be a situation where IBM has to interpret the message. > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Peter Hunkeler > > Sent: Tuesday, December 09, 2014 5:37 AM > > To: [email protected] > > Subject: What is JES2 waitning for after $TSPL(volser),SPACE=MAX? > > > > Hi, > > We're on z/OS 2.1. I'm trying to expand a spool data set using > > $TSPL(volser),SPACE=MAX There has been free space immediately after > > the SYS1.DATASET on the disk (in fact this is the only dataset apart > > from the VTOX index). > > > > Responds to a $DSPL,L *before the $T command: > > $HASP893 VOLUME(SPL901) > > $HASP893 VOLUME(SPL901) STATUS=ACTIVE,DSNAME=SYS1.HASPACE, > > $HASP893 SYSAFF=(ANY),TGNUM=21500,TGINUSE=7, > > $HASP893 TRKPERTGB=3,PERCENT=1,RESERVED=NO, > > $HASP893 MAPTARGET=NO > > $HASP893 VOLUME(SPL902) > > $HASP893 VOLUME(SPL902) STATUS=ACTIVE,DSNAME=SYS1.HASPACE, > > $HASP893 SYSAFF=(ANY),TGNUM=349335, > > $HASP893 TGINUSE=190615,TRKPERTGB=3,PERCENT=54, > > $HASP893 RESERVED=NO,MAPTARGET=NO > > > > Response to the $TSPL(SPL901),SPACE=MAX command: > > $HASP893 VOLUME(SPL901) > > $HASP893 VOLUME(SPL901) STATUS=ACTIVE,AWAITING(EXTEND), > > $HASP893 COMMAND=(EXTEND),PERCENT=1 > > > > Since then and still after more that 30 minutes, JKES2 shows: > > $DSPL,L > > $HASP893 VOLUME(SPL901) > > $HASP893 VOLUME(SPL901) STATUS=EXTENDING,AWAITING(E2), > > $HASP893 DSNAME=SYS1.HASPACE,SYSAFF=(ANY), > > $HASP893 TGNUM=21500,TGINUSE=7,TRKPERTGB=3, > > $HASP893 PERCENT=1,RESERVED=NO,MAPTARGET=NO > > $HASP893 VOLUME(SPL902) > > $HASP893 VOLUME(SPL902) STATUS=ACTIVE,DSNAME=SYS1.HASPACE, > > $HASP893 SYSAFF=(ANY),TGNUM=349335, > > $HASP893 TGINUSE=190615,TRKPERTGB=3,PERCENT=54, > > $HASP893 RESERVED=NO,MAPTARGET=NO > > > > The explanation of $HASP893 is not helpful. What is JES waiting for? > > "E2" is the member where all the commands have been issed. There is > > one other member "M1" in the MAS. > > > > From ISPF 3.4, I can see that the data set has indeed be expanded as > > desired. > > > > Has anyone already tried this? What am I missing? > > > > -- > > Peter Hunkeler > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
