SDISC Assembler Call - NetEx

More documents

Recommendations

Info

Establishing a SessionThe following figure is a flow chart showing how a connection is established using the session layer interface.Only steps which may occur in a normal process are shown in the figure. Other possibilities that are lesslikely to occur are discussed in the accompanying text.This figure references an NRB. An NRB (discussed in “NETEX Request Block”) is a block of parametersused to signal requests to NETEX and to return status to programs.Figure 5. Establishing a SessionThe following numbered items refer to the steps above. The steps are numbered to simplify the discussionand do not necessarily represent the exact order which the events occur.1. Program A prepares for the session by opening files and creating an NRB.2. Program A issues an SOFFER to make it available to other NETEX programs. The SOFFER may specifya data area for data associated with an upcoming SCONNECT.Page 12 Intertask Communication MAN-REF-H307IP-04
3. Program B is a program that needs to establish a session with program A. Program B must first open filesand create its own NRB.4. Program B then issues an SCONNECT. The SCONNECT may contain data such as a password5. Program B then checks the NRB to determine the status of the request. The NRB indicates one of thefollowing:• a request is in process• a request has completed successfully• the request has generated an errorThe session continues assuming the NRB indicated normal completion. If the NRB indicates that a requestis in process, it would have to be rechecked after a short delay. If the NRB indicates an error, theerror code would be logged and the session would not be established. The calling program should theneither try again to establish a session, or should act appropriately (such as closing files that were openedbefore the session was attempted).6. Program B expects program A to respond to the SCONNECT with a SCONFIRM or an SDISCONNECT.Program B issues an SREAD which would detect program A’s response.7. Program A checks its NRB to see whether the SOFFER completes. The NRB indicates that program Bhas issued an SCONNECT.If the NRB indicates that an error occurred, program A will act appropriately (which could be disconnectingfrom this session and reissuing the SOFFER).A password may be required at this time. The password could be sent as data associated with theSCONNECT. After the SCONNECT is received, the password is examined. The password could beused to restrict access to certain files, restrict access by certain programs, or have other customized uses.If a program attempts to access restricted files or has an incorrect password, program A may issue anSDISCONNECT and terminate the session.8. If all conditions associated with the SCONNECT are acceptable, program A issues a SCONFIRM to establishthe session. The SCONFIRM may contain data.9. Program A checks the NRB to make sure that the SCONFIRM was accepted by NETEX. If it was, programA will continue with the session. If NETEX did not accept the SCONFIRM, program A will eitherretry issuing the SCONFIRM or take other appropriate action.10. Program B checks the NRB to determine if the SREAD has successfully completed and to see what callprogram A issued. If program A had responded with a SCONFIRM, program B would continue with thesession. If program A had responded with an SDISCONNECT, program B would have to examine thereason code associated with the SDISCONNECT, and take the appropriate action.The previous discussion outlines the rules to be followed when establishing a NETEX session. It also introducesthe concept of using the NRB for communication with NETEX. After requests are issued, the NRB isexamined to see when NETEX completes the request. This may be done using the SWAIT request, or by periodicallychecking the NRB fields. The NRB fields are discussed in “NETEX Request Block”.MAN-REF-H307IP-04 Intertask Communication Page 13
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 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 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?