7.0.10.3 fsimm310: resource language...

7.0.10.3

FSIMM310: Resource Language Reference

FLEX ESRelease 7.0.10

FSIMM310: Resource Language Reference

Documentation Version 7.0.10.3

Fundamental Software, Inc.Fremont, CA 94538

FSI welcomes your comments on this documentation. Commentsmay be submitted to

Fundamental Software, Inc.46750 Fremont BoulevardFremont, CA 94538USA

or via e-mail to the name fsipubs in the Internet domain funsoft.comAll comments submitted become the property of FSI.

Copyright c© 1992–2010 by Fundamental Software, Inc.All Rights Reserved

Unpublished — Rights reserved under the copyright laws of the United States.

v

Notices

"FLEX-ES" and "FLEXCUB" are registered trademarks of Fundamental Software, Inc.

"FakeTape ," "Software Archaeology ," and "Software doesn’t rust " are trademarks of Funda-mental Software, Inc.

All other trademarks and registered trademarks appearing in Fundamental Software, Inc. documents are theproperties of their owners and are used for purposes of identification only.

See the volume FSIMM990:Legal Noticesfor trademark acknowledgments and for the notices requiredbyredistributable software packages provided withFLEX ES.

This document and the software that it describes are Licensed Materials whose use is governed by theFLEX ESLicense Agreement. Use of the information contained in thisdocument or of the software described by thisdocument constitutes an acceptance of the terms of theFLEX ES License Agreement. This information andsoftware is provided without warranty of any kind. Fundamental Software, Inc. is not liable for any damagesarising out of your use of or inability to use this information or software.

FLEX ES 7.0.10.3 FSIMM310: Resource Language Reference

vi

FSIMM310: Resource Language Reference FLEX ES 7.0.10.3

vii

Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1. Notational Conventions . . . . . . . . . . . . . . . . . . . . . 1

1.1.1. Statement Syntax . . . . . . . . . . . . . . . . . . . . . . . 1

1.1.2. Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3. Resource Configuration Files . . . . . . . . . . . . . . . . . . . . 7

4. Resource Language Syntax . . . . . . . . . . . . . . . . . . . . 9

4.1. Format and Whitespace . . . . . . . . . . . . . . . . . . . . . 9

4.2. Syntactic Elements . . . . . . . . . . . . . . . . . . . . . . . 9

4.3. Reserved Keywords . . . . . . . . . . . . . . . . . . . . . . . 9

4.4. UserSpecified Names . . . . . . . . . . . . . . . . . . . . . . 11

4.5. Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.6. Punctuation . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.7. Literal Strings . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.8. Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

5. Resource Sets . . . . . . . . . . . . . . . . . . . . . . . . . . 13

5.1. Overall Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 13

5.1.1. The resources Block . . . . . . . . . . . . . . . . . . . . . . 13

5.1.2. The Resource Definition . . . . . . . . . . . . . . . . . . . . 13

5.1.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

5.2. Statements Not Defining Resources . . . . . . . . . . . . . . . 14


viii

5.2.1. Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

5.2.2. Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5.3. Resource Types . . . . . . . . . . . . . . . . . . . . . . . . . 16

5.3.1. FSI PCA Block Multiplexor Channels . . . . . . . . . . . . . . . 16

5.3.2. FSI PCA Byte Multiplexor Channels . . . . . . . . . . . . . . . 16

5.3.3. FSI PCA Selector Channels . . . . . . . . . . . . . . . . . . . 17

5.3.4. FSI SCA (serial) Channels . . . . . . . . . . . . . . . . . . . . 17

5.3.5. Channel Paths . . . . . . . . . . . . . . . . . . . . . . . . 17

5.3.6. Control Units . . . . . . . . . . . . . . . . . . . . . . . . . 18

5.3.6.1. Overall Syntax . . . . . . . . . . . . . . . . . . . . . . . . 18

5.3.6.2. Control Units by Channel Type . . . . . . . . . . . . . . . . 18

5.3.6.3. cu Statement: interface . . . . . . . . . . . . . . . . . . . 18

5.3.6.3.1. FLEXES local and network interface Statements . . . . . . . 19

5.3.6.3.2. FLEXCUB serial and parallel interface Statements . . . . . . 20

5.3.6.3.3. Emulated Channel Interface Parameters . . . . . . . . . . 21

5.3.6.3.4. Parallel Channel Interface Parameters . . . . . . . . . . . 22

5.3.6.3.5. Serial Channel Interface Parameters . . . . . . . . . . . . 23

5.3.6.4. cu Statement: options . . . . . . . . . . . . . . . . . . . . 24

5.3.6.5. cu Statement: cloned . . . . . . . . . . . . . . . . . . . . 24

5.3.6.6. cu Statement: tracesize . . . . . . . . . . . . . . . . . . . 25

5.3.6.7. cu Statement: device . . . . . . . . . . . . . . . . . . . . 26

5.3.6.7.1. Directly Connected TN3270 Sessions . . . . . . . . . . . . . 29

5.4. Resource Set Grammar Summary . . . . . . . . . . . . . . . . 30

6. System Configurations . . . . . . . . . . . . . . . . . . . . . . 31

6.1. cachesize . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

6.2. channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32


ix

6.3. cpu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

6.4. cu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

6.4.1. All Channel Types: devad . . . . . . . . . . . . . . . . . . . 37

6.4.2. All Channel Types: path . . . . . . . . . . . . . . . . . . . . 38

6.4.3. Emulated Channel Types Only: resource . . . . . . . . . . . . 38

6.4.4. FSI PCA Only: interlocked . . . . . . . . . . . . . . . . . . . 39

6.4.5. FSI PCA Channels: shared . . . . . . . . . . . . . . . . . . . 39

6.4.6. FSI PCA Channels: sharedb . . . . . . . . . . . . . . . . . . 40

6.4.7. FSI PCA Only: streaming . . . . . . . . . . . . . . . . . . . . 40

6.4.8. FSI SCA Only: link . . . . . . . . . . . . . . . . . . . . . . . 40

6.4.9. FSI SCA Only: cuadd . . . . . . . . . . . . . . . . . . . . . 41

6.4.10. FSI PCA and SCA Channels: unitadd . . . . . . . . . . . . . 41

6.5. epoch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6.6. essize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6.7. feature (System/370 Mode) . . . . . . . . . . . . . . . . . . . 43

6.8. feature (ESA/390 Mode) . . . . . . . . . . . . . . . . . . . . . 44

6.9. feature (z Mode) . . . . . . . . . . . . . . . . . . . . . . . . 45

6.10. feature (ECPS:VSE Mode) . . . . . . . . . . . . . . . . . . . . 46

6.11. instset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6.12. lparname . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

6.13. lparnum . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

6.14. memsize . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

6.14.1. 370 memsize . . . . . . . . . . . . . . . . . . . . . . . . . 48

6.14.2. 370 EA memsize . . . . . . . . . . . . . . . . . . . . . . . 48

6.14.3. 390 (370XA, ESA/370, ESA/390) memsize . . . . . . . . . . . . 49

6.14.4. z memsize . . . . . . . . . . . . . . . . . . . . . . . . . . 49


x

6.14.5. vse memsize . . . . . . . . . . . . . . . . . . . . . . . . . 50

6.15. timerres . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

6.16. tracesize . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

6.17. System Grammar Summary . . . . . . . . . . . . . . . . . . . 51

7. Supported Control Units and Devices . . . . . . . . . . . . . . . 53

7.1. Control Units . . . . . . . . . . . . . . . . . . . . . . . . . . 53

7.2. Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

8. Control Unit Device Limits . . . . . . . . . . . . . . . . . . . . . 61

9. Nonstandard CKD Emulated DASD Maximums . . . . . . . . . . . 65

10. Emulated Device Fields . . . . . . . . . . . . . . . . . . . . . 67

10.1. Emulated DASD . . . . . . . . . . . . . . . . . . . . . . . . 67

10.1.1. CKD Emulated DASD . . . . . . . . . . . . . . . . . . . . . 67

10.1.2. FBA Emulated DASD . . . . . . . . . . . . . . . . . . . . . 67

10.2. Emulated Tape Devices . . . . . . . . . . . . . . . . . . . . 67

10.3. Emulated Communications Devices . . . . . . . . . . . . . . 68

10.3.1. TN3270 Emulated Devices . . . . . . . . . . . . . . . . . . . 68

10.3.2. Emulated 3172 Devices for TCP/IP . . . . . . . . . . . . . . . 69

10.3.3. Emulated OSA and XCA Devices for TCP/IP . . . . . . . . . . 70

10.3.4. Emulated OSA and XCA Devices for SNA . . . . . . . . . . . 71

10.3.5. Emulated CETI . . . . . . . . . . . . . . . . . . . . . . . . 71

10.3.6. Emulated k200 Devices for TCP/IP . . . . . . . . . . . . . . . 73

10.3.7. TWX Emulated Devices . . . . . . . . . . . . . . . . . . . . 74

10.3.8. 3215 Emulated Devices . . . . . . . . . . . . . . . . . . . . 74

10.3.9. FSI ICA Emulated Devices . . . . . . . . . . . . . . . . . . . 75

10.3.10. Emulated BSC Devices . . . . . . . . . . . . . . . . . . . 75

10.4. Emulated Unit Record Devices . . . . . . . . . . . . . . . . . 75


xi

10.4.1. Emulated Printers . . . . . . . . . . . . . . . . . . . . . . . 75

10.4.2. Emulated Card Equipment . . . . . . . . . . . . . . . . . . 76

10.5. Other Emulated Devices . . . . . . . . . . . . . . . . . . . . 76

11. Emulated Control Unit Considerations . . . . . . . . . . . . . . . 77

11.1. Channel Types for Emulated 2701d Control Units . . . . . . . . . 77

11.2. Channel Types for Emulated OSA Control Units . . . . . . . . . . 77

12. Emulated Control Unit Options . . . . . . . . . . . . . . . . . . 79

12.1. CKD DASD Emulated Control Units . . . . . . . . . . . . . . . 79

12.1.1. trackcachesize . . . . . . . . . . . . . . . . . . . . . . . . 79

12.1.2. ssid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

12.1.3. smartsid . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

12.2. Ethernet and Token Ring Emulated Control Units . . . . . . . . . 81

12.2.1. adapternumber . . . . . . . . . . . . . . . . . . . . . . . 81

12.2.2. enablemgtime . . . . . . . . . . . . . . . . . . . . . . . . 82

12.2.3. ipaddress . . . . . . . . . . . . . . . . . . . . . . . . . . 82

12.2.4. multicastipaddress . . . . . . . . . . . . . . . . . . . . . . 85

12.2.5. tunipaddress . . . . . . . . . . . . . . . . . . . . . . . . . 86

12.3. FSI ICA Emulated Control Units . . . . . . . . . . . . . . . . . 88

13. Emulated Device Options . . . . . . . . . . . . . . . . . . . . 89

13.1. 3278 Terminals . . . . . . . . . . . . . . . . . . . . . . . . . 89

13.1.1. allowhostccws . . . . . . . . . . . . . . . . . . . . . . . . 89

13.1.2. convertsysreqtotestreq . . . . . . . . . . . . . . . . . . . . 89

13.1.3. tn3287 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

13.2. TWX Terminals . . . . . . . . . . . . . . . . . . . . . . . . . 89

13.2.1. initfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

13.3. 1403, 3203, 3211, 3262, 4245, 4248 Printers . . . . . . . . . . . . 90


xii

13.3.1. initfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

13.3.2. linelength . . . . . . . . . . . . . . . . . . . . . . . . . . 90

13.3.3. onlcr . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

13.3.4. useformfeeds . . . . . . . . . . . . . . . . . . . . . . . . 90

13.3.5. writetimeout . . . . . . . . . . . . . . . . . . . . . . . . . 91

13.4. 3286 Printers . . . . . . . . . . . . . . . . . . . . . . . . . . 91

13.4.1. initfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

13.4.2. writetimeout . . . . . . . . . . . . . . . . . . . . . . . . . 91

13.5. CKD Emulated DASD . . . . . . . . . . . . . . . . . . . . . . 91

13.5.1. trackcachesize . . . . . . . . . . . . . . . . . . . . . . . . 91

13.5.2. writethroughcache . . . . . . . . . . . . . . . . . . . . . . 92

13.6. FBA Emulated DASD . . . . . . . . . . . . . . . . . . . . . . 92

13.6.1. blockcachesize . . . . . . . . . . . . . . . . . . . . . . . 92

13.6.2. numblocks . . . . . . . . . . . . . . . . . . . . . . . . . . 92

13.7. Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

13.7.1. allowdisconnects . . . . . . . . . . . . . . . . . . . . . . . 93

13.7.2. allowmountccws . . . . . . . . . . . . . . . . . . . . . . . 93

13.7.3. autoloader . . . . . . . . . . . . . . . . . . . . . . . . . 94

13.7.4. awscompressalldata . . . . . . . . . . . . . . . . . . . . . 94

13.7.5. awscompressdata . . . . . . . . . . . . . . . . . . . . . . 95

13.7.6. awsnewtape . . . . . . . . . . . . . . . . . . . . . . . . . 95

13.7.7. createmode . . . . . . . . . . . . . . . . . . . . . . . . . 95

13.7.8. forcereadaheadon . . . . . . . . . . . . . . . . . . . . . . 96

13.7.9. key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

13.7.10. maxwritesize . . . . . . . . . . . . . . . . . . . . . . . . 98

13.7.11. noidrc . . . . . . . . . . . . . . . . . . . . . . . . . . . 99


xiii

13.7.12. nonewtape . . . . . . . . . . . . . . . . . . . . . . . . . 99

13.7.13. nooldtape . . . . . . . . . . . . . . . . . . . . . . . . . 99

13.7.14. password . . . . . . . . . . . . . . . . . . . . . . . . . . 99

13.7.15. scsilun . . . . . . . . . . . . . . . . . . . . . . . . . . 100

13.7.16. scsitarget . . . . . . . . . . . . . . . . . . . . . . . . . 101

13.7.17. scsitimeout . . . . . . . . . . . . . . . . . . . . . . . . 101

13.7.18. awswritesegmentsize . . . . . . . . . . . . . . . . . . . 102

13.8. CTCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

13.8.1. M360 . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

13.8.2. M370 . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

13.9. FSI ICA Emulated SDLC and BSC Devices . . . . . . . . . . . 102

13.9.1. leased (and Dialup) . . . . . . . . . . . . . . . . . . . . 102

13.9.2. rtson . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

13.9.3. nrzi . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

13.10. FSI ICA TTC2 Devices . . . . . . . . . . . . . . . . . . . . 103

13.10.1. acc . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

13.10.2. baudrate . . . . . . . . . . . . . . . . . . . . . . . . . 103

13.10.3. leased . . . . . . . . . . . . . . . . . . . . . . . . . . 103

13.10.4. noreadint . . . . . . . . . . . . . . . . . . . . . . . . . 104

13.10.5. notimeout . . . . . . . . . . . . . . . . . . . . . . . . 104

13.10.6. nowriteint . . . . . . . . . . . . . . . . . . . . . . . . . 104

13.10.7. rtson . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

13.10.8. stopbits . . . . . . . . . . . . . . . . . . . . . . . . . . 104

13.11. Emulated BSC (bsca) . . . . . . . . . . . . . . . . . . . . 104

13.11.1. tributary . . . . . . . . . . . . . . . . . . . . . . . . . 104

14. ChannelAttached Peripheral Parameters . . . . . . . . . . . 105

15. Information for Older Versions . . . . . . . . . . . . . . . . . 107

15.1. lparnum (Releases Through 7.0.3) . . . . . . . . . . . . . . . 107

15.2. Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

16. Volume Index . . . . . . . . . . . . . . . . . . . . . . . . . 109


xiv


1

1. Introduction

ThisResource Language Referencedescribes the language used to specify the configuration of the emulated andphysical resources ofFLEX ES R©. It also contains the listings of all supported control unitand device types andall supported control unit and device options.

It is intended as a reference document, not a tutorial. Examples of system and device configurations may befound in FSIMM300:System Programmer’s Guide.

It does not document the command line invocations of theFLEX ES resource compiler or resource manager.These command line invocations are documented in the volumeFSIMM200: Operator’s Guide.

1.1. Notational Conventions

1.1.1. Statement Syntax

In the descriptions below, words inbold type are to be entered exactly as typed. Words in italic type specify valuesthat you must supply. Square brackets ([, ]), vertical bars (|), question marks (?), plus signs (+), and asterisks(*) are used to punctuate the command descriptions. They should not be entered as a part of the command.Parentheses, when present, are a part of the command’s syntax and should be entered.

Square brackets group alternatives, and the vertical bar distinguishes between alternatives (it acts as a logical"or"). For example,

epoch[ local | gmt ] date

specifies commands of the form

epoch local 1960

or

epoch gmt 1900

Optional items are grouped with brackets and followed by a question mark. For example, in:

cu devad (devaddr[ , devcount]? )

the parameter devcount, along with the comma separating it from the previous parameter, is optional.

Items which may be repeated zero or more times are grouped with brackets and followed by an asterisk (* ). Forexample, in:

cu path ( pathnum[ , pathnum]* )

the parameter pathnum, along with the comma separating it from the previous parameter, may be repeated zeroor more times.

Items which may be repeated one or more times are handled in a similar fashion, save that a plus sign (+) is usedinstead of an asterisk (* ).


2

Commands and hexadecimal values are case insensitive. (They may be upper or lower case or a mixture of both.)

Quantities do not contain commas or embedded spaces.

Legal: memsize(16384)

Illegal: memsize(16,384)

Quantities do not contain suffixes such as "K" or "M."

Illegal: memsize(16K)

1.1.2. Numbers

In the Resource Language, numbers are by default decimal. This is in contrast to theFLEX ES CLI, wherenumbers are hexadecimal.

Hexadecimal numbers may be specified (and are often specifiedin practice) in the Resource Language by use ofthe "0x" prefix (the numeral 0 followed by a lower-case letterx). (This usage derives from the conventions ofthe C programming language.)

For example, the units on thememsizestatement are kilobytes. Each of the following statements expresses amemsizeof 64 Megabytes:

memsize(65536)

memsize(0x10000)


3

2. Example

This is an example of a small resource configuration file. It isthe same example as filespgexample0(document ID FSIMX300) in FSIMM300:System Programmer’s Guide. The compilable source code of thisresource configuration file is available as the filespgexample0 (document ID: FSIMX300) in the electronicdistribution of the documentation.

It is intended simply to give the general flavor of what a configuration file looks like, while illustrating in briefthe use of a single configuration file to generate configuration information for more than one server. It is notintended to illustrate any particular real mainframe configuration.

It presents a configuration file for a small VM/ESA system which uses resources on both its own server ("server1")and a remote server ("server2"). It illustrates only a few ofthe configuration options ofFLEX ES.

Assuming that this example were stored in a file called "spgexample0 ", it would be compiled by issuing thecommand:

cfcomp spgexample0

This would produce three files:

A system configuration file named "vmesa1.syscf ".

Two resource configuration files named "server1.rescf " and "server2.rescf ".

A resource configuration file such as this may be written on anymachine and compiled on anyFLEX ESserver. It is the responsibility of the system administrator to move the compiled system configuration file"vmesa1.syscf " to "server1", the compiled resource file "server1.rescf " to "server1", and the compiledresource file "server2.rescf " to "server2".


4

# FSIMX300: spgexample0# FSIMM300: System Programmer’s Guide# FSIMM310: Resource Language Reference# Copyright 1999-2001 by FSI# Revision 1.4

# A small VM/ESA system

system vmesa1:memsize(32768) # K of mainframe Main Storagecachesize(1024) # K of mainframe instructions of per-CPU ca chinginstset(esa) # ESA (ESA/390, ESA/370, XA-370; vs S/370 or EC PS:VSE)tracesize(256) # Trace buffer size, in entries, per CPU

cpu(0) dedicated # single CPU dedicated to a server processo r

channel(00) localchannel(01) networkchannel(02) blockmux chpbt0 # chpbt0 is an FSI PCA channel re source

# Control Units for emulated devices# The "resource(name)" parameter links these to actual reso urcescu devad (0x00c,3) path(0) resource(cu2821) # card, printe rcu devad (0x020,16) path(0) resource(cu3274) # terminalscu devad (0x180,4) path(1) resource(server2:cu3422) # Ser ver 2 tapecu devad (0x230,4) path(0) resource(vsedasd) # 3390 DASD

# 32 DC-Interlocked terminals on a physical communications controller# on PCA channel chpbt0 (that is, path 2)cu devad (0x5a0,32) path(2) unitadd(0xa0) interlockedend vmesa1

# Resource definition for Server 1

resources server1:

# An emulated 2821 (unit record) control unit# attaching an emulated reader/punch and an emulated printe rcu2821: cu 2821clonedinterface local(1) # up to 1 local Instance of the CUdevice(00) 2540R OFFLINE # card reader, device name to be mou nteddevice(01) 2540P OFFLINE # card punch, device name to be moun teddevice(02)1403 OFFLINE # 1403 printer, device name to be mou ntedend cu2821


5

# An emulated 3274 control unit# attaching emulated 3278 terminalscu3274: cu 3274interface local(1)device(00) 3278 console # name "console" arbitrarydevice(01) 3278 term1 # name "term1" arbitrarydevice(02) 3278 stanley # name "stanley" arbitrarydevice(03) 3278 oliver # name "oliver" arbitrarydevice(04) 3278 @204.179.93.3 # bypass terminal solicitordevice(05) 3278 @204.179.93.4 # bypass terminal solicitordevice(06) 3278 OFFLINE # device name filled in by mount comm anddevice(07) 3278 OFFLINE # device name filled in by mount comm anddevice(08) 3278 OFFLINE # device name filled in by mount comm anddevice(09) 3278 OFFLINE # device name filled in by mount comm anddevice(10) 3278 OFFLINE # device name filled in by mount comm anddevice(11) 3278 OFFLINE # device name filled in by mount comm anddevice(12) 3278 OFFLINE # device name filled in by mount comm anddevice(13) 3278 OFFLINE # device name filled in by mount comm anddevice(14) 3278 OFFLINE # device name filled in by mount comm anddevice(15) 3278 OFFLINE # device name filled in by mount comm andend cu3274

# An emulated 3990 control unit with attached 3390 drivesvsedasd: cu 3990interface local(1)device(00) 3390-2 /usr/flexes/links/vmresdevice(01) 3390-2 /usr/flexes/links/vmwk01device(02) 3390-2 /usr/flexes/links/vmwk02device(03) 3390-2 OFFLINEend vsedasd

# A physical PCA channelchpbt0: blockmux/dev/chpbt/ch0end chpbt0

end server1

# Resource definition for Server 2resources server2:cu3422: cu 3422clonedinterface local(1)interface network(1)device(00) 3422 OFFLINE # Tape, device name filled in by moun tdevice(01) 3422 OFFLINE # Tape, device name filled in by moun tdevice(02) 3422 OFFLINE # Tape, device name filled in by moun tdevice(03) 3422 OFFLINE # Tape, device name filled in by moun tend cu3422end server2


6


7

3. Resource Configuration Files

A resource configuration file defines zero or more sets of resources (e.g., emulated devices, PCA channels, etc.)and zero or moreFLEX ES system definitions. (At least one resource set or system definition must be definedin any given resource configuration file.) A resource configuration file is compiled by theFLEX ES resourcecompiler,cfcomp(1) , into a set of object files. One object file is generated for each resource set or systemdefinition. The volume FSIMM200:Operator’s Guidedescribes the use of the resource compiler.

There is no correspondence between the host on which a resource file is written, maintained, and compiled usingcfcomp(1) and the node (host) on which the resource sets or system definitions specified by the resource fileare instantiated. Resource files may be compiled on any system on whichcfcomp(1) has been installed, andFLEX ES resources and systems may be instantiated on any node on which aFLEX ES system (or a portion of itsufficient to provide the resources in question) has been installed.

Because multiple resource sets and system configurations may be defined in a single configuration file, andbecause the resource compiler produces separate object files for each of these, resource managers andFLEX ESsystems on many different nodes (hosts) may use resource sets and system configurations which are maintainedin a single resource configuration file. This provides significant advantages for uniform resource configurationmaintenance across multiple hosts.

(Of course, the resource manager and theFLEX ES systems on any node (host) may use compiled resource setsand system configurations generated from any resource configuration file on any node (host); indeed, theFLEX ESsystems on a given host may use system configurations compiled from many different resource configurationfiles. FLEX ES provides the potential for both unified and distributed configuration administration.)


8


9

4. Resource Language Syntax

Examples of many language features are given in FSIMM300:System Programmer’s Guide.

4.1. Format and Whitespace

