SDISC Assembler Call - NetEx

More documents

Recommendations

Info

InstallationPrerequisitesThe prerequisites for installing and running H307IP are:• Unisys 1100 or 2200 processor running OS 1100 release 39R1 or higher (IOAID$ supported.)• A DX/E with at least one PB225/NB22x host interface and PDNTx/NDNTx NETEX or other supportedStorageTek supported hardware attached to a FIPS blockmux channel.Or a NESiGate Channel Offload adapter with the appropriate host interface installed.Pre-InstallationBefore using H307IP, the DX/E or NESiGate adapter(s) must be defined to the exec. See Appendix C fornotes on this procedure for the various types of hardware.Installation ProcedureThe following steps are required to install and run H307IP. They are described in detail below:1. Unload tape2. Customize3. Define your network configuration and run the Configuration Manager to build a PAM file4. Load the PAM using the NCT Loader5. Verify installation6. Re-map current applications (optional)Step 1. Unload TapeThe H307 installation tape contains several files. Only the first file is required to install H307IP.@ASG,TJ@CAT,P@COPY,GH307 TAPE,T,h307H2X,F///999H307TAPE,N2XThe second file is needed to build the NCT (ConfMang) and to load the NCT (NCTL) into the offloadNETEX.@CAT,P@COPY,GCONFIG,F///999H307TAPE,CONFIGThe third file (PASCAL) is only needed if you need to make changes to ConfMang or NCTL. To load it, enterthe following@CAT,P@COPY,G@SYMPASCAL,F///999H307TAPE,PASCALN2XPRT,,devicePage 78 Installation MAN-REF-H307IP-04
Step 2. Customize H307IPStep 2a. Modify System(s) Interface Configuration (Required)The multi-site configuration feature allows you to generate H307IP for all 1100/2200 systems with a singleBLD procedure. You can also gen a single H307IP on each system. The interfaces are defined for systems inthe BLD runstream on SYS statements. The format for this is:SYS siteid1 unitname1, 1stunit, numunits, hostname, ssnm [,Netex-GNA][unitname2, 1stunit, numunits, hostname, ssnm [,Netex-GNA] ]. (field-2 repeated for each hardware interface).SYS siteid2 … (SYS SGS repeated for each site to be configured)siteidThe 1100/2200 system siteid as configured in the OS1100 sysgen. If the settings do not match, theH307IP common bank will deny access to callers. This check may be disabled by changing the tagSITECHECK in N2XDEFSunitnameThe OS2200 device name of the first configured unit (e.g. HYPA00).1stunitThe device address of the first configured unit (usually 0)numunitsThe number of devices (subchannels) to be used by H307.hostnameIf there are multiple hosts sharing an offload NETEX, then this name can be used to distinguishSOFFRs made for the same process name on the hosts (e.g. BFXJS). This name would then match aHost Group name for this NETEX in the connecting NETEX NCT. This field can be left empty ifthere is only one host using the offload NETEX.ssnmThe interface name for specific allocation requests. It is one to four alphanumeric characters. If thisparameter is not defined, SSG returns an ERROR saying that the fifth parameter is missing. Thisvalue can be specified in the NRBSSNM field to select an interface.Netex-GNAThis field must be present for DX NETEX and omitted for NESiGate offload. It is a 4-byte octal ordecimal value corresponding to the DX/E GNA address configured in the DX/E. For example, if theNETEX GNA is 0101B3C0, this field would be: 1,1,0263,0300 or 1,1,179,192.Note:There must be exactly one SYS SGS for each system for which you are building an H307IP. If youprefer to do each build on its own system, then there should be only on SYS SGS in each build. Referto the sample configuration in Figure 6.Step 2b. Modify Site-Specific Parameters (Optional)If no changes to default parameter values are needed, you may skip to the next step.The following parameters may be changed at the top of module N2XDEFS (default value in parentheses):DATATO (30)MAN-REF-H307IP-04 Installation Page 79
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 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?