As promised, here's more about VS1 6.7. Much of this announcement will probably repeat things I said in the VS1 6.0 announcement, but I'll try to explain things if I can in the context of VS1 6.7.
The VS1 6.7 system we found has a nasty bug that prevents display consoles from initializing correctly. It looks like a timing bug: display console initialization tries to use fields that haven't yet been initialized, and abends as a result. When it looked like we were going to have a fully-functional VS1 6.0 system, I decided to leave 6.7 until later. Because of the APF problems with 6.0, I got back to 6.7. After resolving several incidental problems along the way, I've developed a usermod to circumvent the console initialization bug, allowing display console initialization to work correctly.
Thus we now have a tape of VS1 Release 6.7 distribution libraries, and a usermod to allow VS1 6.7 to work correctly. Initially, you will generate VS1 6.7 and IPL it with a printer-keyboard console and no display consoles, to avoid the display console initialization bug. Once you have the VS1 6.7 environment built, you can then install the usermod to circumvent the display console initialization bug, which will let you IPL with display consoles.
Eventually there will be a prebuilt 6.7 system. For now, though, I've posted the DLIBs as well as the jobs I'm using to build a 6.7 system that I will use to create a prebuilt system. As I've said before, this is a work in progress; everything worked for me, but you need to verify everything to make sure it will work for you.
To generate a new VS1 system, you have two options. You can use an existing system, perhaps the MVS Turnkey system, as the generating system. Or you can use the VS1 6.0 starter system as your generating system. The OS system generation process imposes a peculiar requirement: distribution libraries must have "SYS1" names (there's no way to specify a high-level qualifier for DLIBs), and they must be cataloged (you can't specify a DLIB volser). If you're using an existing OS/VS system as your generating system, you can create a VSAM user catalog that has the DLIBs cataloged in it, and specify that catalog as a JOBCAT in your stage 2 jobs. Alternatively, you can use the VS1 6.0 starter system as your generating system, and catalog the VS1 DLIBs in its system catalog.
I've provided and tested generation jobs for each option. Job files with "starter" in the file name set up the environment for using the VS1 6.0 starter system and its system catalog. Job files with "nonstarter" will build the DLIB user catalog and insert a DD statement for it in stage 2 jobs. You can do it either way. If you go the "nonstarter" route, your generating system must support VSAM and have a VSAM master catalog (which is guaranteed to be true for every MVS system).
VS1 6.7 has SMP Release 4. This will make maintenance and modification of the 6.7 system much easier than 6.0.
The files are in the "Files" section of the H390-OSVS group, in the "VS1 Release 6.7" directory. They are:
o zdlf67_vs1-6.7-unloaded-dlibs_2021-04-22.zip
o zdlf67_vs1-6.7-unloaded-dlibs_2021-04-22_tapemap.txt
A zipped labeled AWS tape (ZDLF67) of VS1 6.7 DLIBs unloaded with IEBCOPY, and a map of the ZDLF67 tape.
o vs167gen_2021-06-11.zip
A zip file containing the jobs that I've been using to test building a system from these DLIBs. The system I've been working on is the one I will eventually use to generate a prebuilt system, hence the name "generating-system" scattered throughout file names. I'll post a more detailed description of the files in this zip file in a bit.
When I posted the VS1 6.7 files, I moved the VS1 6.0 starter system to its own directory. That directory is called "VS1 6.0 Starter System", and contains the files:
o vs1r60_starter_3330.zip
o vs1r60_starter_3330_tapemap.txt
A zipped unlabeled AWS tape of the IBM VS1 6.0 starter system, and a map of the starter system tape. This is a pretty basic system that doesn't have VSAM or SMF or most other options. The first file on the tape, which you won't need, has IBCDASDI followed by IBCDMPRS. The second file on the tape is an IEHDASDR dump of a 3330 VS1 6.0 sysres volume, which you can restore using IEHDASDR.
BUT.... you won't need to download the starter system tape and restore it. The vs167gen_2021-06-11.zip file already includes the VS1 6.0 starter system restored to tape, in the dasd/ directory, file dliba1.150.cckd. I made a couple of minor modifications to the starter system configuration (increasing the partition size, increasing the SWA size) and cold started it, so all you have to do is IPL it.
In addition to the "VS1 Release 6.7" and "VS1 6.0 Starter System" directories, there is another directory: "Support-Programs". In it is a tape I've built containing all the OS compilers that IBM says were supported under SVS, along with their subroutine libraries. The "Support-Programs" directory contains:
o zsup2a_sys2link_2021-06-11.zip
o zsup2a_sys2link_2021-06-11_tapemap.txt
A labeled AWS tape (ZSUP2A) of a SYS2.LINKLIB containing OS COBOL, FORTRAN and PL/I compilers and their subroutine libraries, and a tape map of the ZSUP2A tape. There is a job in the generating-system/ directory to restore the files from the ZSUP2A tape, so you need to obtain the tape before you can run that job.
Several user modifications have been developed for VS1 6.7. User modification jobs, along with an index of user modifications, will be found in the usermods/ directory in the vs167gen_2021-06-11.zip file.
A complete listing of VS1 user modifications I've created is at:
In a future post, I will describe the sysgen process and sysgen jobs in more detail.
--
