Reference information for DOS/VS R29 includes valid and detailed information about running POWER II (not Power/VS) on DOS/360 and is a very useful tool for understanding the POWER II system generation process.
There are two differences: R29 POWER II supported additional disk device types (3330 and 3340), and it supported five partitions. In POWER for DOS/VS R29, the POWPART generation parameter replaced the F2 parameter.
Here are the steps:
Deblock and catalog the POWER II distribution tape.
Assemble and catalog the POWER phase
Link edit the remaining POWER II phases
Define spool space
Create startup JCL for POWER II
Start POWER II and format the Queue and Data files
Link utilities for use in F2
Link Sort/Merge for use in F2
Link Assembler and compilers for use in F2
Space allocation for POWER II queue and data files is subject to a number of constraints, some of which are describedand coded in the supplied POWER generation macro. Read POWER02.JCL to review those. Here are the others
The Data File must be allocated in whole cylinders starting on a cylinder boundary.
The Data File must be large enough to hold the number of tracks defined by the track group size and the number of track groups.
The Queue File must be large enough to hold one record per track group plus one.
The Queue File must be a single extent, and if larger than a cylinder, must be allocated in whole cylinders and start on a cylinder boundary.
If the Queue File is smaller than a cylinder, the extent must be completely contained in a single cylinder.
Increasing the size of the spool space is therefore a process that requires careful analysis, a likely re-generation of POWER, and a cold start of the queue and data files. (Cold starts erase the current content of the files.)
We'll allocate a Job stream file at the beginning of SPOOL1, followed by a small Queue file. The Data file follows at 1,000 tracks, aligned on a cylinder boundary. See POWER05.JCL for specifics. Note that if you move the job stream file, you'll need to change power04.jcl as well. (And re-run both if you're changing things after the initial setup.)
Note that steps 7-9 could have been completed in the SYSGEN stage. One can link edit phases for another partition by including " ACTION F2 " (or F1) just after the // OPTION CATAL card. ACTION F2 tells LNKEDT to use F2 partition addresses when building the phase(s). But by doing the link steps here, we a) avoid adding lots of ACTION F2 cards to the job streams, and b) you get a sense of how operation with POWER II compares to operation without.
The devinit Hercules commands in the following procedure include the CRLF option. This option should be omitted if you're using Hercules on a Linux system. If you omit CRLF when using a Windows platform, you'll have to fix the resulting file for viewing with Windows notepad using the following command:
type inputfile.txt | find /v "" > outputfile.txt
The first file on the POWER II distribution tape is a card image file blocked 40 records to the block, with 81 character records (the leading character is a stacker select code). This file has four sections separated by DOS/360 end-of-file cards ("/*"). These file sections catalog, respectively:
Base function source books (POWER II generation macros)
Base function relocatable modules
Remote Job Entry (RJE) source books (POWER II RJE generation macros)
Remote Job Entry relocatable modules
POWER01 first uses the utility TPTP to deblock the tape and strip the leading stacker select card column. The rest of the job catalogs the four sections into a private relocatable and source statement library on SPOOL1. At the end of this step we'll be ready to assemble a POWER II system.
Note that the "devinit 280 ..." command typed into Hercules to mount the POWER II distribution tape below must be entered on one line, thus:
devinit 280 tape/ibm.360d052006.dos.power.II.with.rje.opt2.v4m1.aws
Review the printout to see that the tape was deblocked and modules and books cataloged correctly.
This step can be re-run if needed. You don't need to restart Hercules to rerun this step; just restart at the "devinit 00e" statement entered on the Hercules console. Respond "DELETE" when you receive "OVERLAP ON UNEXPRD FILE" messages during a restart.
No RJE support is generated in this procedure.
Accept track group size, number of track groups, and dblock size as coded in the POWER macro. These parameters are very intimately tied to the spool disk track geometry, and changing them is not trivial.
This step can be re-run as many times as needed if errors are reported.
In addition to the assembled POWER phase, there are a number of phases that must be linked.
This step can be re-run as many times as needed if errors are reported.
POWER will be started from a set of job control statements written to a disk file on SPOOL1. To save operator typing at POWER startup, the DLBL and EXTENT statement for IJSYSIN, the file that contains POWER startup JCL, will be loaded into F1 partition standard labels.
Unfortunately, setting this up is a pain in the butt. In Hercules, we can define additional unit record devices and load them that way. But more interesting is the process that would need to have followed when using DOS/360 on real hardware. Just for a trip back in time, that's what we'll do here.
We'll unassign the printer and reader from BG, batch F1, assign the printer, assign the reader, and then submit the job stream. Then restore the old printer and reader assignments.
Review the printout to verify that the partition standard labels for IJSYSIN were loaded correctly. You may re-submit the job as many times as needed without a special restart procedure. When labels are correctly loaded, continue with:
This job uses DOS/360 card to disk and disk to print utilities to load the JCL used to start POWER. The JCL to be loaded to disk is keyed starting in column two to keep the "/&" in the JCL being loaded from being interpreted as EOF/EOJ of the job that loads the JCL. Control statements for the card to disk shifts the output data one column to the left so that it will be correctly interpreted when the F1 partition is activated to run POWER II.
You can run this job as many times as you wish. If you do re-run, you'll get:
4433A EQUAL FILE ID IN VTOC UOUT SYS005=191 SPOOL1
If you do, respond DELETE on the telnet console.
POWER will be started from JCL written to disk in POWER05. We'll stop BG, batch F1, assign SYSIN to the volume containing the JCL file, start devices, and then batch f2 and start the BG partitions. Partition standard labels will also be written in F2, and the private core image library containing programs linked to run in F2 will be assigned. This does mean that partition standard labels are loaded each time F2 is started, but that is not a problem. While Partition standard labels are persistent across IPLs and partition restarts, there is no harm loading them repeatedly.
Note: In foreground partitions, "START" and "BATCH" are not synonyms. You must use the BATCH command to activate F1 and later F2. If you inadvertently "START" a partition--as I did more than once--you'll get the message "READ COMMAND NOT GIVEN." Type "CANCEL," return, and then STOP and return. Then you can try BATCH again.
POWER will start running. You'll be asked "FORMAT Q'S ?" the first time you start POWER. Respond "D" to format queue and data files. After the first start up, you can just press return to warm-start POWER. When you see the following, POWER is running.
F1 // JOB POWER STARTUP
12.10.48
F1 FORMAT Q'S ? D
F1 BATCH PARTITION(S) MAY NOW BE STARTED
F1 $OPC14I 03 PROG BUFFERS
F1 $OPC15I 17 DATA BUFFERS
If you format the queues later on, you will receive the following messages; respond "delete" as shown:
F1 FORMAT Q'S ? d
F1 POWER360.QUEUE.FILE
4733A EQUAL FILE ID IN VTOC QFILE SYS001=191 SPOOL1
F1 delete
F1 POWER360.DATA.FILE
4733A EQUAL FILE ID IN VTOC DATAFIL SYS002=191 SPOOL1
F1 delete
Continue with start commands for the spooled reader, printer, and punch, restart BG, and activate F2.
A job will run in each of BG and F2. These jobs load labels (F2) and complete partition assignments to printer, reader, and punch (BG & F2).
You'll notice that when POWER is running, you do not have to continually press enter on the Telnet console to get jobs to run to completion.
This job links a collection of system components and utilities for execution in the F2 partition. A new link step is needed because the starting address of the F2 partition is different from that of the BG partition, and DOS/360 does not include a relocating loader. The results of this step are stored in a private core image library for F2's exclusive use; step SYSGEN06 created this library earlier.
This job is very similar to SYSGEN03, but those utilities linked in SYSGEN03 that are self-relocating can run in BG or F2 without change and are not included in this job.
You will notice that you do not need to press Enter on the Telnet console for the job to start processing. POWER II will read in a deck of cards as soon as it is placed in the card reader and start is pressed (in Hercules, the devinit command takes the place of a real card deck).
When the job is complete, enter
This step can be re-run as many times as needed if errors are reported. You may need to condense system libraries by running job sysgen90 to reclaim space.
This job is very similar to SYSGEN04, but catalogs to the F2 private core image library.
This step can be re-run as many times as needed if errors are reported. You may need to condense system libraries by running job sysgen90 to reclaim space.
This step can be re-run as many times as needed if errors are reported. You may need to condense
system libraries by running job sysgen90 to reclaim space.
This step catalogs the 44K assembler and every compiler available in the DOS release 26.2 distribution in the F2 private core image library. This allows you to assemble and compile programs in F2. In a real production system, this probably would not be done, as F2 would be used for production jobs, not compiles and testing.
The PL/I compiler is linked to include support for system files on disk, as it is in BG.
This job is very similar to job SYSGEN07.
This step can be re-run as many times as needed if errors are reported. You may need to condense system libraries by running job sysgen90 to reclaim space.
POWER should be shut down prior to shutting down DOS/360, re-IPL'ing the machine, or quitting Hercules. Do the following
We won't get into the absolute silliness of having a one-character shutdown command, let alone the character that is the most frequently used in the English language. IBM didn't fix this until sometime after DOS/VS Release 29 with POWER/VS, when the shutdown command was changed to "PEND".
Actually, the one-letter "really disruptive" command is not unique to POWER under DOS/360. Many releases of VM/370 and its successors used a one-letter command ("I") to IPL a virtual machine. When issued from a privileged account, though, it was taken as a command to IPL the real hardware, immediately trashing everything running--every VM user and guest machine, including guest machines running production operating systems like DOS/VS and MVS. I don't know if current releases of VM still allow this silliness.
It is left as an exercise for the reader to figure out how I know this to be true. (Hint: I was a VM systems programmer for many years.)
When shutdown is complete, you'll see the message
1C10A PLEASE ASSIGN SYSRDR
from BG, F1, and F2. Respond with "UNBATCH" to the F1 and F2 messages to terminate processing in those partitions. Continue in the BG partition:
You may now use DOS/360 without POWER II or shut down Hercules entirely. To shut down Hercules:
Use the following commands at a command prompt to compress the four 2314 disk volumes that we just restored. It's as simple as the commands to create the disks:
cckdcomp dasd/dosres.2314
cckdcomp dasd/spool1.2314
cckdcomp dasd/wrk14a.2314
cckdcomp dasd/wrk14b.2314
Continue to the VERIFY stage.