IBM System/370 145 Manual page 172

2. One or more initialized System/370 disk volumes must be formatted
by executing the IBM-supplied disk fo.rmatting program on a
Model 145 under OS MFT or MVT control.
3. A 1400/7010 tape-to-disk utility program must be executed on a
Model 145 under emulator program control to restore the 1400/7010
data on tape to the formatted System/310 disk volume(s}.
The data records on one 1400/7010 disk track are formatted into one
fixed-length record, which is generally placed on one System/370 disk
track. If one System/310 track is not large enough to contain the
fixed-length record created from one 1400/1010 track, the Track OVerflow
feature is required on the System/310 device or another System/310 disk
device type must be used. Depending on the disk devices involved, one
system/370 disk track may be large enough to contain the data from more
than one 1400/1010 disk track, and use of the Track OVerflow feature is
an option. If used, it may result in more efficient use of System/310
direct access space. However, I/O processing time is increased by use
of the Track Overflow feature.
Job submission and operator Communication
Os job control and Model 145 1400/7010 Emulator program control
statements must
be
present for emulated 1400/7010-series object
programs. Several 1400/7010 programs can be emulated in one os job
step. subject to the restrictions listed previously, existing 1400/7010
programs need not be modified.
The required emulator control statements for emulated 1400/7010
programs are provided in a card, tape, or disk sequential data set or in
the input stream. The 1400/7010 object programs to be emulated can be
placed in the input stream, on tape, or in a partitioned data set on
disk.
An
emulator control statement describes their location.
Card input to 1400/7010 programs can be placed in the input stream to
be read by the reader/interpreter and placed in a SYSIN data set.
Alternatively, card input can
be
emulated via a tape or disk sequential
data set. Data to be printed or punched can be placed in a sequential
tape or disk data set or in a SYSOUT data set on disk for transcription
by an output writer. Use of an os reader interpreter and output writer
to hand1e unit record operations should reduce the execution time
required to emulate 1400/1010 programs.
The operator communicates with an emulator partition or region via
emulator commands that can
be
entered using the operating system
console. The commands provided allow simula't.ion of 1400/7010 console
operations and can also be used in debugging operations. The operator
can display I/O assignments, sense switch settings, etc., in effect for
an executing 1400/1010 program. In addition, the operator can alter and
dump processor storage selectively within the emulator program partition
or region.
If multiple console support (Mes) is included in the as control
program generated, emulator program messages can be routed to a specific
console device so that emulation messages are isolated. Automatic reply
routines that process 1400/7010 program messages can be user-written and
added to the generated emulator program. This facility can be used to
avoid having 1400/1010 program messages printed on a console.
Installing ~ Emulator
The following outlines the general procedure required to make the
transition from 1400/1010 system operation or stand-alone system/360
1400/7010 emulation to Model 145 emulation under as.
162 A Guide to the IBM System/370 Model 145