The NPU statement names the NPU and defines the node number by which the NPU is to be referenced by the network software. There must be one NPU state m e n t f o r e v e r y N e t w o r k P r o c e s s i n g U n i t i n t h e network. The format of the NPU statement is shown
i n fi g u r e 3 - 2 .
The OPGO value used remains in effect., for as long as the network definition is used. The DMP value used remains in effect until it is overridden by an operator DUMP command or LOAD command NDMP option.
An operator LOAD command applies only to one loading operation on the NPU, so the DMP parameter value is a g a i n u s e d w h e n t h a t o p e r a t i o n i s c o m p l e t e d . A n operator DUMP command remains in effect until the network is shut down, so the DMP parameter value is not used until the network is again initialized.
For example, consider the following NPU statement:
NPUA: NPU, N0DE=2, VARIANT=N3L, OPGO, DMP.
T h i s d e fi n i t i o n d e s c r i b e s N P U A ( a f r o n t - e n d N P U with a node number of 2). NPUA is loaded according to the Network Supervisor program directives in the p r o g r a m i n i t i a t i o n c o n t r o l b l o c k ( P I C B ) c a l l e d N 3 L w i t h i n t h e n e t w o r k l o a d fi l e .
B e c a u s e O P G O i s u s e d , a n o p e r a t o r i n t e r v e n t i o n r e q u i r e m e n t e x i s t s f o r N P U A w h e n e v e r i t s l o a d i n g p r o c e s s i s c o m p l e t e d . B e f o r e t y p i n g G O , t h e operator can enable or disable any of the network e l e m e n t s a s s o c i a t e d w i t h t h e N P U . N P U A a l w a y s e s t a b l i s h e s a s u p e r v i s o r y r e l a t i o n s h i p w i t h a C o mmu n i c a ti o n s S u p e r vi so r ( C S ) p ro g ra m a n d t h e n requests operator permission (a GO command) before i t b e g i n s t o s e r v i c e i t s c o n fi g u r e d c o m m u n i c a t i o n l i n e s .
Because DMP is used, the long-term dump flag of the Network Supervisor (NS) for NPUA is set. The NS will dump the memory of NPUA each time NPUA is loaded, unless a NPU, a diagnostic or a host oper ator (NOP, DOP, or HOP) unsets the dump flag with a DMP command, or unless repeated loads occur within a s h o r t t i m e s p a n . ( R e p e a t e d r e l o a d i n g d u r i n g a short time span is presumed to result from repeated failures with the same cause, so multiple dumps are redundant.)
I f D M P = N O w e r e s p e c i fi e d o n t h e N P U d e fi n i t i o n statement, the long-term dump flag for NPUA would not be set at network Initiation (unless the NOP or HOP set it with a command).
npu: lfl>U,N0DE=node,VARIANT=picbnameC,0PG0C=yni:,DMPC=yn2::.
npu node
picbname
yn1
yn2
The element name of the NPU being described, v a l u e .
This name is required; there is no default The network node number (1 < node £255) by which the network software references this NPU. All values declared for node must be unique within the current network definition and should be numbered consecutively. This number is required; there is no default value.
The name assigned to the program initiation control block (PICB) on the network load file for this NPU. The PICB contains directives to the Network Supervisor for dumping and
loading a given NPU. This name consists of one through six alphabetic and numeric characters/ the first of which must be alphabetic. The name is required; there is no default value. (Self-loading, self-configuring NPUs also roust have a value declared for this parameter; use a dummy name.) See the NOS installation handbook for more information about this parameter.
An optional reserved word value (YES or NO) for an optional stand-alone keyword; this parameter indicates whether an operator GO command is required to start NPU operation after loading is completed. If OPGO or 0PG0=YES is specified, the HOP or controlling NOP must type GO each time the NPU is loaded before the NPU can become active. If OPGO is omitted or 0PG0=N0 is specified, operator intervention is not required to start the NPU.
You should define an 0PG0=YES value only if frequent configuration changes are anticipated for the NPU.
An optional reserved word value (YES or NO) for an optional stand-alone keyword; this parameter indicates whether a long-term requirement exists for an NPU dump each time the NPU is loaded. If DMP or DMP^YES is specified, or if DMP is omitted, the NPU is dumped before it is loaded, unless the operation is overridden by a HOP or NOP command. If DMP=N0 is specified, no dump occurs before the NPU is loaded, unless specifically
requested by a HOP or NOP command. (Note that an NPU dump is essential for CDC to analyze NPU failure problems.)
Figure 3-2. NPU Statement Format
3-2 60480000 N
jl|pR!\^
SUPLINK STATEMENT
The SUPLINK statement describes a supervision path between the NPU and a copy of CS which can supervise t h a t N P U a n d d e fi n e s t h e p r i o r i t y f o r u s e o f t h a t p a t h . A s u p e r v i s i o n p a t h , o r s u p e r v i s o r y l i n k , corresponds to a logical link between the NPU and a h o s t .
O n l y o n e s u p e r v i s o r y l i n k c a n b e d e fi n e d i n e a c h SUPLINK statement. If there is more than one logi cal link between an NPU and the host computer, each can appear in a separate SUPLINK statement; these s t a t e m e n t s m u s t a p p e a r i n d e s c e n d i n g o r d e r o f p r i o r i t y . T h e fi r s t s u p e r v i s o r y l i n k d e fi n e d h a s t h e h i g h e s t p r i o r i t y, t h e s e c o n d d e fi n e d h a s t h e n e x t h i g h e s t p r i o r i t y, a n d s o o n . T h e s u p e r v i s o r y l i n k s a r e u s e d i n t h e o r d e r o f t h e i r p r i o r i t y i f t h e l o g i c a l l i n k i n a h i g h e r p r i o r i t y s u p e r v i s i o n path fails or the CS becomes available.
The SUPLINK statement must follow an NPU statement or another SUPLINK statement. The SUPLINK statement i s o p t i o n a l i f t h e r e i s o n l y o n e l o g i c a l l i n k b e t w e e n t h e N P U a n d a h o s t . T h e f o r m a t o f t h e SUPLINK statement is shown in figure 3-3.
SUPLINK,LLNAME=loglink.
l o g l i n k E l e m e n t n a m e o f t h e l o g i c a l l i n k that is to be used as a super visory link by the NPU. This name must appear on a LOGLINK statement within the same net w o r k d i v i s i o n .
Figure 3-3. SUPLINK Statement Format
An example of the SUPLINK statement in an NDL pro gram sequence is
NPUA: NPU, N0DE=5, VARIANT=N3L, DMP=YES.
SUPLINK, LLNAME=LGLNK1.
CPLR1: COUPLER, N0DE=1.
LGLNK1: LOGLINK, NCNAME=NPUA.
This example defines the logical link called LGLNK1 as the only logical link for NPU supervisory message t r a f fi c w i t h a C o m m u n i c a t i o n s S u p e r v i s o r p r o g r a m . LGLNK1 exists between coupler node 1 and network n o d e 5 w i t h i n t h e N P U c a l l e d N P U A . F o r a n N P U which has logical links to more than one host, you c a n d e fi n e t h e l o g i c a l l i n k a s a s u p e r v i s o r y l i n k only if the release level of the NCF being used on the host matches the release level of the CCP being run on the NPU.
COUPLER STATEMENT
The COUPLER statement identifies a channel coupler to an NPU. A front-end NPU can be equipped with one or two channel couplers connecting the NPU to a host. The format of the COUPLER statement is shown i n fi g u r e 3 - 4 .
One COUPLER statement is required for each coupler in the network. The COUPLER statement must follow the NPU statement defining the NPU that uses the coupler to function as a front-end NPU.
E a c h C D C h o s t c o m p u t e r c a n s u p p o r t u p t o e i g h t couplers on separate data channels. CDC host soft w a r e i d e n t i fi c a t i o n o f e a c h c o u p l e r i s d e t e r m i n e d by an entry in the NOS equipment status table (EST).
The value you use for the NODE declaration on each COUPLER statement must be the value assigned as the node number in the EST entry for the corresponding N P U c o u p l e r . T h e c o u p l e r ' s e n a b l e d o r d i s a b l e d s t a t u s a t n e t w o r k i n i t i a t i o n i s a l s o c o n t r o l l e d b y
this EST entry.
coupler: COUPLER,NODE=nodeC,HNAME=hostnam,LOC=cplrloc:.
coupler node
hostnam
c p l r l o c
The element name to assign to the front-end coupler being configured, required; there is no default value.
This name is The host node number (1 £ node £ 255) by which the network software references this coupler. This value must match the node number in the EST entry for the coupler. All values declared for NODE keywords must be unique within the current NDL program division
and should be numbered consecutively. This number is required; there is no default value.
The name assigned to the host to which the coupler connects. The hostnam value is 1 to 7 letters or digits; the first character must be a letter. The hostnam you assign
identifies the corresponding node number on the host availability display seen by the t e r m i n a l u s e r. T h i s p a r a m e t e r i s o p t i o n a l ; i f o m i t t e d , t h e d e f a u l t v a l u e i s A S C I I b l a n k s . The reserved word value (PRIMARY or SECOND) that indicates the coupler's location in the 255x cabinet. PRIMARY specifies the coupler in the primary coupler slots and SECOND specifies the coupler in the secondary coupler slots. If an NPU has two couplers,
LOC=SECOND is required for the secondary coupler. This parameter is optional; the default value is PRIMARY.
Figure 3-4. COUPLER Statement Format
60480000 N 3-3
The NODE value and the HNAME value appear as a eeX on the host availability display seen by the termi nal user. The user can select connection to a host by specifying a node number or host name in a com mand to CCP; nonblank HNAME values are recommended to aid users in selecting the appropriate node.
T h e c i r c u i t b o a r d s f o r a c o u p l e r a r e l o c a t e d i n slots marked as either primary or secondary within the upper card cage of the 255x series NPU cabinet.
These markings are similar to port numbers for the couplers and are used in that manner for the LOC parameter.
I f t h e N P U h a s o n e c o u p l e r, i t c a n b e l o c a t e d i n e i t h e r t h e p r i m a r y o r s e c o n d a r y s l o t . I f t h e N P U h a s a c o u p l e r i n t h e s e c o n d a r y s l o t , t h e c o u p l e r must be defined as a secondary coupler.
I For example, suppose NPUA in SVLnet (figure 2-1 in
■ section 2) contained two couplers, only one of which (the secondary one) belonged to the network shown.
The circuit boards in the secondary slot would be cabled to host data channel number 4; the EST entry w o u l d a s s o c i a te n o d e n u m b e r 1 w i th d a ta c h a n n e l n u m b e r 4 . T h i s c o u p l e r c o u l d b e c o n fi g u r e d c o r rectly only by the statement:
NPUA: NPU, N0DE=5, VARIANT=N3L, DMP.
CPLR1: COUPLER N0DE=1, LOC=SECOND.
As used in the sample network configured by section 11 , N P U A c o n t a i n s o n l y o n e c o u p l e r. I t t h e r e f o r e is configured correctly by the statement:
NPUA: NPU, N0DE=5, VARIANT=N3L, DMP.
CPLR1: COUPLER NODE=l,HNAME=SYS173.
B o t h e x a m p l e s d e fi n e c o u p l e r C P L R 1 , w h i c h i s physically contained in the cabinet of NPUA; NPUA uses CPLR1 to function as a front-end NPU. CPLR1 has a NOS EST entry of 1 for its host node number.
Note that NPUA contains both a host node (node 1) f o r i t s c o u p l e r a n d a n e t w o r k n o d e ( n o d e 5 ) f o r I t s e l f .
The COUPLER statement also defines a possible path the NPU can use for a request to be loaded and/or dumped by a host.
LOGLINK STATEMENT
The LOGLINK statements define a path over which t e r m i n a l t o a p p l i c a t i o n o r a p p l i c a t i o n t o -a p p l i c -a t i o n c o n n e c t i o n s c -a n b e e s t -a b l i s h e d . Yo u must supply one LOGLINK statement for each logical link in your network. You need LOGLINK statements t o d e fi n e t h e l o g i c a l l i n k b e t w e e n a c o u p l e r a n d the NPU that contains the coupler and between a coupler and each NPU connected to the front-end NPU c o n t a i n i n g t h e c o u p l e r. Yo u a l s o n e e d a L O G L I N K s t a t e m e n t t o d e fi n e e a c h h o s t - t o - h o s t l o g i c a l l i n k between two couplers if application programs in the two hosts are to communicate with each other.
Application programs in two hosts can communicate with each other without having a LOGLINK statement f o r t h e t w o c o u p l e r s i n v o l v e d o n l y i f t h e r e i s a n i n t e r v e n i n g X . 2 5 n e t w o r k b e t w e e n t h e t w o h o s t s . ( L o g i c a l l i n k s c a n n o t s p a n X . 2 5 p u b l i c d a t a networks, but always terminate at the NPU connected to the public data network.)
O n l y o n e l o g i c a l l i n k c a n b e d e fi n e d b e t w e e n a n y given pair of coupler and NPU or coupler node num b e r s . I t i s p o s s i b l e , h o w e v e r, t o h a v e m o r e t h a n one logical link between an NPU and a host computer.
Figure 3-5 shows the logical links in SVLnet. Each | logical link uses a separate trunk between the NPU a n d / o r a d i ff e r e n t c o u p l e r.
L o g i c a l l i n k s c a n o n l y b e d e fi n e d o v e r p a t h s t h a t do not cross more than one trunk. In the example s h o w n i n fi g u r e 3 - 5 , n o l o g i c a l l i n k c a n e x i s t between NPUC and coupler 11.
The LOGLINK statement must follow the COUPLER statement that defines the coupler for the host end o f t h e l o g i c a l l i n k b e i n g d e fi n e d . L O G L I N K s t a t e ments define which NPUs can access that coupler.
For a coupler-to-coupler link, the LOGLINK statement c an fol l ow ei t her of th e C OU P LE R s t ate me nt s, but cannot appear after both. The format of the LOGLINK statement is shown in figure 3-6.
F o r e x a m p l e , i n S V L n e t ( fi g u r e 2 - 1 i n s e c t i o n 2 ) , | NPUA (node 5) contains coupler CPLR1 (node 1) and is connected to NPUE (node 9). NPUB (node 6) con tains coupler CPLR2 (node 2) and is also connected t o N P U E . N P U E h a s c o n n e c t i o n s t o s e v e r a l o t h e r f r o n t - e n d N P U s , g i v i n g i t s n e t w o r k n o d e f o u r possible logical links to the same host.
The host node in NPUA is node 1; the host node in NPUB is 2 (the host node number is always the number associated with the coupler). The following LOGLINK s t a t e m e n t s w o u l d p r o p e r l y c o n fi g u r e t w o o f t h e logical links involving NPUE as network node 9:
NPUA: NPU, N0DE=5, VARIANT-N3L, DMP.
CPLR1: COUPLER N0DE=1,HNAME=SYS173.
LINK1: LOGLINK NCNAME=NPUE.
NPUB: NPU, N0DE=6, VARIANT=N5L.
CPLR2: COUPLER NODE=2,HNAME=SYS173.
LINK2: LOGLINK NCNAME=NPUE.
NPUE: NPU, N0DE=9,...
3-4 60480000 N
/iP^N
HOST 1 HOST 2
HOST 4
M O D E 4 \ TERMINAL /
Figure 3-5. Logical Links
60480000 N 3 - 5
loglink: LOGLINK,NCNAME=ncnameC,DIE=yn::.
l o g l i n k
yn
The element name to assign to the logical link you are
c o n fi g u r i n g . T h i s n a m e i s required; there is no default v a l u e .
The element name of the flPU or coupler that is the other end of t h i s l o g i c a l l i n k . T h i s n a m e must be the element name used in an NPU or coupler statement in the same network division. This name is required; there is no d e f a u l t v a l u e .
An optional reserved word value (YES or NO) for an optional stand-alone keyword; this parameter specifies the status a s s i g n e d t o t h i s l o g i c a l l i n k a t n e tw o r k i n i ti a ti o n . W h e n D I o r DI=YES is specified, the logical link is disabled at network initiation and cannot be used until the HOP or NOP enables it.
If DI is omitted or DI=N0 is s p e c i fi e d , t h e l o g i c a l l i n k i s g i v e n a n i n i t i a l s t a t u s o f enabled unless the NOP or HOP s p e c i fi e s o t h e r w i s e .
TABLE 3-1. RECOMMENDED FRAME SIZES FOR TRUNK LINES
Figure 3-6. LOGLINK Statement Format
TRUNK STATEMENT
The TRUNK statement describes the trunk communi c a t i o n l i n e t h a t p h y s i c a l l y c o n n e c t s t w o N P U s . T h er e c an be only o n e tru n k de fine d b etw een any p a i r o f N P U s i n a n e t w o r k . P o r t n u m b e r s f o r a l l t r u n k s / l i n e s s h o u l d b e a s s i g n e d c o n s e c u t i v e l y, s t a r t i n g w i t h o n e . S i n c e t h e N P U r e s e r v e s c o n t i guous memory space for ports, this conserves memory space.
T h e f o r m a t o f t h e T R U N K s t a t e m e n t i s s h o w n i n figure 3-7. The recommended values for the FRAME parameter are given in table 3-1.
T r a f fi c is Mostly
Trunk Line Speed in Bits Per Second 4800 or Less 9600 19200 56000
I n t e r a c t i v e 1050 1050 1050 1050
Batch and 256 500 1050 1050
I n t e r a c t i v e
Batch 1050 1050 1050 1050
T h e N I a n d N 2 v a l u e s i n d i c a t e t h a t t h e t r u n k connects the NPUs NPUA and NPUE. The PI and P2 p a r a m e t e r s i n d i c a t e t h a t t h e t r u n k i s c o n n e c t e d t o the Communications Line Adapter (CLA) port 1 in NPUA and to port 2 in NPUE.