SDISC Assembler Call - NetEx

More documents

Recommendations

Info

NRBMAXRTNRBPROTANRBPROTLNRBPNAMELimit on transmission speed.Address for incoming Odata.Length of buffer to hold Odata.Application name to offer.SOFFR ResultsThe following NRB fields are updated when SOFFR completes.NRBSTATSuccess/failure code.NRBINDContains Connect Indication.NRBLENLength of incoming Pdata.NRBUBITUnused bit count of Pdata.NRBNREF Sref assigned this connection.NRBBLKO Maximum transmission Pdata size.NRBBLKIMaximum reception Pdata size.NRBMAXRT Max transmission speed of path.NRBPROTL Length of Odata received.NRBHNAME Name of host where S-conn originated.NRBPNAME Name of application where S-conn originated.Page 50 FORTRAN Interface MAN-REF-H307IP-04
SCONN FORTRAN <strong>Call</strong>The SCONN (connect) call provides a means for a program to request a session with a program that has issuedan SOFFR. Before issuing the SCONN, an NRB must be provided for use by the user interface.<strong>Call</strong> Operation ParametersCALL SCONN[W] (nrb, buffer, length, datamd, pname, hname)The following parameters were shown in the SCONN call format. The parameters must be specified in theorder presented. If parameters are omitted, the commas must still be used.CALLThis is the required standard high level call instruction.SCONNThis is the verb for the call. Either SCONN or SCONNW must be specified.SCONNWThis indicates that the calling program should wait for the call to complete before processing is resumed.nrbThis required parameter is the address of the NRB data area that is to be passed to NETEX.bufferThis optional parameter specifies the start of an array that holds the user data that is to be sent to thecorresponding application.LengthThis optional parameter specifies the length of the data (in addressable units - words for Unisys) thatis to be sent to the corresponding application, to be presented with the completion of the correspondingapplication’s OFFER request. If no data needs to be sent to the other application, the length maybe set to zero. The data type of length should be INTEGER.datamdThis optional parameter specifies the datamode that is to be used to send the connect data to the correspondingapplication. The data type of datamd should be INTEGER. Refer to NRBDMODE in“NETEX Request Block” on page 25 for a discussion of the datamode parameter.PnameThis optional parameter specifies the alphabetic name of the process SOFFR'd by the correspondingcalling program. The name offered is determined by the other calling program. This name may beprovided as a CHARACTER*8 variable or as a string in the CALL statement if padded with blanks toeight characters in length.HnameThis required parameter specifies the alphabetic name of the host computer to be accessed to determineif the correct SOFFR is available. The “names” of the host computers in the network are determinedby the NETEX installation systems programmer. This may be provided as a CHARACTER*8variable or provided as a string in the CALL statement if padded with blanks to eight characters inlength.MAN-REF-H307IP-04 FORTRAN Interface Page 51
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: SOFFR FORTRAN CallThe SOFFR (offer)
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 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?