SDISC Assembler Call - NetEx

More documents

Recommendations

Info

CODECONV - Hardware code conversion is installed. Note that this must be specified ifhardware code conversion is to be used.DEVNAMEThis parameter, which is optional except for H307, specifies a logical device name for this adapter.The “device name” may be from one to eight alphanumeric characters. The DEVNAME is requiredfor H307 (for adapters on the local host). It identifies the device name which NETEX will use to assignthe device. It must match the name assigned to the device in the OS2200 sysgen.For P/NB220 adapters, this is the lowest device which NETEX will use. The other device names aregenerated by incrementing the last nonblank character of DEVNAME. It is suggested that theDEVNAME end in at least one “0” digit.T0, T1, T2, and T3This required parameter defines the trunks that are attached to the network adapter. At least one operandmust be defined for each HYPERchannel adapter. As there are no TRUNK statements in defininga HYPERchannel 10-Mbps network, these parameters are not used in that context. The associatedlabels specify the label of a preceding TRUNK statement. The referenced TRUNK must be definedin this LOCALNET. The physical placement of the trunks in the back of the adapter is quiteimportant; T0 is the trunk interface on the left as one faces the back of the adapter, and T3 is therightmost trunk interface. If any of the four operands are missing, the adapter is assumed not to havea trunk interface in that position.Note:The hardware always scans from highest (T3) to lowest (T0). Proper configuration of thetrunks allows balance of the network traffic.PORTThis parameter which is required when using P/NB40x adapters only, specifies the port number towhich the associated HOST is attached. This operand is ignored unless MODEL=n4xx is specified inthe ADAPTER statement. This value is specified as a decimal integer. Valid port numbers are 0, 1,2, and 3 (decimal).ADAPTThis is required only if a single processor has more than one interface to a single P/NB40x adapter.This parameter is optional when using P/NB40x adapters. This value is specified as one to eight alphanumericcharacters.Of all the ADAPTER statements for a multi-port adapter, only one may have its label specified. Thatone will be referred to as the “main” adapter. The main adapter should not have its ADAPT parameterspecified. All subsequent ADAPTER statements referencing the main one must specify theirADAPT parameters to be the label of the main adapter. MODEL, NETADDR, and Tx parameters onsubsequent ADAPTER statements must agree with those parameters for the main ADAPTER definition.The ADAPTER statements may be in any order, but the main adapter must have a label specified.The ADAPT parameter is NOT used in defining a multi-task adapter. However, it may be used whendefining a multi-task, multi-part adapter. The following examples describe the same configuration intwo different ways to explain the ADAPT parameter when defining a multi-task, multi-port adapter.H1 HOSTmain ADAPTER MODEL=N400, NETADDR=01, T0=Alpha,PORT=l, SMGDREF=61H2 HOSTADAPTER MODEL=N400, NETADDR=61, T0=Alpha,PORT=1, SMGDREF=03H3 HOSTPage 100 Configuration Manager MAN-REF-H307IP-04
Another way:H1H2ADAPTERHOSTADAPTERHOSTADAPTERMODEL=N400, NETADDR=61, T0=Alpha,PORT=2, SMGDREF=02, ADAPT=mainMODEL=N400, NETADDR=61, T0=Alpha,PORT=1, SMGDREF=6l, ADAPT=mainMODEL=N400, NETADDR=61, T0=Alpha,PORT=1, SMGDREF=03, ADAPT=mainH3 HOSTmain ADAPTER MODEL=N400, NETADDR=01, T0=Alpha,PORT=2, SMGDREF=02INTRFACE (optional)This parameter, which is required when using P/NB40x interfaces, specifies the type of interface usedto connect the host to the P/NB40x interface. This operand is ignored unless MODEL=x400 is specifiedin the ADAPTER statement. This operand is not currently used by NETEX and therefore is forreadability only. The option may be any name desired by the user which is from one to eight alphanumericcharacters long.MAN-REF-H307IP-04 Configuration Manager Page 101
Page 1:
H307IP NETEX ® User Interfacefor U
Page 4 and 5:
PrefaceThis manual describes the H3
Page 6 and 7:
Notice to the ReaderThe material co
Page 8 and 9:
Glossaryasynchronous: A class of da
Page 10 and 11:
Table of ContentsRevision Record ..
Page 12 and 13:
FORTRAN NETEX Request Blocks.......
Page 14 and 15:
FiguresFigure 1. Basic I/O Flow....
Page 16 and 17:
Design Efficiency and FlexibilityTh
Page 18 and 19:
NESiGate Offload NETEXThis NETEX pr
Page 20 and 21:
Figure 3. NETEX and the ISO ModelSe
Page 22 and 23:
Intertask CommunicationNETEX is a s
Page 24 and 25:
General Concept of a SessionBefore
Page 26 and 27:
Establishing a SessionThe following
Page 28 and 29:
Data TransferUnlike the rules for e
Page 30 and 31:
Figure 7. Concurrent SREAD and SWRI
Page 32 and 33:
Figure 8. One-Way Data TransferThe
Page 34 and 35:
Terminating a SessionNETEX sessions
Page 36 and 37:
Programming NotesThe following sect
Page 38 and 39:
used so that it may remain an “in
Page 41 and 42:
NRBINDNRBIND indicates the type of
Page 43 and 44:
xx84 to xxFF ReservedThe total requ
Page 45 and 46:
The conversion options are selected
Page 47 and 48:
On completion of the offer or confi
Page 49 and 50:
NRBHNAME (NRBHOST)NRBHNAME specifie
Page 51 and 52:
Assembler Procedure FormatAll of th
Page 53 and 54:
SCONNECT Assembler CallThe SCONNECT
Page 55 and 56:
SREAD Assembler CallThe SREAD call
Page 57 and 58:
SCLOSE Assembler CallThe SCLOSE cal
Page 59 and 60:
NETEX Procedure CodeThe code genera
Page 61 and 62:
FORTRAN InterfaceNETEX includes a l
Page 63 and 64: SOFFR FORTRAN CallThe SOFFR (offer)
Page 65 and 66: SCONN FORTRAN CallThe SCONN (connec
Page 67 and 68: SCONF FORTRAN CallThe SCONF (confir
Page 69 and 70: SREAD ResultsThe following NRB fiel
Page 71 and 72: SCLOS FORTRAN CallThe SCLOS (close)
Page 73 and 74: SWAIT FORTRAN CallThe SWAIT call pr
Page 75 and 76: NRBPROTLLength of outgoing Odata.SD
Page 77 and 78: 120 FORMAT (I5)CC Send request to r
Page 79 and 80: NETEX Calling SequenceIn order to c
Page 81 and 82: Driver InterfaceIntroductionThe Dri
Page 85: DCONNECT Entry ParametersThe follow
Page 90 and 91: Exec status is the operating system
Page 92 and 93: InstallationPrerequisitesThe prereq
Page 94 and 95: Seconds to allow incoming data to r
Page 96 and 97: Step 4. Load the PAM Using the NCT
Page 98 and 99: User ExitsH307IP provides user exit
Page 100 and 101: Utility/Test ProgramsNTXCONSThis pr
Page 102 and 103: The program will respond with the f
Page 104 and 105: DESELECT hostname hostname...5. To
Page 106 and 107: VERSION StatementThe VERSION statem
Page 108 and 109: TRUNK StatementThe TRUNK statement
Page 110 and 111: HOST StatementThe HOST statement pr
Page 112 and 113: ADAPTER StatementThe ADAPTER statem
Page 116 and 117: LINK StatementThe LINK statement is
Page 118 and 119: PORT StatementAt least one PORT sta
Page 120 and 121: Network Configuration Example* Curr
Page 122 and 123: Appendix A. NRBSTAT Error CodesWhen
Page 124 and 125: H307IP User Interface Error CodesTh
Page 126 and 127: 1300 Driver Level - Read Time Out.
Page 128 and 129: CONF010E TYPE missing in LOCALNET s
Page 130 and 131: CONF074E Invalid trunk (0,1) define
Page 132 and 133: Explanation: All hosts in the same
Page 134 and 135: ESCON/SBCON InterfacesThe STK DX/E
Page 136 and 137: FFiber Distributed Data Interface (
Page 138 and 139: Ppath .............................
Page 140: Comment SheetNetwork Executive Soft
show all

SDISC Assembler Call - NetEx

Create successful ePaper yourself

Delete template?

Save as template?