开云体育

John, It has been a VERY LONG TIME AGO – however, I seem to remember there is a HIGH VALUES record at the end There were many tricks with the old IMS data bases – like loading in reverse sequence

Dave, You asked - WASTE OF TIME AND EFFORT (IMHO) Sorry to sound negative. -J- Jeff Bassett Bassettj@... (301) 424-3362 (office) (240) 388-7148 Cell Time spent flying - is NOT

So... a brief update in case anyone is really interested. A couple of little tweaks to the COBOL code and to the VSAM cluster setup, and it all appears to have worked. A hundred thousand segments

Many thanks for the replies. Creating the IEAAPP00 member has indeed solved the imediate problem. But, as usual, that has just meant that I've moved on to something else. I can report that both the

I think its an interesting idea but ... Not everyone is a linux user! You might need to slow it down. We already have issues with emulated tape becaus

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

Looking at the DL/1 manual in the OS360 file section ( /g/hercules-os360/files/DLI/360D-01.6.007.pdf ), on page 161, it refers to IGG019Z8 as the Channel End Appendage (CHEAPP), but

Look in the MVS 3.7 manual on Bitsavers. GC28-0681-2 OS/VS2 SPL Initialization and Tuning?Guide.? Even though it says 3.7, that's when the parameter was added, and will be applicable for MVS 3.8. I

Hi I am a novice here but I have to admit this seems very interesting: *The IEAAPP00 member did in fact exist in MVS.* Does this mean that it is possible to apply this member to MVS TK4/5 with the

Hi I am a novice here but I have to admit this seems very interesting: *The IEAAPP00 member did in fact exist in MVS.* Does this mean that it is possible to apply this member to MVS TK4/5 with the

The IEAAPP00 member did in fact exist in MVS. That TK5 does not have one simply means that no appendages are used. The member, and what appendages are and how to use them, is described starting at

Thanks for your thoughts. About the only documentation that I can find about the abend in question is in a z/OS manual. It says...... An OPEN macro instruction was issued using the EXCP access method

It's been a loooong time but ISTR the 360 version of DL/1 couldn't run on MVS. The OSAM open routines built a DEB which goes into (I think) LSQA or CSA for local protected storage. In MVS there was a

I haven't had time to do anything lately with the IMS/360 DLI tape that was being discussed here a year or so ago. But I've just had a chance to have another go at it, and I've run into what's looking

The following items have been added to the Files area of the [email protected] group. * /tapemgr.tgz ( /g/H390-MVS/files/tapemgr.tgz ) *By:* Stephen Dennis

In case you are interested in seeing what the 3850 MSS looked like when it was operating, fetching the tapes from the honeycomb, I found these videos at this

This brings back cringing memories! We were part of the bleeding edge community and has 2 3850 MSS devices. In the pre HSM days, we actually were quite successful in implementing a migration/retrieval

ISTR that JES3 had some issues if the data to be transmitted via NJE/RJE was on a MSS volume that needed to be mounted. The line would hang until everything was ready causing timeouts and line

Let me clarify a few things here: User data was never read directly from or written directly to the magnetic tapes in the MSS. There was a viertualization layer where physical disk space was allocated

Bill, Sounds like your version of my mvsInstallationResources archive, whichever you use - Windows or Linux - is not the correct match for the instructions on the page. Whenever I update these