SDISC Assembler Call - NetEx

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