Re: Determining 3390 Model
The maximum realizable 3390 mod number with an EAV is 241,182. You had best allow for six digits. This number is the result of dividing 16 to the 7th power (the maximum possible number of cylinders) by 1,113 (the number of cylinders in a 3390-1). The DCE, which is findable from one of the may UCB segments and/or UCB system services, contains the number of cylinders. This number is also in the data returned with the Read Device Characteristics CCW. The DCE can also be dumped with the DEVSERV QDASD operator command. Bill Fairchild Programmer Rocket Software 408 Chamberlain Park Lane • Franklin, TN 37069-2526 • USA t: +1.617.614.4503 • e: bfairch...@rocketsoftware.com • w: www.rocketsoftware.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
Bill, Very nice indeed! I made my PL/I nickname field character(6) varying after running through a similar but not quite identical exercise. I thought I might get a question about that; but I did not, probably because no one looked at the program. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
In 511ecceb@phoenixsoftware.com, on 02/15/2013 at 04:03 PM, Edward Jaffe edja...@phoenixsoftware.com said: And be prepared to handle greater than two-digit model numbers. I know that 54 wasn't a real model number, but wasn't there an official 3390-27? -- Shmuel (Seymour J.) Metz, SysProg and JOAT Atid/2http://patriot.net/~shmuel We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
I get quite a few queries about this concerning MXI as it does not show 3390-27, 3390-54 etc in the device type fields for DASD and always use the following in my reply : (i) 3390 devices have x'200F' in UCBTBYT3+4 (ii) 3390-A have x'3E' in DCEOBRDT whereas 3390-9 have x'32' (for completeness x'24' = 3390-3, x'27' = 3390-2 and x'26' = 3390-1) (iii) Names such as 3390-27 and 3390-54 are colloquial terms that do not relate to an actual device model specification - they are just large 3390-9s split on some capacity-based ranges. What I do allow if for the user to set up their own local definitions on what they believe a 3390-27 is and they can then use this as a grouping filter (or scope as we call it) - for example : Scope=Name(3390-27),Subject(DASD),Type(Group), Expr(DASD.TOTALK/1024 8578 AND DASD.TOTALK/1024 = 27555) Scope=Name(3390-54),Subject(DASD),Type(Group), Expr((DASD.TOTALK (1024*27555) AND DASD.DEVTYPE NE 3390-A)) Rob Scott Lead Developer Rocket Software 77 Fourth Avenue . Suite 100 . Waltham . MA 02451-1468 . USA Tel: +1.781.684.2305 Email: rsc...@rs.com Web: www.rocketsoftware.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Jaffe Sent: 16 February 2013 21:36 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Determining 3390 Model On 2/16/2013 11:04 AM, Mike Schwab wrote: A is when you get to EAVs with Cylinder Allocations. 9 is non-EAV without Cylinder Allocation areas. The problem with this theory is that EAV is a z/OS software concept only. It does not apply to other operating systems. More to the point, the hardware doesn't know about track-managed space, cylinder-managed space, break-point values, etc; it knows only about the size of the volume in cylinders (or Mod1 multiples). Yet, the DS8100 (2107) hardware console--whose display I would paste in if IBM-MAIN allowed anything other than plain text--shows 3390-9 as the model number for the Mod-51 volume and shows 3390-A as the model number for the Mod-81 volume. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- 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
Re: Determining 3390 Model
The comment ine | min(i | MDLTAB.tab.ncyl = cyls) in my previous post should be | min(i | MDLTAB.tab.ncyl(i) = cyls) I need to give more attention to debugging my comments. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
The DVOL and PDS commands use the DCE (returned from UCBSCAN) to determine the 3390 model number. Until EAV, any volumes larger than a model 9 were identified as model 9. The DCE model number for EAV DASD is A. There is a SHARE requirement to document the DCE in MACLIB. Regards, John K -IBM Mainframe Discussion List IBM-MAIN@listserv.ua.edu wrote: - To: IBM-MAIN@listserv.ua.edu From: Edward Jaffe Sent by: IBM Mainframe Discussion List Date: 02/15/2013 07:19PM Subject: Re: Determining 3390 Model On 2/15/2013 4:19 PM, Dale McCart wrote: Any thing larger than a Mod 1 is listed as Mod 3 if not larger than a 3 Any thing larger than a Mod 3 is listed as Mod 9. Not true. If not Mod1, Mod2, Mod3 or Mod9, it is reported as ModA. This is true for both DS8xxx HMC and z/OS displays. DS P,8339 IEE459I 17.08.42 DEVSERV PATHS 648 UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS RTYPE SSID CFW TC DFW PIN DC-STATE CCA DDC CYL CU-TYPE 08339,3390A ,A,041,MVSEV0,12=+ 2E=+ 2107 8003 Y YY. YY. N SIMPLEX 39 39 262668 2107 SYMBOL DEFINITIONS A = ALLOCATED + = PATH AVAILABLE Note this volume is listed as 3390A aka ModA. (Mod9 would be listed as 33909.) Since the volume has 262,668 cylinders, it would be listed as Mod236 using the technique suggested earlier in this thread. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
Thanks for all replies. Our SPACE command also uses DCE to determine model number. Two points: 1. The reason I'd like to display a 'meaningful' model number is not for ordinary allocation but for volume-to-volume activities like copy (ADRDSSU) or mirroring. In such cases, it's important that the target volume match the source volume. Of course total capacity is the key, but an eyeball indicator would be helpful. We've had cases where a mismatched 'Mod-9' was incorrectly selected as target for a full-volume operation. For such purposes, all Mod-9s are not equal. 2. I tried DS P on one of our 'Mod27' volumes. It's reported as a Mod-9 rather than Mod-A: UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS RTYPE SSID CFW TC DFW PIN DC-STATE CCA DDC CYL CU-TYPE 0149E,33909 ,A,000,R13DLB,A0=+ BF=+ C3=+ AE=+ A5=+ B7=+ C0=+ C4=+ 2107 1400 Y YY. YY. N SIMPLEX 9E 9E 30051 2107 SYMBOL DEFINITIONS This volume has a capacity of 3,0050 cylinders. But it's not EAV. 3. The SPACE command is very handy for day to day operations. As a TSO command, it can be issued at READY or anywhere a command line is available. No special authorization or environment is required. . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Edward Jaffe edja...@phoenixsoftware.com To: IBM-MAIN@LISTSERV.UA.EDU, Date: 02/16/2013 08:26 AM Subject:Re: Determining 3390 Model Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On 2/16/2013 6:14 AM, John P Kalinich wrote: The DVOL and PDS commands use the DCE (returned from UCBSCAN) to determine the 3390 model number. Until EAV, any volumes larger than a model 9 were identified as model 9. The DCE model number for EAV DASD is A. As Dale McCart points out, a Mod6 volume (smaller than Mod9) is also shown as Mod9 by the DS,P command: IEE459I 08.20.48 DEVSERV PATHS 206 UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS RTYPE SSID CFW TC DFW PIN DC-STATE CCA DDC CYL CU-TYPE 08110,33909 ,O,000,T4RES1,12=+ 2E=+ 2107 8001 Y YY. YY. N SIMPLEX 10 10 6678 2107 SYMBOL DEFINITIONS O = ONLINE + = PATH AVAILABLE There is a SHARE requirement to document the DCE in MACLIB. Cheryl Watson looked this up for me in the SHARE requirements system. The SHARE requirement number is SSMVSS12002. It contains the following. Don't shoot the messenger. :\ Response Code: RJ-Rejected Date: 2012-10-26 by Response: IBM does not intend to provide a solution to this request for the following reason: Reject Reason : Technical Reject Explanation : The DCE is not intended to be an external API. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
On 2/16/2013 8:29 AM, Skip Robinson wrote: 2. I tried DS P on one of our 'Mod27' volumes. It's reported as a Mod-9 rather than Mod-A: We have various odd-sized volumes, so I did some experimentation. A Mod-51 shows as Mod9. A Mod-81 shows as ModA. I don't have a Mod-54 or Mod-55 to see for sure where the device number changes, but I suspect Mod-54 and lower is shown as Mod9 and Mod-55 and higher is shown as ModA. Does anyone have empirical evidence to confirm this? -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
A is when you get to EAVs with Cylinder Allocations. 9 is non-EAV without Cylinder Allocation areas. On Sat, Feb 16, 2013 at 12:57 PM, Edward Jaffe edja...@phoenixsoftware.com wrote: On 2/16/2013 8:29 AM, Skip Robinson wrote: 2. I tried DS P on one of our 'Mod27' volumes. It's reported as a Mod-9 rather than Mod-A: We have various odd-sized volumes, so I did some experimentation. A Mod-51 shows as Mod9. A Mod-81 shows as ModA. I don't have a Mod-54 or Mod-55 to see for sure where the device number changes, but I suspect Mod-54 and lower is shown as Mod9 and Mod-55 and higher is shown as ModA. Does anyone have empirical evidence to confirm this? -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
It depends upon what is in the table or how a set of nested if-then-else statements were written. Such code is easy to replace. Consider mdlfind: procedure(MDLTABp, cyls) returns(character(6) varying) reorder ; /* uses lub-seeking binary search to find the subscript i of the element MDLTAB.tab.ncyl(i) for which MDLTAB.tab.ncyl = cyls is a minimum, i.e., min(i | MDLTAB.tab.ncyl = cyls) If such a lub is found the return code is set to 0 and the nickname of the corresponding pseudo-3390 model is returned as the value of this function. If instead no lub is found the return code is set to 1 and a null string is returned as the value of this function. */ /* parameters */ declare (MDLTABp /* - MDLTAB */ pointer, cyls /* cylinders */ binary fixed(31,0)) nonassignable ; /* table template */ declare 1 MDLTAB based(MDLTABp), 2 eye character(8) /* eyecatcher: 'MDLTAB ' */ 2 nmd/* number of models */ signed binary fixed(31,0), 2 tab(1 refer(MDLTAB.nmd), 3 ncyl /* number of cylinders */ signed binary fixed(31,0), 3 nick /* nickname */ character(6) varying ; /* LIFO scratch storage */ declare (lo, mi, hi, retcode) signed binary fixed(31,0) ; declare (again, bounded, search_higher) aligned bit ; declare nickout character(6) varying ; /* named constants, BIF used */ declare (F0 initial(0b), F1 initial(1b), F2 initial(10b)) signed binary fixed(31,0) ; declare pliretc builtin ; lo = F1 ; hi = MDLTAB.nmd ; do again = (lo = hi) repeat(lo = hi) while(again) ; mi = lo + (hi - lo)/F2 ; search_higher = (cyls MDLTAB.tab.ncyl) ; if search_higher then lo = mi + F1 ; else hi = mi - F1 ; end ; bounded = (hi = MDLTAB.nmd) ; if bounded then do ; retcode = F0 ; nickout = MDLTAB.tab.nick(hi) ; end ; else do ; retcode = F1 ; nickout = '' ; end ; call pliretc(retcode) ; return ; end mdlfind ; This is PL/I, but it could serve as a template for another implementation. One in assembly language would be easy; one in C would be possible. The merits of such an approach are that it consistently produces a least upper bound on a cylinders value and is easily changed/extended by changing only the external table it uses. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
On 2/16/2013 11:04 AM, Mike Schwab wrote: A is when you get to EAVs with Cylinder Allocations. 9 is non-EAV without Cylinder Allocation areas. The problem with this theory is that EAV is a z/OS software concept only. It does not apply to other operating systems. More to the point, the hardware doesn't know about track-managed space, cylinder-managed space, break-point values, etc; it knows only about the size of the volume in cylinders (or Mod1 multiples). Yet, the DS8100 (2107) hardware console--whose display I would paste in if IBM-MAIN allowed anything other than plain text--shows 3390-9 as the model number for the Mod-51 volume and shows 3390-A as the model number for the Mod-81 volume. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
On Sat, Feb 16, 2013 at 3:35 PM, Edward Jaffe edja...@phoenixsoftware.com wrote: On 2/16/2013 11:04 AM, Mike Schwab wrote: A is when you get to EAVs with Cylinder Allocations. 9 is non-EAV without Cylinder Allocation areas. The problem with this theory is that EAV is a z/OS software concept only. It does not apply to other operating systems. More to the point, the hardware doesn't know about track-managed space, cylinder-managed space, break-point values, etc; it knows only about the size of the volume in cylinders (or Mod1 multiples). Yet, the DS8100 (2107) hardware console--whose display I would paste in if IBM-MAIN allowed anything other than plain text--shows 3390-9 as the model number for the Mod-51 volume and shows 3390-A as the model number for the Mod-81 volume. -- Edward E Jaffe But they did code into the DS8### the number of cylinders for the Mod 3, Mod 9, 32K cylinders, 64K cylinders, the 2 bit EAV limit, and now the 4 bit EAV value. -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Determining 3390 Model
We have an old TSO command call SPACE that gives a quick display of online DASD, tape, and some other stuff. It reports a DASD device as 3390-xx based on a table lookup using some data in the returned UCB. This command never reports a device as bigger than a Mod-9 even though the capacity may be several times that, e.g. Mod-27 or Mod-54 in common (though unofficial) parlance. It appears that nothing in the UCB indicates Mod-9, so the command may need to be modified to calculate a mythical model number based cylinder capacity, which SPACE does report accurately. Any advice? . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
As I was once told : Use the Source, Luke! On Feb 15, 2013 5:13 PM, Skip Robinson jo.skip.robin...@sce.com wrote: We have an old TSO command call SPACE that gives a quick display of online DASD, tape, and some other stuff. It reports a DASD device as 3390-xx based on a table lookup using some data in the returned UCB. This command never reports a device as bigger than a Mod-9 even though the capacity may be several times that, e.g. Mod-27 or Mod-54 in common (though unofficial) parlance. It appears that nothing in the UCB indicates Mod-9, so the command may need to be modified to calculate a mythical model number based cylinder capacity, which SPACE does report accurately. Any advice? . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -- 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
Re: Determining 3390 Model
Divide the Cylinder count by 1113. On Fri, Feb 15, 2013 at 5:13 PM, Skip Robinson jo.skip.robin...@sce.com wrote: We have an old TSO command call SPACE that gives a quick display of online DASD, tape, and some other stuff. It reports a DASD device as 3390-xx based on a table lookup using some data in the returned UCB. This command never reports a device as bigger than a Mod-9 even though the capacity may be several times that, e.g. Mod-27 or Mod-54 in common (though unofficial) parlance. It appears that nothing in the UCB indicates Mod-9, so the command may need to be modified to calculate a mythical model number based cylinder capacity, which SPACE does report accurately. Any advice? JO.Skip Robinson -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
On 2/15/2013 3:47 PM, Mike Schwab wrote: Divide the Cylinder count by 1113. And be prepared to handle greater than two-digit model numbers. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
Skip, I tried to get an APAR on this years ago. They said that QD gave the cyl# and that was all the data you should need. Any thing larger than a Mod 1 is listed as Mod 3 if not larger than a 3 Any thing larger than a Mod 3 is listed as Mod 9. Some samples from my volumes: This is a Mod 56 in size (reported as a 9) DS P,2913 IEE459I 16.00.13 DEVSERV PATHS 875 UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS RTYPE SSID CFW TC DFW PIN DC-STATE CCA DDC CYL CU-TYPE 02913,33909 ,A,011,DATAB2,10=+ 14=+ 2107 2900 Y YY. YY. N SIMPLEX 13 13 63441 2107 SYMBOL DEFINITIONS A = ALLOCATED + = PATH AVAILABLE DS QD,VOL=DATAB2 IEE459I 15.52.52 DEVSERV QDASD 677 UNIT VOLSER SCUTYPE DEVTYPE CYL SSID SCU-SERIAL DEV-SERIAL EFC 02913 DATAB2 2107921 2107900 63441 2900 0175-AHYR1 0175-AHYR1 *OK 1 DEVICE(S) MET THE SELECTION CRITERIA 0 DEVICE(S) FAILED EXTENDED FUNCTION CHECKING --A mod 6 (reported as a 9) DS P,2617 IEE459I 15.59.36 DEVSERV PATHS 740 UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS RTYPE SSID CFW TC DFW PIN DC-STATE CCA DDC CYL CU-TYP 02617,33909 ,A,057,ESAL97,10=+ 14=+ 2107 2600 Y YY. YY. N SIMPLEX 17 17 6678 2107 SYMBOL DEFINITIONS A = ALLOCATED + = PATH AVAILABLE DS QD,VOL=ESAL97 IEE459I 15.53.47 DEVSERV QDASD 698 UNIT VOLSER SCUTYPE DEVTYPE CYL SSID SCU-SERIAL DEV-SERIAL EFC 02617 ESAL97 2107921 2107900 6678 2600 0175-AHYR1 0175-AHYR1 *OK 1 DEVICE(S) MET THE SELECTION CRITERIA 0 DEVICE(S) FAILED EXTENDED FUNCTION CHECKING - Mod 3 (reported as a 3) DS P,201F IEE459I 15.58.22 DEVSERV PATHS 737 UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS RTYPE SSID CFW TC DFW PIN DC-STATE CCA DDC CYL CU-TYPE 0201F,33903 ,A,000,PAGE01,10=+ 14=+ 2107 2000 Y YY. YY. N SIMPLEX 1F 1F 1113 2107 SYMBOL DEFINITIONS A = ALLOCATED + = PATH AVAILABLE DS QD,VOL=PAGE01 IEE459I 15.54.29 DEVSERV QDASD 702 UNIT VOLSER SCUTYPE DEVTYPE CYL SSID SCU-SERIAL DEV-SERIAL EFC 0201F PAGE01 2107921 2107900 1113 2000 0175-AHYR1 0175-AHYR1 *OK 1 DEVICE(S) MET THE SELECTION CRITERIA 0 DEVICE(S) FAILED EXTENDED FUNCTION CHECKING Mod 2 (reported as 3) DS P,281F IEE459I 16.12.04 DEVSERV PATHS 315 UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS RTYPE SSID CFW TC DFW PIN DC-STATE CCA DDC CYL CU-TYPE 0281F,33903 ,O,000,KMFCL2,10=+ 14=+ 2107 2800 Y YY. YY. N SIMPLEX 1F 1F 2226 2107 SYMBOL DEFINITIONS O = ONLINE + = PATH AVAILABLE +GSVX014I SYJDM02 entered command MVS ds qd,vol=KMFCL2 DS QD,VOL=KMFCL2 IEE459I 16.12.27 DEVSERV QDASD 318 UNIT VOLSER SCUTYPE DEVTYPE CYL SSID SCU-SERIAL DEV-SERIAL EFC 0281F KMFCL2 2107921 2107900 2226 2800 0175-AHYR1 0175-AHYR1 *OK 1 DEVICE(S) MET THE SELECTION CRITERIA 0 DEVICE(S) FAILED EXTENDED FUNCTION CHECKING Dale McCart Senior Systems Programmer / zSeries, z/OS Kawasaki Motors Corp., U.S.A. 9950 Jeronimo Rd. Irvine, California 92618-2084 Telephone: (949) 770-0400 extension 2316 Fax: (949) 460-5576 E-mail: dale.mcc...@kmc-usa.com Visit our website at http://www.kawasaki.com From: Skip Robinson jo.skip.robin...@sce.com To: IBM-MAIN@LISTSERV.UA.EDU, Date: 02/15/2013 03:13 PM Subject:Determining 3390 Model Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU We have an old TSO command call SPACE that gives a quick display of online DASD, tape, and some other stuff. It reports a DASD device as 3390-xx based on a table lookup using some data in the returned UCB. This command never reports a device as bigger than a Mod-9 even though the capacity may be several times that, e.g. Mod-27 or Mod-54 in common (though unofficial) parlance. It appears that nothing in the UCB indicates Mod-9, so the command may need to be modified to calculate a mythical model number based cylinder capacity, which SPACE does report accurately. Any advice? . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -- 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
Re: Determining 3390 Model
50,000 tracks = Mod 3 150,000 tracks = Mod 9 Figure out the rest from there. Doug On 2/15/2013 6:47 PM, Mike Schwab wrote: Divide the Cylinder count by 1113. On Fri, Feb 15, 2013 at 5:13 PM, Skip Robinson jo.skip.robin...@sce.com wrote: We have an old TSO command call SPACE that gives a quick display of online DASD, tape, and some other stuff. It reports a DASD device as 3390-xx based on a table lookup using some data in the returned UCB. This command never reports a device as bigger than a Mod-9 even though the capacity may be several times that, e.g. Mod-27 or Mod-54 in common (though unofficial) parlance. It appears that nothing in the UCB indicates Mod-9, so the command may need to be modified to calculate a mythical model number based cylinder capacity, which SPACE does report accurately. Any advice? JO.Skip Robinson -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
Sure you don't need more than 3 digits? 64K Cyl * 16 EAV multiplier = 1048576 / 1113 = 942 M1s. On Fri, Feb 15, 2013 at 6:03 PM, Edward Jaffe edja...@phoenixsoftware.com wrote: On 2/15/2013 3:47 PM, Mike Schwab wrote: Divide the Cylinder count by 1113. And be prepared to handle greater than two-digit model numbers. -- Edward E Jaffe Phoenix Software International, Inc -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Determining 3390 Model
On 2/15/2013 4:19 PM, Dale McCart wrote: Any thing larger than a Mod 1 is listed as Mod 3 if not larger than a 3 Any thing larger than a Mod 3 is listed as Mod 9. Not true. If not Mod1, Mod2, Mod3 or Mod9, it is reported as ModA. This is true for both DS8xxx HMC and z/OS displays. DS P,8339 IEE459I 17.08.42 DEVSERV PATHS 648 UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS RTYPE SSID CFW TC DFW PIN DC-STATE CCA DDC CYL CU-TYPE 08339,3390A ,A,041,MVSEV0,12=+ 2E=+ 2107 8003 Y YY. YY. N SIMPLEX 39 39262668 2107 SYMBOL DEFINITIONS A = ALLOCATED + = PATH AVAILABLE Note this volume is listed as 3390A aka ModA. (Mod9 would be listed as 33909.) Since the volume has 262,668 cylinders, it would be listed as Mod236 using the technique suggested earlier in this thread. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
