Re: $HASP003 RC=(136) with $MSPL
Lucas, Thank you! That is exactly what I was looking for. I normally would have humbly accepted "RTFM" as a response, but I'm not sure I would have found it. The manual (in KC and the online PDF) doesn't describe it in a way that's intuitive to me, and the example they give: $dspl(*),unitdata $HASP893 VOLUME(SPOOL1) $HASP893 VOLUME(SPOOL1) UNITDATA=(EXTENT=00,TRKRANGE=(0087, $HASP893 0293),RECMAX=12,TRKPERCYL=15) $HASP893 VOLUME(SPOOL2) $HASP893 VOLUME(SPOOL2) UNITDATA=(EXTENT=01,TRKRANGE=(0001, $HASP893 001E),BASETRAK=0E,RECMAX=10, $HASP893 TRKPERCYL=15) $HASP646 2.5225 PERCENT SPOOL UTILIZATION Unit-specific information about spool volumes SPOOL1 and SPOOL2 is displayed. Note that SPOOL1 is using absolute addressing and SPOOL2 is using relative addressing. doesn't match what my system tells me (which is fortunately displayed just as plainly as you described): $DSPOOL,UNITDATA RESPONSE= $HASP893 VOLUME(vv) $HASP893 VOLUME(vv) UNITDATA=(EXTENT=00,TRKRANGE=(, $HASP893 ),RECMAX=12,TRKPERCYL=15, $HASP893 ATTRIBUTE=ABSOLUTE) I'm glad IBM improved the display. Hopefully the doc caught up in v2r3... Art On Thu, 17 May 2018 18:39:29 -0300, Lucas Rosalen wrote: >Hello Art, > >I think $DSPOOL(vv),UNITDATA would show that information in ATTRIBUTE >parm. > >--- >*Lucas Rosalen* >rosalen.lu...@gmail.com / lucas.rosal...@ibm.com >http://br.linkedin.com/in/lrosalen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: $HASP003 RC=(136) with $MSPL
Hello Art, I think $DSPOOL(vv),UNITDATA would show that information in ATTRIBUTE parm. --- *Lucas Rosalen* rosalen.lu...@gmail.com / lucas.rosal...@ibm.com http://br.linkedin.com/in/lrosalen 2018-05-17 18:15 GMT-03:00 Art Gutowski : > I've been playing around with $MIGRATE SPOOL, and have had a few degrees > of success, however, on some of our rather archaic systems, I get: > > $HASP003 RC=(136),M 775 > $HASP003 RC=(136),M SPL(vv) - Command is not allowed on a > $HASP003target volume with this format. > > This is a MERGE operation...both volumes are ACTIVE. I have read through > the various restrictions, and the messages book. While the plain text is > useful, it falls short of specifying the disallowed format. If I had to > guess, and I don't like to guess, I'd say that my target volume is using > absolute, rather than relative addressing. I have tried migrating to each > available target volume in the configuration, all with the same results. I > would assume therefore, that my source volume is also absolute, and hence a > MOVE operation to a new volume would fail as unceremoniously. > > Is there any way for me to know for certain that these volumes are > absolute, rather than relative? The $DSPOOL,MIGDATA, while useful for > selecting a target with sufficient space, does not provide this > information, and I do not see anything in the SDSF SP display to indicate > addressing mode. > > Follow up question, if I allocate and format a new spool, leaving it > ACTIVE for a MERGE, will it default to absolute addressing like the others, > or will it use relative addressing? I fear offload and COLD start might be > my only way around this mess... > > I am at z/OS 2.2 JES2, $ACTIVATE=z11, LARGEDS=Allowed, CYL_MANAGED=FAIL. > > Thanks, > Art Gutowski > General Motors, LLC > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
$HASP003 RC=(136) with $MSPL
I've been playing around with $MIGRATE SPOOL, and have had a few degrees of success, however, on some of our rather archaic systems, I get: $HASP003 RC=(136),M 775 $HASP003 RC=(136),M SPL(vv) - Command is not allowed on a $HASP003target volume with this format. This is a MERGE operation...both volumes are ACTIVE. I have read through the various restrictions, and the messages book. While the plain text is useful, it falls short of specifying the disallowed format. If I had to guess, and I don't like to guess, I'd say that my target volume is using absolute, rather than relative addressing. I have tried migrating to each available target volume in the configuration, all with the same results. I would assume therefore, that my source volume is also absolute, and hence a MOVE operation to a new volume would fail as unceremoniously. Is there any way for me to know for certain that these volumes are absolute, rather than relative? The $DSPOOL,MIGDATA, while useful for selecting a target with sufficient space, does not provide this information, and I do not see anything in the SDSF SP display to indicate addressing mode. Follow up question, if I allocate and format a new spool, leaving it ACTIVE for a MERGE, will it default to absolute addressing like the others, or will it use relative addressing? I fear offload and COLD start might be my only way around this mess... I am at z/OS 2.2 JES2, $ACTIVATE=z11, LARGEDS=Allowed, CYL_MANAGED=FAIL. Thanks, Art Gutowski General Motors, LLC -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
