90 Netfinity/EFS
The cu type 3172 is a defined FLEX-ES keyword and defines an LCS-type LAN connection to
S/390. (On the S/390 side, there would normally be two CTC addresses (even/odd
addresses) defined. A LAN device for use by OS/390 TCP/IP must be specified exactly as
shown (except that the device name of the interface might be different). That is, it will be
defined as two devices (00 and 01), with the second device OFFLINE. The IP address for this
interface would be specified in the OS/390 TCP/IP profile.
An additional parameter may be required for a LAN definition. A real 3172 unit may have up
to four adapters. These are numbered 0-3, and this number appears in the OS/390 TCP/IP or
VTAM specifications.
By default, FLEX-ES uses number zero. If you want a different number,
you must include an options statement:
R10A3088: cu 3172
options ‘adapternumber=1’
interface local(1)
device(00) 3172 eth0
device(01) 3172 OFFLINE
end R10A3088
This emulates the real 3172 adapter number 1. This is not related to the actual LAN adapter
number in your Netfinity. The actual Netfinity LAN adapter that is used is specified by the
device parameter.
You cannot share a LAN adapter between Open UNIX and OS/390 TCP/IPs. You can share a
LAN adapter between Linux and OS/390 TCP/IP on a ThinkPad/EFS system. Do not confuse
the different capabilities of these two EFS systems.
Cloned devices
The FLEX-ES documentation includes an optional cloned parameter for many resources
definitions. We did not use this parameter. This parameter applies to a limited set of
devicesemulated printers and card readers are good examplesfor which the resources
definitions can be automatically replicated to serve multiple S/390 instances. This is
meaningful only when multiple S/390 instances are used. It potentially saves a little time when
creating resources definitions. We suggest it may be better to take the extra time to directly
create all the resources definitions you need and ignore the cloned parameter.
Common rules
FLEX-ES names, in general, may be up to 255 characters and use upper/lowercase letters,
numeric digits, and a few special characters. These special characters are underscore,
hyphen, dollar, at, and period. A name cannot consist of a decimal or hexadecimal number.
The following are not valid names: 2, 123, 1403, 0X1, 7F, 7f, 1C2a30.
White space (usually blanks) may be included almost anywhere between words. Two special
cases exist:
򐂰 No white space may exist in the parameters of an options statement or in a devopt
parameter. For example,
device(00) 3390-1 /S390/VOLAs1 devopt ‘trackcachesize = 10’
is incorrect; there should not be spaces before or after the equal sign.
򐂰 If a device number range is used, there must be spaces before and after the hyphen. For
device(00 - 15) 3278 OFFLINE
The same situation exists with a P/390 or MP3000 emulated I/O LAN adapter. It is known as the MPTS number in
these cases.

Get S/390 Partners in Development: Netfinity Enabled for S/390 now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.