SDISC Assembler Call - NetEx

More documents

Recommendations

Info

Explanation: All hosts in the same group must have specified the same session manager DREF.System Action: Display error message, set ValidNCT flag to FALSE and continue processing.CONF057I Parsing completed VaIidNCT = ‘flag’, Errors = ‘number’, Warnings = ‘number’Explanation: This is only an informational message. The state of the ValidNCT flag is displayedalong with the number of error and warning messages encountered.System Action: Display message and continue processing.CONF072E Multi-task adapters require unique CHANADDRsExplanation: On a multi-process host, two adapters were encountered with the same NETADDRand the same CHANADDR. The CHANADDR values must be different. See ADAPTER statementsection for details on multi-process hosts.System Action: Display error message, set ValidNCT flag to FALSE and continue processing.MAKEPAM Processing MessagesThe errors that could be encountered in CONFgetPAM (while processing the MAKEPAM command) are asfollows. The actual value of the identifier will replace an identifier enclosed in single quotes (for example:‘HOSTname’).CONF058E HOST not defined in global configuration: ‘HOSTname’Explanation: The HOST specified was not found in the NCT.System Action: Generate error message. No PAM is returned to caller.CONF059E NCT is invalid, PAM cannot be builtExplanation: The parser has detected one or more errors, therefore, the PAM cannot be built.System Action: Generate error message. No PAM is returned to caller.CONF060E No path from HOST: ‘HOSTname’ to HOST: ‘HOSTname’Explanation: No path exists from the specified local host to the specified remote host.System Action: Generate error message. No PAM is returned to caller.CONF061E NCT is invalid, HOST Configuration cannot be builtExplanation: The parser has detected one or more errors, therefore, this entry cannot be built.System Action: Generate error message. No entry is returned to caller.CONF099I Path exists from HOST: ‘hostname’ to HOST: ‘hostname’Explanation: There is a route from the first ‘hostname’ to the second. Informational message only.System Action: Generate message and continue processing.Page 118 Appendix B. ConfMang Messages MAN-REF-H307IP-04
Appendix C. Sysgen NODE StatementsThe following are the SYSGEN node statements required to define NETEX adapters. Note that in newerUnisys systems this is now done by the ODB configuration.P/NB22x or PB25x DX/Es or NesiGate InterfacesA control unit sysgen statement example follows:NODE hypera IS ARBCU AND CONNECTS TO i1mod6 VIA SUB-CHANNEL 12The device sysgen statement example:NODE hypa,0 THRU hypa,3 ARE ARBDEV AND CONNECT TO hyperaThis statement configures devices hypa0, hypal, hypa2, and hypa3. In the preceding example, DEVNAME inthe NCT would be hypa0.hypera is the adapter name by which you wish to refer to this control unit.i1mod6 is the node name in the OS system for the block mux channel.12 This is the subchannel position occupied by this adapter. It is the (decimal) start address of thechannel interface module i1mod6.In the NETEX NCT, the ADAPTER CHANADDR field must correspond to this. For example, ifSUB-CHANNEL is 12, then CHANADDR is C0.This must also correspond to the switches on the device board of the adapter or the profiled controlunit address.The equipment type ARBCU and ARBDEV indicate that NETEX will be using the arbitrary device handler(IOAID$) to access the adapter. If SINCH is to be used instead (P/NB22x only), replace the equipment typeARBCU with HYPCU and ARBDEV with HYPDEV. Do not define the NETEX devices on HYPNET SGSs.When configured this way, NETEX may be configured to use either SINCH (A2225 EQU 1) or IOAID(A222S EQU 2). Non-NETEX applications (e.g., DDP) may use other adapter addresses, greater thanNUMADDRS, which require them to be SINCH devices.MAN-REF-H307IP-04 Appendix C. Sysgen NODE Statements Page 119
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 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 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?