SDISC Assembler Call - NetEx

More documents

Recommendations

Info

MAPing NETEX ApplicationsTo MAP a NETEX application, you must include the appropriate interface subroutine library:• N2XFTN for ASCII FORTRAN• N2XPAS for U of Md PASCAL• N2XPLS for PLUS, etc..See the sample MAP source elements MAPFTN and MAPMASM for guidance.Page 66 MAPping NETEX Applications MAN-REF-H307IP-04
Driver InterfaceIntroductionThe Driver Interface service allows a NETEX user to invoke driver functions without using the NETEX sessionservice. This eliminates typical “session” overhead by placing responsibility for driver control directlywith the user.NOTE: Driver level calls are NOT SUPPORTED for the NESiGate Interface.Hardware ProtocolsThe user is responsible for providing all the information required by the adapter to conduct messages across anetwork. A message consists of the “message proper” and, optionally, associated data. The message properis limited to a length of 64 8-bit bytes; associated data is limited to a length not to exceed the installation definedMaximum Block Out (MAXBO) value.Two new fields in the NETEX request block are used to pass information regarding the message proper. Themessage proper is provided by the user in storage designated by the address specified as NRBPROTA. Thelength of the buffer whose address is in NRBPROTA must be specified in field NRBPROTL.Message ProperMessages must follow the format described below to be properly interpreted and executed. The first eightbytes of the message are interpreted by the adapter to direct the message to the proper destination. Byte 8optionally may be used to indicate if the message is in a NETEX format, and if the message contains satellitelink information.• Byte 0 – Trunk Mask (HYPERchannel trunk protocol only)Bits 0-3 - Trunks to Try (transmit). These bits specify to the sending adapter which of the availabletrunks to try when transmitting this message and associated data. Bits 0,1, 2, and 3 correspond to trunks0, 1, 2, and 3 respectively. The adapter transmits the message on the first trunk available of those selected.Bits 4-7 - Trunks to Try (receive). These bits specify to the receiver which trunks to try when sending anactive frame to the transmitter. It is necessary that at least one trunk, common to each adapter, be selectedfor each transmission.• Byte 1 – ControlBit D - Exception message. This bit is checked when a message is input to the channel. If this bit is set,the INPUT MESSAGE operation is terminated with an ending status of “channel end”, “device end”, and“unit exception”. If the bit is not set, the INPUT MESSAGE operation is terminated with an endingstatus of “channel end”, and “device end”. In either case, the entire message is transmitted to the channel.The exception message has no effect on transmit messages.Bit E - Burst Mode. When this bit is set, the forced burst mode is enabled. In this mode of operation, thetransmitting adapter gains access to the trunk and maintains control until the end of the transmission. NoMAN-REF-H307IP-04 Driver Interface Page 67
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: NETEX Calling SequenceIn order to c
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 114 and 115: CODECONV - Hardware code conversion
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?