Mainframe Stuff

MVS Utilities this repository includes some very useful utilities for people working with MVS, z/OS on real mainframes or emulated ones. Most of the topics covered by these programs are covered in my youtube mainframe channel here:  https://www.youtube.com/channel/UCR1ajTWGiUtiAv8X-hpBY7w Here are some of the programs and tools included in this repo: recv390 is a receive command for Linux or Windows. It extracts XMIT files. recv390 is by James Morrison. I made some fixes and somall enhancement to the program. compile simply with gcc -o recv90 recv390.c. SYCPLK.ccdk is a 3390-3 volume (SYSCPK) which incluedes about 10 or 12 compilers for the mainframe, including: PLI F compiler Cobol compiler from the 60s RPG compiler PL/360 compiler Pascal compiler the amazing ASSIST assembler Simula compiler Basic and many other goodies. Simply mount the volume on your system, add it to the VTLST00 member as private, and then extend your JES2 to use the included SYS2.PROCLIB

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. 

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.

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

1.  To shut down JES3 on the local, you can issue the JES3 "*SEND" command to    route a JES3 "* RETURN " command to system B:      *t,tk4b,* return    JES3 will end on system B.  You will need to enter "QUIESCE" directly on the    system B MVS console.                   To shut down JES3 on the global processore, initiate first your standard MVS shutdown procedure. In TK4, that is                 from the JES3 console (you can enter MVS commands from the JES3 console, btw)                f bsppilot,shutdown                 Once everyhting is shutdown, you stop JES3 by issuing this command on the JES3 console:                *return               The JES3 console will deactivate and you will be back on the MVS console, from which you can issue your usual z                 eod and quiesce commands.  2.  The message:      IAT3046 DISABLE ANY OTHER RUNNING JES3 PROCESSOR IN COMPLEX (DONE)    at startup isn't normal.  It gets issued if the JE

UPDATE: January 19, 2019 The procedures here work for me and hundreds of others repeatedly and I have made a video about all this which you can find on Youtube here : Prerequisites 1. Hercules 3.12/Spinhawk/4.00(hyperion) with Peter Jansen's CTC extensions I use the Hercules as provied by the latest version of Juergen Winkelmann's amazing MVS 3.8J TK4- distribution (update 8) which you can get from here.  Notice that we don't actually use the MVS3.8J distrubution at all, we only use the Hercules binaries that come with TK4-. You find them under ../hercules/linux/64/bin 2. The MVS 3.8J with JES3 distribution from Kevin's website. Notice that I have a MVS3.8A and a MVS3.8B directory. A is for the global MVS image and B is for the local MVS image. You need both TK4A:   http://www.j76.org/misc/tk4-_ update_07.jes3_2016-09-15.zip TK4B:   http://www.j76.org/misc /tk4-_update_07.jes3b_2016-10- 04.zip Or you can also get them from here :  3. any 3270 t

JES2 processing is considered to be independently controlled. Each JES2 image processes its own job input, job scheduling and job output. JES2 uses a contention-based paradigm for managing a multi-image workload. Each image “wakes up” periodically and attempts to serialize the JES2 checkpoint using a hardware serialization technique. The image that succeeds carries out job and output scheduling activities. The others go back “to sleep” waiting for another chance. There is no cooperative decision-making process. The order in which activities occur and on which images is random.   By contrast, JES3 processing is considered to be centrally controlled. One image is designated as the focal point for the entry and distribution of jobs and for the control of resources needed by the jobs. That image, called the global processor, distributes work to itself and the other images in the configuration, known as local processors. It is from the global processor that JES3 manages jobs and reso