Posts

Showing posts from February, 2017

Moseley's Compiler SYSCPK on 3390 disk image for Hercules

A lot of people wish they had Moseley's 3350 disk image with all the MVT compilers in 3390 form so they can use it on more modern operating systems... (aehmmm). It's not a trivial job because certain libraries expect to be stored in a certain format, but I got my 3390 image done with all the SYSCPK stuff and it's working fine. You can find the 3390-3 disk image here: https://github.com/moshix/mvs Obviously, you need to add the volume to your Hercules configuration file. Then IPL your MVS or any other MVS-like OS (same for 24, 31 or 64 bit). Then vary it online. Then update your VATLST00 member in SYS1.PARMLIB to add this new volume. Finally, update your JES2 procedure to add a new proclib, like SYS2.PROCLIB (which you find on the SYSCPLK volume. In that proclib you find procedures for all compilers on the volume. Restart JES2 and Bob's your uncle. 

Running ASP 3.2 on IBM MVT

Asymmetric Multiprocessing System (ASP) Version 3.2 is a loosely-coupled multiprocessing extension of OS/360 and OS/VS2 Release 1. ASP provides basic spooling capabilities, similar to  HASP . In addition, ASP includes extensive support for for workload management functions, such as processor and device scheduling and dependent job control. ASP was the predecessor of JES3. The product's original name was Attached Support Processor, hence the ASP acronym. The  base ASP Version 3.2 tape  in AWS image format is available from  cbttape.org . There is an MVT system with ASP installed. The turnkey system is available for  download  from ibiblio.org. Unzip the asp.zip file and follow instructions in the  README  file. HASP is also installed on the turnkey system. More documentation on ASP will be posted here as it becomes available.

IBM MVT 21.8F Distributions for Hercules

What's MVT? MVT is a beautiful operating system. Extremely reliable and a great way to learn and understand the modern day successor (or grand-grand-grandchild), z/OS.  When IBM announced the System/360 mainframe line in April 1964, the plan was to provide just one operating system for batch-oriented use, known simply as the System/360 Operating System (less formally as OS/360, or OS). OS was big, complex and ambitious for its day, and the resulting system was late, buggy and resource-intensive. Installations that couldn't wait, or couldn't afford the hardware required to run OS, opted for one of the smaller, simpler systems that IBM created as alternatives: BOS/360, TOS/360, DOS/360. Eventually, with most of the bugs shaken out OS/360 became IBM's flagship System/360 operating system. By the time of the final OS/360 release in 1974, system programmers building an OS system had the choice of two control programs: MFT, Multiprogramming with a Fixed number of