The resource configuration language is, with two exceptionsas noted below, free-format. That is it does notdepend on line breaks or other "whitespace". Whitespace can be composed of one or more blank spaces, tabcharacters, or newlines. Whitespace must occur between keywords and names in order to distinguish them; itneed not occur between names and punctuating characters (e.g., colons and parentheses).

The first exception to this concerns comments. Comments begin with the pound sign (#) and end with the nextnewline.

The second exception to this occurs in the use of the hyphen character to specify ranges of device numbers.When so used, the hyphen must have at least one whitespace character on either side.

4.2. Syntactic Elements

The language may be thought of as consisting of reserved keywords, user-specified names, numbers, punctuation,and literal strings (including filenames, IP addresses, DNSnames, and device options strings).

4.3. Reserved Keywords

The reserved keywords consist of the following identifiers.


10

addraliasblockmuxbytemuxcachesizechannelchanpathclonedcpucucuadddevaddevicedevoptepochessizefeatureinstsetinterfaceinterlockedlinklocallocalbytelocalosamaxinterlockedmemorymemsizenetworknetworkbytenetworkosanodesoptionspathparallelresourceresourcesselectorserialsharedsharedbstreamingsystemtimerrestracesizeunitadd

Figure 1 Reserved Keywords


11

The values required forinstset and feature statements (e.g., vse, 4kpgonly, lpar) are not considered languagekeywords. Thus, it is valid to have a system named "vse".

Note: the names of devices are typically numbers, and therefore cannot be used as user-defined names. Thosefew devices with names which qualify syntactically as user-defined names (e.g., ctc) may be used as such. Thus,it is valid to have a system named "ctc".

4.4. UserSpecified Names

Names used as system or resource names may be up to 249 characters in length, and may consist of the ten digits,lowercase alphabetic characters, uppercase alphabetic characters, the underscore character, the hyphen character,the dollar sign, the commercial at sign, and the period. (Theuse of the commercial at sign at the start of adevicefile name on a communications device has a special meaning.)

Names are case-sensitive; "samplesys" and "SampleSys" aredistinct names. The following are examples of validnames:

Names may not be valid decimal numbers.

Reserved keywords must not be used as names.

A name may not begin with a pair of characters the first character of which is one of the digits and the secondcharacter of which is an upper or lower case "x" character or an upper or lower case character in the range "a"through "f".

The following are valid names:

samplesyssamplesys1samplesys1samplesys-10samplesys-1

Figure 2 Sample Valid Names

Further examples of valid (and invalid) names are given in FSIMM300: System Programmer’s Guide.

4.5. Numbers

Numbers are positive integers. They are by default decimal.Hexadecimal numbers are specified by prepending"0x" (this convention derives from the C programming language).

4.6. Punctuation

Punctuation characters include:


12

: (the colon)( (the left parenthesis)) (the right parenthesis)- (the hyphen or dash)’ (the single quotation mark)

Figure 3 Reserved Keywords

When the hyphen is used to specify ranges of devices, it must have at least one whitespace character on eachside. When the single-quote character is used to delimitoptions or devopt strings, no whitespace may appearbetween the opening and closing single quotes.

4.7. Literal Strings

Strings of characters which are to be interpreted literallyoccur in various circumstances:

As filename parameters ondevicestatementsAs name parameters ondevicestatementsAs IP addresses or DNS resolvable hostnames on certain communicationsdevicestatements.In optionsstatements anddevopt device option specifications

In the first three of these situations, the literal string appears without enclosing quotation marks. For example:

device(00) 3390-3 /dev/rdsk/c0b0t1d0s3device(00) 3278 consoledevice(00) 3278 @test.funsoft.comdevice(00) 3278 @192.168.1.1

In the fourth situation (theoptions statement anddevopt specifications) the string must be enclosed in eithersingle or double quotation marks. Each string must use only one type of quotation mark (thus, it is not valid tobegin a string with a single quotation mark and end it with a double quotation mark) but strings delimited byeach type of quotation mark can be mixed within the same control unit definition. For example:

vmdasd: cu 3990options ’trackcachesize=100’device(00) 3390-3 /dev/rdsk/c0b0t1d0s3 devopt "trackcac hesize=5"device(01) 3390-3 /dev/rdsk/c0b0t1d0s3 devopt ’trackcac hesize=30’device(02) 3390-3 /dev/rdsk/c0b0t1d0s3 devopt "trackcac hesize=30"device(03) 3390-3 /dev/rdsk/c0b0t1d0s3 devoptend vmdasd

(This example defines an emulated 3990 CKD DASD control unit attaching four emulated 3390-3 DASD. Thezeroth DASD has been specified so as to have the minimum cache,5 tracks’ worth. The first and second DASDeach have 30 tracks’ worth of cache. The third DASD has the default cache (15 tracks’ worth). The optionsstatement specifies that 20 tracks worth of cache (100 - (5 + 30+ 30 + 15)) floats between the various DASD onan as-needed basis.)

4.8. Comments

Comments begin with a "#" character and terminate at the end of the line.


13

5. Resource Sets

A resource set definition declares the resources, and the characteristics of the resources, to be made availableon a singleFLEX ES node. A resource configuration file may contain any number of resource set definitions.These resources are not made available until the resource configuration file has been compiled with the resourcecompiler,cfcomp(1) , and the resulting compiled resource definition has been used to start or refresh a resourcemanager on a particularFLEX ES node (host).

5.1. Overall Syntax

5.1.1. The resourcesBlock

Each resource set begins with the keywordresources, followed by the name of the resource set, followed by acolon. Then the individual resources which are available within this resource set (that is, available on this node(host), or "node," when this resource set is used to configurethis node’s resource manager) are defined in a seriesof statements. Each resource set ends with the keywordend followed by the name of the resource set. Thus, theoverall form of a resource set definition for a resource set called "sampleres1" might look like this:

resources sampleres1:# resource definitions go hereend sampleres1

5.1.2. The Resource Definition

Within the resource set, each resource is defined in a block ofstatements. The block defining a resource beginswith the symbolic name for the resource, followed by a colon and the keyword for the type of the resource. Thena series of statements define the resource. The resource definition block then ends with the keywordend followedby the name of the resource. For example, the overall form of each resource definition block for a 3274 controlunit named "sample3274" might look like this:

resources sampleres1:

. . .

sample3274: cu 3274# resource characteristics go hereend sample3274

. . .

end sampleres1

5.1.3. Example

The following is an example of a resource set for a very small node. It defines only two control units: an emulated3274 terminal control unit which, in this configuration, hasattached to it a single emulated 3278 terminal, and anemulated 3803 control unit supporting two emulated 3420 tape drives. The details of these resource definitionswill be described later.


14

resources smallres:

## Define an emulated 3274 terminal control unit, with# an emulated 3278 terminal# Define an emulated 3803 control unit, with# two emulated 3420 tape drives#cu3274: cu 3274cloned

interface local(1)

device(00) 3278 OFFLINE # device name filled in by mount comm and

end cu3274

cu3803: cu 3803cloned

interface local(1)

device(00) 3420 OFFLINE # device name filled in by mount comm anddevice(01) 3420 OFFLINE # device name filled in by mount comm and

end cu3803

end smallres

5.2. Statements Not Defining Resources

Two types of statements which do not define resources may appear within resource definition blocks. (Note:They must appear within a resource definition block; they arenot allowed outside of resource definition blocksor within system definitions.)

5.2.1. Aliases

alias pseudonym= realname[ : node]?

The alias statement establishes an alternative name,pseudonym, for the resource named by itsrealnameparameter. By default this resource is one on the current system (a part of this resource set). It may also beon another server (node) as specified by the optionalnode parameter. Either a numeric IP address or a DNSresolvable host name may be used.

Example:

resources server1:

...

alias firststring = cu3880alias realtape = c1:server2

...end samplenode


15

In the first example above, the name "firststring" is made equivalent to the resource "cu3880" (presumably"cu3880" represents an emulated 3880 control unit; however, the name "cu3880" is arbitrary; it could name anytype of resource). In the second example, the name "realtape" is made equivalent to the resource "c1" on node(server) "server2".

Thealias statement is the only resource statement which does not employ anend terminator.

5.2.2. Nodes

nodes : [ anynode| nodename]+ end nodes

Thenodes statement establishes a list of remote hosts, or "nodes", which are permitted to access the resourcesdefined on the local host.

If the keywordanynode is used, then all remote nodes are allowed to access defined resources on the local host.If this keyword is specified, then no actual node names may be specified.

If a list of node names is specified, then each name may be specified only once. Node names are the TCP/IPDNS (Domain Name System) names by which remote computers areknown on the TCP/IP network.

Example:

resources samplenode:

...

nodes: host1 host2 host3end nodes

...end samplenode

In the example above, the nodes named "host1", "host2", and "host3" are declared to be known to the currentnode. All other nodes will be denied access to the resources on the current node.

Example:

resources samplenode:

...

nodes: anynodeend nodes

...end samplenode

In the example above, any node is allowed to access the resources on the current node.

What is meant by "allowed to access the resources on the current node" is that CLI consoles started on thespecified remote node(s) will be allowed to connect to resources on the node "owning" the resource. Also,network channels from the specified remote node(s) will be allowed to connect to resources on the node "owning"the resource (assuming there is an available network channel on the resource that is connected to).


16

What is meant by " denied access to the resources on the currentnode" is that any attempt to connect to a resourcefrom a non-allowed node will be rejected immediately.

If a nodesstatement is not present, the default behavior is to deny allother nodes to access the resources on thecurrent node.

5.3. Resource Types

The following resources are supported:

5.3.1. FSI PCA Block Multiplexor Channels

resourcename: blockmux devicefileend resourcename

A blockmux resource is a Parallel Channel Adapter (PCA) block multiplexor channel provided by the localnode (host). Thedevicefileparameter specifies the file name of the server OS "device special" file through whichaccess to the channel is provided. When the FSI PCA package is installed, many device special files are createdfor it in the /dev/chpbt/ directory. Of these, the device special filenames of the following form are used:

/dev/chpbt/chN

In these files, "N" is the number of the channel as installed.

Example:

channel0:blockmux /dev/chpbt/ch0end channel0

In this example, a block multiplexor channel named "channel0" is defined and is associated with the specifieddevice special file of a PCA.

Note that the syntax of the command language does not depend on line breaks. Thus, the following alternativeforms are equivalent to the example above:

channel0: blockmux/dev/chpbt/ch0end channel0

channel0: blockmux /dev/chpbt/ch0 end channel0

Other arrangements are possible as well.

5.3.2. FSI PCA Byte Multiplexor Channels

resourcename: bytemux devicefileend resourcename

A bytemux resource is a Parallel Channel Adapter (PCA) byte multiplexor channel provided by the local node(host). Thedevicefileparameter specifies the file name of the server OS "device special" file through whichaccess to the channel is provided.


17

Example:

channel0:bytemux /dev/chpbt/ch0end channel0

In this example, a byte multiplexor channel named "channel0" is defined and is associated with the specifieddevice special file of a Parallel Channel Adapter (PCA).

5.3.3. FSI PCA Selector Channels

resourcename: selectordevicefileend resourcename

A selector resource is a Parallel Channel Adapter (PCA) selector channel provided by the local node (host).Thedevicefileparameter specifies the file name of the server OS "device special" file through which access tothe channel is provided.

5.3.4. FSI SCA (serial) Channels

resourcename: serial devicefileend resourcename

A serial resource is an FSI Serial Channel Adapter (SCA) serial channel provided by the local node (host). Thedevicefileparameter specifies the file name of the server OS "device special" file through which access to thechannel is provided. FSI SCA channels use device special files of the same style ("chpbt") as FSI PCA channels.

The FSI SCA provides type CNC serial channels. It does not provide serial channels of types CTC, CVC, orCBY.

5.3.5. Channel Paths

resourcename: chanpath devicefile[ blockmux | serial ] end resourcename

A chanpath (channel path) resource identifies an FSI PCA or FSI SCA port for use by an emulated ControlUnit. Only channel paths of typesblockmux (PCA block multiplexor) andserial (SCA, which implies typeCNC Channels for the FSI SCA-1, which in turn implies block multiplexor operation) are supported. Channelpaths for PCA byte multiplexor, PCA selector, or SCA of non-CNC channel types, are not supported.

Thedevicefilespecifies the server OS device special file which identifies the FSI PCA or FSI SCA driver. It is ofthe form/dev/chpbt/chX , whereX is the port number as installed.

Multiple PCA or SCA ports may be used for Channels or for Control Units independently of each other. A singlePCA or SCA port may not be used simultaneously as a Channel andas a Control Unit, however.

Examples:


18

pcacuside0: chanpath/dev/chpbt/ch0 blockmuxend pcacuside0

scacuside0: chanpath/dev/chpbt/ch1 serialend scacuside0

5.3.6. Control Units

5.3.6.1. Overall Syntax

resourcename: cu cutype custatementsend resourcename

The cu resource defines the identity and characteristics of an emulated device control unit, its interfaces, andits devices. Acu resource must exist for each emulated control unit, whetherit is intended to be attached to aFLEX ES Instance via aFLEX ES emulated channel or to a mainframe from any manufacturer viathe ControlUnit Side capabilities of the FSI SCA or FSI PCA.

The control unit type,cutype, is one of the types described in the "Supported Control Units and Devices" chapterlater in this document.

The variouscustatementswithin acu resource are described in separate sections below.

5.3.6.2. Control Units by Channel Type

Emulated control units may be distinguished by the type of channel path through which they are attached. Threecategories of channel path types are possible:

EmulatedFSI PCAFSI SCA

All FLEX ES emulated control units, including those which use the FSI Integrated Communications Adapter(ICA), may be attached toFLEX ES Instances throughFLEX ES emulated channels (cu interface typeslocal ornetwork).

CertainFLEX ES emulated control units may be attached to any mainframe fromany manufacturer which supportsOEMI parallel channels. These emulated control units use the FSI Parallel Channel Adapter (PCA) as a controlunit interface (cu interface typeparallel).

CertainFLEX ES emulated control units may be attached to any mainframe fromany manufacturer which supportsESCON or ESCON compatible channels. These emulated controlunits use the FSI Serial Channel Adapter (SCA)as a control unit interface (cu interface typeserial).

5.3.6.3. cu Statement: interface

resourcename: cu . . . interface [ [ local ( interfacenum) ] | [ network ( interfacenum) ] | [ parallelpcaresourcename paralleloptions* ] | [ serial scaresourcename serialoptions* ] ]? . . . end resourcename


19

The interface statement describes an interface to aFLEX ES (or FLEXCUB) emulated control unit. At least oneinterface statement is required in each emulated control unit.

Four types of interfaces are possible:local, network, parallel, andserial.

5.3.6.3.1. FLEXES local and network interface Statements

Two of the four possible types of interfaces are used inFLEX ES (as opposed toFLEXCUB) operation. Interfaces ofthe typelocalare emulated interfaces on the local host which are attachedtoFLEX ES emulated block multiplexor,byte multiplexor, or selector channels. Interfaces of the typenetwork are emulated interfaces on networked hostswhich are attached toFLEX ES emulated block multiplexor, byte multiplexor, or selectorchannels.

Multiple interface statements of any of the four types may appear within acu definition. (WhileFLEX ESInstances use only the two emulated types of interfaces (local and network) a FLEXCUB Control Unit canbe used by both traditional hardware-based mainframes (over serial andparallel interfaces) and byFLEX ESmainframes.) However, each type of emulatedinterface statement (local or network) may only be specifiedonce in eachcu definition. Thus, the following is a valid definition:

testcu: cu 3990interface local(1)interface network(1)device(00) 3390-1 OFFLINEend testcu

However, the following definition is not valid, because it has two interface localstatements:

testcu: cu 3990interface local(1)interface local(1)device(00) 3390 OFFLINEend testcu

One type of emulated Control Unit may be shared between multipleFLEX ES Instances: DASD emulated ControlUnits of type3990; no other type of emulated Control Unit may be shared. To specify this sharing in the ControlUnit definition, specify the required number of interfaces in the numeric parameter to thelocal or networkstatement(s). For example, to share an emulated3990Control Unit between twoFLEX ES Instances on the sameserver, specify:

testcu: cu 3990interface local(2)device(00) 3390 OFFLINEend testcu

To share an emulated3990Control Unit between twoFLEX ES Instances on different servers, specify:

testcu: cu 3990interface local(1)interface network(1)device(00) 3390 OFFLINEend testcu


20

Do not, however, attempt to share an emulated3990Control Unit between twoFLEX ES Instances by specifyingmore than onelocal or more than onenetwork interface statement. As noted in an earlier example in thissection, the following is not valid:

testcu: cu 3990interface local(1)interface local(1)device(00) 3390 OFFLINEend testcu

Note also that multipathing from a singleFLEX ES Instance toFLEX ES emulated Control Units (of any type) isnot presently supported.

The limit on the total number of interfaces of all types, combined, to a singleFLEX ES or FLEXCUB type3990DASD emulated Control Unit is 32.

5.3.6.3.2. FLEXCUB serial and parallel interface Statements

The other two types of interfaces are used inFLEXCUB (as opposed toFLEX ES) operation. Interfaces ofthe typeserial are physical interfaces using the FSI SCA. They allow the connection of the control unit toany mainframe which supports ESCON or ESCON compatible channels, either directly or through an ESCONDirector. Interfaces of the typeparallel are physical interfaces using the FSI PCA. They allow the connection ofthe control unit to any mainframe which supports OEMI parallel channels.

Multiple interface statements of any of the four types may appear within acu definition. Interfaces of typesparallel andserial may be specified multiple times in eachcu definition (unlike interfaces of typeslocal andnetwork, which cannot). Thus, the following is a valid definition:

testcu: cu 3990interface serial [additional parameters here]interface serial [additional parameters here]device(00) 3390-1 OFFLINEend testcu

The following is also valid:

testcu: cu 3990interface local(2)interface network(3)interface serial [additional parameters here]interface serial [additional parameters here]device(00) 3390 OFFLINEend testcu

One type of emulated Control Unit may be shared (between multiple traditional mainframes and/or multipleFLEX ES Instances): DASD emulated Control Units of type3990; no other type of emulated Control Unitmay be shared. To specify the sharing of a3990; Control Unit between multiple traditional mainframes inFLEXCUB Operation, use multipleinterface serial or parallel interface statements, one for each connection.(If the Control Unit is also to be shared between one or moreFLEX ES Instances, use theinterface local and/orinterface network statement(s) as described earlier.


21

For example, to share an emulated3990Control Unit between two traditional mainframes over two FSI SCAcards, a specification similar to the following might be used:

testcu: cu 3990interface serial sca0 addr(0x00) path(0) cuadd(0)interface serial sca1 addr(0x00) path(0) cuadd(0)device(00) 3390 OFFLINEend testcusca0: chanpath/dev/chpbt/ch0 serialend sca0sca1: chanpath/dev/chpbt/ch1 serialend sca1

To share the same control unit additionally between twoFLEX ES Instances, over, for example,FLEX ES networkemulated channels, specify:

testcu: cu 3990interface serial sca0 addr(0x00) path(0) cuadd(0)interface serial sca1 addr(0x00) path(0) cuadd(0)interface network(2)device(00) 3390 OFFLINEend testcusca0: chanpath/dev/chpbt/ch0 serialend sca0sca1: chanpath/dev/chpbt/ch1 serialend sca1

Multipathing to emulated control units is presently supported only inFLEXCUB operation (that is, over physicalFSI SCA or FSI PCA channels, not over emulatedFLEX ES channels) and that such multipathing is supportedonly to CKD emulated DASD Control Units of type3990.

The limit on the total number of interfaces of all types, combined, to a singleFLEX ES or FLEXCUB DASDemulated Control Unit is 32.

5.3.6.3.3. Emulated Channel Interface Parameters

Interfaces of the typeslocal andnetwork take a single parameter on thelocal or network keyword, enclosed inparentheses. (They do not take any additional keywords, as do serial or parallel interfaces, as described below.)For example:

testcu: cu 3990interface local(1)interface network(1)device(00) 3390 OFFLINEend testcu


22

The meaning of this numeric parameter and reasonable valuesfor it depend upon the context.

For non-cloned control units, this parameter specifies the number of paths of the specified type into the controlunit. Reasonable values for this number depend upon the typeof control unit. Only CKD emulated DASDcontrol units support the sharing of devices. So for emulated CKD DASD control units it is reasonable to specifyvalues greater than one such that the sum of all values does not exceed the maximum number of connectionsallowed for the control unit.

For other types of non-cloned control units, only one interface may be active at any given time. Attempts touse multiple interfaces simultaneously to share devices may lock the system. The maximum reasonable valuefor these types of control units is therefore 1. However, it is reasonable to specify bothlocal (or localbyte) andnetwork (or networkbyte) interfaces, each with a value of 1, so long as only one of the interfaces is to be activeat any time.

For cloned control units, the meaning of this number changescompletely. Rather than specifying the number ofinterfaces, it instead specifies the maximum the number of control units that may be cloned. Each cloned controlunit has exactly one interface.

Because each cloned control unit has exactly one interface,it is not possible to use cloned control units for sharedCKD DASD.

Another implication of the behavior of cloned control unitsis that the specification of bothclonedand an interfacevalue of 1 is not incorrect, but is redundant. Such a control unit could only be cloned once, and would thereforenot be functionally different from a single non-cloned control unit.

5.3.6.3.4. Parallel Channel Interface Parameters

. . . interface parallel pcaresourcename[ addr ( controlunitaddress) ] ? [ [ interlocked ( speed) ] | [maxinterlocked ] | [ streaming (speed) ] ]?

Note: When a Control Unitinterface of type parallel is in use, the Control Unit is being used inFLEXCUBOperation. This statement and its parameters should not be confused with the System definitions for FSI PCAattached peripherals.

Interfaces of theparallel type do not take any numeric parameter in parentheses after the parallel keyword(as do local and network interfaces as described above). They take one or more parameters specified byadditional keywords. They require at least one parameter: the name of the resource associated with the FSI PCA.Optionally, they may also take theaddr parameter and, again optionally, exactly one of the following parameters:interlocked, maxinterlocked, or streaming.

The addr optional parameter specifies the control unit’s address on the channel. That is, it specifies the firstdevice address on the channel, counting from 00, that the control unit will respond to. This address may bespecified in decimal or in hexadecimal, and must be a value between 0 and 255 decimal. If this parameter is notspecified, the control unit’s address on the channel defaults to 0.

Thestreamingoptional parameter specifies that this interface is to operate, if possible, in streaming mode at thespeed specified. The speeds allowed are limited to: 2 Megabytes per second (specified by20), 3 Megabytes persecond (specified by30), and 4.5 Megabytes per second (specified by45).


23

The interlocked optional parameter specifies that this interface is to operate in DC interlocked mode operationat the speed specified. The speed should be specified as an integer indicating tenths of Megabytes per second.For example, 20 would indicate 2 Megabytes per second. Any speed may be specified, but the control unit mayin operation select a lower speed than the one specified.

The maxinterlocked optional parameter specifies that this interface is to operate in DC interlocked modeoperation at the highest speed that the interface can handle.

If no interlocked, maxinterlocked, or streamingparameter is specified, then the default ismaxinterlocked.

Example:

cu3990: cu 3990interface parallel cupbt0 addr(0xa0) streaming(45)device(00) 3390-3 /dev/raw/33903a00end cu3990

cupbt0: chanpath/dev/chpbt/ch0 blockmuxend cupbt0

In this example, a control unit is defined which has a parallelinterface provided by thechanpath resource"cupbt0", which in turn specifies an FSI PCA block multiplexor channel path. The control unit is at address a0hexadecimal on the channel, and is configured forstreamingoperation at up to 4.5 Megabytes per second.

5.3.6.3.5. Serial Channel Interface Parameters

. . . interface serial scaresourcename[ addr ( controlunitaddress) ] ? [ path ( pathnum) ] ? [ cuadd (imagenum) ]?

Note: When a Control Unitinterface of type serial is in use, the Control Unit is being used inFLEXCUBThis statement and its parameters should not be confused with the System definitions for FSI SCA attachedperipherals.

Interfaces of theserial type do not take any numeric parameter in parentheses after theparallel keyword (as dolocal andnetwork interfaces as described above). They take one or more parameters specified by additionalkeywords. They require at least one parameter: the name of the resource associated with the FSI SCA. Optionally,they may take any of the following parameters (specified at most once each):addr, path, or cuadd.

Theaddr optional parameter specifies the address of the Control Uniton the Channel. That is, it specifies thefirst device address on the Channel, counting from 00, that the Control Unit will respond to. This address maybe specified in decimal or in hexadecimal, and must be a value between 0 and 255 decimal. If it is not specified,the default is 0.

Thepath optional parameter specifies the logical path number of the interface. When multipleserial interfacesare specified for a single Control Unit, each should have a differentpath number. If it is not specified, the defaultis 0.


24

Note however that multipathing to emulated Control Units isnot presently supported. Thus, while it is not invalidto define multipleserial interfaces to a Control Unit, only one should be used at any time.

Thecuaddoptional parameter specifies the Control Unit image number seen by the interface. The valid range ofvalues is 0 through 0xF. If it is not specified, the default is 0. Thecuaddcorresponds to the "CUADD" parameterin a traditional CNTLUNIT IOCP macro.

For example:

cu3990a: cu 3990interface serial scacu0 addr(0x00) path(0) cuadd(0)device(0x00) 3390-3 /dev/raw/33903b00device(0x01) 3390-3 /dev/raw/33903b01device(0x02) 3390-3 /dev/raw/33903b02device(0x03) 3390-3 /dev/raw/33903b03end cu3990a

scacu0: chanpath/dev/chpbt/ch0 serialend scacu0

5.3.6.4. cu Statement: options

resourcename: cu . . . options ’ optionstring’ . . . end resourcename

Theoptions statement allows a character string of options to be passed to the control unit process. It may appearat most once in anycu statement. This string must be delimited by single apostrophes ("forward single quotes").No spaces are allowed within this quoted string. The contents of this options string are device dependent; theavailable device options are described in the "Emulated Control Unit Options" chapter later in this document.

5.3.6.5. cu Statement: cloned

resourcename: cu . . . cloned. . . end resourcename

A control unit with the optionalclonedstatement creates a new instance of itself each time a new channel pathto it is created. This allows a single definition of a control unit to be used multiple times.

When a control unit is defined ascloned, the meaning of the values for theinterface localandinterface networkstatements changes. In control units defined ascloned, the sum of the values of theseinterface statements istaken to be the maximum number of instances of this control unit which can be created.

A control unit defined asclonedmust have at least oneinterface statement of the type desired.

For example, in a non-cloned control unit such as this:

cu3880: cu 3880interface local(2)interface network(3)device(00-03) 3380-A OFFLINEend cu3880


25

a single instance of the control unit will be created. This single instance will have five interfaces (two on localemulated channels and three on network emulated channels).

By way of contrast, in a cloned control unit such as this:

cu3803: cu 3803clonedinterface local(2)interface network(3)device(00-03) 3420 OFFLINEend cu3803

up to five instances of the control unit would be created (two attached on local emulated channels, three attachedon network emulated channels). Each of these instances would have a single interface. This interface would beof type local or network as required.

A cloned control unit which lacks an interface statement of agiven type may not be attached via that type ofconnection. For example:

cu3803: cu 3803clonedinterface network(3)device(00-03) 3420 OFFLINEend cu3803

In the control unit definition above, the only type of interface specified is anetwork interface. This control unitcould not be attached on anetwork channel.

Control units defined ascloned must not specify finite server resources. This generally means that they mustdefine their devices asOFFLINE . The reason for this is simply that the various clones of the control unit cannotrefer statically to the same resources. Resources to be associated with these control units should be specifiedusing CLImount command.

The only exception to this is the/dev/tty filename for emulated 3215 devices, because this file is differentfor each server OS user.

Emulated 3270 class device names may also be specified statically, but this can result in confusion as each cloneof the control unit would present a set of devices with identical names.

Note that even DASD may be specified asOFFLINE in this fashion. However, since each clone of the controlunit has exactly one interface it is not possible to share CKDDASD usingclonedcontrol units.

Theclonedstatement may appear at most once in anycu definition.

5.3.6.6. cu Statement: tracesize

resourcename: cu . . . tracesize (traceentries) . . . end resourcename


26

The optionaltracesizestatement, if present in a control unit definition, specifiesthe size of the event trace tablemaintained for the control unit in terms of the number of entries in the table. The parameter is a single decimalor hexadecimal integer which must be a power of 2. The minimumvalue is 0. The maximum value is 67108864,however, server memory considerations and the value of the server kernel shared memory tunable parameter maylimit the control unit event trace table size achievable in practice. Each trace buffer entry consumes 16 bytes ofserver RAM.

If this keyword is not specified, the size of the table is set toan unspecified but not unreasonable value.

Note that setting this value to 0 will disable the writing of event trace entries, but may not actually disable thetracing of events and will not necessarily improve performance.

Note that in a system definitiontracesizespecifies the size of the cpu instruction trace buffer, not the cpu eventtrace buffer (which cannot be tuned). In control unit definitions tracesizespecifies the size of the control unit’sevent trace buffer.

5.3.6.7. cu Statement: device

resourcename: cu . . . device (devlist) devtype[ devfile]? [ devopt ’ options’ ]? . . . end resourcename

Thedevicestatement defines the emulated devices attached to this control unit. Multiple devicestatements mayappear in a singlecu block.

Different types of emulated control units have different restrictions on the maximum number of devices theysupport. These restrictions are listed in the chapter "Control Unit Device Limits" later in this volume.

Thedevlistoption specifies either a single device or a range of device numbers. This option is required for eachdevicestatement. When a range of devices is specified, whitespace must be present on each side of the hyphenin the range expression. Whitespace is defined as one or more space, tab, or newline characters.

The actual device address is the sum of the control unit’s address and the device number. (The control unit’saddress is specified in thedevadparameter of thecu statement which defines the control unit to the system inthe system definition.) For instance, if the control unit is at address 180 hexadecimal, device 00 on that controlunit is at device address 180 hexadecimal, device 01 on that control unit is at device address 181 hexadecimal,and so forth.

For example:


interface local(1)

device(00) 3278 OFFLINEdevice(01 - 03) 3278 OFFLINE

end cu3274

In this example, the firstdevicestatement specifies a single device. The seconddevicestatement specifies threedevices, numbered 01 through 03.


27

Device numbers may be any decimal or hexadecimal integer reasonable to use as a device number. However, thenumbering of devices on a control unit must start at zero and be continuous. Device numbers which are specifiedin hexadecimal must be prefixed by the characters0x to indicate that they are in hexadecimal.

Thedevtypeoption specifies the device type. This option must appear in eachdevicestatement. The valid devicetypes are listed in the "Supported Control Units and Devices" section later in this document.

The optionaldevfileparameter specifies the server OS file associated with the device. For example, an emulated1403 printer could be associated initially with a server OS disk file in the following manner:

cu2821: cu 2821

interface local(1)

device(01) 1403 /usr/flexes/print/p1

end cu2821

In this example, an emulated 2821 control unit is defined witha single device attached to it, an emulated 1403printer. This printer prints to a server OS disk file named/usr/flexes/print/p1 .

A device which has mountable device files, such as a printer, tape drive, or card reader, may either have itsdevice file specified here or by themount CLI command. If the device’s file is to be mounted, then the value"OFFLINE" or "offline" should be specified here. For example:


interface local(2)

device(01) 1403 OFFLINE

end cu2821

In this example, an emulated 2821 control unit is defined witha single device attached to it, an emulated 1403printer. This printer will be associated with a particular server OS file when amount command is issued to it,but initially it is not associated with any file and is thus "OFFLINE".

A device such as a channel to channel adapter, which does not require a server OS file, need not have thisparameter specified at all. For example:

cctc: cu ctc

interface local(2)

device(00) ctc

end cctc

In this example, an emulated ctc control unit is defined with asingle device attached to it, an emulated channelto channel adapter.

In the specification of an emulated DASD, thedevfileparameter specifies the server OS disk storage associatedwith that DASD.


28

In the case of an emulated DASD which uses only a single disk chunk, this parameter simply specifies this chunk.

UnixWare example:

cu3880: cu 3880

interface local(1)

device(00) 3380-A /dev/rdsk/c0b0t2d0s3

end cu3880

In this example, an emulated 3880 control unit is defined witha single device attached to it, an emulated 3380-ACKD DASD. This DASD is associated with a UnixWare raw disk slice, identified by the UnixWare "devicespecial" file/dev/rdsk/c0b0t2d0s3 .

Note that devices which specify server OS files, except/dev/tty files, should not becloned.

The optionaldevopt parameter specifies a literal string which is to be passed to the device as startup options.This string must be enclosed in single forward quotes.

The supported keywords and values which may appear indevopt strings are described in the section "EmulatedDevice Options" later in this volume. The examples given in this present section are intended simply to illustratethe use of thedevoptparameter, not to indicate the full range of device options.

If multiple device options are to be given, then all options should be enclosed in a single string. Multiple optionsmust be separated by commas. No spaces are allowed on either side of these commas.

Example:


interface local(3)

device(00) 1403 OFFLINE devopt ’useformfeeds’

end cu2821

In this example, an emulated 2821 control unit is defined to which is attached an emulated 1403 printer. Theserver OS device (file or printer) to be associated with this emulated printer via a CLImount command is definedas one which accepts ASCII formfeed characters.

cu3880: cu 3880

interface local(1)

device(00) 3380-A /dev/rdsk/c1b0t2d0s3 devopt’writethroughcache,trackcachesize=1024’

end cu3880

In this example, an emulated 3880 control unit is defined to which is attached an emulated 3380-A DASD. Theseoptions on this DASD define it to have a write-through cache which caches 1,024 tracks of the DASD to serverRAM.


29

5.3.6.7.1. Directly Connected TN3270 Sessions

Ordinarily, theFLEX ES Terminal Solicitor manages all TN3270 protocol sessions. This provides the greatestdegree of flexibility and the least degree of operator intervention.

Under some circumstances, however, it may be useful to allowTN3270 sessions to connect directly to emulateddevices at particular device addresses. To do this, the TCP/IP IP address of the system from which the TN3270session originates is associated with the 3270 device definition. This may be done in one of two ways.

The IP address may be specified explicitly in the configuration file. For example, the following definition definesan emulated 3274 control unit with one emulated 3278 terminal attached to it. This emulated 3278 is associatedwith the IP address "123.123.123.2". Note that the IP address must have the "at sign" (@) prefixed to it, withoutintervening spaces. This IP address is that of the remote machine on which the user’s 3270 terminal emulatorwill run.

(Note: In addition to numeric IP addresses, any DNS (Domain Name System) hostname resolvable by the servermay be used.)

cu3274: cu 3274

interface local(1)

device(00) 3278 @123.123.123.12

end cu3274

Alternately, the device may be defined as OFFLINE and the CLImount command may be used by the systemoperator to mount the device. For example, assume that a system definition uses the cu3274 control unit definedabove:

system samplesys1:...channel(0) local...cu devad(0x20, 1) path(0) resource(cu3274)...end samplesys1

The CLI mount command would specify the device address of the 3278 and the IP address, prefixed by the "atsign":

mount 20 @123.123.123.12

If this feature is being utilized to provide direct user connection to a mainframe application, bypassing boththe Terminal Solicitor and any mainframe operating system logon screen, it may be necessary to configure themainframe operating system or one of its components (e.g., VTAM) to start the desired application rather than topresent a logon screen.

Multiple 3270 class terminal devices may have the same IP address defined in either of these ways. If multipledevices have the same IP address, any of these devices may be connected to an incoming TN3270 session fromthe IP address so indicated.


30

5.4. Resource Set Grammar Summary

The following informal phrase structure grammar defines thesyntax of the language used to specify resourcesets. Reserved names are printed inbold, user-supplied quantities are printed in italic type, and names used toorganize the grammar are printed in ordinary type.

resources -> resourcesidentifier : resourcedef+end identifierresourcedef -> identifier :bytemux identifierend identifier

-> identifier : blockmux identifierend identifier-> identifier : selectoridentifierend identifier-> identifier : serial identifierend identifier-> identifier : chanpath identifier [blockmux | serial ] end identifier-> identifier : cu cutype rcuopts*end identifier-> nodes: [ identifier+ |anynode] end nodes-> alias identifier = identifier [: identifier ]

rcuopts -> options ’ string ’-> interface intftype-> deviceintlist devtype [identifier |OFFLINE ]? devopt?-> cloned-> tracesize (integer)

intlist -> ( integer)-> ( integer-integer)-> ( integer [, integer ]+)

intftype -> local ( integer)-> network ( integer)-> parallel identifier pcacuopts *-> serial identifier scacuopts *

devopt -> devopt ’ string ’pcacuopts -> addr ( integer)

-> interlocked ( integer)-> maxinterlocked-> streaming ( integer)

scacuopts -> addr ( integer)-> path ( integer)-> cuadd ( integer)

cutype -> {reserved control unit names}devtype -> {reserved device names}

Figure 4 Resource Set Grammar


31

6. System Configurations

A system definition declares the characteristics and features of aFLEX ES emulated system. A resource config-uration file may contain any number of system definitions. These systems are not instantiated until the resourceconfiguration file has been compiled using the resource compiler, cfcomp(1) , and the resultant compiledsystem configuration definition is used as the configuration file for aFLEX ES system being started on a node.

Each system configuration definition begins with the keywordsystem, followed by the name of the system,followed by a colon. Then the resources which define the system are given in a list of statements. Each systemconfiguration definition ends with the keywordend followed by the name of the system. Thus, the overall formof a system configuration definition for a system called "samplesys1" might look like this:

system samplesys1:# system definitions go hereend samplesys1

The following system definition statements are supported:

6.1. cachesize

cachesize (kilobytes)

The cachesize declaration specifies the size of the internal instruction cache for each emulated CPU in anemulated uniprocessor or multiprocessor CPU complex in units of kilobytes of mainframe instructions. In amultiprocessor CPU complex, each CPU has a cache of this size. The actual server RAM used by the translatedinstruction cache is approximately 11 times the value specified. For example, a single-processor Instance witha cachesizeof 1024 would cache one Megabyte (1024 Kilobytes) of mainframe instructions. This would useapproximately 11 Megabytes of server RAM. A two-processor Instance with the samecachesizewould use twicethis.

The CPU instruction cache size defaults to zero if nocachesizestatement is specified. Systems typically shouldspecify a CPU instruction cache size. The numeric value specified should be an integral power of two greaterthan or equal to 64. Setting the value to 0 will turn off caching and will result in a significant performancedegradation.

Values of 1024 to 4096 are reasonable for most present servers and configurations. Typical sizes may be differentin the future and at all times with special configuration requirements.

Thecachesizedeclaration may be specified no more than once per system definition.

Example:

system samplesys1:...cachesize(1024) # K of mainframe instructions of per-CPU ca ching...end samplesys1

In this example, the per-emulated-CPU internal instruction cache is defined to be 1024 kilobytes of mainframeinstructions in size.


32

6.2. channel

channel ( channelnum) [ local | localbyte | localosa | network | networkbyte | networkosa | [ blockmuxdevicefile] | [ bytemux devicefile] | [ selectordevicefile] | [ serial devicefile] ]

The channel declaration defines a channel within the system definition. The channel is assigned a number,channelnum, which may be specified in decimal or in hexadecimal, the value of which must be between 0 and255 (decimal), inclusive. (For System/370 configurations,the channel number must not exceed 32 (decimal.))This channel number will be used later in the system definition’s cu statement’spath parameter.

Ten types of channels are supported:

local channels are emulated block multiplexor or selector channels provided by the local node (host, server)on which this system will be run.

localbytechannels are emulated byte multiplexor channels provided by the local node (host, server) on whichthis system will be run. Emulated control units of type2701dused with the FSI ICA should be attachedto emulated byte multiplexor channels such aslocalbyte channels. (Other types of emulated control unitsused with the FSI ICA should use emulated block multiplexor channels such aslocal channels.)

localosachannels are emulated OSA channels (but not OSA express or OSA direct-express channels)provided by the local node (host, server) on which this system will be run. Only emulated OSA control units(typesosa, osaTR, osasna, andosasnaTR) should be attached tolocalosaemulated channels. Althoughsome mainframe OSs may accept emulated OSA control units attached tolocal (as opposed tolocalosa)channels, the local channel attachment of emulated OSA control units is done most correctly onlocalosaemulated channels.

network channels are emulated block multiplexor or selector channels provided to otherFLEX ES machinesover the TCP/IP network connecting the hosts.

networkbyte channels are emulated byte multiplexor channels provided to otherFLEX ES machines overthe TCP/IP network connecting the hosts. Emulated control units of type2701dused with the FSI ICAshould be attached to emulated byte multiplexor channels such asnetworkbyte channels. (Other typesof emulated control units used with the FSI ICA should use emulated block multiplexor channels such asnetwork channels.)

networkosachannels are emulated OSA channels (but not OSA express or OSA direct-express channels)provided to otherFLEX ES machines over the TCP/IP network connecting the hosts. Onlyemulated OSAcontrol units (typesosa, osaTR, osasna, and osasnaTR) should be attached tonetworkosa emulatedchannels. Although some mainframe OSs may accept emulated OSA control units attached tonetwork (asopposed tonetworkosa) channels, the network channel attachment of emulated OSA control units is donemost correctly onnetworkosaemulated channels.

blockmux channels are physical block multiplexor FSI Parallel Channel Adapter (PCA) channels providedon the local node (host, server) on which this system will be run.

bytemux channels are physical byte multiplexor FSI Parallel Channel Adapter (PCA) channels provided onthe local node (host, server) on which this system will be run.


33

selectorchannels are physical selector FSI Parallel Channel Adapter (PCA) channels provided on the localnode (host, server) on which this system will be run.

serial channels are physical FSI Serial Channel Adapter (SCA) channels provided on the local node (host,server) on which this system will be run. The FSI SCA implements type CNC serial channels (not typesCVC, CBY, or CTC). With type CNC channels, the serial protocol is always block multiplexor.

Example:

system samplesys1:...channel(00) localchannel(01) localbytechannel(02) localosachannel(03) networkchannel(04) networkbytechannel(05) networkosachannel(06) blockmux chpbt0channel(07) bytemux chpbt1channel(08) serial chpbt2...end samplesys1

where there exist named resources such as these:

resources sampleserver1...chpbt0: blockmux /dev/chpbt/ch0 end chpbt0chpbt1: bytemux /dev/chpbt/ch1 end chpbt1chpbt2: serial /dev/chpbt/ch2 end chpbt2...end sampleserver1

In the example above, the first six channels (00 through 05) are emulated channels of various types. Theblockmux andbytemux channels are physical channels provided by one or more optional FSI Parallel ChannelAdapters (PCAs). Theserial channel is a physical channel provided by the optional FSI Serial Channel Adapter(SCA). The physical channel types (FSI PCA and FSI SCA) require in the server’s resource configuration thespecification of a server OS "device special" file to associate the channel with the hardware which is providingthe channel. This file’s name is of the form "/dev/chpbt/ch0 ", where the final number is the number of theFSI PCA or FSI SCA port as it is recognized by the server OS. Theselectorchannel type is not shown, as it israre. It would be coded in the same manner as theblockmux andbytemux channels.

6.3. cpu

cpu ( cpunumber) [ [ dedicated[ ( servercpunumber) ]? ] | [ bound ( servercpunumber) ] ]?


34

Thecpu declaration defines an emulated CPU. The CPU is assigned a number. In the case of ECPS:VSE modeCPUs, this number must be 0. In the case of System/370 mode CPUs, this number must be be 0 or 1. In the caseof FLEX ES ESA mode CPU complexes, which may have up to eight CPUs, this number must be between 0 and7, inclusive. Each CPU is defined with a separatecpu statement, and eachcpu statement within a single systemconfiguration must specify a unique CPU number.

Thededicatedkeyword is optional, and is meaningful only in multiprocessor servers. It indicates that the serverOS should attempt as much as possible to dedicate a single server processor to this CPU. No more than oneInstance may use a given server processor asdedicatedat any given time.

The optional parameter to thededicatedkeyword indicates that the CPU should be dedicated on the indicatedserver processor.

If CPUs in a configuration are to be dedicated, then all CPUs inthe configuration should be declared to bededicated. Do not mix dedicated and non-dedicated CPUs in a single system configuration, and do not mixdedicatedandbound CPUs in a single system configuration.

Thebound keyword is optional, and is meaningful only in multiprocessor servers. It indicates that the emulatedmainframe CPU should run only on the indicated server processor, but that other server work may also run onthis processor. The numeric parameter on thebound keyword which indicates the processor to which the CPUis bound is required.

A CPU may bededicatedor bound, but not both.

Note that once a CPU starts on a particular server processor it will not move to different processors even if it isneitherdedicatednor bound.

It is possible to make mistakes in the use of thededicatedandbound keywords which would require multipleInstances to use more server processors than are enabled. Ifthis is done, the Instance or Instances which forcesuch a condition will not start.

Historical note: The ability to dedicate a CPU specifically to a particular server processor, and the ability to binda CPU to a particular server processor, were of considerablevalue in the NUMA environment (which is no longera shipping environment), where it was desirable to keep server resources together on a single NUMA quad. Itwas thus reasonable in a NUMA server environment to specify,for example, a single processorFLEX ES systemwith its processor bound to a particular server so as to keep processor and memory resources together. Theseconsiderations generally do not apply to SMP servers.

Examples:

system samplesys1:...# A single CPU numbered 0cpu(0)...end samplesys1


35

system samplesys2:...instset(esa)...# A single CPU numbered 3cpu(3)...end samplesys2

system samplesys3:...instset(esa)...# Two un-dedicated, un-bound CPUscpu(0)cpu(1)...end samplesys3

system samplesys4:...instset(esa)...# Two dedicated CPUscpu(0) dedicatedcpu(1) dedicated...end samplesys4

system samplesys5:...instset(esa)...# Two dedicated CPUs, dedicated to specific server processo rscpu(0) dedicated(1)cpu(1) dedicated(0)...end samplesys5

system samplesys6:...instset(esa)...# Two bound CPUscpu(0) bound(1)cpu(1) bound(0)...end samplesys6


36

6.4. cu

cu parameters

Thecu declaration specifies a physical or emulated device controlunit associated with this system configuration.Note that the actual characteristics of emulated control units are defined in the resource configuration for a node.The control unit information provided in the system configuration is the minimum necessary for the operation ofthe channel.

All cu declarations take two required parameters:

devadpath

All cu declarations take at least one additional parameter. The number of additional parameters, as well as theirtypes and values, depends upon the type of the channel (emulated, parallel (FSI PCA), or serial (FSI SCA)) andthe particular characteristics of the control unit, its configuration, and its attachment.

All control units on emulated channels (channel typeslocal, localbyte, localosa, network, networkbyte, andnetworkosa) require a single third parameter:resource. This parameter identifies theFLEX ES resource whichprovides the control unit and its devices.

Physical FSI PCA attached control units do not use theresourceparameter.

Instead, they require at least one additional parameter,unitadd, and also take zero or more of the followingoptional parameters:

interlockedsharedsharedbstreaming

Physical FSI SCA attached control units do not use theresourceparameter. Neither do they use theinterlocked,shared, sharedb, or streamingoptional parameters used by FSI PCA control units.

Instead, they require at least two additional parameters,unitadd andcuadd. If the control unit is attached viaan ESCON Director, then itscu statement must also specify thelink parameter. If the control unit is directlyattached (no ESCON Director), then itscu statement must not specify thelink parameter.

Example:


37

system samplesys1:...channel(0) localchannel(1) networkchannel(2) blockmux chpbt1channel(3) serial chpbt2channel(4) serial chpbt3

cu devad(0x020) path(0) resource(cu3274)cu devad(0x080,6) path(1) resource(cu3803)cu devad(0x090,16) path(2) unitadd(0x90) streaming(45)cu devad(0x300,16) path(3) unitadd(0x00) cuadd(0x00) lin k(0xc1)cu devad(0x310,16) path(4) unitadd(0x00) cuadd(0x00)...end samplesys1

In the example above, the firstcu statement specifies an emulated control unit at device address 020 hexadecimal.The number of devices for which this control unit is configured to respond is not specified and so defaults toone. The secondcu statement specifies an emulated control unit at device address 80 hexadecimal, configuredto respond on any of six devices. The thirdcu statement specifies a physical FSI PCA attached control unit(intended to be a 3480 in this example) at device address 90 hexadecimal, configured to respond on any of 16devices. Fewer than 16 actual tape drives may be installed with this control unit. The fourthcu statementspecifies a physical FSI SCA attached control unit at device address 300 hexadecimal, attached to an ESCONDirector at link address c1 hexadecimal and configured to respond on any of 16 devices. The fifthcu statementspecifies a physical FSI SCA attached control unit at device address 310 hexadecimal which is directly connected(not connected through an ESCON Director). It must not specify the link parameter. Note also that it must beon a different FSI SCA port.

6.4.1. All Channel Types: devad

cu ... devad (devaddr[ , devcount] ) . . .

Thedevadparameter specifies the device address of the control unit and, optionally, the number of devices forwhich the control unit is configured to respond. The device address is a hexadecimal number of no more thanfour digits, prefixed with the characters "0x" to indicate that it is hexadecimal.

Thedevadparameter is required for all channel types.

If present, thedevcountparameter specifies the number of devices for which the control unit is configured torespond. For emulated control units, this is typically the number of devices on the control unit. For PCA andSCA attached physical control units, however, this is not necessarily equal to the number of devices on the controlunit. This parameter may be specified as a decimal number of devices or, when prefixed with the characters"0x", as a hexadecimal number of devices. If thedevcountparameter is not present, then the number of devicesdefaults to one.


38

Note: It is very important that the number of devices specified in thedevadparameter’sdevcountfield matchesexactly the number of devices for which the control unit has been configured to respond. This is true bothfor emulated control units and for PCA and SCA attached physical control units. For PCA and SCA attachedphysical control units, this number is potentially independent of physically installed units. For example, 3480control units often are configured to respond for 16 devices,even though there may be only two or four physicaldrives installed.

6.4.2. All Channel Types: path

cu . . . ... path ( pathnum) ...

The path parameter specifies the channel path by which the control unit is attached to the CPU. The channelpath,pathnum, is a number between 0 and 255 decimal, inclusive. If a hexadecimal number in that range is used,it must be prefixed by the characters "0x" (the numeral zero followed by a lower-case letter x) to indicate that itis hexadecimal.

Thepath parameter is required for all channel types.

There must be exactly one path defined for each control unit. Multiple paths are currently not supported on anytype of channel.

Example:

system samplesys1:...channel(0) localchannel(1) blockmux chpbt0channel(2) networkchannel(3) serial chpbt1

cu devad(0x020,2) path(0) resource(cu3274)cu devad(0x180,6) path(1) unitadd(0x180) interlocked sha redcu devad(0x380,4) path(2) resource(cu3880)cu devad(0x500,16) path(3) unitadd(0x00) cuadd(0x00) lin k(0xc3)...end samplesys1

In the example above, the firstcu statement specifies a control unit on path 0. Path 0, in this definition, is alocalemulated channel. The secondcu statement specifies a control unit on path 1, which is an FSI PCA physicalblock multiplexor channel. The thirdcu statement specifies a control unit on path 2, which is a network emulatedchannel. The fourthcu statement specifies a control unit on path 3, which is an FSI SCA serial channel.

6.4.3. Emulated Channel Types Only: resource

cu . . . resource (resourcename) ...

The resourceparameter specifies theFLEX ES resource which implements this control unit. It is valid onlyfor, and is required on, control units attached via emulatedchannel paths (local, localbyte, localosa, network,networkbyte, andnetworkosachannel paths).


39

Example:

system samplesys1:...channel(0) localchannel(1) network

cu devad(0x020,2) path(0) resource(cu3274)cu devad(0x080,6) path(1) resource(cu3803)...end samplesys1

In the example above, the firstcu statement specifies a control unit implemented by the resource "cu3274", whilethe secondcu statement specifies a control unit implemented by the resource "cu3803".

6.4.4. FSI PCA Only: interlocked

cu ... interlocked ...

The interlocked optional parameter specifies that the control unit should operate in DC Interlocked mode. Itis only valid for control units connected via physical Parallel Channel Adapter (PCA) channels specified asbytemux, blockmux, or selector.

Example:

system samplesys1:...channel(0) blockmux chpbt0

cu devad(0x20,2) path(0) unitadd(0x20) interlocked...end samplesys1

6.4.5. FSI PCA Channels: shared

cu requiredparmsshared

Thesharedoptional parameter specifies that the devices to be attachedto this control unit have an I/O concurrencylevel of 1. Such devices share Unit Control Words ("UCWs"), but do not block on unit checks as willsharedbdevices. This parameter is only valid for control units connected via physical Parallel Channel Adapter (PCA)channels specified asblockmux, or selector.

Example:


cu devad(0x20,4) path(0) unitadd(0x20) interlocked share d...end samplesys1


40

6.4.6. FSI PCA Channels: sharedb

cu requiredparmssharedb

The sharedb optional parameter specifies that the devices to be attachedto this control unit have an I/Oconcurrency level of 3. Such devices share Unit Control Words ("UCWs"), as doshared devices. However,when a unit check occurs on asharedbdevice, the device’s control unit must hold any further I/O to any deviceson that control unit until it starts I/O to the device which unit checked. This parameter is only valid for controlunits connected via physical Parallel Channel Adapter (PCA) channels specified asbytemux, blockmux, orselector.

Example:


cu devad(0x220,32) path(0) unitadd(0x20) interlocked sha redb...end samplesys1

6.4.7. FSI PCA Only: streaming

cu ... streaming (speed) ...

Thestreamingoptional parameter specifies that the control unit should operate in streaming mode at a speed upto the indicated speed. Valid speeds are the same as those forcontrol unit interfaces:20, 30, and45, indicating2.0 Megabytes per second, 3.0 Megabytes per second, and 4.5 Megabytes per second, respectively. It is onlyvalid for control units connected via physical Parallel Channel Adapter (PCA) channels specified asblockmux,or selector.

Example:


cu devad(0x80,2) path(0) unitadd(0x80) streaming (45)...end samplesys1

In this example, a control unit is defined at channel address 80 hexadecimal, connected through channel path 0, aParallel Channel Adapter (PCA) block multiplexor channel.This control unit attaches two devices and operatesin streaming mode, at speeds up to 4.5 Megabytes per second.

Note that the control unit itself always controls the actualchannel transfer rate, so in practice the speed specifiedhere may not be realized.

6.4.8. FSI SCA Only: link

cu ... link ( linkaddr ) ...


41

Thelink parameter specifies the ESCON Director port or link number Itis required for control units attached viaESCON Directors to FSI SCA channels. It is incorrect to specify this for FLEX ES emulated control units, forFSI PCA attached control units, or for directly attached (noESCON Director) FSI SCA attached control units.

Example:

system samplesys1:...channel(1) serial chpbt0

cu devad(0x220,32) path(1) unitadd(0x00) cuadd(0x00) lin k(0xc1)...end samplesys1

In this example, a single control unit presented at device address 220 hexadecimal is attached to an FSI SCAattached ESCON Director at link address c1 hexadecimal.

6.4.9. FSI SCA Only: cuadd

cu ... cuadd ( imagenumber) ...

Thecuadd required parameter specifies the control unit image number of a control unit on an FSI SCA channel.The imagenumbermust be in the range 0 to 15, decimal. It must be specified even if the number it specifies iszero. This statement is valid only for, and is required on, control units attached via FSI SCA channels.

system samplesys1:...channel(1) serial chpbt0

cu devad(0x220,32) path(1) unitadd(0x00) cuadd(0x02) lin k(0xc3)...end samplesys1

6.4.10. FSI PCA and SCA Channels: unitadd

cu ... unitadd ( unitaddress) ...

The unitadd parameter specifies the unit address of the first device attached to a physical Parallel ChannelAdapter (PCA) or Serial Channel Adapter (SCA) attached control unit. It is only valid for control units attachedvia these types of channels, and is required for such controlunits (even if the address it specifies is zero). Thevalueunitaddressmust be in the range 0 to 255 decimal (but may be specified in decimal or hexadecimal).

Example:


42

system samplesys1:...channel(0) blockmux chpbt0channel(1) serial chpbt0

cu devad(0x20,6) path(0) unitadd(0x20) interlockedcu devad(0x430,16) path(1) unitadd(0x00) cuadd(0x00)...end samplesys1

In the first case above, a control unit is defined at address 20 hexadecimal, connected through channel path 0, aphysical FSI PCA block multiplexor channel and operating inDC Interlocked mode. This control unit attachessix devices. In the second case, a control unit is defined at address 430 hexadecimal, connected through channelpath 1, a physical FSI SCA serial channel. Since nolink parameter is specified, this control unit must be directlyattached (not attached via an ESCON Director).

6.5. epoch

epoch[ gmt | local ] date

Theepoch declaration specifies the epoch according to which the emulated ESA/370’s TOD clock will be set.When aFLEX ES system is invoked, the ESA/370 TOD clock is always set to the current time (based on theserver OS system time), assuming a particular starting epoch.

The epoch may be set in relation tolocal time or to Universal Coordinated Time (called "gmt" for its formerdesignation, "Greenwich Mean Time"). In each case, a beginning year must be specified. The epoch begins onJanuary 1 of the specified year, at 00:00.

The "Standard Epoch" recommended in theIBM System/370 Principles of Operation[IBM: GA22-7000] beginson January 1, 1900 relative togmt. However, some systems (e.g., OS/360 MVT) require an epoch beginningrelative tolocal time, 1960. If no value is set by theepochdeclaration, then the "Standard Epoch" is assumed.

Example:epoch local 1960

Example:epoch gmt 1900

6.6. essize

essize (Megabytes)

The essizedeclaration specifies the size of the Expanded Storage of theemulated machine in a decimal orhexadecimal number of Megabytes. The number of Megabytes specified must be evenly divisible by 16. If thespecified Expanded Storage size is too large, given server space and mainframe architectural limitations, thiswill be indicated at system startup. Expanded Storage is notvalid on 370 mode and ECPS:VSE mode emulatedmachines.

Theessizedeclaration is optional. If it does not appear, then the CPU has no Expanded Storage.


43

The maximum allowable value foressizeis determined by the architecture. Expanded Storage consists of4 kilobyte blocks which are addressable by a 32 bit unsigned integer. This gives a theoretical maximum of4,294,967,296 4 kilobyte blocks, or 16,777,216 Megabytes (16 Terabytes). This maximum exceeds the practicallimits of current machines. AFLEX ES CPU may fail to start if it requests more Expanded Storage than can besupplied by the server.

Additionally, the server imposes both physical limitations (that is, a certain amount of RAM will have beeninstalled on the server) and server OS limitations. These limitations are dicussed further in the chapter "Memory"in volume FSIMM300:System Programmer’s Guide.

6.7. feature (System/370 Mode)

feature [ 4kpgonly | das | ea | ef | key4k | lpar | mp | nomvcin | sus| vma ]

The feature declaration specifies several optional features of the emulated CPUs of Instances. This sectionidentifies the features appropriate to a370(System/370) mode Instance. The features listed here are, unless noted,not relevant tovsemode (ECPS:VSE),esamode (ESA/390, ESA/370 and 370-XA), orz mode (z/Architecture64-bit) Instances.

If multiple features are to be declared for the Instance, each should be declared in its ownfeature statement (thatis, specify only one feature perfeature statement).

The following features may be defined:

feature 4kpgonly

Some System/370 machines did not come with 2K page translation. Thefeature 4kpgonly declarationdisables 2K page translation (in each of the CPUs of this system configuration) for compatibility with suchmachines.

feature das

The feature dasdeclaration enables the "Dual Address Space" feature in theCPU complex of this systemconfiguration.

feature ea

The feature eadeclaration enables the "Extended Real Addressing" feature in each of the CPUs of thissystem configuration.

feature ef

The feature efdeclaration enables the "Extended Facility" in each of the CPUs of this system configuration.Note that the MVS Assist feature is a part of the Extended Facility.

feature key4k

The feature key4k declaration enables the "Storage Key 4K-Byte-Block Facility" in each of the CPUs ofthis system configuration.


44

feature lpar

FLEX ES does not implement PR/SMTM or its Logical Partition (LPAR) capabilities. However, to accom-modate certain software,FLEX ES may be configured to respond to control program queries as if the controlprogram were running in an LPAR.

Thefeature lpar declaration is used to accomplish this. Thelpar feature is valid in370mode (System/370)Instances. (It is also valid inesamode (z/Architecture 31-bit, ESA/390, ESA/370 and 370-XA)andz mode(z/Architecture 64-bit) Instances, but is not valid invsemode (ECPS:VSE) Instances.) It sets the LPAR bitin the System Control Program (SCP) information. It has no other effect.

In FLEX ES releases starting with 7.0.4, iffeature lpar is coded, then both thelparnum statement, and thelparname statement must also be coded. It is always necessary to recompile theFLEX ES configuration filewhen moving from a release earlier than 7.0.4 to a current release. If the existing configuration includesfeature lpar then it may be necessary to recode thelparnum statement to conform to the current rules forthat statement, and it will be necessary to add an appropriate lparname statement.

In FLEX ES releases through 7.0.3,feature lpar could be coded without coding thelparnum statement, andthe lparname statement did not exist.

feature lpar may be of use in avoiding "active wait" in VM systems. It is also required when thelparnumstatement is coded. For further discussion of the use offeature lpar, see volumes FSIMM300:SystemProgrammer’s Guide. and FSIMM320:Resource Language Tutorial.

AlthoughFLEX ES does not implement PR/SM, it does have the ability to run multiple operating systemson the same machine through the use of multipleFLEX ES Instances.

feature mp

The feature mp declaration enables multiprocessing for this system configuration.

feature nomvcin

The feature nomvcindeclaration disables the Move Inverse Facility (MVCIN) forthis system configuration.

feature sus

The feature susdeclaration turns on the ESA/370 suspend/resume facility.If not specified, then this facilitydefaults to off.

feature vma

The feature vma declaration enables the "Virtual Machine Assist" in each ofthe CPUs of this systemconfiguration.

6.8. feature (ESA/390 Mode)

feature [ lpar | enable370]


45

The feature declaration specifies several optional features of the emulated CPUs of Instances. This sectionidentifies the features appropriate to anesa(ESA/390, ESA/370 and 370-XA) mode Instance. The features listedhere are, unless noted, not relevant to370 mode (System/370),z mode (z/Architecture 64-bit), orvsemode(ECPS:VSE) Instances.

If multiple features are to be declared for the Instance, each should be declared in its ownfeature statement (thatis, specify only one feature perfeature statement).

The following features may be defined:

feature enable370

370 mode SIE guests are normally disabled on ESA instructionset Instances. Setting this feature enables370 mode guests. This should be done only if 370 mode guests are required, as it may lead to a performancedegradation.

(Note: VM/ESA 2.2.0 and older releases of VM/ESA ESA featureCP require System/370 mode SIE featuresin order to IPL. The absence of these features will result in adisabled wait state "9030" if an attempt ismade to IPL. VM/ESA 2.3.0 and later do not require these features to IPL. These features are not enabledby default inFLEX ES, but may be enabled through the use of "feature enable370".)

feature lpar


Thefeature lpar declaration is used to accomplish this. Thelpar feature is valid inesamode (z/Architecture31-bit, ESA/390, ESA/370 and 370-XA) Instances. (It is alsovalid in 370mode (System/370) andz mode(z/Architecture 64-bit) Instances, but is not valid invsemode (ECPS:VSE) Instances.) It sets the LPAR bitin the System Control Program (SCP) information. It has no other effect.

Note: One other LPAR-related characteristic, the LPAR number, may be specified through the use of thelparnum statement described elsewhere in this volume.



6.9. feature (z Mode)

feature [ lpar ]

The feature declaration specifies several optional features of the emulated CPUs of Instances. This sectionidentifies the features appropriate to az mode (z/Architecture 64-bi) mode Instance The features listed here are,unless noted, not relevant to370mode (System/370),esamode (ESA/390, ESA/370 and 370-XA), orvsemode(ECPS:VSE) Instances.


46

The following feature may be defined:

feature lpar


Thefeature lpar declaration is used to accomplish this. Thelpar feature is valid inz mode (z/Architecture64-bit) Instances. (It is also valid in370mode (System/370) andesamode (z/Architecture 31-bit, ESA/390,ESA/370 and 370-XA) Instances, but is not valid invsemode (ECPS:VSE) Instances.) It sets the LPAR bitin the System Control Program (SCP) information. It has no other effect.

Note: One other LPAR-related characteristic, the LPAR number, may be specified through the use of thelparnum statement described elsewhere in this volume.



6.10. feature (ECPS:VSE Mode)

No feature declarations are available forvse(ECPS:VSE) mode.

6.11. instset

instset ([ 370 | esa| 390 | z | vse] )

The instsetstatement specifies the operating mode of theFLEX ES Instance. Valid values are: "370", "esa" (forwhich "390" is a synonym), "z" (in versions ofFLEX ES which support it), and "vse". This statement must becoded exactly once in each system definition.

The "370" value specifies System/370 mode operation. For System/370mode operation with Extended RealAddressing, see alsofeature ea

Example:instset(370)

The "esa" and "390" values are synonyms for each other. They specify ESA/390 mode operation. If "esa" isused, it must be in lower case. There are no modes corresponding specifically to 370-XA or to ESA/370. If youneed a 370-XA or ESA/370 Instance, you should define it as anesaInstance.

Example:instset(390)

Example:instset(esa)

The "z" value, which must be in lowercase, specifies the z/Architecture R© mode of operation. It may be specifiedonly when using aFLEX ES license which is enabled for z/Architecture support.


47

Example:instset(z)

The "vse" value specifies ECPS:VSE mode operation.

Example:instset(vse)

6.12. lparname

lparname ( lparname)

Thelparnum statement allows the specification of the Instance’s LPAR name (not surprisingly). If this statementis coded, thenfeature lpar andlparnum must also be coded.

The LPAR name specified must be a one to eight character stringcomposed of digits or alphabetic letters. It mustbe without whitespace and enclosed between a pair of single quotes or a pair of double quotes. It must beginwith a non-digit first character. Both uppercase and lowercase letters may be used in coding this statement, butlowercase letters are converted to uppercase letters automatically by the Resource Compiler.

The following LPAR names are reserved by IBM and may not be used: "PHYSICAL", "REC", "SYSTEM", andnames of the form "PRIMnnnn" (where "nnnn" is a four digit string of hexadecimal digits).

This statement was introduced inFLEX ES release 7.0.4.

6.13. lparnum

lparnum ( lparnumber)

Thelparnum statement allows the specification of the Instance’s LPAR number. This number must be a decimalor hexadecimal number from 1 to 15 (1 to F), inclusive. The statement has no other effect.

If this statement is specified, then thefeature lpar andlparname statements must also be specified. Because allthree statements must be used if any of the three are used (as enforced sinceFLEX ES Release 7.0.4), there is nolonger any concept of a defaultlparnum value.

This statement is meaningful only ifinstsetspecifies370mode (System/370),esamode (z/Architecture 31-bit,ESA/390, ESA/370 and 370-XA), orz mode (z/Architecture 64-bit). It is not meaningful, and should not bespecified, invse(ECPS:VSE) mode.

Migration Note: Because of the changes tolparnum , feature lpar, andlparname introduced inFLEX ES Release7.0.4, it is necessary to recompileFLEX ES configurations when moving to the current release from releases priorto 7.0.4. This is the case whether or not these configurationsinvolvedfeature lpar or lparnum . Additionally, ifthese configurations involved uses offeature lpar or lparnum it will be necessary to re-code them to meet thecurrent configuration language requirements forlparnum , feature lpar, andlparname.

Historical Note: In release 7.0.4, the behavior of thelparnum statement changed. Previously, anlparnum of0 was accepted by the Resource Compiler and it was possible, although not meaningful, to specify anlparnumwithout also specifyingfeature lpar andlparname (which did not then exist as a statement).

Compatibility Note: The use oflparnum , lparname, andfeature lpar provide only the functionality specifiedhere. They do not imply the general functionality of the PR/SM Facility.


48

Application Note: Thelparnum statement may be of use with shared DASD under the VSE operating system.For further discussion of the use of this statement, see volumes FSIMM300:System Programmer’s Guide. andFSIMM320: Resource Language Tutorial.

6.14. memsize

memsize (kilobytes)

Thememsizestatement specifies the size of the Main Storage of the emulated machine. This statement must becoded exactly once in each system definition.

The value specified here is subject to restrictions based on the architectural level of the emulated machine. Thesearchitectural limitations are discussed in the following sections.

Additionally, the server imposes both physical limitations (that is, a certain amount of RAM will have beeninstalled on the server) and server OS limitations. These limitations are dicussed further in the chapter "Memory"in volume FSIMM300:System Programmer’s Guide.

6.14.1. 370 memsize

For machines operating in370mode without Extended Real Addressing (that is, whenfeature eais not coded),the value formemsizeis specified as a decimal or hexadecimal number of kilobytes.The maximum value is16384 decimal (0x4000 hexadecimal), which represents 16 Megabytes. Values may be specified in 1 kilobyteincrements, though care should be taken to ensure that a reasonable system is defined given the standard 2 kilobytepage size (or 4 kilobyte page size iffeature 4kpgonly is coded).

The minimum value is 0, but generally this is not useful.

Values should be specified without commas or spaces. Hexadecimal values, if used, should be prefixed with thetwo character string "0x" (the numeral zero followed by the lowercase letter x).

Example:memsize(8192)

Example:memsize(0x2000)

In both of these examples, Main Storage is defined to be 8,192 kilobytes (8 Megabytes) in size.

6.14.2. 370 EA memsize

For machines operating in370 mode with Extended Real Addressing (that is, whenfeature ea is coded), thevalue for memsize is specified as a decimal or hexadecimal number of kilobytes.The maximum value is65536 decimal (0x10000 hexadecimal), which represents 64 Megabytes. Values may be specified in 1 kilobyteincrements, though care should be taken to ensure that a reasonable system is defined given the standard 2 kilobytepage size (or 4 kilobyte page size iffeature 4kpgonly is coded).




49



In both of these examples, Main Storage is defined to be 32,768kilobytes (32 Megabytes) in size.

6.14.3. 390 (370XA, ESA/370, ESA/390) memsize

For machines operating in390 (esa) mode, the value formemsizeis specified as a decimal or hexadecimalnumber of kilobytes. Values specified must be evenly divisible by 1 Megabyte. The maximum value whichmay be specified is 2097152 decimal (0x200000 hexadecimal),which represents 2 Gigabytes. However, specificserver environments may impose further limitations. If large values (in excess of 1 Gigabyte) are contemplated,please consult your FSI certified reseller. Note that while very large values may be specified, Main Storagesize should never be so large that, taken together with various other server RAM considerations it causes thepaging of emulated Main Storage from server RAM. For a further discussion of server RAM issues, see volumeFSIMM300: System Programmer’s Guide.





In both of these examples, Main Storage is defined to be 1,048,576 kilobytes (1 Gigabyte) in size.

6.14.4. z memsize

For machines operating inz (z/Architecture) mode, the value formemsizeis specified as a decimal or hexadecimalnumber of kilobytes. Values specified must be evenly divisible by 1 Megabyte. The maximum value whichmay be specified is 2097152 decimal (0x200000 hexadecimal),which represents 2 Gigabytes. However, specificserver environments may impose further limitations. If large values (in excess of 1 Gigabyte) are contemplated,please consult your FSI certified reseller. Note also that while very large values may be specified, Main Storagesize should never be so large that, taken together with various other server RAM considerations it causes thepaging of emulated Main Storage from server RAM. For a further discussion of server RAM issues, see volumeFSIMM300: System Programmer’s Guide.





In both of these examples, Main Storage is defined to be 1,048,576 kilobytes (1 Gigabyte) in size.


50

6.14.5. vse memsize

For machines operating invsemode, the value formemsizeis specified as a decimal or hexadecimal numberof kilobytes. The only permitted value, however, is 16384 decimal (0x4000 hexadecimal), representing 16Megabytes.

The value should be specified without commas or spaces. A hexadecimal value, if used, should be prefixed withthe two character string "0x" (the numeral zero followed by the lowercase letter x).



In both of these examples, Main Storage is defined to be 16384 kilobytes (16 Megabytes) in size.

6.15. timerres

timerres ( bitposition)

The timerres declaration specifies the resolution of the interval timer.The interval timer is a 32 bit word inemulated Main Storage. The interval timer is so constructedthat its bit position 23 is, or would be, reduced by 1every 1/300 of a second. Thebitpositionargument totimerres specifies the highest (closest to 31) bit positionthat contains meaningful timer information. The valid values for this argument are 21 through 31.

6.16. tracesize

tracesize (traceentries)

All FLEX ES CPUs implement two kinds of tracing: event tracing and instruction tracing.

Event tracing is done automatically. It cannot be disabled or configured. When a CPU encounters an error suchthat it dumps an "alert trace" to Server OS disk, it is this event tracing information which is dumped.

Instruction tracing is done only when tracing or breakpointing is enabled. This slows the CPU executionconsiderably, and is only done in debugging situations. Instruction tracing is recorded in a circular buffer. Inmultiprocessor CPU complexes, a separate instruction trace buffer exists for each CPU.

The tracesize declaration specifies the size of the instruction trace buffer of each CPU in terms of the numberof trace entries. All CPUs in a multiprocessor CPU complex have trace buffers of this size.

The minimum valid value for the instruction trace buffer size is zero. However, this can hamper debuggingoperations on a running system if it is determined that instruction tracing is required. (In order to change thesize of the instruction trace buffer, the system must be rebooted with a new configuration; it cannot be changeddynamically.) In typical installations, therefore, a minimum value of 256 is suggested. Typical reasonable valuesfor current systems might range from 1024 to 4096.

Example:tracesize(4096)



51

In both of these examples, the trace table is defined to be 4096trace entries in size.

6.17. System Grammar Summary

The following informal phrase structure grammar defines thesyntax of the language used to specify systemdefinitions. Reserved names are printed inbold, user-supplied quantities are printed in italic type, and namesused to organize the grammar are printed in ordinary type.

system -> system identifier: sysdef+end identifiersysdef -> memsize (integer)

-> essize (integer)-> cachesize (integer)-> tracesize (integer)-> instset ([ 370 | esa| 390] )-> lparname ( name)-> lparnum ( integer)-> feature [ featurez | featureesa | feature370 | featurevse ]-> timerres ( bitposition)-> epoch[ gmt | local ] date-> cpu ( integer) dedicated-> channel ( integer) channeltype-> cu cuoption*

featurez -> [ lpar ]featureesa -> [lpar | s390only]feature370 -> [4kpgonly | das | ea | ef | key4k | lpar | mp | nomvcin | sus| vma s390only ]featurevse -> { none}channeltype -> local

-> localbyte-> localosa-> network-> networkbyte-> networkosa-> blockmux devicefile-> bytemux devicefile-> selector devicefile

cuoption -> devad (devaddr [ , devcount ]?)-> path ( pathnum [, pathnum ]*)-> resource (resourcename)-> unitadd ( unitaddress)-> streaming (speed)-> interlocked-> shared-> sharedb

Figure 5 System Definition Grammar


52


53

7. Supported Control Units and Devices

7.1. Control Units

The following table lists the supported emulated control units. Each type of control unit supports the indicatedtypes of emulated devices. Refer to the tables of devices later in this chapter for more information on thecharacteristics of the devices. Note that some DASD device names designate equivalent devices. For example,a 3380Ssingle density 3380 is effectively the same as a3380-A. Note also that the names for control units anddevices do not necessarily correspond exactly with physical control units or devices.

CU Name Emulated Device Name(s)

2314 23142835 2305-23880 3330, 3330-11, 3340-35, 3340-70, 3350,

3375, 3380-A, 3380-D, 3380-E, 3380-J,3380-K, 3380S, 3380D, 3380T

3990 3380-A, 3380-D, 3380-E, 3380-J, 3380-K,3380S, 3380D, 3380T, 3390-1, 3390-2, 3390-3,3390S, 3390D, 3390T, 3390-9,

9341 9345-1, 9345-29343 9345-1, 9345-26880 6280

Figure 6 CKD DASD Control Units


3310 33103880FBA 3370, 3370-1, 3370-26010 9332-200, 9332-400, 9332-600, 93356310 9332-200, 9332-400, 9332-600, 9335, 9336-10, 9336-20

Figure 7 FBA DASD Control Units


54


3422 3422as FakeTape, AWSTAPE, or OMA/2 (read-only)3422as Cartridge Tape (DAT (DDS), DLT)3422as SCSI 9-Track



3480 3480as FakeTape, AWSTAPE, or OMA/2 (read-only)3480as Cartridge Tape (DAT (DDS), DLT)3480as SCSI 3480

3490 3490as FakeTape, AWSTAPE, or OMA/2 (read-only)3490as Cartridge Tape (DAT (DDS), DLT)3490as SCSI 34903490-Eas FakeTape, AWSTAPE, or OMA/2 (read-only)3490-Eas Cartridge Tape (DAT (DDS), DLT)3490-Eas SCSI 3490-E

3803 3420,-4,-6,-8as FakeTape, AWSTAPE, or OMA/2 (read-only)3420,-4,-6,-8as Cartridge Tape (DAT (DDS), DLT)3420,-4,-6,-8as SCSI 9-Track

3590 3590as FakeTape, AWSTAPE, or OMA/2 (read-only)

Figure 8 Tape Control Units

Note: The3423differs from the3422only in the sense ID information returned. Consult the IBM documentationfor your IBM operating system concerning the use of devices defined as3423 with that operating system.Otherwise, use the3422device type in preference to the 3423.

Note: TheFLEX ES type 3590emulated tape drive supports operation only to server disk (as FakeTape, AW-STAPE, or OMA/2). It does not support operation to server cartridge tape.


55


2701 twx(2701 ASCII Telegraph Adapter Type II tty terminal)Xxtwx (X based TWX terminal)twxmodem (TWX full-duplex ASCII modem)twxmodemh (TWX half-duplex ASCII modem)bsca(Emulated BSC over TCP/IP)

2701d rbsca(FSI ICA BSC)rsdlc (FSI ICA SDLC)rttc2 (FSI ICA TTC2)

3172 3172(3172, EthernetTM functionality, for TCP/IP)3172TR 3172(3172, Token Ring functionality, for TCP/IP)3174 3270 Displays (3178, 3179, 3180, 3278, 3279, 3290)3215 3215(3215 tty-style)

3215nc(3215, tty-style, no curses)Xx3215(3215 X-based)Xx3215nc(3215 X-based, no curses)

3274 3270 Displays (3178, 3179, 3180, 3277, 3278, 3279, 3286-1, 3286-2, 3290)9221ICA bsca(Emulated BSC over TCP/IP)9373ICA bsca(Emulated BSC over TCP/IP)6034 ceti8025(CETI 4 Megabit Token Ring, for TCP/IP and SNA)6035 ceti8023(CETI Ethernet, for TCP/IP)6134 ceti8025(CETI 16 Megabit Token Ring, for TCP/IP and SNA)9221ICAd rbsca(FSI ICA BSC)

rsdlc (FSI ICA SDLC)rttc2 (FSI ICA TTC2)

9373ICAd rbsca(FSI ICA BSC)rsdlc (FSI ICA SDLC)rttc2 (FSI ICA TTC2)

k200 k200(emulated Spartacus/Fibronics Ethernet controller, for TCP/IP)osa osa(OSA Ethernet for TCP/IP)osaTR osa(OSA Token Ring for TCP/IP)osasna osasna(OSA Ethernet for SNA)osasnaTR osasna(OSA Token Ring for SNA)xca xca(XCA Ethernet for TCP/IP)xcaTR xca(XCA Token Ring for TCP/IP)xcasna xcasna(XCA Ethernet for SNA)xcasnaTR xcasna(XCA Token Ring for SNA)

Figure 9 Communications Control Units

Note: The Ethernet controllers (3172, osa, osasna, xca, xcasna, 6035, andk200) and their devices, in conjunctionwith server Ethernet hardware, provide Ethernet functionality. TCP/IP and SNA functionality based on this isprovided by the mainframe operating system. Similarly, theToken Ring controllers (3172TR, osaTR, osasnaTR,xcaTR, xcasnaTR, 6034, and6134) and their devices, in conjunction with server Token Ring hardware, provideToken Ring functionality. TCP/IP and SNA functionality based on this is provided by the mainframe operatingsystem.


56


2501 2501Card Reader2821 2540RCard Reader/Punch, Reader Side

2540PCard Reader/Punch, Punch Side1403Printer1403-N1Printer

3203 3203-1, -2, -4, -5Printers3211 3211Printers3262 3262-1, -11Printers4245 4245Printers

4245-1Printers4245-12Printers4245-20Printers

4248 4248Printers4248-1Printers4248-2Printers

Figure 10 Unit Record Control Units


ctc ctc (Channel to Channel Adapter)

Figure 11 Other Control Units

7.2. Devices

The following tables gives theFLEX ES resource configuration names for the supported emulated device types.


57

Name Device

2305-2 2305 Model 22314 23143330 3330 Model 1 (a single 3336-1 disk pack)3330-11 3330 Model 11 (a single 3336-11 disk pack)3330-II synonym for 3330-113340-35 3340 (a single 3348 - 35 Data Module)3340-70 3340 (a single 3348 - 70 Data Module)3350 3350 Native Mode3375 33753380S 3380 Single Density (888 cylinders)3380-A 3380 Model A (888 cylinders)3380-D 3380 Model D (888 cylinders)3380-J 3380 Model J (888 cylinders)3380D 3380 Double Density (1774 cylinders)3380-E 3380 Model E (1774 cylinders)3380T 3380 Triple Density (2660 cylinders)3380-K 3380 Model K (2660 cylinders)3390S 3390 Single Density (1117 cylinders)3390-1 3390 Model 1 (1117 cylinders)3390D 3390 Double Density (2230 cylinders)3390-2 3390 Model 2 (2230 cylinders)3390T 3390 Triple Density (3343 cylinders)3390-3 3390 Model 3 (3343 cylinders)3390-9 3390 Model 9 (10038 cylinders)6280 Amdahl 62809345-1 9345-019345-2 9345-01

Figure 12 Emulated CKD DASD Names

Name Device

3310 33103370 3370, 3370-1 FBA DASD3370-1 3370-1 FBA DASD3370-2 3370-2 FBA DASD9332-200 9332-2009332-400 9332-4009332-600 9332-6009335 93359336-10 9336-109336-20 9336-20

Figure 13 Emulated FBA DASD Names


58

Name Device

3172 3172 Communications Controller, Ethernet functionality3172TR 3172 Communications Controller, Token Ring functionality3178 3178 Display3179 3179 Display3180 3180 Display3215 3215 Console (under a tty-style interface)3215nc 3215 Console (under a tty-style interface, no curses)3270n 3270-series Terminal, networked (with TN3270)3277 3277 Display3278 3278 Display3279 3279 Display3286 3286 Display/Printer3286-1 3286-1 Display/Printer3286-2 3286-2 Display/Printer3290 3290 DisplayXx3215 3215 Console (under the X Window System, using a curses-based interface)Xx3215nc 3215 Console (under the X Window System, no curses)Xxtwx 2701 ASCII Telegraph Adapter Type II (TWX) (under the X WindowSystem)bsca Emulated BSC (BiSync) line over TCP/IPceti8023 CETI Ethernetceti8025 CETI Token Ring, 4 Megabit if on 6034 controllerceti8025 CETI Token Ring, 16 Megabit if on 6134 controllerk200 k200 Spartacus/Fibronics Ethernet controllerosa OSA TCP/IP over Ethernet or Token Ringosasna OSA SNA over Ethernet or Token Ringrbsca FSI ICA BSC (BiSync) linersdlc FSI ICA SDLC linerttc2 FSI ICA TTC2 line (US ASCII Telegraph Control Type 2)twx 2701 ASCII Telegraph Adapter Type II (TWX) (under a tty-styleinterface)twxmodem 2701 ASCII Telegraph Adapter Type II (TWX) (as a full-duplex ASCII modem)twxmodemh 2701 ASCII Telegraph Adapter Type II (TWX) (as a half-duplex ASCII modem)xca XCA TCP/IP over Ethernet or Token Ringxcasna XCA SNA over Ethernet or Token Ring

Figure 14 Emulated Display, Console, Terminal, and Communication Line Names

Note that display devices on local or network channel paths are supported via the TN3270 protocol, and thereforerequire a 3270 front-end program such asx3270(1) for use.


59

Name Description

3420 3420 (Emulated or SCSI responding as 3420)3420-4 3420 (Emulated or SCSI responding as a 3420-4)3420-6 3420 (Emulated or SCSI responding as a 3420-6)3420-8 3420 (Emulated or SCSI responding as a 3420-8)3422 3422 (Emulated or SCSI responding as 3422)3423 3423 (Emulated or SCSI responding as 34223)3430 3430 (Emulated or SCSI responding as 3430)3480 3480 (Emulated or SCSI responding as 3480)3490 3490 (Emulated or SCSI responding as 3490)3490-E 3490-E (Emulated or SCSI responding as 3490-E)3590 3590 (Emulated only, responding as 3590)

Figure 15 FLEX ES Emulated and SCSI-Attached Tape Drive Names

Name Description

1403 1403 Printer1403-N1 1403 N1 Printer2501 2501 Card Reader2540 2540 Card Reader/Punch as a punch2540P 2540 Card Reader/Punch as a punch2540R 2540 Card Reader/Punch as a reader3203-1 3203-1 Printer3203-2 3203-2 Printer3203-4 3203-4 Printer3203-5 3203-5 Printer3211 3211 Printer3262-1 3262-1 Printer3262-11 3262-11 Printer3286 3286 Printer4245 4245 Printer4245-1 4245-1 Printer4245-12 4245-12 Printer4245-20 4245-20 Printer4248 4248 Printer4248-1 4248-1 Printer4248-2 4248-2 Printer

Figure 16 Emulated Unit Record Equipment Names

The following printers originally designed as display/printers are supported.


60

Name Description

3286 3286 Display/Printer3286-1 3286-1 Display/Printer3286-2 3286-2 Display/Printer

Figure 17 Other Emulated Printer Names

Name Device

ctc Emulated Channel-to-Channel Adapter

Figure 18 Miscellaneous Emulated Devices


61

8. Control Unit Device Limits

The following limitations on the number of devices which maybe defined for a single control unit apply toFLEX ES emulated control units (including those used with the FSI ICA). They do not apply to physical PCAattached control units.

CU Name Maximum Devices

2314 322835 323880 323990 329341 329343 326880 32

Figure 19 CKD DASD CU Device Limits


3310 2563380FBA 2566010 2566310 256

Figure 20 FBA DASD CU Device Limits


3422 2563423 2563430 2563480 2563490 2563803 256

Figure 21 Tape CU Device Limits


62


2701 with bsca device 12701 with other devices 2562701d 63172 23172TR 23174 2563215 2563274 2569221ICA 19221ICAd 69373ICA 19373ICAd 66034 exactly 46035 exactly 46134 exactly 4k200 exactly 3osa exactly 2osaTR exactly 2osasna exactly 1osasnaTR exactly 1xca exactly 2xcaTR exactly 2xcasna exactly 1xcasnaTR exactly 1

Figure 22 Communications CU Device Limits

Note also that control units of types2701d, 9221ICAd, and9373ICAd cannot be defined ascloned.


2501 2562821 2563203 2563211 2563262 2564245 2564248 256

Figure 23 Unit Record CU Device Limits


63


ctc exactly 1

Figure 24 Other CU Device Limits

Note that control units of typectc cannot be defined ascloned.


64


65

9. Nonstandard CKD Emulated DASD Maximums

Note: These data are not a part of the configuration language at all. They are included here for convenienceof reference. They are more properly documented in volumes FSIMM200: Operator’s Guideand FSIMN050:Installing AWS DASD Images

Support for non-standard sized CKD emulated DASD is provided for all FLEX ES or FLEXCUB CKD emulatedDASD models, even those models emulating devices which did not support the Read Device CharacteristicsCCW. Unlike standard sizedFLEX ES or FLEXCUB CKD emulated DASD,FLEX ES or FLEXCUB non-standardsized CKD emulated DASD have no alternate, CE, or SA cylinders or blocks.

For all CKD emulated DASD types except the 3380-K, 3380T, and3390-9, the maximum number of cylindersfor a nonstandard variant of the device is the same as the number of primary (not alternate, CE, or SA) cylindersthat would ordinarily exist on a standard device of the same type. For nonstandard 3380-K and 3380T DASD,the maximum is 3,393 cylinders (this limit was introduced inrelease 7.0.5). For nonstandard 3390-9 DASD, themaximum is 32,760 cylinders. These values are summarized inthe table below, together with the track size (inKilobytes) and the number of tracks per cylinder for each DASD type.

To find the total space required for a CKD emulated DASD of nonstandard size, multiply the track size timesthe number of tracks per cylinder times the total number of cylinders. Convert the result from Kilobytes toMegabytes. Note that a Megabyte is 1024 Kilobytes, or 1,048,576 bytes. If the DASD is to be emulated onmultiple chunks, for each chunk add an amount not less than the FLEX ES or FLEXCUB requirement for anadditional cylinder (in practice, it is often easiest simply to add another Megabyte). Then round the total up tothe next integral Megabyte.


66

Type Track Size (K) Tracks/Cyl NumCyls

2305-2 15 8 962314 8 20 2003330 13 19 4043330-11 13 19 8083340-35 9 12 3483340-70 9 12 6963350 19 30 5553375 36 12 9593380-A 47 15 8853380-D 47 15 8853380-J 47 15 8853380S 47 15 8853380-E 47 15 17703380D 47 15 17703380-K 47 15 33933380T 47 15 33933390-1 57 15 11133390S 57 15 11133390-2 57 15 22263390D 57 15 22263390-3 57 15 33393390T 57 15 33393390-9 57 15 327606280 27 20 8339345-1 47 15 14409345-2 47 15 2156

Figure 25 Nonstandard CKD Emulated DASD Maximums


67

10. Emulated Device Fields

This chapter summarizes the fourth field of thedevicestatement. The first field of this statement is the keyword"device" itself. The second field, contained in parentheses, is the device number. Devices must be numberedsequentially starting from 0. The third field is the device name. The contents of the fourth field vary considerably,but in general it describes the environment-specific information needed by the device. These four fields arerequired (the only exception is thectc device, which takes no fourth field). An additional, optional, devoptdevice option field may be present. (Specifying device options usingdevopt is discussed in a later chapter.)

10.1. Emulated DASD

10.1.1. CKD Emulated DASD

The fourth field for CKD emulated DASD contains either the keyword OFFLINE (which indicates that thedevice is offline) or the fully qualified filename of the first (or only) chunk used as backing storage for the DASD.For example:

cu3880: cu 3880interface local(1)device(00) 3380 /usr/flexes/dasd/wk01device(01) 3380 OFFLINEend cu3880

10.1.2. FBA Emulated DASD

The fourth field for FBA emulated DASD contains either the keywordOFFLINE (which indicates that the deviceis offline) or the fully qualified filename of the chunk used as backing storage for the DASD. For example:

cu3880FBA: cu 3880FBAinterface local(1)device(00) 3370 /usr/flexes/dasd/3370-1device(01) 3370 OFFLINEend cu3880FBA

10.2. Emulated Tape Devices

The fourth field for emulated tape devices contains either the keywordOFFLINE (which indicates that the deviceis offline), or the fully qualified filename of the first FakeTape, AWSTAPE, or OMA/2 "tape" to be mounted bythis device, or the server OS device special filename of the SCSI server cartridge (DAT, DLT) tape drive or SCSI3480, 3490, or 3490-E compatible tape drive to be used with this device.

For FakeTape, AWSTAPE, and OMA/2, this filename is the server OS filename of the emulated tape.

For server-attached (SCSI) mainframe compatible tape drives and server cartridge tape acting as mainframe tape(DLT, DAT), this filename is the server OS device special filename of the drive.

In the UnixWare environment, this SCSI tape name may take anyof several forms (such as/dev/rmt/ctape1or /dev/rmt/c0s0n ).


68

In the Linux environment prior toFLEX ES Release 6.2.16, only "SCSI generic" device special filenames couldbe used for SCSI tape. This restriction has been removed, andin current releases the "SCSI tape" names may beused.

SCSI generic device special filenames take the form/dev/sg0 , etc. while SCSI tape device special filenamestake the form/dev/st0 . In the Linux environment, the available SCSI generic devices may be determinedin several ways. Thescsi info(1) command may be used, specifying/dev/sgN device special filenamesuntil all have been discovered. This information may also bedetermined by examining, as root, the virtual filesin the directory/proc/scsi/sg

For example:

cu3490: cu 3490interface local(1)device(00) 3490 /bigspace/tape00 # FakeTape filedevice(01) 3490 /dev/rmt/ctape1 # server cartridgedevice(02) 3490 /dev/rmt/ctape2 # SCSI 3490 compatibledevice(03) 3490 OFFLINEend cu3490

In the example above, server OS device special filenames of the form appropriate for UnixWare/OpenUNIX areused.

cu3490l: cu 3490interface local(1)device(00) 3490 /bigspace/tape00 # FakeTape filedevice(01) 3490 /dev/sg1 # server cartridgedevice(02) 3490 OFFLINEdevice(03) 3490 OFFLINEend cu3490

In the example above, server OS device special filenames of the form appropriate for UnixWare/OpenUNIX areused.

10.3. Emulated Communications Devices

10.3.1. TN3270 Emulated Devices

Emulated TN3270 terminal devices used with emulated3174control units (3178, 3179, 3180, 3278, 3279, and3290) and with emulated3274control units (3178, 3179, 3180, 3277, 3278, 3279, 3286-1, 3286-2, 3290) take asa fourth field either the keywordOFFLINE (which indicates that the device is offline) or an arbitrary name whichidentifies the device. Restrictions on valid names are discussed in volume FSIMM300:System Programmer’sGuide. Names used in this field need not be unique. For example, the following are both valid:


69

cu3274a: cu 3274interface local(1)device(00) 3278 consoledevice(01) 3278 termdevice(02) 3278 termdevice(03) 3278 OFFLINEend cu3274a

cu3274b: cu 3274interface local(1)device(00) 3278 consoledevice(01) 3278 term1device(02) 3278 term2device(03) 3278 OFFLINEend cu3274b

Whether the use of many identical names (with perhaps a few unique names for special devices such as theconsole) is more or less confusion to the user is left as an exercise for the reader.

10.3.2. Emulated 3172 Devices for TCP/IP

Control units for emulated 3172 Ethernet or Token Ring devices used for TCP/IP (control unit types3172and3172TR) must specify exactly two devices.

The first of these two devices takes as a fourth field either thekeywordOFFLINE (which indicates that thecontrol unit and its devices are offline) or the server OS identification of the Ethernet or Token Ring server device.In the UnixWare/OpenUNIX environment, this will be the server OS device special filename for the Ethernet orToken Ring NIC (Network Interface Controller). In the Linuxenvironment this will be the Linux interface name(e.g., "eth0"). The second of these two devices must specifythe keywordOFFLINE .

Examples (UnixWare/OpenUNIX):

cu3172: cu 3172interface local(1)device(00) 3172 /dev/net1device(01) 3172 OFFLINEend cu3172

cu3172TR: cu 3172TRinterface local(1)device(00) 3172 /dev/net1device(01) 3172 OFFLINEend cu3172TR

Examples (Linux):


70

cu3172: cu 3172options ’ipaddress=192.168.0.1’interface local(1)device(00) 3172 eth0device(01) 3172 OFFLINEend cu3172

cu3172TR: cu 3172TRoptions ’ipaddress=192.168.0.1’interface local(1)device(00) 3172 tr0device(01) 3172 OFFLINEend cu3172TR

10.3.3. Emulated OSA and XCA Devices for TCP/IP

Control units for emulated OSA and XCA Ethernet or Token Ringdevices used for TCP/IP (control unit typesosa, osaTR, xca, andxcaTR) must specify exactly two devices.

The first of these two devices takes as a fourth field either thekeywordOFFLINE (which indicates that thecontrol unit and its devices are offline) or the server OS identification of the Ethernet or Token Ring server device.In the UnixWare/OpenUNIX environment, this will be the server OS device special filename for the Ethernet orToken Ring NIC (Network Interface Controller). In the Linuxenvironment this will be the Linux interface name(e.g., "eth0"). The second of these two devices must specifythe keywordOFFLINE .


cuosa: cu osainterface local(1)device(00) osa /dev/net1device(01) osa OFFLINEend cuosa

cuosaTR: cu osaTRinterface local(1)device(00) osa /dev/net1device(01) osa OFFLINEend cuosaTR

Examples (Linux):

cuxca: cu xcaoptions ’ipaddress=192.168.0.1’interface local(1)device(00) xca eth0device(01) xca OFFLINEend cuxca


71

cuxcaTR: cu xcaTRoptions ’ipaddress=192.168.0.1’interface local(1)device(00) xca tr0device(01) xca OFFLINEend cuxcaTR

10.3.4. Emulated OSA and XCA Devices for SNA

Control units for emulated OSA and XCA Ethernet or Token Ringdevices used for SNA (control unit typesosasna, osasnaTR, xcasna, andxcasnaTR) must specify exactly one device. This device takes as a fourth fieldeither the keywordOFFLINE (which indicates that the control unit and its device is offline) or the server OSidentification of the Ethernet or Token Ring server device. In the UnixWare/OpenUNIX environment, this willbe the server OS device special filename for the Ethernet or Token Ring NIC (Network Interface Controller). Inthe Linux environment this will be the Linux interface name (e.g., "eth0").


cuosasna: cu osasnainterface local(1)device(00) osasna /dev/net1end cuosasna

cuosasnaTR: cu osasnaTRinterface local(1)device(00) osasna /dev/net1end cuosasnaTR

Examples (Linux):

cuxcasna: cu xcasnainterface local(1)device(00) xcasna eth0end cuxcasna

cuxcasnaTR: cu xcasnaTRinterface local(1)device(00) xcasna tr0end cuxcasnaTR

10.3.5. Emulated CETI

Control units for emulated CETI Ethernet or Token Ring devices:

Control unit type6035with devices of typeceti8023, for TCP/IPControl unit type6034with devices of typeceti8025, for TCP/IPControl unit type6034with devices of typeceti8025, for SNAControl unit type6134with devices of typeceti8025, for TCP/IPControl unit type6134with devices of typeceti8025, for SNA


72

must specify exactly four emulated devices. The first of these four devices takes as a fourth field either the keywordOFFLINE (which indicates that the control unit and its devices are offline) or the server OS identification ofthe Ethernet or Token Ring server device. In the UnixWare/OpenUNIX environment, this will be the serverOS device special filename for the Ethernet or Token Ring NIC (Network Interface Controller). In the Linuxenvironment this will be the Linux interface name (e.g., "eth0"). The rest of the devices must specify the keywordOFFLINE .


cu6035uw: cu 6035 # Ethernet for TCP/IPinterface local(1)device(00) ceti8023 /dev/net1device(01 - 03) ceti8023 OFFLINEend cu6035uw

cu6034uw1: cu 6034 # 4 M/s Token Ring for TCP/IP or SNAinterface local(1)device(00) ceti8025 /dev/net1device(01 - 03) ceti8025 OFFLINEend cu6034uw1

cu6134uw2: cu 6134 # 16 M/s Token Ring for TCP/IP or SNAinterface local(1)device(00) ceti8025 /dev/net1device(01 - 03) ceti8025 OFFLINEend cu6134uw2

Examples (Linux):

cu6035lx: cu 6035 # Ethernet for TCP/IPoptions ’ipaddress=192.168.0.1’interface local(1)device(00) ceti8023 eth0device(01 - 03) ceti8023 OFFLINEend cu6035lx

cu6034lx1: cu 6034 # 4 M/s Token Ring for TCP/IPoptions ’ipaddress=192.168.0.1’interface local(1)device(00) ceti8025 tr0device(01 - 03) ceti8025 OFFLINEend cu6034lx1

cu6134lx1: cu 6134 # 16 M/s Token Ring for TCP/IPoptions ’ipaddress=192.168.0.1’interface local(1)device(00) ceti8025 tr0device(01 - 03) ceti8025 OFFLINEend cu6134lx1


73

cu6034lx2: cu 6034 # 4 M/s Token Ring for SNAinterface local(1)device(00) ceti8025 tr0device(01 - 03) ceti8025 OFFLINEend cu6034lx2

cu6134lx2: cu 6134 # 16 M/s Token Ring for SNAinterface local(1)device(00) ceti8025 tr0device(01 - 03) ceti8025 OFFLINEend cu6134lx2

Note that a space is required on each side of the hyphen (dash)in the device range specification. If a control unitoptionsstatement is present, the string it specifies must contain nospaces.

10.3.6. Emulated k200 Devices for TCP/IP

Thek200 emulation of a Spartacus/Fibronics Ethernet control unit must specify exactly three devices, each oftypek200. The first of these three devices takes as a fourth field eitherthe keywordOFFLINE (which indicatesthat the control unit and its devices are offline) or the server OS identification of the Ethernet server device. Inthe UnixWare/OpenUNIX environment, this will be the serverOS device special filename for the Ethernet NIC(Network Interface Controller). In the Linux environment this will be the Linux interface name (e.g., "eth0").The rest of the devices must specify the keywordOFFLINE .

(Note: Thek200 is an emulated Ethernet control unit; it does not support Token Ring. Typically, mainframe OSsupport provides only TCP/IP, not SNA, over this control unit.)

Example (UnixWare/OpenUNIX):

cuk200: cu k200interface local(1)device(00) k200 /dev/net1device(01 - 02) k200 OFFLINEend cuk200

Example (Linux):

cuk200: cu k200options ’ipaddress=192.168.0.1’interface local(1)device(00) k200 eth0device(01 - 02) k200 OFFLINEend cuk200

Note that a space is required on each side of the hyphen (dash)in the device range specification.


74

10.3.7. TWX Emulated Devices

Emulated TWX terminal devices (device typestwx, andXxtwx ) which display either on a server console, ona server emulated terminal (e.g., an "xterm"), or via the server’s X Window System display, take as a fourthfield either the keywordOFFLINE (which indicates that the device is offline) or the server OS pseudo-device"/dev/tty ". Multiple TWX devices all take this same filename; the serverOS resolves it into differentpseudo-devices for each TWX.

cutwx1: cu twxinterface local(1)device(00) twx /dev/ttydevice(01) Xxtwx /dev/ttydevice(02) Xxtwx /dev/ttydevice(03) twx OFFLINEend cutwx1

If the TWX line is used by a physical serial-attached terminal, however, it specifies as its fourth field either thekeywordOFFLINE (which indicates that the device is offline) or the server OS device special filename of theserial line on which the terminal is attached. For example:

cutwx2: cu twxinterface local(1)device(00) twx /dev/ttyS0device(01) twx OFFLINEend cutwx2

(The serial line specified in the example above is of a form appropriate for Linux.)

If the emulated TWX terminal device is to attach a modem (device typestwxmodem, andtwxmodemh) it takesas a fourth field either the keywordOFFLINE (which indicates that the device is offline) or the server OS devicespecial filename of the serial line on which the modem is attached.

cutwxmodem: cu twxmodeminterface local(1)device(00) twx /dev/ttyS0device(01) twx OFFLINEend cutwxmodem

(The serial line specified in the example above is of a form appropriate for Linux.)

10.3.8. 3215 Emulated Devices

Emulated 3215 terminal devices (device types3215, 3215nc, Xx3215, andXx3215nc) take as a fourth field eitherthe keywordOFFLINE (which indicates that the device is offline) or the server OS pseudo-device "/dev/tty ".Multiple 3215 devices all take this same filename; the serverOS resolves it into different pseudo-devices for each3215. For example:


75

cu3215: cu 3215interface local(1)device(00) 3215 /dev/ttydevice(01) 3215nc /dev/ttydevice(02) Xx3215 /dev/ttydevice(03) Xx3215nc /dev/ttydevice(04) 3215 OFFLINEdevice(05) 3215 OFFLINEend cu3215

10.3.9. FSI ICA Emulated Devices

FSI ICA emulated BSC (rbsca), SDLC (rsdlc), and TTC2 (rttc2 ) devices, attached to control units of type2701d, 9221ICAd, or 9373ICAd, take as a fourth field either the keywordOFFLINE (which indicates that thedevice is offline) or the server OS device special filename which specifies the FSI ICA line associated with thisdevice. For example:

cu2701d: cu 2701dinterface local(1)options ’/dev/emu/emu0p0:/usr/open370/bin/emu.img’device(00) rbsca /dev/fsiica/ica0p0device(01) rsdlc /dev/fsiica/ica0p1device(02) rbsca OFFLINEdevice(03) rsdlc OFFLINEend cu2701d

Note that the device options (not shown in the example above,which takes the default device options) are oftenquite important in FSI ICA definitions. For further information, see the "Emulated Device Options" chapter laterin the present volume, and the volume FSIMM300:System Programmer’s Guide.

10.3.10. Emulated BSC Devices

For further information on emulated BSC (binary synchronous) communications devices (device typebscaoncontrol units of types2701, 9221ICA, or 9373ICA, not FSI ICA devices) please contact your FSI authorizedreseller.

10.4. Emulated Unit Record Devices

10.4.1. Emulated Printers

Emulated printers take as a fourth field either the keywordOFFLINE (which indicates that the device is offline)or the server OS filename for the server file to which the emulated printer is to "print." (This file can be changedlater from the CLI.)

cu2821: cu 2821interface local(1)device(00) 1403 /space/printout1device(01) 1403 OFFLINEend cu2821


76

10.4.2. Emulated Card Equipment

Emulated card readers and punches take as a fourth field either the keywordOFFLINE (which indicates that thedevice is offline) or the server OS filename for the server file from which the emulated reader is to read input orto which the emulated punch is to punch output. (These files can be changed later from the CLI.)

cu2821: cu 2821interface local(1)device(00) 2540R /space/inputdeckdevice(01) 2540R OFFLINEdevice(02) 2540P /space/outputdeckdevice(03) 2540P OFFLINEend cu2821

10.5. Other Emulated Devices

Control units for emulated CTC take exactly one device of type ctc. This device is unusual as it takes takesnothing at all as a fourth field.

cuctc: cu ctcinterface local(2)device(00) ctcend cuctc

(Note: The emulated CTC is also unusual in that it must specify two interfaces. Further information is availablein volume FSIMM300:System Programmer’s Guide.)


77

11. Emulated Control Unit Considerations

11.1. Channel Types for Emulated 2701d Control Units

The emulated 2701d control unit used with the FSI ICA must be attached via an emulated byte multiplexorchannel (eitherlocalbyteor networkbyte).

The other emulated control units used with the FSI ICA (9221ICAdand9373ICAd) may be attached via emulatedblock multiplexor channels (eitherlocal or network).

11.2. Channel Types for Emulated OSA Control Units

Emulated Open Systems Adapter (OSA) Ethernet and Token Ringcontrol units (typesosa, osaTR, osasna, andosasnaTR) should be attached vialocalosaor networkosaemulated channels.

If the Instance is to run one of the z/OS family of mainframe operations systems, OSA control units must be soconnected (vialocalosaor networkosaemulated channels).

If the Instance is to run one of the z/VM family of mainframe operating systems, it is possible to connectemulated OSA control units vialocal or network emulated channels. However, it is more correct to uselocalosaor networkosaemulated channels.


78


79

12. Emulated Control Unit Options

The options described in this chapter are specified at the control unit level via the control unitoptionsstatement.For example:

cuoptexample: cu 3990interface local(1)options ’trackcachesize=100’device(00) 3390-3 /usr/flexes/dasd/syswk01end cuoptexample

12.1. CKD DASD Emulated Control Units

12.1.1. trackcachesize

trackcachesize=numtracks

All cache specified via the device’sdevoptparameter is cache dedicated to a particular device. It is also possibleto specify cache in the control unit’soptionsstatement. If the value so specified is less than or equal to the totaldedicated cache for all devices attached to the control unit, then this value has no effect. However, if the value sospecified is greater than the total dedicated cache for all devices attached to the control unit, then the additionalcache specified by the difference between this value and the dedicated cache total is applied as cache which floatson an as-needed basis between the devices on the control unit.

The value oftrackcachesizespecifies a decimal number of tracks. It need not be an even multiple of any value.All CKD emulated DASD control units may specify this option.

The minimum value which should be specified is 5. This value isequal to the minimum specifiable value for thecache size of a single DASD.

The total cache for a CKD emulated DASD control unit, including all cache on all devices and all "floating"cache in the control unit, cannot exceed 8,191 tracks. This limit is enforced at run time, not by the configurationfile compiler (cfcomp(1) ).

For some control unit and device combinations, it is possible to specify more tracks of cache than there are on alldevices on the control unit. However, doing so merely wastesserver RAM.

To calculate the server RAM required by CKD emulated DASD caching, first calculate the amount of spacerequired for the caches dedicated to each device. (Multiplythe number of tracks of cache for the device by therequired track size of the device. For information on the required track sizes, see volume FSIMM100:PlanningGuide. If devices with different track sizes are attached to the control unit, use the track size of the largest devicefor all calculations.) Then calculate the amount of space required for the floating cache using the same method.Add these two values for the total space requirements. For example:

cufloatcache: cu 3990interface local(1)options ’trackcachesize=20’device(00) 3390-3 /usr/flexes/dasd/339031 devopt ’track cachesize=5’device(01) 3380-A /usr/flexes/dasd/3380A1 devopt ’track cachesize=5’end cufloatcache


80

The device on the control unit with the largest track size is the 3390-3 (requiring 57 kilobytes per track) so itstrack size will be used in these calculations. Device 00, an emulated 3390-3, specifies 5 tracks of cache andtherefore requires (5 tracks * 57 kilobytes/track) = 285 kilobytes of server RAM for its cache. Device 01 is anemulated 3380-A, which has a smaller track size. However, since it is on a control unit with a device with a largertrack size, the track size of that larger device should be used. The calculation for this device is therefore thesame: (5 tracks * 57 kilobytes/track) = 285 kilobytes of server RAM for its cache. The two devices, therefore,require 570 kilobytes of server RAM for their dedicated caches. Additionally, the control unit provides (20 - 5 -5) = 10 tracks of floating cache. The space requirements for this floating cache should be calculated on the basisof the largest tracksize on any device on the control unit; 57kilobytes/track in this example. Thus: (10 tracks *57 kilobytes/track) = 570 kilobytes of server RAM for floating cache. Taken together, the caches of this controlunit require 1,140 kilobytes of server RAM.

A further discussion of the nature of DASD caching appears inthe volume FSIMM300System Programmer’sGuide.

See also the device option (devopt) trackcachesizelater in this present volume.

12.1.2. ssid

ssid=idnum

This option is valid only on 3880, 3990, and 9341, and 9343 CKDDASD control units. It specifies the subsystemID for the control unit. The value specified must be exactly four hexadecimal digits.

The subsystem ID is particularly important in modern z/OS and OS/390 installations. In these installations, eachCKD DASD control unit of types 3880, 3990, 9341, and 9343 musthave a unique SSID. If they do not, theoperating system may exhibit unusual behavior (for example, devices may appear and disappear apparently atrandom).

In releases ofFLEX ES through (and including) 5.9.20, if the SSID was not specifiedexplicitly it defaulted tohexadecimal 0000.

In releases ofFLEX ES from 5.9.21, if the SSID of a CKD DASD control unit is not specified explicitly it defaultsto one more than the control unit’s sequential number in the configuration file. Thus, the zeroth 3880, 3990,9341, or 9343 CKD DASD control unit to appear in a resource configuration file is given a default SSID of 0001,the first such CU is given a default SSID of 0002, and so forth.

If a control unit specifies an SSID explicitly, that SSID is used. Such a control unit still counts in the sequence bywhich default control units are defined. Thus, if the zeroth and first control units use default SSIDs, their SSIDswill be 1 and 2, respectively. If the second control unit specifies an SSID explicitly, it will use its specified SSID.If the third control unit uses a default SSID, its SSID will be4.

Note that the assignment of default SSIDs is uniform within asingle resource configuration definition. It itunrelated to the system definitions of the Instance or Instances which will attach the control units.

There are three situations where reliance upon default SSIDs can produce duplicate SSIDs.


81

First, if a resource configuration is refreshed with modifiedCKD DASD control unit definitions, it is possible forthe new default SSIDs to conflict with existing ones. For thisreason, it is recommended that before refreshinga resource set in which default SSIDs are significant and may have changedall currently running 3880, 3990,9341, and 9342 CKD DASD control units be terminated.

Second, since the default SSID depends upon the position of the control unit in a resource configuration file,network channel attached control units may have duplicate SSIDs. The solution in this case is to specify SSIDsexplicitly.

Third, if a control unit specifies an SSID that is the same as a default SSID, both will have the same SSID. Donot do this.

12.1.3. smartsid

smartsid

This option allows the CKD emulation to search all the records on a track using one SID CCW rather than havingto fetch a separate SID CCW for each record. This may improve the performance of certain applications.

12.2. Ethernet and Token Ring Emulated Control Units

12.2.1. adapternumber

Emulated 3172, OSA, and XCA control units, types:

3172(3172 TCP/IP Ethernet)3172TR(3172 TCP/IP Token Ring)osa(OSA TCP/IP Ethernet)xca (XCA TCP/IP Ethernet)osaTR(OSA TCP/IP Token Ring)xcaTR (XCA TCP/IP Token Ring)osasna(OSA SNA Ethernet)xcasna(XCA SNA Ethernet)osasnaTR(OSA SNA Token Ring)xcasnaTR(XCA SNA Token Ring)

optionally may be supplied with anadapternumber string in anoptionsstatement.

adapternumber=anum

This specifies the adapter number of the control unit as seen from mainframe OS services such as VTAM. It isunrelated to the adapter number of the underlying Ethernet or Token Ring NIC (Network Interface Controller).This number must match the number configured in the mainframeoperating system. This option may be specifiedat most once.

Valid values for TCP/IP control units are in the range 0 to 255, inclusive. If this option is not specified, the defaultvalue is 0. For example:


82

cu3172: cu 3172options ’adapternumber=1’interface local(1)device(00) 3172 OFFLINEdevice(01) 3172 OFFLINEend cu3172

The example above specifies that the adapter number of a 3172 TCP/IP control unit is 1, not the default of 0.

Valid values for SNA control units are in the range 1 to 255, inclusive. If this option is not specified, the defaultvalue is 1. For example:

cuosa: cu osasnaoptions ’adapternumber=2’interface local(1)device(00) osa /dev/net1device(01) osa OFFLINEend cuosa

The example above specifies that the adapter number of an OSA SNA control unit is 2, not the default of 1.

12.2.2. enablemgtime

All emulated CETI control units, types:

6035(CETI 6035 Ethernet)6034(CETI 6034 4 Megabit Token Ring)6134(CETI 6134 16 Megabit Token Ring)

optionally may be supplied with anenablemgtimekeyword in anoptionsstatement.

enablemgtime

This option controls the response of these control units to MGTIME attention interrupts. If this option is notspecified, the default value is to ignore MGTIME attention interrupts. If this option is specified, MGTIMEattention interrupts are recognized. This option may be specified at most once.

12.2.3. ipaddress

All emulated Ethernet and Token Ring control units on which mainframe operating systems provide TCP/IPsupport, types:


83

3172(3172 TCP/IP Ethernet)3172TR(3172TR TCP/IP Token Ring)osa(OSA TCP/IP Ethernet)xca (XCA TCP/IP Ethernet)osaTR(OSA TCP/IP Token Ring)xcaTR (XCA TCP/IP Token Ring)6035(CETI 6035 TCP/IP Ethernet)6034(CETI 6034 TCP/IP 4 Megabit Token Ring)6134(CETI 6134 TCP/IP 16 Megabit Token Ring)k200 (k200 TCP/IP Ethernet)

optionally may be supplied with anipaddressstring in anoptionsstatement.

ipaddress=ipaddr

The IP address, addresses, or range or ranges of addresses specified by one or moreipaddressoptions shouldbe thought of as filters. Packets reaching the control unit with a destination IP address which matches the IPaddress(es) specified are accepted by the control unit. Packets which do not match are ignored. Ifipaddressisnot specified, then the control unit accepts all packets regardless of their destination address.

The IP address must be specified in "dotted quad" notation (with an optional CIDR-style bitmask; see below).Host names and fully or partially qualified DNS names are not permitted. This option may be specified multipletimes within a single control unitoptionsstring, up to a maximum of fourteen times.

If desired, the IP address may be specified using a CIDR (Classless Inter-Domain Routing) style bitmask. Thisis written as a forward slash character after the IP address,followed by a decimal number in the range 0 to 32.No spaces are allowed. The decimal number specifies the number of contiguous bits, proceeding from the left,in a bitmask that is applied to 32-bit IP(v4) addresses. Portions of an IP address that are masked on (1) areinterpreted as network bits, while portions masked off (0) are interpreted as host bits. For example, if the CIDR-style ipaddressof 192.168.1.0/24 is specified, the bitmask would be (expressed in decimal) "255.255.255.0".The leftmost 24 bits (masked by "255.255.255") would specify one of 16,777,216 (256**3) possible networks,leaving the rightmost 8 bits (masked by "0") to specify one of256 possible hosts within this network. With thisCIDR-style addressing, a singleipaddressoption can now specify an entire network of hosts.

For convenience, here is a table of CIDR-style netmasks:


84

CIDR netmask number of networks hosts per network note/8 255.0.0.0 256 (256 * (256 **2)) = 16,777,216 former class A/9 255.128.0.0 256 * 2 (128 * (256 **2)) = 8,388,608/10 255.192.0.0 256 * 4 (64 * (256 **2)) = 4,194,304/11 255.224.0.0 256 * 8 (32 * (256 **2)) = 2,097,152/12 255.240.0.0 256 * 16 (16 * (256 **2)) = 1,048,576/13 255.248.0.0 256 * 32 (8 * (256 **2)) = 524,288/14 255.252.0.0 256 * 64 (4 * (256 **2)) = 262,144/15 255.254.0.0 256 * 128 (2 * (256 **2)) = 131,072/16 255.255.0.0 (256**2) (256 * 256) = 65,536 former class B/17 255.255.128.0 (256**2) * 2 (128 * 256) = 32,768/18 255.255.192.0 (256**2) * 4 (64 * 256) = 16,384/19 255.255.224.0 (256**2) * 8 (32 * 256) = 8,192/20 255.255.240.0 (256**2) * 16 (16 * 256) = 4,096/21 255.255.248.0 (256**2) * 32 (8 * 256) = 2,048/22 255.255.252.0 (256**2) * 64 (4 * 256) = 1,024/23 255.255.254.0 (256**2) * 128 (2 * 256) = 512/24 255.255.255.0 (256**3) 256 former class C/25 255.255.255.128 (256**3) * 2 128/26 255.255.255.192 (256**3) * 4 64/27 255.255.255.224 (256**3) * 8 32/28 255.255.255.240 (256**3) * 16 16/29 255.255.255.248 (256**3) * 32 8/30 255.255.255.252 (256**3) * 64 4/31 255.255.255.254 (256**3) * 128 2 see RFC 3021/32 255.255.255.255 (256**3) * 256 1 route to an individual host

Figure 25

Note that in this table the number in the "hosts per network" column includes addresses 0 and 255 within eachnetwork. Typically, these addresses are reserved, meaningthat in practice "/30" is the largest CIDR-style bitmaskgenerally in use.

CIDR values down to "/0" are legal, but as "/8" (former class A) represents the largest networks assigned by theIANA (Internet Assigned Number Authority), values under "/8" would be useful only in unusual circumstancesin intranets.

In the UnixWare environment, each emulated Ethernet or Token Ring control unit must be associated with aphysical Network Interface Controller (NIC), and this NIC is not shared with UnixWare. Consequently, if it isassumed that all packets which reach the control unit are in fact intended for it, theipaddressoption need not bespecified. (It may, however, be specified if desired.)


85

In the Linux environment, each emulated Token Ring control unit must be associated with a physical TokenRing NIC (interfacetr0 , tr1 , and so forth). Each emulated Ethernet control unit must be associated either with aphysical Ethernet NIC (interfaceeth0, eth1, etc.) or with the virtual TUN/TAP device (interfacetun). PhysicalNICs may be shared with the host Linux system. If the emulatedcontrol unit is associated with a physical NIC,and if this physical NIC is also available for use by the host Linux system, then at least oneipaddressoptionshould be specified. If done correctly, this ensures that theFLEX ES mainframe and the mainframe OS runningon it see only those packets intended for them, rather than all packets on the NIC. If the emulated control unit isassociated with the virtual TUN/TAP interface, then theipaddressoption need not be specified for this reason(see the section on thetunipaddressoption, below). It may be specified if desired, however, and may be of usein, for example, configuring the control unit when proxyARP support is used in VM’s TCP/IP configuration insupport of guest LANs or other guests whose TCP/IP stacks have no direct LAN connection

An emulated control unit which uses theipaddressoption may be cloned.

The following example defines an emulated 3172 Ethernet controller which specifies a singleipaddressoption.This control unit accepts all packets destined for this IP address, and ignores all others.

cu3172: cu 3172options ’ipaddress=192.168.0.1’interface local(1)device(00) 3172 eth0device(01) 3172 OFFLINEend cu3172

The following example defines an emulated 3172 Ethernet controller which specifies twoipaddressoptions. Thefirst of these specifies a network in CIDR notation, while the second specifies a single host. This control unitaccepts all packets destined for addresses in this network and for this single host, and ignores all others.

cu3172: cu 3172options ’ipaddress=192.168.1.0/24,ipaddress=192.168. 0.1’interface local(1)device(00) 3172 eth0device(01) 3172 OFFLINEend cu3172

12.2.4. multicastipaddress

All emulated Ethernet control units on which mainframe operating systems provide TCP/IP support, types:

3172(3172 TCP/IP Ethernet)osa(OSA TCP/IP Ethernet)xca (XCA TCP/IP Ethernet)6035(CETI 6035 TCP/IP Ethernet)k200 (k200 TCP/IP Ethernet)

optionally may be supplied with one or moremulticastipaddressstrings in anoptionsstatement.

multicastipaddress=ipaddr


86

The multicast IP address must be specified in "dotted quad" notation. Host names and fully or partially qualifiedDNS names are not permitted. This option may be specified multiple times within a single control unitoptionsstring, up to a maximum of fourteen times.

If present, this option specifies a multicast IP address to which the control unit will listen. The default, if theoption is not present, is to listen to no multicast IP address.

This option is necessary for3172emulated Ethernet control units in order to listen to a multicast IP address.

This option is available on emulatedosa, xca, 6035, andk200. However, the multicast IP address for thesecontrol units may also be configured from the mainframe OS, sothis option may not be necessary for them.

The following example defines an emulated 3172 controller which will listen on the multicast IP address 224.0.0.1.The controller controls two 3172 TCP/IP lines. The Ethernetdevice to be associated with these will be filled inby theFLEX ES CLI mount command.

cu3172: cu 3172options ’multicastipaddress=224.0.0.1’interface local(1)device(00) 3172 OFFLINEdevice(01) 3172 OFFLINEend cu3172

The following example is identical save that it also specifies theipaddressoption.

cu3172: cu 3172options ’ipaddress=192.168.0.1,multicastipaddress=22 4.0.0.1’interface local(1)device(00) 3172 OFFLINEdevice(01) 3172 OFFLINEend cu3172

Note that while the multicast IP address may be specified for the k200 emulated Ethernet control unit, itwill always be overridden by the mainframe OS startup sequence for that control unit. Therefore, specifyingmulticastipaddressfor ak200 is not invalid, but is not useful.

12.2.5. tunipaddress

In the Linux environment, all emulated Ethernet (but not Token Ring) control units on which mainframe operatingsystems provide TCP/IP support, types:

3172(3172 TCP/IP Ethernet)osa(OSA TCP/IP Ethernet)xca (XCA TCP/IP Ethernet)6035(CETI 6035 TCP/IP Ethernet)k200 (k200 TCP/IP Ethernet)

optionally may be supplied with atunipaddressstring in anoptionsstatement.

tunipaddress=ipaddr


87

The IP address must be specified in "dotted quad" notation. Host names and fully or partially qualified DNSnames are not permitted. The IP address must be a host address; CIDR-style netmask specifications are notpermitted. This option may be specified at most once.

The TUN IP address is the IP address to be used with the Linux TUN/TAP virtual network driver. These arevirtual network devices provided by Linux which are suitable for applications such as network TUNnelling andvirtual Ethernet (EtherTAP) services. InFLEX ES, they are used to provide a network connection through theLinux kernel independently of any physical Network Interface Cards (NICs) which might be present, even if noNICs are present.

The ipaddress and tunipaddress options are quite different in meaning, and should not be conflated. Asdescribed earlier, theipaddressoption acts as a network filter, allowing in to the control unit only those addressesit specifies. By way of contrast, thetunipaddress option configures the Linux TUN IP address at which thecontrol unit will appear.

To use the TUN/TAP device, two things must be done in the control unit configuration. Firstly, thetunipaddressoption must be specified in anoptions string. Secondly, thetun device must be present on the zeroth deviceon the control unit. (This device will show up as a "tap" device to the host Linux system’sifconfig(1)command.) It may either be coded explicitly, as in this example:

cu3172: cu 3172options ’ipaddress=192.168.0.1’interface local(1)device(00) 3172 tundevice(01) 3172 OFFLINEend cu3172

or it may be coded asOFFLINE in the configuration and mounted via the CLI, as in this example:

cu3172: cu 3172options ’ipaddress=192.168.0.1’interface local(1)device(00) 3172 OFFLINEdevice(01) 3172 OFFLINEend cu3172

The tunipaddressoption may be used in conjunction with other options, including the ipaddressoption. Forexample:

cuosa: cu osaoptions ’ipaddress=192.168.100.139,ipaddress=192.168 .100.140,tunipaddress=192.168.100.150’interface local(1)device(00) osa tundevice(01) osa OFFLINEend cuosa

Note: In this example, theoptions string should be entered as a single string without spaces ornewlines. It hasbeen broken here to fit the page.


88

In the original use of the example above, address 192.168.100.139 was used by a z/VM system running onFLEX ES. Address 192.168.100.140 was used by a z/Linux guest running on z/VM, receiving its network trafficthrough the z/VM TCP/IP stack and its proxy ARP support. TUN address 192.168.100.150 was the address ofthe Linux host system on whichFLEX ES was running.

The control unit accepts only packets with destination addresses specified by theipaddressoptions. In thisexample, this means that both the z/VM system and its guest z/Linux system are reachable from the outsideworld. The outside world (in this case the host Linux system)is reachable at thetunipaddress, 192.168.100.150.

It is not invalid to specify thetunipaddress option on a control unit mounted on a physical NIC card (not ondevicetun), but if this is done, thetunipaddressoption has no effect.

In the Redhat 9 Linux environment, thetun device is necessary for communications between a mainframeOSand the host Linux system in both the situation where there isno physical NIC on the host or where there is aphysical NIC but it is not plugged in to an active network hub or switch. (In earlier Redhat Linux environments,a physical NIC would work in the second of these situations.)

12.3. FSI ICA Emulated Control Units

Each FSI ICA 6-port RS-232 BSC/SDLC Integrated Communications Adapter ("FSI ICA") must have associatedwith it exactly one emulated ICA control unit of type2701d, 9221ICAd, or 9373ICAd. This control unit musthave a control unitoptionsstatement of the form:

devfile:imagefile

In this statement,devfileindicates the server OS device special file name of the first device associated with theICA, andimagefileindicates the name of the "image" file associated with the ICA. (This image file is downloadedinto the card, and is required for its operation.) The entireoption string must be enclosed in single apostrophes("forward single quotes"). No spaces are allowed within this quoted string. Exactly one such statement mustappear for each control unit providing FSI ICA devices. It must identify the zeroth device. The FSI ICA usesthe image file called "pica960.img ". These files are provided with the standardFLEX ES distribution.

For example, an FSI ICA might have an options statement of theform shown in the following resource definitionfragment:

cu2701d: cu 2701doptions ’/dev/fsiica/ica0p0:/usr/flexes/bin/pica960. img’interface network(1)device(00) rbsca /dev/fsiica/ica0p0device(01) rsdlc /dev/fsiica/ica0p1end cu2701d

Note: Device options for FSI ICA communications lines are discussed in the "Emulated Device Options" chapterlater in this volume.


89

13. Emulated Device Options

13.1. 3278 Terminals

Emulated 3278 terminal devices support the following device options.

13.1.1. allowhostccws

allowhostccws

This indicates that the device may use a CCW that supports issuing server OS commands from VM/ESA usingthe CMS AIX command, redirecting any standard output and standard error output back to VM/ESA.

13.1.2. convertsysreqtotestreq

convertsysreqtotestreq

This indicates that the device should convert messages froma client which contain only a SYSREQ AID to aTESTREQ. This is needed to handle some TN3270E clients that generate hexadecimal F0 for a SYSREQ (e.g.,IBM PC/3270 and Attachmate).

13.1.3. tn3287

This indicates that the emulated 3278 on an emulated 3274 control unit is a local, non-SNA device acting as anemulated 3287 printer using the tn3287e protocol. This device may, through the Terminal Solicitor, be utilizedas a 3287 printer by a remote TCP/IP tn3287 desktop client (a third-party product).

When this device option is specified, theFLEX ES device name mounted for this device is considered to be theLUNAME used by the remote tn3287e client. It does not appear on the Terminal Solicitor screen. The devicenames (LUNAMEs) for multiple 3287 devices must all be unique, and are case sensitive. The device name(LUNAME) used to mount the device must match that specified bythe remote client.

The mainframe operating system and relevant systems software must be configured to know about this deviceand to do I/O to it.

Example:

printercu: cu 3274interface local (1)device(00) 3278 devopt ’tn3287’device(01-07) OFFLINEend printercu

13.2. TWX Terminals

13.2.1. initfile

Emulated TWX terminal devices of all types support the following device option:

initfile= filename


90

No spaces are permitted on either side of the "=" sign.

13.3. 1403, 3203, 3211, 3262, 4245, 4248 Printers

The following printers:

14031403-N13203-13203-23203-43203-532113262-13262-1142454245-14245-124245-2042484248-14248-2

support the following options.

13.3.1. initfile

initfile= filename


13.3.2. linelength

linelength=length


The valuelengthis an integer which specifies the maximum line length which will be printed, in characters. Thedefault value if this device option is not specified is decimal 132.

13.3.3. onlcr

onlcr

This option indicates that the printer should do the following translations in its ASCII output. (1) Each newlinecharacter becomes two characters: a carriage returns followed by a newline, (2) Each form feed character becomestwo characters: a carriage returns followed by a form feed.

13.3.4. useformfeeds

useformfeeds


91

Theuseformfeedsoption indicates that ASCII formfeed characters should be used to generate form feeds in theoutput of the emulated printer.

13.3.5. writetimeout

writetimeout=seconds


This option specifies the number of seconds that a write command will wait before timing out and generating anIntervention Required signal. The default is 60 seconds.

13.4. 3286 Printers

The 3286 printer supports the following options.

13.4.1. initfile

initfile= filename


13.4.2. writetimeout

writetimeout=seconds


This option specifies the number of seconds that a write command will wait before timing out and generating anIntervention Required signal. The default is 60 seconds.

13.5. CKD Emulated DASD

All CKD emulated DASD support the following options.

13.5.1. trackcachesize

trackcachesize=size


This option specifies the size of the dedicate cache for the emulated DASD, in terms of tracks of the emulatedDASD.

The smallest cache value which should be specified on any individual CKD emulated DASD is 5 tracks. (Theconfiguration file compiler,cfcomp(1) , disallows only negative values, but values of 0 through 4 should notbe specified.)


92

The total cache for a CKD emulated DASD control unit, including all cache on all devices and all "floating"cache in the control unit, cannot exceed 8,191 tracks. This limit is enforced at run time, not by the configurationfile compiler (cfcomp(1) ).

A further discussion of the nature of DASD caching appears inthe volume FSIMM300System Programmer’sGuide.

13.5.2. writethroughcache

writethroughcache

All FLEX ES CKD emulated DASD are cached to the Main Storage of the server. The default behavior of thisCKD emulated DASD cache is "write-back", where write operations to cached portions of the CKD emulatedDASD are written to the cache. This provides the best performance, at the slight risk of corruption shouldthe system fail before the cache is written back to server disk. All write-back CKD emulated DASD cachesare flushed to server disk every five seconds. Thewritethroughcache device option indicates that the CKDemulated DASD should use write-through caching. In write-through caching, all write operations to the cacheare immediately written through to disk. This provides slower, but safer operation.

This option must be specified on a per-device basis as a deviceoption (devopt). There is no correspondingcontrol unit level option.

13.6. FBA Emulated DASD

All FBA emulated DASD support the following options.

Note: All FBA emulated DASD implement write-through caching. No device option exists to change thisbehavior.

13.6.1. blockcachesize

blockcachesize=size


This option specifies the size of the cache for the emulated DASD, in terms of 512 byte blocks.

The minimum value which may be specified is 16. The value specified must be a multiple of 2. The restrictionson this value are enforced at run time, not atcfcomp(1) compile time.

The maximum value should not be so large that it causes serverRAM to page, and should not exceed 4194304blocks (2 Gigabytes of cache).

The default value is 2048, or 1 Megabyte of cache.

13.6.2. numblocks

numblocks=nblocks



93

This option specifies the size of the FBA emulated DASD in terms of 512 byte blocks.

(Note: This is useful in moving P/390 FBA emulated DASD toFLEX ES. The P/390 allowed emulated FBAemulated DASD to be different in size from physical FBA emulated DASD.)

13.7. Tape

13.7.1. allowdisconnects

Specifying the tape device option:

allowdisconnects

allows Channel End (CE) to be separated from Device End (DE) on write Channel Control Words (CCWs). Thedefault if this option is not specified is to present CE and DE together. Ifallowdisconnectsis specified, then CEis presented after the data has been received on a write CCW and DE is presented after the data has been writtento disk. This may increase performance in certain environments.

This option is supported on allFLEX ES emulated tape drives operating as FakeTape, AWSTAPE, or OMA/2drives to server disk. These include emulated drives in the 3420 series (3420, 3420-4, 3420-6, 3420-8, 3422,3423, and3430), the3480and3490, the3490-E, and the3590.

This option is also supported on certainFLEX ES emulated tape drives operating on server cartridge tape.Supported device types are those in the 3420 series (3420, 3420-4, 3420-6, 3420-8, 3422, 3423, and3430), the3480and3490, and the3490-E. The emulated3590does not support operation to server cartridge tape.

This option is also supported on FSI certified SCSI-attached3420 series, 3480 series, 3490, and 3490-E compatibletape drives.

Device options such asallowdisconnectsare neither relevant nor specifiable on PCA-attached peripherals.

13.7.2. allowmountccws

Specifying the tape device option:

allowmountccws

allows use of CCWs that support changing the filename associated with the device and displaying the filenameassociated with the device. These CCWs are used by the VM/ESA CMS mount command.





94

Device options such asallowmountccwsare neither relevant nor specifiable on PCA-attached peripherals.

Note that in server OS environments which require the specification ofscsilunorscsibus(see below) the changingof a mount filename may not be sufficient to change the mountingof the device.

13.7.3. autoloader

The

autoloader

device option causes the emulated or SCSI-attached tape drive to operate as if it had an autoloader. Whenspecified, the sense bits for a sense command (0x04) and the data for a read device characteristics command(0x64) are set up to indicate that there is an autoloader. This can eliminate problems with some utilities such asDDR.

This option is supported on certainFLEX ES emulated tape drives operating on server cartridge tape. Supporteddevice types are the3480, 3490, and3490-E. The emulated3590does not support operation to server cartridgetape.

This option should not be specified on emulated or SCSI-attached 3420 family devices.

This option is also supported, but is not relevant, on certain FLEX ES emulated tape drives operating as FakeTape,AWSTAPE, or OMA/2 drives to server disk. These include3480, 3490, 3490-E, and3590emulated tape drives.

Specifying this option when the drive does not have an autoloader is not an error, but is not useful. Emulateddrives in FakeTape, AWSTAPE, and OMA/2 operation do not have autoloaders.

Device options such asautoloaderare neither relevant nor specifiable on PCA-attached peripherals.

There is no relationship between theautoloaderoption and theUNLOADIMM SCSI command.

13.7.4. awscompressalldata

The

awscompressalldata

device option indicates that emulated tapes, when of AWS format, should be compressed regardless of thespecified tape model and the host CCWs.

The compression of AWSTAPE format emulated tapes does not support user data blocks greater than 65,536bytes. In releases of FLEX-ES through 7.0.5 which support AWSTAPE compression, an attempt to compressan AWSTAPE format emulated tape which contains a block greater than 65,535 bytes will fail with an IncorrectLength indication in the device status unless the channel program has suppressed incorrect length indication.Beginning in release 7.0.6, such an attempt will fail, incorrect length indication will be set in the device statussubject to the channel program’s suppression of incorrect length, and a Unit Check will be set.


95

13.7.5. awscompressdata

The

awscompressdata

device option indicates that emulated tapes, when of AWS format, should be compressed. The compression iscontrolled by the specified tape model and the host CCWs.

The compression of AWSTAPE format emulated tapes does not support user data blocks greater than 65,536bytes. In releases ofFLEX ES through 7.0.5 which support AWSTAPE compression, an attemptto compress anAWSTAPE format emulated tape which contains a block greater than 65,535 bytes will fail with an IncorrectLength indication in the device status unless the channel program has suppressed incorrect length indication.Beginning in release 7.0.6, such an attempt will fail, incorrect length indication will be set in the device statussubject to the channel program’s suppression of incorrect length, and a Unit Check will be set.

13.7.6. awsnewtape

The

awsnewtape

device option indicates that a newly created emulated tape will be in the AWS format. The default behavior ifthis option is not specified is to create the new emulated tapein the FakeTape format.

13.7.7. createmode

Thecreatemodedevice option specifies the server OS file permissions for thecreation of FakeTape and AWSTAPEemulated tape files.

The format of this device option statement is:

createmode=mode

where "mode" is a three digit octal integer specifying the mode in the traditional server OS notation.

In this notation, the first octal digit specifies the permissions for the file’s owner, the second for users in the file’sgroup, and the third for all users. For each, the permissionsare thought of as three binary digits: read, write, andexecute. These three binary digits are represented as a single octal digit.

For example, a file with read, write, and execute permission would specify "111" (often written mnemonically as"rwx"). Read and execute permission would be specified as "101" ("r-x").

A file which had read, write, and execute permissions set for the owner, and read and execute set for the groupand for all others, would be: "111101101" ("rwxr-xr-x"). When each group of three digits is expressed as asingle octal digit, this become: "755"


96

Thecreatemodedevice option is useful in working around a problem with NFS filesystems. In certain serverOS environments (at least UnixWare 7.0.,1, UnixWare 7.1.1,and OPEN UNIX 8) the NFS server can reject validwrites to a newly created tape because it is not handling file permissions for group correctly. A "createmode=666"devopt, which allows read and write access by all, may circumvent this difficulty. Note however that setting readand write access on for all users may introduce security concerns.

13.7.8. forcereadaheadon

On Qualstar brand SCSI-attached 3420 compatible (9-track)tape drives,FLEX ES by default turns off read-aheadfor read/write mounts. While this reduced performance on reads, it reduces the chances of repositioning errorsfrom the device. For read-only mounts, a cautious read-ahead strategy is employed.

Specifying the device optionforcereadaheadonturns on the read-ahead feature on the device.

This device option is not required for other types of emulated or SCSI-attached tape drives. However, it is not anerror to specify it for other drives, and tape drives defined with this option may be used for other types of tapes(e.g., for FakeTapes).

Device options such asforcereadaheadonare neither relevant nor specifiable on PCA-attached peripherals.

13.7.9. key

Emulated tape encryption is supported for FakeTape format and AWSTAPE format emulated tapes. It is notsupported for OMA/2 format emulated tapes (which can only beread). It is supported in bothFLEX ES andFLEXCUB.

Thekey device option specifies that the emulated tape is to be encrypted.


key=algorithm:keyfile

No spaces should be present on each side of the colon in the in thealgorithm:keyfileargument.

The algorithm must be one of the following keywords:aes128cbc, aes192cbc, aes256cbc. These specify theUS Advanced Encryption Standard in Cipher Block Chaining mode with keys of length 128, 192, or 256 bits,respectively.

Thealgorithmkeyword may be omitted. If it is omitted, the colon followingit should be omitted as well. Thedefault if it is omitted isaes256cbc.

The key file specifies the location in the filesystem (fully qualified pathname and filename) of a file containingdata to be used as a key for the encryption process. This key may be further protected by a user-entered password.The key file is mandatory; it may not be omitted.

Examples:


97

cu3480: cu 3480interface local(1)device(00) 3480 OFFLINEdevopt ’aes128cbc:/path/to/keyfile,password=The Pass P hrase’device(01) 3480 OFFLINE devopt ’aes192cbc:/path/to/keyf ile,password=’device(02) 3480 OFFLINE devopt ’aes256cbc:/path/to/keyf ile’device(03) 3480 OFFLINEdevopt ’aes128cbc:/path/to/keyfile,password=The Pass P hrase’device(04) 3480 OFFLINE devopt ’aes192cbc:/path/to/keyf ile,password=’device(05) 3480 OFFLINE devopt ’aes246cbc:/path/to/keyf ile’device(06 - 15) 3480 OFFLINEend cu3480

In the examples above, device 00 specifies an algorithm explicitly, a keyfile, and a password for unlocking thatkeyfile. Device 01 is similar, but specifies a null password (it’s keyfile is not password protected, and because anull password was specified explicitly no password will be prompted for at mount time). Device 02 is similar,but it does not specify a password at all. (A password will be prompted for at mount time, whether or not thekeyfile is password protected.) Devices 03, 04, and 05 are correspondingly similar, but they do not specify thealgorithm explicitly.

To set up a key file for a 128-bit key for emulated tape encryption, with a null password protecting it, do:

dd if=/dev/random bs=1 count=16 of=/path/to/device/key1 28

It is important that the output file, named in this example/path/to/device/key128 be written directlyto a removable medium. It should not be written first to regular disk and then moved to a removable medium,because it is difficult to guarantee that a file is indeed securely erased from a disk.

To set up a key file for a 128-bit key for emulated tape encryption, with password protection for the key, do thefollowing (enter this command on a single line):

dd if=/dev/random bs=1 count=16 |openssl enc -aes-128-cbc -md sha1 -k<password> -out /path/to/device/key128

Replace<password> with a password to be used to protect the resulting key file. Replacekey128 with thefile name, possibly partially or fully qualified, of the key file.

Be aware that if your shell has a history mechanism this command, including the password string, may be retainedon disk. In some shells, such asbash(1) the history mechanism may be controlled or disabled via environmentvariables. Consult your command shell documentation for further information.

Note that the/dev/random device may block (that is, temporarily stop producing output) if the system"entropy" is too low. To increase system entropy on a system with a GUI, move the mouse around betweenwindows. To increase entropy on a system where you do not haveaccess to a GUI, start a process which initiatessignificant disk activity. (The system random number generator generates random numbers by sampling verylow-level physical activity on the system.) Do not use the/dev/urandom device instead. This device will notblock if the system runs out of entropy, but in consequence itwill, in such a situation, supply nonrandom data.

To set up a key file for 192 bit or 256 bit keys, use the same processes but specify instead:


98


or

dd if=/dev/random bs=1 count=24 |openssl enc -aes-192-cbc -md sha1 -k <password>-out /path/to/device/key192

for 192 bit keys, or:


or

dd if=/dev/random bs=1 count=32 |openssl enc -aes-256-cbc -md sha1 -k <password>-out /path/to/device/key256

for 256 bit keys.

Much of the security of the encryption depends upon the security of the key. In best practice, it should be kepton a removable medium which is, in fact, removed after the emulated tape has been mounted.

13.7.10. maxwritesize

Themaxwritesizedevice option specifies the maximum tape size, in Megabytes.


maxwritesize=megabytes




Device options such asmaxwritesizeare neither relevant nor specifiable on PCA-attached peripherals.

When the writing of an emulated tape approaches this size, theequivalent of the reflective strip at the end ofthe tape is emulated. An appropriate number of blocks may be written after this point, but no blocks may bewritten beyond the maximum size specified in themaxwritesizedevopt. If an attempt is made to write past thesize specified by maxwritesize causes the EOT indication to be made in the device status and device sense data.Whether these bytes are in fact written to the backing medium depends on whether there is space available onthat medium.


99

It is possible for a situation to occur where the tape emulation runs out of space before a specifiedmaxwritesize,or if it runs out of space when nomaxwritesize, is specified. Such situations might occur if, when writing to theserver filesystem, available disk space is no longer available or server OS file size limits are reached. It mightalso occur if, when writing to SCSI-attached DAT (DDS) or DLTcartridge tape, the end of the DAT or DLT wasreached. In these situations, the EOT indication is made in the device status and device sense data.

13.7.11. noidrc

The

noidrc

device option should be specified only on 3480 emulated and SCSI-attached devices (that is, devices of type"3480" as SCSI-attached 3480-compatible tape drives, server cartridge tape, FakeTape, AWSTAPE, or OMA/2).

This option causes the device to respond as if it did not have the IDRC feature (Improved Data RecordingCapability). By default the device is assumed to have IDRC.

Note: While it is not illegal to code this option for3490or 3490-Edevices, it has no effect if so coded thesedevices are assumed always to have IDRC. It is illegal to codethis option for other types of devices.

13.7.12. nonewtape

The

nonewtape

device option indicates that an emulated tape mounted (using the CLImount command) must already exist. Ifthis device option is specified and the emulated tape does notexist, no new tape will be created and the mountwill fail. The default behavior if this device option is not specified and the emulated tape does not exist is tocreate a new emulated tape (if possible).

13.7.13. nooldtape

The

nooldtape

device option indicates that an emulated tape mounted (using the CLImount command) must not already exist.If this device option is specified and the emulated tape does exist, the mount will fail. The default behavior if thisdevice option is not specified and the emulated tape does exist is to use the existing emulated tape (if possible).

13.7.14. password

The

password


100

device option is used in conjunction with thekey device option. Ifpassword is specified, it identifies thepassword used to protect the emulated tape encryption key. If password is not specified, then the password isprompted for by the CLImount command when the emulated tape is mounted.


password=password

Passwords may contain any character other than the single-quote character (which is used to delimit the deviceoption string), the double quote character (which is used server command invocations such as those of theFLEX ES standalone utilities and theopenssl(1) command used to generate a key-protected password), andthe comma character (which is used to delimit device optionswithin the device option string).

To specify a null password, use a string of zero length.

See thekey parameter for further information on emulated tape encryption.

Note in particular that although this parameter is optional, a password must always be supplied in some way(even if it is a null password for keys which do not employ password protection). If the password is not specifiedusing this paramter, it will be prompted for by the CLImount command when the emulated tape is mounted.

There are two operational implications in the way in which key passwords are handled.

First, since a password must always be supplied, if an emulated tape is to be mounted automatically the first timeby the system (that is, if it is not defined in the Resource Configuration File asOFFLINE ) then its passwordmust be specified using this paramter.

Second, since it may be undesirable to code the password explicitly (and potentially visibly) in the ResourceConfiguration File, it may be a better practice to define the emulated tape device asOFFLINE and to mount itexplicitly via the CLI (at which time a password may be supplied).

Examples:

cu3480: cu 3480interface local(1)device(00) 3480 OFFLINEdevopt ’aes128cbc:/path/to/keyfile,password=The Pass P hrase’device(01) 3480 OFFLINE devopt ’aes192cbc:/path/to/keyf ile,password=’device(02) 3480 OFFLINE devopt ’aes256cbc:/path/to/keyf ile’device(03 - 15) 3480 OFFLINEend cu3480

In the examples above, device 00 specifies a password for unlocking the keyfile. Device 01 is similar, but specifiesa null password (it’s keyfile is not password protected, and because a null password was specified explicitly nopassword will be prompted for at mount time). Device 02 is similar, but it does not specify a password at all. (Apassword will be prompted for at mount time, whether or not the keyfile is password protected.)

13.7.15. scsilun

The:


101

scsilun

device option specifies the the SCSI Logical Unit Number ("LUN") of a SCSI-attached server cartridge tape driveor a SCSI-attached mainframe compatible tape drive.

The format of this option statement is:

scsilun = lun

where "lun" is to be replaced by the actual LUN of the device.

Note that this option should not be specified for emulated tape drives providing FakeTape, AWSTAPE, or OMA/2on server disk.

13.7.16. scsitarget

The:

scsitarget

device option specifies the the SCSI ID of a SCSI-attached server cartridge tape drive or a SCSI-attachedmainframe compatible tape drive.

The format of this option statement is:

scsitarget =target

where "target" is to be replaced by the actual SCSI ID of the device.

Note that this option should not be specified for emulated tape drives providing FakeTape, AWSTAPE, or OMA/2on server disk.

13.7.17. scsitimeout

Thescsitimeoutdevice option allows the timeout period of a SCSI-attached tape drive to be specified explicitly.If this option is not specified, the default timeout value is 300 seconds.

The form of this option is:

scsitimeout=nnn

wherennn is a decimal number of seconds, specified without any commas or other numeric punctuation.


This device option is meaningful for SCSI-attached devices. Specifying this option on a non-SCSI device(FakeTape, AWSTAPE, or OMA/2 on server disk) is not an error, but is not meaningful.

This option is useful in certain unusual situations where the timeout must exceed 300 seconds.


102

13.7.18. awswritesegmentsize

The

awswritesegmentsizesize

device option specifies the segment size to be used when writing AWS format emulated tapes. This is specifiedas an integral decimal number of kilobytes. The valid range is from 1 kilobyte to 65,535 kilobytes, inclusive.The default if this option is not specified is four kilobytes.

13.8. CTCA

Emulated CTCA devices support the following device options.

13.8.1. M360

M360

This option configures the CTCA to emulate the IBM System/360CTCA Channel Feature.

13.8.2. M370

M370

This option configures the CTCA to emulate the IBM System/370CTCA Channel Feature.

13.9. FSI ICA Emulated SDLC and BSC Devices

The BSC and SDLC devices provided via the FSI ICA support the following "devopt" device options. Eachcommunications line in a card’s definition may specify a different set of options.

The volume FSIMM300:System Programmer’s Guidegives examples of FSI ICAdevopt options.

13.9.1. leased (and Dialup)

BSC and SDLC ICA lines which specify no options, or which do not specify theleaseddevice option operateby default as dialup lines. On these lines, transmission control signals (e.g., DTR) will be managed to reflect thestate of the transmission. An enable CCW will wait indefinitely on a dialup line.

BSC and SDLC ICA lines which specify theleaseddevice option operate as leased lines. These are lines whichdo not go through a switched network and on which the Carrier Detect is signal is always present. In leasedoperation, the devices on the line expect a DSR (Data Set Ready) signal immediately, as the line is alwaysconnected. An enable CCW will wait for DSR for three seconds in leased operation.


103

13.9.2. rtson

Thertson device option specifies that the the Ready to Send (RTS) transmission control signal will always be on.It is intended for use on four-wire full-duplex circuit connections which may constantly send and receive withoutline turnaround. (Note that while the circuit is full-duplex, the traffic flow (connection) is always half-duplex.)The advantage to doing this is that the turnaround time for the modems can be eliminated (this is usually a fewmilliseconds). This device option cannot be used for 2-wireconnections (such as dialup connections).

Thertson device option should not be specified on lines connected to half-duplex telco circuits. When in doubt,omit this option.

That thertson device option may be used in conjuntion with theleaseddevice option, but does not require it.

13.9.3. nrzi

SDLC ICA lines of any type may optionally also specifynrzi . This specifies the use of Non-Return to ZeroInverted (NRZI) encoding, rather than the default Non-Return to Zero (NRZ) encoding. Both ends of theconnection must specify the same type of encoding. BSC ICA lines may not specifynrzi .

13.10. FSI ICA TTC2 Devices

The TTC2 device provided via the FSI ICA supports the following "devopt" device options. Each communicationsline in a card’s definition may specify a different set of options.

13.10.1. acc

The

acc=XX

device option specifies a single additional control character as two hexadecimal digits. This character is ininverted 8-bit ASCII with parity.

13.10.2. baudrate

The

baudrate=rate

device option specifies the baud rate of the TTC2 line as one ofthe following values: 75, 110, 134.5, 300, 600,1200, 2400, 4800, 9600, or 19200. The default is 1200.

13.10.3. leased

The

leased

device option specifies that the device is to be attached to a non-switched line.


104

13.10.4. noreadint

The

noreadint

device option inhibits the read interrupt feature.

13.10.5. notimeout

The

notimeout

device option disables read timeouts.

13.10.6. nowriteint

The

nowriteint

device option inhibits the write interrupt feature.

13.10.7. rtson

Thertson device option specifies that the the Ready to Send (RTS) transmission control signal will always be on.It is intended for use on four-wire full-duplex circuit connections which may constantly send and receive withoutline turnaround. (Note that while the circuit is full-duplex, the traffic flow (connection) is always half-duplex.)

13.10.8. stopbits

The

stopbits=numbits

device option specifies the number of stop bits. Valid valuesare: "1", "1.5", and "2". The default is 2 for 110baud lines, 1.5 for 134.5 baud lines, and 1 for all other baud rates.

13.11. Emulated BSC (bsca)

13.11.1. tributary

Emulated BSC devices not employing the FSI ICA (bscadevices) may specify the option:

tributary= tributaryaddr

The tributary address is specified in hexadecimal.


105

14. ChannelAttached Peripheral Parameters

When attaching physical devices and their control units via the Parallel Channel Adapter (PCA), there is oftensome question as to appropriatecu parameters ("streaming()", " interlocked", "shared", and/or "sharedb"). Thefollowing tables provide suggested values based on the device or control unit type. Note that these values, evenif specified in terms of devices, apply to control unit statements (cu) in the system definition.

Note: These tables reflect experience; they are not intendedto be comprehensive.

Device Configuration Parameters

3174 non-SNA shared3174 SNA do not specifyshared3705 Models CA2, CA3, CA4 CU interlocked3725 interlocked3745 NCP interlocked4993 interlocked shared4994 interlocked shared7170 interlocked7171 interlocked shared

Figure 26 Physical Communications Device Parameters


3258 interlocked shared3272 interlocked shared3274 Model A interlocked3274 Models B and D interlocked shared3791 interlocked5088 interlocked, optionallyshared

Figure 27 Physical Display and Console Printers


3411 interlocked shared3411 (interlocked or streaming()), andshared3430 interlocked shared3480 (interlocked or streaming())Memorex-Telex 5490 (interlocked or streaming()), andsharedb

Figure 28 Tape Drives and Controllers


106


2821 CU interlocked1442 interlocked1443 interlocked3203 interlocked3262 interlocked3811 interlocked3505 interlocked3525 interlocked3800 interlocked or streaming4245 interlocked

Figure 29 Printers and Unit Record Control Units


3088, CTC, "Dataexchange" (interlocked or streaming())3890 Checksorter interlocked

Figure 30 Other


107

15. Information for Older Versions

15.1. lparnum (Releases Through 7.0.3)

This section describes the behavior of thelparnum statement in releases ofFLEX ES through (including) 7.0.3.For current releases, and for issues of migrating from 7.0.3or earlier to current releases, please see the mainsection onlparnum , above.

lparnum ( lparnumber)

This statement is meaningful only iffeature lpar is defined and if theinstsetspecifies370mode (System/370),esamode (z/Architecture 31-bit, ESA/390, ESA/370 and 370-XA), or z mode (z/Architecture 64-bit). It is notmeaningful invse(ECPS:VSE) mode. Iffeature lpar is not specified, or ifinstsetspecifiesvsemode, then thelparnum statement, if present, is ignored.

Thelparnum statement allows the specification of the Instance’s LPAR number. This number must be a decimalor hexadecimal number from 0 to 15 (0 to F), inclusive. The statement has no other effect.

If feature lpar is specified but nolparnum is present, the LPAR number defaults to 0.

Note that the use oflparnum andfeature lpar provide only the functionality specified here. They do not implythe general functionality of the PR/SM Facility.

15.2. Memory

The information in this section applies only to releases through 6.2.16. Beginning with release 7.0.0, it is nolonger necessary (and is incorrect) to use thememory resource or to reserve contiguous server RAM.

resourcename: memory memorysizeend resourcename

The memsizedeclaration in a system definition declares the amount of emulated Main Storage available onan Instance, in kilobytes. If the system uses no Parallel Channel Adapter (PCA) channels, then amemsizedeclaration is sufficient.

If, however, the system contains one or more Parallel Channel Adapter (PCA) channels, then it is necessary todefine amemory resource which is to be associated with the Instance at run time. Onememory resource isrequired for each system (CPU complex). The name of thememory resource must correspond with the name ofthe system.

A memory resource defines the amount of physical memory on the server needed to support the namedFLEX ESsystem and its PCA channels, in Megabytes. This value shouldbe the value of its Main Storage (as defined byits memsizedefinition) plus 3 percent. Expanded Storage, if present (theessizedefinition) is not included in thiscalculation. When calculating this value, round up to the next integral Megabyte.

The total size specified in allmemory resources for all Instances which run simultaneously cannot exceed theamount of Contiguous RAM available on the server.

As noted earlier, physical memory defined by thememory resource is associated with aFLEX ES Instance’ssystem definition by means of its name. Theresourcenamespecified in thememory resource must be identicalto the name of the system as defined in itssystemdeclaration.


108

Example:

vm1: memory66end vm1

In this example, amemorydefinition is given for a system called "vm1", defined by a system definition elsewhere.The amount of memory defined, 66 Megabytes, is appropriate for a system with 64 Megabytes of emulated MainStorage.


109

16. Volume Index

2701d, emulated, emulated channel requirements . . . . . . . . .. . . . . . . . . . . . . . 77370 mode operation, extended real addressing . . . . . . . . . . . .. . . . . . . . . . . . 46370 mode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46370-xa mode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 466034 token ring device count . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 716035 token ring ethernet device count . . . . . . . . . . . . . . . . . . .. . . . . . . . 716134 token ring device count . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 71OSA, control unit definitions . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 54XCA, control unit definitions . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 54acc fsi ica ttc2 device options . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 103adapternumber control unit option . . . . . . . . . . . . . . . . . . . . .. . . . . . . . 81anynode nodes keyword, resource grammar . . . . . . . . . . . . . . . .. . . . . . . . . 30architectural level specification . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 46baudrate fsi ica ttc2 device options . . . . . . . . . . . . . . . . . . . .. . . . . . . . 103block multiplexor channels, defined . . . . . . . . . . . . . . . . . . . .. . . . . . . . 32blockmux channels, defined . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 32blockmux resource keyword, resource grammar . . . . . . . . . . . .. . . . . . . . . . . 30bsc ica device options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 102byte multiplexor channels, defined . . . . . . . . . . . . . . . . . . . . .. . . . . . . 32byte multiplexor emulated channels, when to use . . . . . . . . . .. . . . . . . . . . . . . 77bytemux channels, defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 32bytemux resource keyword, resource grammar . . . . . . . . . . . . .. . . . . . . . . . . 30ceti 6034 token ring device count . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 71ceti 6035 token ring ethernet device count . . . . . . . . . . . . . . .. . . . . . . . . . 71ceti 6134 token ring device count . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 71channel statement, defined . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 32channels, fsi pca block multiplexor, defined . . . . . . . . . . . . .. . . . . . . . . . . . 32channels, fsi pca blockmux, defined . . . . . . . . . . . . . . . . . . . . .. . . . . . . 32channels, fsi pca byte multiplexor, defined . . . . . . . . . . . . . .. . . . . . . . . . . 32channels, fsi pca bytemux, defined . . . . . . . . . . . . . . . . . . . . . .. . . . . . 32channels, fsi pca selector, defined . . . . . . . . . . . . . . . . . . . . .. . . . . . . . 32channels, fsi sca, defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 32channels, local, defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 32channels, localbyte, defined . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 32channels, localosa, defined . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 32channels, network, defined . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 32channels, networkbyte, defined . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 32channels, networkosa, defined . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 32channels, pca block multiplexor, defined . . . . . . . . . . . . . . . .. . . . . . . . . . 32channels, pca blockmux, defined . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 32channels, pca byte multiplexor, defined . . . . . . . . . . . . . . . . .. . . . . . . . . . 32channels, pca bytemux, defined . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 32channels, pca selector, defined . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 32channels, serial, defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 32chanpath resource keyword, resource grammar . . . . . . . . . . . .. . . . . . . . . . . . 30cloned cu-resource keyword, resource grammar . . . . . . . . . . .. . . . . . . . . . . . 30control unit options, 3172, adapternumber . . . . . . . . . . . . . .. . . . . . . . . . . 81


110

control unit options, 3172, ipaddress . . . . . . . . . . . . . . . . . .. . . . . . . . . . 82control unit options, 3172, multicastipaddress, ethernet. . . . . . . . . . . . . . . . . . . . 85control unit options, 3172, tunipaddress . . . . . . . . . . . . . . .. . . . . . . . . . . 86control unit options, 3172TR, adapternumber . . . . . . . . . . . .. . . . . . . . . . . . 81control unit options, 3172TR, ipaddress . . . . . . . . . . . . . . . .. . . . . . . . . . 82control unit options, 6034, ipaddress . . . . . . . . . . . . . . . . . .. . . . . . . . . . 82control unit options, 6035, ipaddress . . . . . . . . . . . . . . . . . .. . . . . . . . . . 82control unit options, 6035, multicastipaddress, ethernet. . . . . . . . . . . . . . . . . . . . 85control unit options, 6035, tunipaddress . . . . . . . . . . . . . . .. . . . . . . . . . . 86control unit options, 6134, ipaddress . . . . . . . . . . . . . . . . . .. . . . . . . . . . 82control unit options, CETI control units, enablemgtime . . .. . . . . . . . . . . . . . . . . 82control unit options, SNA control units, adapternumber . . .. . . . . . . . . . . . . . . . . 81control unit options, TCP/IP control units, adapternumber. . . . . . . . . . . . . . . . . . . 81control unit options, TCP/IP control units, ipaddress . . . .. . . . . . . . . . . . . . . . . 82control unit options, TCP/IP control units, multicastipaddress, ethernet . . . . . . . . . . . . . . 85control unit options, TCP/IP control units, tunipaddress .. . . . . . . . . . . . . . . . . . . 86control unit options, adapternumber . . . . . . . . . . . . . . . . . . .. . . . . . . . . 81control unit options, ceti, ipaddress . . . . . . . . . . . . . . . . . .. . . . . . . . . . 82control unit options, ceti, multicastipaddress, ethernet. . . . . . . . . . . . . . . . . . . . . 85control unit options, ceti, tunipaddress . . . . . . . . . . . . . . .. . . . . . . . . . . . 86control unit options, enablemgtime . . . . . . . . . . . . . . . . . . . .. . . . . . . . 82control unit options, ipaddress . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 82control unit options, k200, ipaddress . . . . . . . . . . . . . . . . . .. . . . . . . . . . 82control unit options, k200, multicastipaddress, ethernet. . . . . . . . . . . . . . . . . . . . 85control unit options, k200, tunipaddress . . . . . . . . . . . . . . .. . . . . . . . . . . 86control unit options, multicastipaddress, ethernet . . . . .. . . . . . . . . . . . . . . . . . 85control unit options, osa, adapternumber . . . . . . . . . . . . . . .. . . . . . . . . . . 81control unit options, osa, ipaddress . . . . . . . . . . . . . . . . . . .. . . . . . . . . 82control unit options, osa, multicastipaddress, ethernet .. . . . . . . . . . . . . . . . . . . . 85control unit options, osa, tunipaddress . . . . . . . . . . . . . . . .. . . . . . . . . . . 86control unit options, osaTR, adapternumber . . . . . . . . . . . . .. . . . . . . . . . . . 81control unit options, osaTR, ipaddress . . . . . . . . . . . . . . . . .. . . . . . . . . . 82control unit options, osasna, adapternumber . . . . . . . . . . . .. . . . . . . . . . . . . 81control unit options, osasnaTR, adapternumber . . . . . . . . . .. . . . . . . . . . . . . 81control unit options, tunipaddress . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 86control unit options, xca, adapternumber . . . . . . . . . . . . . . .. . . . . . . . . . . 81control unit options, xca, ipaddress . . . . . . . . . . . . . . . . . . .. . . . . . . . . 82control unit options, xca, multicastipaddress, ethernet .. . . . . . . . . . . . . . . . . . . . 85control unit options, xca, tunipaddress . . . . . . . . . . . . . . . .. . . . . . . . . . . 86control unit options, xcaTR, adapternumber . . . . . . . . . . . . .. . . . . . . . . . . . 81control unit options, xcaTR, ipaddress . . . . . . . . . . . . . . . . .. . . . . . . . . . 82control unit options, xcasna, adapternumber . . . . . . . . . . . .. . . . . . . . . . . . . 81control unit options, xcasnaTR, adapternumber . . . . . . . . . .. . . . . . . . . . . . . 81control units, emulated, required parameter . . . . . . . . . . . .. . . . . . . . . . . . . 36control units, fsi pca, optional parameters . . . . . . . . . . . . .. . . . . . . . . . . . . 36control units, fsi sca, optional parameters . . . . . . . . . . . . .. . . . . . . . . . . . . 36control units, pca, optional parameters . . . . . . . . . . . . . . . .. . . . . . . . . . . 36control units, sca, optional parameters . . . . . . . . . . . . . . . .. . . . . . . . . . . 36cu resource keyword, resource grammar . . . . . . . . . . . . . . . . . .. . . . . . . . 30


111

cu system keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36cu system statement required parameters . . . . . . . . . . . . . . . .. . . . . . . . . . 36cuadd cu system keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 41devad cu system keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 36devad cu system keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 37device count, ceti 6034 token ring . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 71device count, ceti 6035 ethernet . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 71device count, ceti 6134 token ring . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 71device cu-resource keyword, resource grammar . . . . . . . . . . .. . . . . . . . . . . . 30devopt cu-resource keyword, resource grammar . . . . . . . . . . .. . . . . . . . . . . . 30emulated 2701d, emulated channel requirements . . . . . . . . . .. . . . . . . . . . . . . 77emulated control units, required parameter . . . . . . . . . . . . .. . . . . . . . . . . . 36emulated osa, emulated channel requirements . . . . . . . . . . . .. . . . . . . . . . . . 77enablemgtime control unit option . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 82esa/370 mode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 46esa/390 mode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 46fsi ica bsc and sdlc device options . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 102fsi ica emulated control unit options . . . . . . . . . . . . . . . . . . .. . . . . . . . . 88fsi ica ttc2 device options . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 103fsi ica, emulated channel requirements . . . . . . . . . . . . . . . . .. . . . . . . . . . 77fsi pca control units, optional parameters . . . . . . . . . . . . . .. . . . . . . . . . . . 36fsi sca channels, resource . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 17fsi sca channels, server device special files . . . . . . . . . . . . .. . . . . . . . . . . . 17fsi sca control units, optional parameters . . . . . . . . . . . . . .. . . . . . . . . . . . 36ica bsc and sdlc device options . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 102ica emulated control unit options . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 88ica ttc2 device options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 103ica, emulated channel requirements . . . . . . . . . . . . . . . . . . . .. . . . . . . . 77instruction set specification . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 46instset 370 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46instset 390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46instset esa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46instset vse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46instset z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46instset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46interface cu-resource keyword, resource grammar . . . . . . . .. . . . . . . . . . . . . . 30interface statement, main entry . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 18interlocked cu system keyword . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 39ipaddress control unit option . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 82leased fsi ica bsc and sdlc device option . . . . . . . . . . . . . . . . .. . . . . . . . . 102leased fsi ica ttc2 device options . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 103link cu system keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 40local channels, defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 32local cu-resource keyword, resource grammar . . . . . . . . . . . .. . . . . . . . . . . . 30localbyte channels, defined . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 32localbyte channels, when to use . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 77localosa channels, defined . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 32localosa emulated channels, when to use . . . . . . . . . . . . . . . . .. . . . . . . . . 77multicastipaddress control unit option, ethernet . . . . . . .. . . . . . . . . . . . . . . . 85


112

network channels, defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 32network cu-resource keyword, resource grammar . . . . . . . . . .. . . . . . . . . . . . . 30networkbyte channels, defined . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 32networkbyte channels, when to use . . . . . . . . . . . . . . . . . . . . . .. . . . . . 77networkosa emulated channels, when to use . . . . . . . . . . . . . . .. . . . . . . . . . 77networksosa channels, defined . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 32nodes keyword, resource grammar . . . . . . . . . . . . . . . . . . . . . . .. . . . . 30noreadint fsi ica ttc2 device options . . . . . . . . . . . . . . . . . . .. . . . . . . . . 103notimeout fsi ica ttc2 device options . . . . . . . . . . . . . . . . . . .. . . . . . . . . 104nowriteint fsi ica ttc2 device options . . . . . . . . . . . . . . . . . .. . . . . . . . . . 104nrzi fsi ica bsc and sdlc device options . . . . . . . . . . . . . . . . . .. . . . . . . . . 103offline cu-resource keyword, resource grammar . . . . . . . . . . .. . . . . . . . . . . . 30osa control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54osa device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54osa, emulated, emulated channel requirements . . . . . . . . . . .. . . . . . . . . . . . . 77osaTR control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54osasna control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 54osasna device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54osasnaTR control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 54parallel cu-resource keyword, resource grammar . . . . . . . . .. . . . . . . . . . . . . . 30path cu system keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 36path cu system keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 38pca control units, optional parameters . . . . . . . . . . . . . . . . .. . . . . . . . . . 36pcacuopts cu-resource keyword, resource grammar . . . . . . . .. . . . . . . . . . . . . . 30quote marks, double, for strings . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 12quote marks, single, for strings . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . 12resource cu system keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 38resource grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29resources keyword, resource grammar . . . . . . . . . . . . . . . . . . .. . . . . . . . 30rtson fsi ica bsc and sdlc device option . . . . . . . . . . . . . . . . . .. . . . . . . . . 102rtson fsi ica ttc2 device option . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 104sca channels, resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 17sca channels, server device special files . . . . . . . . . . . . . . . .. . . . . . . . . . . 17sca control units, optional parameters . . . . . . . . . . . . . . . . .. . . . . . . . . . 36scacuopts cu-resource keyword, resource grammar . . . . . . . .. . . . . . . . . . . . . . 30scsi device information, determining . . . . . . . . . . . . . . . . . .. . . . . . . . . . 67scsi info, linux command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 67sdlc ica device options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 102selector channels, defined . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 32selector resource keyword, resource grammar . . . . . . . . . . . .. . . . . . . . . . . . 30selector resource keyword, resource grammar . . . . . . . . . . . .. . . . . . . . . . . . 30serial channels, defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 32serial channels, resource . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 17serial channels, server device special files . . . . . . . . . . . . .. . . . . . . . . . . . . 17serial cu-resource keyword, resource grammar . . . . . . . . . . .. . . . . . . . . . . . . 30serial, defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32shared cu system keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 39sharedb cu-system keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 39ssid, main entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80


113

stopbits fsi ica ttc2 device options . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 104streaming cu-system keyword . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 40strings, format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12strings, uses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12strings, with explicit delimiters . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . 12strings, without explicit delimiters . . . . . . . . . . . . . . . . . .. . . . . . . . . . . 12system/370 mode operation, extended real addressing . . . . .. . . . . . . . . . . . . . . . 46system/370 mode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 46ttc2 ica device options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 103tunipaddress control unit option . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . 86unitadd cu system keyword . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 41vse mode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46xca control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54xca device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54xcaTR control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54xcasna control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 54xcasna device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54xcasnaTR control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 54z mode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46z/architecture compatible mode operation . . . . . . . . . . . . . .. . . . . . . . . . . . 46


114


7.0.10.3 fsimm310: resource language...

Documents