T h e N e t w o r k D e fi n i t i o n L a n g u a g e a l l o w s y o u t o c o n fi g u r e c o m m u n i c a t i o n l i n e s , t e r m i n a l s , a n d d e v i c e s u s i n g t h e f o l l o w i n g c o m m u n i c a t i o n l i n e p r o t o c o l s :
A s y n c h r o n o u s ( I B M 2 7 4 1 -compatible devices)
o r t e l e t y p e w r i t e r
X . 2 5 p a c k e t s w i t c h i n g n e t w o r k ( t e l e t y p e w r i t e r -compatible devices)
IBM HASP bisynchronous (HASP-compatible devices, including batch equipment)
CDC Mode 4 synchronous (200-User-Terminal or M o d e - 4 C - c o m p a t i b l e d e v i c e s , i n c l u d i n g b a t c h
equipment)
I B M b i s y n c h r o n o u s ( I B M 3 2 7 0 - c o m p a t i b l e d e v i c e s , equipment)
2 7 8 0 - , 3 7 8 0 - , o r i n c l u d i n g b a t c h Site-defined (any devices, compatible or incom patible with any of the above)
B e c a u s e t h e T R U N K s t a t e m e n t c o n t a i n s a l l t h e n e c e s s a r y i n f o r m a t i o n e x p l i c i t l y, i t c a n b e p l a c e d anywhere within the NDL input stream after the NFILE statement. We recommend, for ease of reading, that you place all TRUNK statements at either the begin ning or the end of the division.
An example of a TRUNK statement is
TRUNK1: TRUNK, N1=NPUA, N2=NPUE, Pl-1, P2-2..
NPUA: NPU, N0DE=5, VARIANT=N3L, DMP.
NPUE: NPU, N0DE=9, VARIANT=N5L.
Your NDL program's network division must describe a l l c o m m u n i c a t i o n l i n e s , t e r m i n a l s , a n d d e v i c e s c o n n e c t e d t o t h e s e t o f n e t w o r k p r o c e s s i n g u n i t s . You use the following statements to do this:
LINE or GROUP statements define the physical a n d l o g i c a l s e r v i c e r e q u i r e m e n t s o f e a c h c o m munication line on each NPU.
T E R M I N A L o r T E R M D E V s t a t e m e n t s d e fi n e t h e c l u s t e r i n g o f d e v i c e s c o n n e c t e d t o e a c h c o m m u n i c a t i o n l i n e .
DEVICE or TERMDEV statements define the physical and logical support requirements of each device w i t h i n a t e r m i n a l .
3-6 60480000 N
/ * 8 8 * j j .
^g$p\
0 ^ \
trunk: TRUNK,N1=npu1,N2=npu2,P1=port1,P2=port2
C,N0L0AD1C=yn1:,N0L0AD2C=yn2:,FRAME=frame,DIC=yn3::.
t r u n k npul
npu2
p o r t l
p o r t 2
yn1
yn2
frame
yn3
The element name to be assigned to the trunk communication line being defined. This name is required; there is no default value.
The element name for one of the two NPUs connected by the trunk. This name must appear on an NPU statement in the same network definition. This name is required; there is no default v a l u e .
The element name for the other of the two NPUs connected by the trunk. This name must appear on an NPU statement in the same network definition. This name is required; there is no default value.
The hexadecimal number (1 £ portl <_ FE) of the port on npul to which this trunk is connected. This number cannot appear on another TRUNK or LINE statement (or within a GROUP s t a t e m e n t e x p a n s i o n ) f o r d e fi n i t i o n s a p p l y i n g t o n p u l i n t h e s a m e n e t w o r k d i v i s i o n ; a l l trunk lines on an NPU must be assigned consecutively numbered ports starting at 1, and this number must be the thumbwheel number on the CLA for the trunk line. If npul is to be loaded over this trunk, 1 £ portl < 4.
The hexadecimal number (1 < port2 < FE) of the port on npu2 to which this trunk is connected. This number cannot appear on another TRUNK or LINE statement (or within a GROUP s ta te me nt ex pans i on) f or defini ti ons appl yi ng t o npu2 i n th e s am e net w or k di v i s i on; all trunk lines on an NPU must be assigned consecutively numbered ports starting at 1, and this number must be the thumbwheel number on the CLA for the trunk line. If npu2 is to be loaded over this trunk, 1 _< port2 <_ 4.
An optional reserved word value (YES or NO) for an optional stand-alone keyword; this parameter prohibits loading npul over this trunk. If N0L0AD1 or N0L0AD1=YES is specified, npul cannot be loaded by npu2. If N0L0AD1 is omitted or N0L0AD1=N0 is specified, npul will be loaded by npu2 whenever npul requests that operation. Usually a NO value is specified for trunks connecting NPUs if administrative responsibility for the two NPUs rests with a single site. If the two NPUs are administered by different sites, a YES value i s s p e c i fi e d .
An optional reserved word value (YES or NO) for an optional stand-alone keyword; this parameter prohibits loading npu2 over this trunk. If N0L0AD2 or N0L0AD2=YES is specified, npu2 cannot be loaded by npul. If N0L0AD2 is omitted or N0L0AD2=N0 is s p e c i fi e d , n p u 2 w i l l b e l o a d e d b y n p u l w h e n e v e r n p u 2 r e q u e s t s t h a t o p e r a t i o n . The approximate decimal number (0 £ frame £ 1200) of 8-bit character bytes that will be transmitted as one frame across this trunk. The value you should declare for this parameter depends on the type of data traffic across the trunk and the speed of data transmission on the line. Recommended values appear in table 3-1; declared values are rounded as follows:
Declared Frame Value 0 t h r u 4 9 9 500 thru 1049 1050 thru 1200
Value Used 256 500 1050
An optional reserved word value (YES or NO) for an optional stand-alone keyword; this parameter specifies the status assigned to this trunk at network initiation. When DI or DI=YES is specified, the trunk is disabled at network initiation and cannot be used until the HOP or NOP enables it. If DI is omitted or DI=N0 is specified, the trunk is given an initial status of enabled unless the NOP or HOP specifies otherwise.
Figure 3-7. TRUNK Statement Format
j^*-~\
These statements must contain value declarations to support hardware and protocols known to CDC but can a l s o c o n t a i n d e c l a r a t i o n s t o s u p p o r t s i t e - d e fi n e d h a r d w a r e o r p r o t o c o l s . S i t e - d e fi n e d v a l u e d e c l a r a t i o n s d o n o t h a v e t h e i n t e r d e p e n d e n c i e s o f C D C -d e fi n e -d v a l u e -d e c l a r a t i o n s a n -d r e c e i v e l e s s -d i a g n o s t i c i n s p e c t i o n d u r i n g N D L p r o c e s s o r e x e c u t i o n . Yo u a r e r e s p o n s i b l e f o r p r o p e r a g r e e m e n t a m o n g v a l u e s o n t h e s e s t a t e m e n t s w h e n o n e s t a t e m e n t contains a site-defined value.
60480000 N
These five statements provide the network software w i t h i n f o r m a t i o n t h a t i t t r a n s m i t s t o C C P a s a s e t o f p a i r e d i n f o r m a t i o n b y t e s c a l l e d fi e l d n u m b e r / field value (FN/FV) pairs. Each of these statements ( e x c e p t t h e T E R M I N A L s t a t e m e n t ) c a n c o n t a i n t h e keywords P90 through P99, identifying field numbers n o t u s e d b y t h e r e l e a s e d v e r s i o n o f C D C n e t w o r k
s o f t w a r e .
3-7
I f y o u r s i t e h a s m o d i fi e d C C P s o f t w a r e o r h a s w r i t t e n i t s o w n Te r m i n a l I n t e r f a c e P r o g r a m , t h e s e o p t i o n a l fi e l d n u m b e r p a r a m e t e r s a l l o w y o u t o s p e c i f y t h e v a l u e s t o b e t r a n s m i t t e d f o r t h e c o r
responding field number when the terminal or device i s c o n fi g u r e d . I f y o u p l a c e t h e s a m e fi e l d n u m b e r parameter in more than one of the statements in a h i e r a r c h i c a l s e t , e a c h v a l u e s p e c i fi e d i s u s e d s e p a r a t e l y. E a c h l i n e a n d d e v i c e h a s a s e p a r a t e s e t o f fi e l d n u m b e r / fi e l d v a l u e p a i r s a s s o c i a t e d w i t h i t .
For example, if you place P90 on the GROUP statement and on one of the DEVICE statements in the following s e t :
GROUP statement TERMINAL statement
DEVICE statement DEVICE statement DEVICE statement
the value specified on the DEVICE statement is used a s fi e l d 9 0 f o r t h e c o n fi g u r a t i o n t r a n s m i t t e d t o CCP for that device, and the value specified on the GROUP statement is used as field 90 for each com m u n i c a t i o n l i n e . N o 9 0 v a l u e e x i s t s f o r t h e remaining devices.
The parameters required and the values allowed on the GROUP, LINE, TERMINAL, TERMDEV, and DEVICE s t a t e m e n t s d e p e n d u p o n t h e l i n e p r o t o c o l u s e d . T h i s s e c t i o n p r e s e n t s t h e g e n e r a l f o r m o f e a c h statement. The following sections present the form of each statement and the parameters applicable to each line protocol:
S e c t i o n 4 a p p l i e s t o a s y n c h r o n o u s p r o t o c o l l i n e s .
Section 5 applies to X.25 protocol lines.
Section 6 applies to synchronous protocol lines.
S e c t i o n 7 a p p l i e s t o s i t e - d e fi n e d p r o t o c o l l i n e s .
line: LINE,PORT=port,LTYPE=ltype C,TIPTYPE=tiptype,AUTOr=yni:,:
CXAUT0C=yn2:,Dir=yn3:,LSPEED=lspeed,:
CAL=acclev,DFL=dfl,FRAME=frame,:
CRTIME=timer,RCOUNT=count,:
CNSVC=svcirc,PSN=psn,DCEC=yn4:,:
CDTEA=locadr,ARSPEED=yn5,:
ClMDISCC=yn6:,LCN=lcn,RCC=yn7:,:
CP90=fv90,...,P99=fv99:.
Parameters are described in sections 4 through 7.
Figure 3-8. General LINE Statement Format
Using the GROUP statement can reduce the number of d e fi n i t i o n s y o u m u s t p r o v i d e i n y o u r N D L p r o g r a m without reducing the number of definitions provided i n t h e n e t w o r k c o n fi g u r a t i o n fi l e . T h e g e n e r a l format of the GROUP statement is shown in figure 3 - 9 .
TERMINAL STATEMENT
The TERMINAL statement defines the characteristics of a multiple device workstation, such as a mode 4C t e r m i n a l d e v i c e c l u s t e r . T h i s s t a t e m e n t h a s t h e general format shown in figure 3-10.
LINE STATEMENT
Each LINE statement defines one communication line between a terminal and the NPU. There must be one LINE statement for each CLA port on the NPU that s u p p o r t s t e r m i n a l a c c e s s . F i g u r e 3 - 8 s h o w s t h e general format of the LINE statement.
DEVICE STATEMENT
The DEVICE statement defines the characteristics of a s i n g l e t e r m i n a l i n p u t a n d / o r o u t p u t d e v i c e , s u c h a s a c o n s o l e o r c a r d r e a d e r. T h i s s t a t e m e n t h a s
the general format shown in figure 3-11.
GROUP STATEMENT
You can use the GROUP statement in place of the LINE statement when you want to repeat a line definition a specified number of times. NDLP does not allow GROUP statements for X.25 protocol communication l i n e s .
TERMDEV STATEMENT
T h e T E R M D E V s t a t e m e n t d e fi n e s a t e r m i n a l t h a t consists of a single input and output device, such as an asynchronous console. This statement has the general format shown in figure 3-12.
/ ^ * ? \
3-8 60480000 N
group: GROUP,PORT=port,LTYPE=ltype C,TIPTYPE=tiptype,AUTOC=yni:,:
CXAUTO C=yn2:,DIC=yn3:,LSPEED=Ispeed,:
CAL=acclev,NI=iter,ARSPEED=yn4,:
ClMDISCC=yn5:,LCN=lcn,RCC=yn6:,:
CP90=fv90,...,P99=fv99:.
Parameters are described in sections 4 through 7.
Figure 3-9. General GROUP Statement Format
TERMINALC,STIP=stiptyp,TC=trmclas,:
CCSET=charset,TSPEED=trmsped,:
CCA=clsadr,RIC=yn1,:
CC0=conord,BCFC=yn2:,MREC=rec,:
CW=pacwndw,CTYP=ci rtyp,NCIR=numci r,:
CPAD=string,E0F=yn3:
CNEN=enci r,COLLECTC=yn3::.
Parameters are described in sections 4 through 7.
Figure 3-10. General TERMINAL Statement Format
device: DEVICEC,DT=devtyp,SDT=subdt,TA=trmaddr,ABL=abl,DBZ=dwnlsiz,UBZ=upbsize,:
CDBL=dwnblim,UBL=upblim,XBZ=xmitsiz,DO=devord,STREAM=streamno,:
CAUT0C0NC=yni:,PRIC=yn2:,DIC=yn3:,HN=node,HDC=yn4:,LK=yn5,AB=ab,BR=br,CP=cp,BS=bs,B1=b1,:
CB2=b2,CI=ci,CN=cn,CT=ct,DLC=dlc,DLT0=dlto,DLX=dlx,EBX=ebx,EBR=ebr,EB0=ebo,:
CELX=elx,ELR=elr,ELO=elo,EP=ep,XLC=xlc,XLTO=xlto,XLX=xlx,XLY=xly,IC=ic,:
CIN=in,LI=li,0P=op,0C=oc,PA=pa,PG=pg,PL=pl,PU=pw,RTSC=yn6:,MCI=mc,MLI=ml,E0F=yn7,:
CP90=fv90,...,P99=fv99:.
Parameters are described in sections 4 through 7.
Figure 3-11. General DEVICE Statement Format
device: TERMDEVC,STIP=stiptyp,TC=trmclas,CSET=charset,TSPEED=trmsped,CA=clsadr,RIC=yn1,:
CC0=conord,BCFC=yn2:,MREC=rec,W=pacwndw,NCIR=numcir,PAD=string,NEN=encir,:
CC0LLECTC=yn3:,DT=devtyp,SDT=subdt,TA=trmaddr,ABL=abl,DBZ=dwnlsiz,UBZ=upbsize,:
CDBL=dwnblim,UBL=upblim,XBZ=xmitsiz,DO=devord,STREAM=streamno,:
CAUT0C0NCyn4:,PRIC=yn5:,DlC=yn6:,HN=node,HDC=yn7:,LK=yn8,AB=ab,BR=br,CP=cp,BS=bs,B1=b1,:
CB2=b2,CI=ci,CN=cn,CT=ct,DLC=dlc,DLT0=dlto,DLX=dlx,EBX=ebx,EBR=ebr,EB0=ebo,:
CELX=elx,ELR=elr,ELO=elo,EP=ep,XLC=xlc,XLTO=xlto,XLX=xlx,XLY=xly,IC=ic,:
CIN=in,LI=li,0P=op,0C=oc,PA=pa,PG=pg,PL=pl,PW=pw,RTSC=yn9:,MCI=mc,MLI=ml,E0F=yn10,:
C P 9 0 = f v 9 0 , . . . , P 9 9 = f v 9 9 : .
Parameters are described in sections 4 through 7.
Figure 3-12. General TERMDEV Statement Format
60480000 N 3-9