IBM System/370 145 Manual page 231

Existing user-written Assembler and high-level language programs for
the 2540, 2501, 2520, and 1442 can
be
executed without modification
using a 3505 reader or 3525 punch with comparable features. Assembler
and high-level language programs using a combined read/punch file must
be modified to define two separate files. In all cases, job control
ASSGN statements for both reader and punch programs must be altered to
allocate a 3505 or a 3525, as appropriate.
BTMOD macros that include the optional OBR/SDR error logging
facilities must be reassembled in order 'to operate with the RMSR routine
provided in DOS Version 4. Further, RMSR and OBR/SDR in DOS Version 4
do not support error recording for terminals in QTAM programs.
Therefore, the OBR/SDR parameter in the TERMTBL macro must be removed,
and reassembly using DOS Version 4 is required.
Note that DOS Version 4 does not support System/360 models and
therefore does not include the following,support that is available in
OOS Version 3: 10K variant of Assembler
0,
Compatibility Support/30
(CS/30), compatibility Support/40 (CS/40), Autotest, and Vocabulary File
Utility Program. In addition, job control program size and minimum
batched partition si ze in DOS Ve:['sion 4 are 14K (increased from 10K).
60:30 DOS VERSION
1
AND
!
PORTABILITY
A DOS Version 3 or 4 user with multiple Model 145 systems can
generate a single operating sysbem that can be used on each system,
subject to restraints imposed by differences in hardware configurations
and engineering change levels.
A sing1'9 DOS Version 3 or 4 supervisor can also be portable among
similarly configured System/310 j~odels 135, 145, and 155 because of the
way System/310 DOS RMS routines.are structured. (DOS support is not
provided for the System/370:Model 165 .. ) During IPL, the determination
of the model in use is made 'by the initialization routine, using the
STORE CPU ID instruction. Bits .are then set in the supervisor that are
tested during RMS routine execution to determine which routine should be
used in those cases in which mod1el-dependent routines exist.
To enable a supervisor for thle Model 145 to handle the different
length CPU extended logout areas for Models 145 and 155, a new parameter
(PORT) has been added to the sys·tem generation CONFG macro. The PORT
parameter affects only the loggi]rlg of CPU extended logout data, not
supervisor portability itself.
If a supervisor for the Model 145 is generated with a PORT macro that
specifies the Model '155, when tbe Model 145 supervisor is used on a
Model 155, the 672-byte CPU extended logout for the Model 155 will be
recorded. If the PORT parameter is not included, CPU extended logout
data for the Model 155 will not lbe recorded. When a Model 155
supervisor runs on a Model 145, 1the CPU extended ,logout area will be
recorded. Since there is no CPU extended logout area on a Model 135,
the PORT parameter is not requir1ed to achieve portability of a Model 145
supervisor to a Model 135. However, when a Model 135 supervisor runs on
a Model 145, CPU extended logout::» are disabled and recording of Model
145 CPU extended logouts does
nOit
occur.
A version 4 supervisor for a
I~odel
145 is not portable to a
System/360 model; however, a Version 3 supervisor is. If a single
Version 3 supervisor is to be us~ed for both a System/370 Model 145 (in
BC mode) and a System/360 model, say 30 or 40, Model 145 should be
specified at system generation time so that MCAR and CCH are included.
Model 145 MCAR and CCH routines
'II1i11
not execute properly on a Model 30
or 40. When a DOS Version 3 sup.ervisor containing them is loaded during
IPL, MCAR and CCH are disabled automatically by the initialization
A Guide to the IBM system/370Mociel 145 221