Re: support mod-27
I think it does A couple of ideas to find it out experimentally: - have a look at $DASD$ CONSTS S, it list maximum sizes of all supported DASDs - just try: add a minidisk with the size of a mdl 27 and run DIRECTXA, not supported if DIRECTXA complains about the size. Kris, IBM Belgium, VM customer support The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 2006-10-03 22:32:42: Does zVM 5.1 support or recognize a mod-27?
Re: support mod-27
We're completely mod-27 now, and moved to these before implementing zVM 5.2, so yes, 5.1 does support them. -- .~.Robert P. Nix Mayo Foundation /V\RO-OC-1-13 200 First Street SW /( )\ 507-284-0844Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Duane Weaver Sent: Tuesday, October 03, 2006 3:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: support mod-27 Does zVM 5.1 support or recognize a mod-27?
Re: support mod-27
This is one of those things that would be a nice-to-have addition to the reply from a QUERY rdev or QUERY DASD vser command. It undoubtedly is not worth modifying the command just for this, but could be easily added when other modifications are being made to the command. I have an EXEC that I use to extract the size of a DASD device from the RDEV and display it. I will post it if anyone wants it. Caveat: We have only 3390-03 and 3390-09 FBA DASD, so nothing has been done to verify the results on other devices. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Kris Buelens Sent: Wednesday, October 04, 2006 1:45 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: support mod-27 I think it does A couple of ideas to find it out experimentally: - have a look at $DASD$ CONSTS S, it list maximum sizes of all supported DASDs - just try: add a minidisk with the size of a mdl 27 and run DIRECTXA, not supported if DIRECTXA complains about the size. Kris, IBM Belgium, VM customer support The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 2006-10-03 22:32:42: Does zVM 5.1 support or recognize a mod-27?
Re: support mod-27
The following CP command displays the size of a DASD device. CP Q DASD DETAILS rdev -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Schuh, Richard Sent: Wednesday, October 04, 2006 10:14 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: support mod-27 This is one of those things that would be a nice-to-have addition to the reply from a QUERY rdev or QUERY DASD vser command. It undoubtedly is not worth modifying the command just for this, but could be easily added when other modifications are being made to the command. I have an EXEC that I use to extract the size of a DASD device from the RDEV and display it. I will post it if anyone wants it. Caveat: We have only 3390-03 and 3390-09 FBA DASD, so nothing has been done to verify the results on other devices. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Kris Buelens Sent: Wednesday, October 04, 2006 1:45 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: support mod-27 I think it does A couple of ideas to find it out experimentally: - have a look at $DASD$ CONSTS S, it list maximum sizes of all supported DASDs - just try: add a minidisk with the size of a mdl 27 and run DIRECTXA, not supported if DIRECTXA complains about the size. Kris, IBM Belgium, VM customer support The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 2006-10-03 22:32:42: Does zVM 5.1 support or recognize a mod-27?
Re: support mod-27
Q DASD raddr DETAILS reports the number of cylinders. Brian Nielsen On Wed, 4 Oct 2006 09:13:56 -0700, Schuh, Richard [EMAIL PROTECTED] wrote : This is one of those things that would be a nice-to-have addition to the reply from a QUERY rdev or QUERY DASD vser command. It undoubtedly is not worth modifying the command just for this, but could be easily added when other modifications are being made to the command. I have an EXEC that I use to extract the size of a DASD device from the RDEV and display it. I will post it if anyone wants it. Caveat: We have only 3390-03 and 3390-09 FBA DASD, so nothing has been done to verify the results on other devices. Regards, Richard Schuh
Re: support mod-27
Sorry, got the syntax backwards. Should be: Q DASD DETAILS raddr Brian Nielsen On Wed, 4 Oct 2006 11:24:44 -0500, Brian Nielsen [EMAIL PROTECTED] wrote: Q DASD raddr DETAILS reports the number of cylinders. Brian Nielsen
Re: support mod-27
I wish all my wishes were fulfilled that easily. :-) I can scrap my EXEC. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Brian Nielsen Sent: Wednesday, October 04, 2006 9:26 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: support mod-27 Sorry, got the syntax backwards. Should be: Q DASD DETAILS raddr Brian Nielsen On Wed, 4 Oct 2006 11:24:44 -0500, Brian Nielsen [EMAIL PROTECTED]= wrote: Q DASD raddr DETAILS reports the number of cylinders. Brian Nielsen
Re: support mod-27
Now that is worth something. It comes back with the number of cylinders, not just model. It use to be that model ment somethingthe number of cylinders you could expect. But I've hit too many times, and I've done it also, had the dasd system create small packs. Perhaps it was due to a small amount of space left over in the raid. Perhaps there as a real lock file that only needed to be a few cylinders in size. One of the first things I do with a new or upgraded VM system is to create a $END$ user that specifies the last cylinder of the pack. Then diskmap will show the gap between the last mdisk and the end off the pack. Perhaps we could get the diskmap support people to use this command to query how many actual cylinders there are and report the ending gap if there is one. I came across one VM site (little VM usage, mostly for guest machines, hence never hired a qualified VM systems programmer before), that only used 1/3 of their disk. They had 3390-3 defined, but when VM was laided down as only using 1113 cylinders, and diskmap didn't show the remaining 2226 cylinders, they only used the first third of each pack. Tom Duerbusch THD Consulting [EMAIL PROTECTED] 10/4/2006 11:19 AM The following CP command displays the size of a DASD device. CP Q DASD DETAILS rdev
Re: support mod-27
Yeah. I've scrapped a lot of code myself after IBM implemented functionality that made it obsolete. (Anyone want code to dynamically change the LOGO on VM/370 or VM/SP?) Brian Nielsen On Wed, 4 Oct 2006 09:40:00 -0700, Schuh, Richard [EMAIL PROTECTED] wrote : I wish all my wishes were fulfilled that easily. :-) I can scrap my EXEC . Regards, Richard Schuh
Re: support mod-27
On Wednesday, 10/04/2006 at 11:51 EST, Tom Duerbusch [EMAIL PROTECTED] wrote: Now that is worth something. It comes back with the number of cylinders, not just model. It use to be that model ment somethingthe number of cylinders you could expect. But I've hit too many times, and I've done it also, had the dasd system create small packs. Perhaps it was due to a small amount of space left over in the raid. Perhaps there as a real lock file that only needed to be a few cylinders in size. Of course, since there isn't a 3390 Model 27 (just a 2105 with 32K cylinders) it wouldn't make any sense to display such a thing. And you're right - the model number is irrelevant for dasd any more since you can no longer infer actual cylinder count from the model number (just the maximum). Perhaps we could get the diskmap support people to use this command to query how many actual cylinders there are and report the ending gap if there is one. Requirements, dude, requirements. :-D Alan Altmark z/VM Development IBM Endicott
Re: support mod-27
Thanks That did show ending gaps, but dirmap isn't a rexx exec that I could modify I have diskmap modified to display the device type and the VSE volid, for minidisks: VOLUME USERID CUU DEVTYPE START ENDSIZE VM300B $ALLOC$300B 3380 0 0 1 3380-3 Y2KESA2 144 3380 1 02225 02225 TOTAL1 DOSESA2 14D 3380 02226 03109 00884 CODE02 TSTESA5 228 3380 03110 03330 00221 DB2STR 33313337 7 GAP $ENDPAK$ 300B 3380 03338 03338 1 3380-3 I do have to keep the user direct updated with the proper VSE volsers and $alloc$ with the proper device model (nothing magical happening behind the covers), but it sure serves the purpose I intended. Tom Duerbusch THD Consulting [EMAIL PROTECTED] 10/4/2006 2:04 PM DISKMAP was created in the times that DIRMAP was not standard available in VM, it was part of IPF, later CUF, available at extra cost. Forget about DISKMAP and use DIRMAP. DIRMAP will report gaps at end-of-volume, and it does not report fullpack mindisks as overlap. DIRMAP gives a non-zero returncode when it finds overlaps, etc We define a user FULLPACK that has a fullpack minidisk for each volume, user FULLPACK is exclude in all our backup templates. MAINT 123 no longer exists, but is a LINK to FULLPACK . Kris, IBM Belgium, VM customer support The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 2006-10-04 18:51:31: Now that is worth something. It comes back with the number of cylinders, not just model. It use to be that model ment somethingthe number of cylinders you could expect. But I've hit too many times, and I've done it also, had the dasd system create small packs. Perhaps it was due to a small amount of space left over in the raid. Perhaps there as a real lock file that only needed to be a few cylinders in size. One of the first things I do with a new or upgraded VM system is to create a $END$ user that specifies the last cylinder of the pack. Then diskmap will show the gap between the last mdisk and the end off the pack. Perhaps we could get the diskmap support people to use this command to query how many actual cylinders there are and report the ending gap if there is one. I came across one VM site (little VM usage, mostly for guest machines, hence never hired a qualified VM systems programmer before), that only used 1/3 of their disk. They had 3390-3 defined, but when VM was laided down as only using 1113 cylinders, and diskmap didn't show the remaining 2226 cylinders, they only used the first third of each pack. Tom Duerbusch THD Consulting
