Keyboard Shortcuts
Likes
Search
Historical Question
Basically, each mass storage device held half a 3330 volume for a user.?? In a Hercules environment, a similar effect? could be a user gets a single DASD volume that is mounted when they sign in and demounted when they log off.?? This would require logic to scan the correct range of UCBs for an unused UCB then issuing?the volume mount.? And signoff would unmount the volume. It would allow the system to handle a large number of users without generating a large number of devices so all volumes are online at the same time. On Wed, Feb 19, 2025 at 11:06?PM Dave Trainor - N8ZFM via <dave=[email protected]> wrote: In the interest of the historical pats of this hobby,? having such a device available to use in Hercules might not be a bad idea, (...or maybe it is as I am speculating).? It’s not an autotape library, but it's an auto dasd library of 3330's in appearance to MVS, the support for the device is apparently in the OS already, so it’s a single address and provides a selection of 3330 volumes.? - Admittedly small in size by today's standards, but the allocation in the underlying Linux disk system is not overly large, the mechanical aspects would not exist as it's all software as a Hercules device. --
Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? |
No offense taken, it’s a fair opinion.
toggle quoted message
Show quoted text
Dave, N8ZFM ?On 2/20/25, 9:40 AM, "[email protected] <mailto:[email protected]> on behalf of Jeff Bassett" <[email protected] <mailto:[email protected]> on behalf of bassettj@... <mailto:bassettj@...>> wrote: Dave, You asked - WASTE OF TIME AND EFFORT (IMHO) Sorry to sound negative. -J- Jeff Bassett Bassettj@... <mailto:Bassettj@...> (301) 424-3362 (office) (240) 388-7148 Cell Time spent flying - is NOT deducted from one’s lifespan -----Original Message-----
From: [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]>> On Behalf Of Dave Trainor - N8ZFM via groups.io Sent: Thursday, February 20, 2025 12:07 AM To: [email protected] <mailto:[email protected]> Subject: Re: [H390-MVS] Historical Question In the interest of the historical pats of this hobby, having such a device available to use in Hercules might not be a bad idea, (...or maybe it is as I am speculating). It’s not an autotape library, but it's an auto dasd library of 3330's in appearance to MVS, the support for the device is apparently in the OS already, so it’s a single address and provides a selection of 3330 volumes. - Admittedly small in size by today's standards, but the allocation in the underlying Linux disk system is not overly large, the mechanical aspects would not exist as it's all software as a Hercules device. So the issues relating to this at the time being cumbersome and prone to breakage were all in the mechanical aspect, and it would no doubt be faster in operation. Now I have no idea the effort required to create such a device, and assume one would need to have allocated the entire disk space at the time of creation of this MSS device when adding it to a config file. But it might be interesting to have. The whole allocation is not that excessively large given our host system disk space available. I mean seriously, a Tb is trivial anymore. What are the thoughts of others? I would not be capable at the moment of creating this addition to Hercules itself to allow it to be allocated, and that may be a huge task for all I know it is. This is a question to the developers of Hercules and they no doubt have many competing priorities, this would be low priority. But it might be nice to have it none the less, as a historical artifact, still useful, ecpically since the mechanical issues would not exist. For those using MVS 3.8. It truly was a good idea at the time, and of course disk sizes and technology has passed it by, but so has technology passed by a lot of this and we still play with it. What's anyone think? Dave, N8ZFM, Louisville, KY dave@... <mailto:dave@...> dave40272@... <mailto:dave40272@...> On 2/7/25, 11:23 AM, "[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> on behalf of Charles Bailey" <[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> on behalf of txlogicguy@... <mailto:txlogicguy@...> <mailto:txlogicguy@... <mailto:txlogicguy@...>>> wrote: When I worked for IBM in Tucson, AZ, in the early 1980's, much of our data was stored on MSS. When we would run a foreground job from TSO, the application would typically output a message like: "Allocating datasets, please be patient". That is because executing a statement like "ALLOC DD(xxxx) DSN(xxx.yyy.zzz)" took a half minute to a full minute to execute. The MSS monstrosity was amazing to watch in operation. It consisted of a wall of honeycomb-like compartments where the tapes were stored. The operation of the whole contraption was mostly transparent to the user. The command to allocate a dataset would cause the picker to locate the honeycomb location where the tape was stored, retrieve it, and mount it on a device that emulated a DASD. I don't think the tape was copied to a real DASD. Data was read from and written directly to the tape, which was quite wide. I think each vertical (crosswise) stripe on the tape emulated a DASD track. When a FREE command was executed, the tape would be rewound back into the cartridge and the picker would put it back into the honeycomb. I'm not sure if any special support would be required from Hercules. I think the VOLSER of the tape appeared to the OS as just another 3330 DASD. (This is all from my distant memory of conversations with older engineers would used to work on the beast. I'm sure an internet search would yield a much better description.) Charles Bailey On 2025-02-07 00:21, Dave Trainor - N8ZFM wrote: So I am studying the OS JCL and Utilities book (Michael Trombetta) from the mid 80's, good book ,was recommended to me for the MVS 3.8j era of JCL. Am happy with it and can also recommend it. |
开云体育I did forget about not everyone using Linux or a derivative of Unix as a host. Probably a good point on adding some delay as I can certainly see that instant operation, which a software emulation would have, of this device, could certainly cause problems. How it would be implemented, one huge file vs several in a directory or collection of files would depend on the approach the programmer took to writing the device emulation. I agree the mechanical aspect of this was very interesting, and watching the video of the device work, I enjoy the watchmaking aspect of it but it seems that was also one of the main issues with its reliability.???? I also agree that TCP/IP would be nice, but also we could just run a later version of MVS and get that. ? Is most likely not worth much effort at all if its more than a trivial endeavor as the usefulness of it is not huge, ? Dave, N8ZFM ? ? ? On 20/02/2025 05:06, Dave Trainor - N8ZFM via groups.io wrote:
In the interest of the historical pats of this hobby,? having such a device available to use in Hercules might not be a bad idea, (...or maybe it is as I am speculating).?
It’s not an autotape library, but it's an auto dasd library of 3330's in appearance to MVS, the support for the device is apparently in the OS already, so it’s a single address and provides a selection of 3330 volumes.? - Admittedly small in size by today's standards, but the allocation in the underlying Linux disk system is not overly large, the mechanical aspects would not exist as it's all software as a Hercules device. Not everyone is a linux user! ? So the issues relating to this at the time being cumbersome and prone to breakage were all in the mechanical aspect, and it would no doubt be faster in operation. You might need to slow it down. We already have issues with emulated tape because rewind and unload is instant. ???Now I have no idea the effort required to create such a device, and assume one would need to have allocated the entire disk space at the time of creation of this MSS device when adding it to a config file.?? But it might be interesting to have. The whole allocation is not that excessively large given our host system disk space available. I mean seriously, a Tb is trivial anymore. It depends how you implement it. You could just use one "huge" file and have some king of mapping logic, or one file for each cartridge and actually copy them to tracks on an emulated 3330. What are the thoughts of others???? I would not be capable at the moment of creating this addition to Hercules itself to allow it to be allocated, and that may be a huge task for all I know it is.?? This is a question to the developers of Hercules and they no doubt have many competing priorities, this would be low priority.
?But it might be nice to have it none the less, as a historical artifact, still useful, ecpically since the mechanical issues would not exist.? For those using MVS 3.8.??? It truly was a good idea at the time, and of course disk sizes and technology has passed it by, but so has technology passed by a lot of this and we still play with it.??What's anyone think? I think that what was interesting about this was the mechanical aspects. Remove those and things get a little boring. Does any one run tape sorts... ??Dave,N8ZFM, Louisville, KYdave@...?? dave40272@...??? Dave |