We're finished with the work that can be done outside of the driving system. From here on, everything will be dome from the driving system by running jobs. Some basics of running MFT:
RDR. In the supplied config files, the reader is defined at address 00C. Output is written to a printer by a writer task called
WTR; the printer is defined at address 00E, and printed output will show up in the file
prt00e.txtas it's written. Cards punched by the virtual card punch will appear in the file
devinit 00cfilename (in the command line control panel, or)
ndeviceID filename (in the semi-graphical control panel)
privatein the command.
iaddr(in the command line control panel, or)
udeviceID(in the semi-graphical control panel)
If your system is sitting there, not doing anything, it's probably waiting for a reply to a mount request. See the preceding paragraph.
To start MFT:
hercules -f gen.cnf
HHCTE003I Waiting for console connection on port 3270
telnet localhost 3270
ipl 150(command line control panel, or)
ldeviceID (semi-graphical control panel)
IEA218I MOD=50 ASSUMED S360
IEA101A SPECIFY SYSTEM PARAMETERS FOR RELEASE 21.0 MFT
IEA217I SEREP INTERFACE ESTABLISHED
*00 IEE801D CHANGE PARTITIONS- REPLY YES/NO (,LIST)
IEE866I DEFINE COMMAND BEING PROCESSED
*00 IEE802A ENTER DEFINITION
q=(,f)is only needed the first time you IPL the system after building the system IPL volume; it tells the system to initialize the dataset used for job control. If that's specified, you'll get:
*00 IEF423A SPECIFY JOB QUEUE PARAMETERS
IEF868I 00E WTR WAITING FOR WORK P00
CLASS=Ain P1. It doesn't actually start anything, but rather allows other things to start themselves. It will produce no messages by itself.
ncommand, the reader will see that it has cards to read and read them.
The first job that you'll need to run is CTLGWRK. It has two steps:
CTLGWRK: This step catalogs the work datasets so stage 2 can find them.
MAKECTLG: This step creates and initializes the system catalog on the target MVT system.
This job has just one step. It adds the DLIB datasets to the driving
system's master catalog. The job is in
This job corrects a problem in the
SYS1.MODGEN2 dataset on
the CD: As supplied, it has a modified
IEAANIP macro, which
builds the Nucleus Initialization Program. The modified code will not build
with the rest of the system on the CD. Forutnately, the original version is
still there; this job switches it in place of the unusable one. The job is
SYS1.GENLIB has several modifications from the
standard version. While most of them are harmless, and several are actually
good, they assume an environment that doesn't apply completely here. This
job changes the source macros to eliminate the problems, and the need to
manually edit the stage 2 deck once generated. The job is in
jcl/fixgenlb.jcl. It makes all possible updates in place on
SYS1.GENLIB, but two changes require a new member, so the
dataset is allocated with extra space to accomodate that by
HASP is an add-on package, not part of OS/360 proper. It was developed
independently at the IBM Federal Systems Division in Houston. (Hence the
name, Houston Automatic Spooling Package.) As such, it needed a few
additions to the standard OS/360 programs. Most of those additions are
already in place, but two others need to be added to make the OS/360 I/O
subsystem call HASP at critical points in processing. Three system
generation macros also need to be replaced. (They cannot be updated, since
they do not have complete line numbering.) This job, in
jcl/hasphook.jcl, adds those hooks.
Up to table of contents Previous: Preparing to build MVT Next: Running the stage 1 sysgen
Last updated 29 April 2005