Preparing the Real I/O Configuration File (DMKRIO) The real I/O configuration file consists of macros that describe the I/O devices, control units, and channels attached to the real System/310. uses this information to schedule I/O operations and to allocate
resources. Therefore, the real I/O macro entries must represent the
real hardware configuration accurat.ely. Generally, there must be one
real I/O macro entry for each hardware unit in your configuration. You can include entries for more devices than your installation has
so that devices can be added in the future without performing another
system generation, but bear in mind that the control blocks generated (RDEVBLOK, RCUBLOK
i
and RCHBLOK) occupy space in real storage.
When preparing the RDEVICE and RCTLUNIT entries, refer to "Appendix
B: Con figuration Aid" to assist you in configuring control units and
devices. Following the descriptions of the CLUSTER, TERMINAL, RDEVICE, RCTLUNIT, RCHANNEL, and RIOGEN macros, there is an example showing how
these macros are coded for one particular real configuration.
The macros, in their proper sequence, are:
The Qni TQ Remote Display Stations RDEVICE RCTLUNIT RCHANNEL RIOGEN file is CSECT CLUSTER TERMINAL RDEVICE RCTLUNIT I/O Devices Control Units Channels System Console
placed in the reader
macro
1
macro
1
macros
macros
RCHANNEL macros RIOGEN macro
END
as follows: IThere must be a CLUSTER macro for each 3270 control unit for remote 3270s. Each CLUSTER macro must be followed immediately by the TERMINAL macros representing each display station and printer on that control
unit. The CLUSTER and TERMINAL macro groups must precede all the other
real I/O configuration macros. See the special requirements for the TERMINAL macros for devices attached to the 3214 Model 1C in the
section on "Coding the Real I/O Configuration Macros for Remote 3270s." Part 2. Defining Your VM/310 System 133
Real I/O Configuration File All the groups of CLUSTER and TERMINAL macros must appear first,
followed by all RDEVICE macros, all RCTLUNIT macros, all RCHANNEL
macros, and finally by the RIOGEN macro. In addition, the first
statement in the file must be the DMKRIO CSECT statement (as shown) and
the last statement must be the assembler END statement.
Coding the Real I/O Configuration Macros for
Remote 32705 Two types of remote 3210 configurations are supported: a cluster
control unit 3211 with multiple terminals and printers attached and
standalone display stations. The clustered configurations attach to
either a 3211, 3274 Model 1C, or 3276 control unit, all of which are
coded as a 3271. The standalone station is a 3215 display station which
contains its own built-in control unit. All remote configurations are
attached via binary synchronous communication lines.
To define remote 3270 stations you must code and RDEVICE macros. Code one RDEVICE macro for each binary synchronous line
that supports a remote 3270 configuration. Code one CLUSTER macro to
define the 3210 control unit for each of those lines and code one or
more TERMINAL macros, as needed, to define the devices in the remote 3270 configuration.
The CLUSTER macro defines the control unit (3271, 3274 Model 1C,
3275, or 3276) for the remote 3270 configuration. Each CLUSTER macro
must have a unique label. This label is coded on the RDEVICE macro that
defines the corresponding binary synchronous line and thus logically
links the line and the cluster. The address of the line (defined by the ADDRESS=cuu operand of the RDEVICE macro) is coded in the LINE=cuu
operand of the CLUSTER macro.
Follow each CLUSTER macro with the TERMINAL macros that define the
terminals for the remote 3270 control unit. For the 3271 and 3276
directly following the CLUSTER macro, code a TERMINAL macro for each
terminal address to which a terminal can be attached (regardless of
whether or not the intermediate addresses are unused). For example, if
terminals are attached to the third, fourth, and eighth addresses, you
code eight TERMINAL macros. The first macro represents the first
(lowest) address, the last represents the eighth (highest) address.
For the 3214 Model 1C that has only 3278s (attached via Terminal
Adapter Types A1, A2, or A3), 3287s, or 3289s attached, follow the same
procedure as for the 3271 and 3276 in coding the TERMINAL macros. If
the 3274 Model 1C has 3271s, 3284s, 3286s, 3287s (attached via Terminal
Adapter Types Bl, B2, B3, or B4), or 3288s attached, directly following
the CLUSTER macro, first code TERMINAL macros for all 3218s, 3287s
(attached via Terminal Adapter Types A1, A2, or A3), and 3289s. These
devices must occupy the first 8, low-order addresses, and each following
block of 8 addresses until all of these devices are attached. As
before, a TERMINAL macro must be coded for all unused addresses in each
block of 8 addresses that are required. Immediately following the last TERMINAL macro in the block of 8, 16, or 24, code a TERMINAL macro for
each 3277, 3284, 3286, 3281s (attached via Terminal Adapter Types B1,
B2, B3, or B4), and 3288 that can be attached. These devices will
occupy the higher-order addresses on the controller. Again, a TERMINAL
macro must be coded for each unused address to which a terminal can be
attached up to the last address occupied.
For the 3215, directly following the CLUSTER macro, code a single
TERMINAL macro specifying TERM=3275. If the 3275 has a 3284 or 3286 Model 3 Printer attached, specify MODEL=3 to define the printer;
otherwise, the printer is ignored.
134 IBM VM/370 Planning and System Generation Guide
Previous Page Next Page