ICUSCM*** 2eزICUDDFD_0012D_002#D_003FD_004"i3D_005 2D_006u'D_007F0D_0086D_009>D_010E;D_011N^D_012U D_013^ D_014$e U_001kB U_002Cq  U_003x0 U_004 ~S U_005v U_0061I_001ΎI_002I_003_D_001DEVNT DS SS INIFIN4SETSOUTrANSHANUTIIL CHKD01D02D03D04D_002!6DEVNT DS SS INIFIN4SETSOUTrANSHANUTIIL CHKD01D02D03D04D05D06D07D08D09D10 D11"D12$D13&D14(D15*D16,D17.D180D192D204D_0036DEVNT DS SS INIFIN4SETSOUTrANSHANUTIIL1CK1IL2CK2D01.D020D032D044D_004#VDEVNT DS SS INIFIN4SETSOUTrANSHANUTIIL1CK1IL2CK2D01.D020D032D044D056D068D07:D08<D09>D10@D11BD12DD13FD14HD15JD16LD17ND18PD19RD20TD_005DEVNT DS SS INIFIN4SETSOUTrANSHANUTIMTPCHKD01D02D03D04D_006!6DEVNT DS SS INIFIN4SETSOUTrANSHANUTIMTPCHKD01D02D03D04D05D06D07D08D09D10 D11"D12$D13&D14(D15*D16,D17.D180D192D204D_007DEVIL ITPSS DS NU INIFIN7STRVSTPuINTITOD01D02D03D04D_008 DEVIL ITPSS DS NU INIFIN7STRVSTPuINTITOD01D02D03D04D05D06D07D08D09D10D11D12D13D14D15D16D17D18D19D20D_009DEVMTPSS DS NU INIFIN5STRTSTPsMSGMTOMQLBINBID D01D02D03D04D_010"DEVMTPSS DS NU INIFIN5STRTSTPsMSGMTOMQLBINBID D01D02D03D04D05D06D07D08D09D10D11D12D13D14D15D16D17D18D19D20D_011DEVIL ITPSS DS NU INIFIN7STRVSTPuINTITOMQEQA IOAD01D02D03D04D_012#DEVIL ITPSS DS NU INIFIN7STRVSTPuINTITOMQEQA IOAD01D02D03D04D05D06D07D08D09D10D11D12D13D14D15D16D17D18D19D20D_013/DEVIL ITPD01D02D03D04D05D06D07D08!D09#D10%D11'D12)D13+D14-D_014;DEVIL ITPD01D02D03D04D05D06D07D08!D09#D10%D11'D12)D13+D14-D15/D161D173D185D197D209U_001ADEVNAMCNF TRF!IBR#OBR'SN +U01-U02/U031U043U055U067U079U08;U09=U10?U_002UDEVNAMCNF TRF!IBR#OBR'SN +U01-U02/U031U043U055U067U079U08;U09=U10?U11AU12CU13EU14GU15IU16KU17MU18OU19QU20SU_003:DEVNAMTS  MR "CS $U01&U02(U03*U04,U05.U060U072U084U096U108U_004NDEVNAMTS  MR "CS $U01&U02(U03*U04,U05.U060U072U084U096U108U11:U12<U13>U14@U15BU16DU17FU18HU19JU20LU_005 4DEVNAMU01 U02"U03$U04&U05(U06*U07,U08.U090U102U_006HDEVNAMU01 U02"U03$U04&U05(U06*U07,U08.U090U102U114U126U138U14:U15<U16>U17@U18BU19DU20FI_001/DEVNAM UN UINMB .I_002ADEVNAMPFDNFDSDD SDS!EFI"SUF#GRA$DSZ&UN *UIN+RUT;NB =CUP?MB @I_003DEVNAM FD FNCFLG GRA!DSZ#UN 'INI(FINGQUEfCANUINRUTNB STPCUPMB ICUDBF*** LD_001D_002D_003D_004D_005D_006D_007D_008D_009D_010 D_011D_012D_013D_014U_001$U_002)U_003.U_0043U_0058U_006=I_001BI_002GI_003LD_001D_002D_003D_004D_005D_006D_007D_008D_009D_010D_011D_012D_013D_014U_001U_002U_003U_004U_005U_006I_001I_002I_003glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  glob.lev = 'J'  ~glob.bio  ICUSDFD_001(D_001) (DEV) Device Name [1-16 Chars] # (NT) Number of terminals on this controller #D (DS) Driver Data Size [0-0FFFFH] #H (SS) Driver Stack Size [0-0FFFFH] #H (INI) Term-init Procedure Name [1-31 Chars] # (FIN) Term-finish Procedure Name [1-31 Chars] # (SET) Term-setup Procedure Name [1-31 Chars] # (OUT) Term-out Procedure Name [1-31 Chars] # (ANS) Term-answer Procedure Name [1-31 Chars] # (HAN) Term-hangup Procedure Name [1-31 Chars] # (UTI) Term-utility Procedure Name [1-31 Chars] # (IL) Interrupt Level [Encoded Level] #H (CHK) Term-check for this Level [1-31 Chars] # (D01) Auxiliary 1 #H (D02) Auxiliary 2 #H (D03) Auxiliary 3 #H (D04) Auxiliary 4 #H ##CHG;Do you want any/more @ DEVICEs ?  Ac~Iz (YuDEV"   NT O DS . SS  INI1;p-  FIN1h-  SET1g-  OUT1zh-  ANS1h-  HAN1Jh-  UTI1i-  IL  CHK1-  D01 D02 D03 D04 D_002EF(D_002) (DEV) Device Name [1-16 Chars] # (NT) Number of terminals on this controller #D (DS) Driver Data Size [0-0FFFFH] #H (SS) Driver Stack Size [0-0FFFFH] #H (INI) Term-init Procedure Name [1-31 Chars] # (FIN) Term-finish Procedure Name [1-31 Chars] # (SET) Term-setup Procedure Name [1-31 Chars] # (OUT) Term-out Procedure Name [1-31 Chars] # (ANS) Term-answer Procedure Name [1-31 Chars] # (HAN) Term-hangup Procedure Name [1-31 Chars] # (UTI) Term-utility Procedure Name [1-31 Chars] # (IL) Interrupt Level [Encoded Level] #H (CHK) Term-check for this Level [1-31 Chars] # (D01) #H (D02) #H (D03) #H (D04) #H (D05) #H (D06) #H (D07) #H (D08) #H (D09) #H (D10) #H (D11) #H (D12) #H (D13) #H (D14) #H (D15) #H (D16) #H (D17) #H (D18) #H (D19) #H (D20) #H ##CHG;Do you want any/more @ DEVICEs ?  !/`$Up-Ie )Ea}DEV"   NT O DS . SS  INI1;p-  FIN1h-  SET1g-  OUT1zh-  ANS1h-  HAN1Jh-  UTI1i-  IL  CHK1-  D01 D02 D03 D04 D05 D06 D07 D08 D09 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D_003F(D_003) (DEV) Device Name [1-16 Chars] # (NT) Number of terminals on this controller #D (DS) Driver Data Size [0-0FFFFH] #H (SS) Driver Stack Size [0-0FFFFH] #H (INI) Term-init Procedure Name [1-31 Chars] # (FIN) Term-finish Procedure Name [1-31 Chars] # (SET) Term-setup Procedure Name [1-31 Chars] # (OUT) Term-out Procedure Name [1-31 Chars] # (ANS) Term-answer Procedure Name [1-31 Chars] # (HAN) Term-hangup Procedure Name [1-31 Chars] # (UTI) Term-utility Procedure Name [1-31 Chars] # (IL1) First Interrupt Level [Encoded Level] #H (CK1) Term-check for First Level [1-31 Chars] # (IL2) Second Interrupt Level [Encoded Level] #H (CK2) Term-check for Second Level [1-31 Chars] # (D01) Auxiliary 1 #H (D02) Auxiliary 2 #H (D03) Auxiliary 3 #H (D04) Auxiliary 4 #H ##CHG;Do you want any/more @ DEVICEs ?  #TIz.JfDEV"   NT O DS . SS  INI1;p-  FIN1h-  SET1g-  OUT1zh-  ANS1h-  HAN1Jh-  UTI1i-  IL1 CK11-  IL2Q CK21-  D01 D02 D03 D04 D_004 n(D_004) (DEV) Device Name [1-16 Chars] # (NT) Number of terminals on this controller #D (DS) Driver Data Size [0-0FFFFH] #H (SS) Driver Stack Size [0-0FFFFH] #H (INI) Term-init Procedure Name [1-31 Chars] # (FIN) Term-finish Procedure Name [1-31 Chars] # (SET) Term-setup Procedure Name [1-31 Chars] # (OUT) Term-out Procedure Name [1-31 Chars] # (ANS) Term-answer Procedure Name [1-31 Chars] # (HAN) Term-hangup Procedure Name [1-31 Chars] # (UTI) Term-utility Procedure Name [1-31 Chars] # (IL1) First Interrupt Level [Encoded Level] #H (CK1) Term-check for First Level [1-31 Chars] # (IL2) Second Interrupt Level [Encoded Level] #H (CK2) Term-check for Second Level [1-31 Chars] # (D01) #H (D02) #H (D03) #H (D04) #H (D05) #H (D06) #H (D07) #H (D08) #H (D09) #H (D10) #H (D11) #H (D12) #H (D13) #H (D14) #H (D15) #H (D16) #H (D17) #H (D18) #H (D19) #H (D20) #H ##CHG;Do you want any/more @ DEVICEs ?  #3Ok/`)Zv:Vr 6 R n DEV"   NT O DS . SS  INI1;p-  FIN1h-  SET1g-  OUT1zh-  ANS1h-  HAN1Jh-  UTI1i-  IL1 CK11-  IL2Q CK21-  D01 D02 D03 D04 D05 D06 D07 D08 D09 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D_005(D_005) (DEV) Device Name [1-16 Chars] # (NT) Number of terminals on this controller #D (DS) Driver Data Size [0-0FFFFH] #H (SS) Driver Stack Size [0-0FFFFH] #H (INI) Term-init Procedure Name [1-31 Chars] # (FIN) Term-finish Procedure Name [1-31 Chars] # (SET) Term-setup Procedure Name [1-31 Chars] # (OUT) Term-out Procedure Name [1-31 Chars] # (ANS) Term-answer Procedure Name [1-31 Chars] # (HAN) Term-hangup Procedure Name [1-31 Chars] # (UTI) Term-utility Procedure Name [1-31 Chars] # (MTP) Message Task Priority [0-255] #D (CHK) Term-check Procedure Name [1-31 Chars] # (D01) Auxiliary 1 #H (D02) Auxiliary 2 #H (D03) Auxiliary 3 #H (D04) Auxiliary 4 #H ##CHG;Do you want any/more @ DEVICEs ?  Ac~Iz (YuDEV"   NT O DS ) SS  INI16p-  FIN1h-  SET1g-  OUT1uh-  ANS1h-  HAN1Eh-  UTI1i-  MTP] CHK1s-  D01 D02 D03 D04 D_006&F(D_006) (DEV) Device Name [1-16 Chars] # (NT) Number of terminals on this controller #D (DS) Driver Data Size [0-0FFFFH] #H (SS) Driver Stack Size [0-0FFFFH] #H (INI) Term-init Procedure Name [1-31 Chars] # (FIN) Term-finish Procedure Name [1-31 Chars] # (SET) Term-setup Procedure Name [1-31 Chars] # (OUT) Term-out Procedure Name [1-31 Chars] # (ANS) Term-answer Procedure Name [1-31 Chars] # (HAN) Term-hangup Procedure Name [1-31 Chars] # (UTI) Term-utility Procedure Name [1-31 Chars] # (MTP) Message Task Priority [0-255] #D (CHK) Term-check Procedure Name [1-31 Chars] # (D01) #H (D02) #H (D03) #H (D04) #H (D05) #H (D06) #H (D07) #H (D08) #H (D09) #H (D10) #H (D11) #H (D12) #H (D13) #H (D14) #H (D15) #H (D16) #H (D17) #H (D18) #H (D19) #H (D20) #H ##CHG;Do you want any/more @ DEVICEs ?  !/`$Up-Ie )Ea}DEV"   NT O DS ) SS  INI16p-  FIN1h-  SET1g-  OUT1uh-  ANS1h-  HAN1Eh-  UTI1i-  MTP] CHK1s-  D01 D02 D03 D04 D05 D06 D07 D08 D09 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D_007:|-(D_007) (DEV) Device Name [1-16 Chars] # (IL) Interrupt Level [Encoded Level] #H (ITP) Interrupt Task Priority [0-255] #D (SS) Interrupt Procedure Stack Size [0-0FFFFH] #H (DS) Device Local Data Size [0-0FFFFH] #H (NU) Number of Units on this Device [0-255] #D (INI) Init Procedure Name [1-31 Chars] # (FIN) Finish Procedure Name [1-31 Chars] # (STR) Start Procedure Name [1-31 Chars] # (STP) Stop Procedure Name [1-31 Chars] # (INT) Interrupt Procedure Name [1-31 Chars] # (ITO) Interrupt Time Out [0-0FFFFH] #H (D01) Auxiliary 1 #H (D02) Auxiliary 2 #H (D03) Auxiliary 3 #H (D04) Auxiliary 4 #H ##CHG;Do you want any/more @ DEVICEs ?   /KfL}DEV"   IL  ITPz SS s DS  NU  INI1n-  FIN1~f-  STR1e-  STP1Id-  INT1i-  ITO D01 D02 D03 D04 D_008B5(D_008) (DEV) Device Name [1-16 Chars] # (IL) Interrupt Level [Encoded Level] #H (ITP) Interrupt Task Priority [0-255] #D (SS) Interrupt Procedure Stack Size [0-0FFFFH] #H (DS) Device Local Data Size [0-0FFFFH] #H (NU) Number of Units on this Device [0-255] #D (INI) Init Procedure Name [1-31 Chars] # (FIN) Finish Procedure Name [1-31 Chars] # (STR) Start Procedure Name [1-31 Chars] # (STP) Stop Procedure Name [1-31 Chars] # (INT) Interrupt Procedure Name [1-31 Chars] # (ITO) Interrupt Time Out [0-0FFFFH] #H (D01) #H (D02) #H (D03) #H (D04) #H (D05) #H (D06) #H (D07) #H (D08) #H (D09) #H (D10) #H (D11) #H (D12) #H (D13) #H (D14) #H (D15) #H (D16) #H (D17) #H (D18) #H (D19) #H (D20) #H ##CHG;Do you want any/more @ DEVICEs ?  Uw2c.Jf*Fb~ &DEV"   IL  ITPz SS s DS  NU  INI1n-  FIN1~f-  STR1e-  STP1Id-  INT1i-  ITO D01 D02 D03 D04 D05 D06 D07 D08 D09 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D_009<U(D_009) (DEV) Device Name [1-16 Chars] # (MTP) Message Task Priority [0-255] #D (SS) Message Procedure Stack Size [0-0FFFFH] #H (DS) Device Local Data Size [0-0FFFFH] #H (NU) Number of Units on this Device [0-255] #D (INI) Init Procedure Name [1-31 Chars] # (FIN) Finish Procedure Name [1-31 Chars] # (STR) Start Procedure Name [1-31 Chars] # (STP) Stop Procedure Name [1-31 Chars] # (MSG) Message Procedure Name [1-31 Chars] # (MTO) Message Time Out [0-0FFFFH] #H (MQL) Message Queue length [0-0FFFFH] #H (BIN) Board Instance [0-0FFH] #H (BID) Board ID. [1-10 Chars] # (D01) Auxiliary 1 #H (D02) Auxiliary 2 #H (D03) Auxiliary 3 #H (D04) Auxiliary 4 #H ##CHG;Do you want any/more @ DEVICEs ?  z ;l7RnDEV"   MTPB SS + DS  NU ; INI1n-  FIN16f-  STR1e-  STP1d-  MSG1e-  MTOv MQLZ BIN]  BIDg  D01 D02 D03 D04 D_010$F<}(D_010) (DEV) Device Name [1-16 Chars] # (MTP) Message Task Priority [0-255] #D (SS) Message Procedure Stack Size [0-0FFFFH] #H (DS) Device Local Data Size [0-0FFFFH] #H (NU) Number of Units on this Device [0-255] #D (INI) Init Procedure Name [1-31 Chars] # (FIN) Finish Procedure Name [1-31 Chars] # (STR) Start Procedure Name [1-31 Chars] # (STP) Stop Procedure Name [1-31 Chars] # (MSG) Message Procedure Name [1-31 Chars] # (MTO) Message Time Out [0-0FFFFH] #H (MQL) Message Queue length [0-0FFFFH] #H (BIN) Board Instance [0-0FFH] #H (BID) Board ID. [1-10 Chars] # (D01) #H (D02) #H (D03) #H (D04) #H (D05) #H (D06) #H (D07) #H (D08) #H (D09) #H (D10) #H (D11) #H (D12) #H (D13) #H (D14) #H (D15) #H (D16) #H (D17) #H (D18) #H (D19) #H (D20) #H ##CHG;Do you want any/more @ DEVICEs ?  "7RGc &B^z">ZvDEV"   MTPB SS + DS  NU ; INI1n-  FIN16f-  STR1e-  STP1d-  MSG1e-  MTOv MQLZ BIN]  BIDg  D01 D02 D03 D04 D05 D06 D07 D08 D09 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D_0116OK(D_011) (DEV) Device Name [1-16 Chars] # (IL) Interrupt Level [Encoded Level] #H (ITP) Interrupt Task Priority [0-255] #D (SS) Interrupt Procedure Stack Size [0-0FFFFH] #H (DS) Device Local Data Size [0-0FFFFH] #H (NU) Number of Units on this Device [0-255] #D (INI) Init Procedure Name [1-31 Chars] # (FIN) Finish Procedure Name [1-31 Chars] # (STR) Start Procedure Name [1-31 Chars] # (STP) Stop Procedure Name [1-31 Chars] # (INT) Interrupt Procedure Name [1-31 Chars] # (ITO) Interrupt Time Out [0-0FFFFH] #H (MQE) Maximum Queue Elements [0-0FFFFH] #H (QA) Queue Address # H (IOA) I/O Port Address [0-0FFFFH] #H (D01) Auxiliary 1 #H (D02) Auxiliary 2 #H (D03) Auxiliary 3 #H (D04) Auxiliary 4 #H ##CHG;Do you want any/more @ DEVICEs ?   (D_#TpDEV"   IL  ITP SS  DS   NU  INI1&n-  FIN1f-  STR1e-  STP1_d-  INT1i-  ITO, MQE QA  IOA n D01 D02 D03 D04 D_012> sYs(D_012) (DEV) Device Name [1-16 Chars] # (IL) Interrupt Level [Encoded Level] #H (ITP) Interrupt Task Priority [0-255] #D (SS) Interrupt Procedure Stack Size [0-0FFFFH] #H (DS) Device Local Data Size [0-0FFFFH] #H (NU) Number of Units on this Device [0-255] #D (INI) Init Procedure Name [1-31 Chars] # (FIN) Finish Procedure Name [1-31 Chars] # (STR) Start Procedure Name [1-31 Chars] # (STP) Stop Procedure Name [1-31 Chars] # (INT) Interrupt Procedure Name [1-31 Chars] # (ITO) Interrupt Time Out [0-0FFFFH] #H (MQE) Maximum Queue Elements [0-0FFFFH] #H (QA) Queue Address # H (IOA) I/O Port Address [0-0FFFFH] #H (D01) #H (D02) #H (D03) #H (D04) #H (D05) #H (D06) #H (D07) #H (D08) #H (D09) #H (D10) #H (D11) #H (D12) #H (D13) #H (D14) #H (D15) #H (D16) #H (D17) #H (D18) #H (D19) #H (D20) #H ##CHG;Do you want any/more @ DEVICEs ?  #9Tp :k*Fb~ &B^z " DEV"   IL  ITP SS  DS   NU  INI1&n-  FIN1f-  STR1e-  STP1_d-  INT1i-  ITO, MQE QA | IOA{ n D01 D02 D03 D04 D05 D06 D07 D08 D09 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 D_013*\c&(D_013) (DEV) Device Name [1-16 Chars] # (IL) Interrupt Level [Encoded Level] #H (ITP) Interrupt Task Priority [0-255] #D (D01) Auxiliary 1 #H (D02) Auxiliary 2 #H (D03) Auxiliary 3 #H (D04) Auxiliary 4 #H (D05) Auxiliary 5 #H (D06) Auxiliary 6 #H (D07) Auxiliary 7 #H (D08) Auxiliary 8 #H (D09) Auxiliary 9 #H (D10) Auxiliary 10 #H (D11) Auxiliary 11 #H (D12) Auxiliary 12 #H (D13) Auxiliary 13 #H (D14) Auxiliary 14 #H ##CHG;Do you want any/more @ DEVICEs ?  Ik.JfDEV"   IL  ITPt D01 D02 D03 D04 D05 D06 D07 D08 D09 D10 D11 D12 D13 D14 D_014f4(D_014) (DEV) Device Name [1-16 Chars] # (IL) Interrupt Level [Encoded Level] #H (ITP) Interrupt Task Priority [0-255] #D (D01) #H (D02) #H (D03) #H (D04) #H (D05) #H (D06) #H (D07) #H (D08) #H (D09) #H (D10) #H (D11) #H (D12) #H (D13) #H (D14) #H (D15) #H (D16) #H (D17) #H (D18) #H (D19) #H (D20) #H ##CHG;Do you want any/more @ DEVICEs ?  c,Hd (D`|DEV"   IL  ITPt D01 D02 D03 D04 D05 D06 D07 D08 D09 D10 D11 D12 D13 D14 D15 D16 D17 D18 D19 D20 U_00136j%(U_001) (DEV) Device Name [1-16 Chars] # (NAM) Unit Info Name [1-16 Chars] # (CNF) Connection flags [Encoded] #H (TRF) Terminal flags [Encoded] #H (IBR) Input BAUD Rate [0-0FFFFFFFFH] # H (OBR) Output BAUD Rate [0-0FFFFFFFFH] # H (SN) Scroll Number [0-0FFFFH] #H (U01) Auxiliary 1 #H (U02) Auxiliary 2 #H (U03) Auxiliary 3 #H (U04) Auxiliary 4 #H (U05) Auxiliary 5 #H (U06) Auxiliary 6 #H (U07) Auxiliary 7 #H (U08) Auxiliary 8 #H (U09) Auxiliary 9 #H (U10) Auxiliary 10 #H ##CHG9Do you want any/more @ UNITs ?  Hj7SoDEV"   NAM"  CNFj TRF IBR OBR SN K U01 U02 U03 U04 U05 U06 U07 U08 U09 U10 U_002Ar(U_002) (DEV) Device Name [1-16 Chars] # (NAM) Unit Info Name [1-16 Chars] # (CNF) Connection flags [Encoded] #H (TRF) Terminal flags [Encoded] #H (IBR) Input BAUD Rate [0-0FFFFFFFFH] # H (OBR) Output BAUD Rate [0-0FFFFFFFFH] # H (SN) Scroll Number [0-0FFFFH] #H (U01) #H (U02) #H (U03) #H (U04) #H (U05) #H (U06) #H (U07) #H (U08) #H (U09) #H (U10) #H (U11) #H (U12) #H (U13) #H (U14) #H (U15) #H (U16) #H (U17) #H (U18) #H (U19) #H (U20) #H ##CHG9Do you want any/more @ UNITs ?  >`-Ie )Ea} %DEV"   NAM"  CNFj TRF IBR OBR SN K U01 U02 U03 U04 U05 U06 U07 U08 U09 U10 U11 U12 U13 U14 U15 U16 U17 U18 U19 U20 U_003yz(U_003) (DEV) Device Name [1-16 Chars] # (NAM) Unit Info Name [1-16 Chars] # (TS) Track Size [0-0FFFFH] #H (MR) Maximum Retries [0-0FFFFH] #H (CS) Cylinder Size [0-0FFFFH] #H (U01) Auxiliary 1 #H (U02) Auxiliary 2 #H (U03) Auxiliary 3 #H (U04) Auxiliary 4 #H (U05) Auxiliary 5 #H (U06) Auxiliary 6 #H (U07) Auxiliary 7 #H (U08) Auxiliary 8 #H (U09) Auxiliary 9 #H (U10) Auxiliary 10 #H ##CHG9Do you want any/more @ UNITs ?  8Tp4PlDEV"   NAM"  TS o0 MR  CS is U01 U02 U03 U04 U05 U06 U07 U08 U09 U10 U_004Ё\(U_004) (DEV) Device Name [1-16 Chars] # (NAM) Unit Info Name [1-16 Chars] # (TS) Track Size [0-0FFFFH] #H (MR) Maximum Retries [0-0FFFFH] #H (CS) Cylinder Size [0-0FFFFH] #H (U01) #H (U02) #H (U03) #H (U04) #H (U05) #H (U06) #H (U07) #H (U08) #H (U09) #H (U10) #H (U11) #H (U12) #H (U13) #H (U14) #H (U15) #H (U16) #H (U17) #H (U18) #H (U19) #H (U20) #H ##CHG9Do you want any/more @ UNITs ?  .Jf*Fb~ &B^zDEV"   NAM"  TS o0 MR  CS is U01 U02 U03 U04 U05 U06 U07 U08 U09 U10 U11 U12 U13 U14 U15 U16 U17 U18 U19 U20 U_005(U_005) (DEV) Device Name [1-16 Chars] # (NAM) Unit Info Name [1-16 Chars] # (U01) Auxiliary 1 #H (U02) Auxiliary 2 #H (U03) Auxiliary 3 #H (U04) Auxiliary 4 #H (U05) Auxiliary 5 #H (U06) Auxiliary 6 #H (U07) Auxiliary 7 #H (U08) Auxiliary 8 #H (U09) Auxiliary 9 #H (U10) Auxiliary 10 #H ##CHG9Do you want any/more @ UNITs ?  3Uw;WsDEV"   NAM"  U01 U02 U03 U04 U05 U06 U07 U08 U09 U10 U_006(U_006) (DEV) Device Name [1-16 Chars] # (NAM) Unit Info Name [1-16 Chars] # (U01) #H (U02) #H (U03) #H (U04) #H (U05) #H (U06) #H (U07) #H (U08) #H (U09) #H (U10) #H (U11) #H (U12) #H (U13) #H (U14) #H (U15) #H (U16) #H (U17) #H (U18) #H (U19) #H (U20) #H ##CHG9Do you want any/more @ UNITs ?  )Km1Mi-IeDEV"   NAM"  U01 U02 U03 U04 U05 U06 U07 U08 U09 U10 U11 U12 U13 U14 U15 U16 U17 U18 U19 U20 I_001Jg(I_001) (DEV) Device Name [1-16 Chars] # (NAM) Device-Unit Name [1-13 Chars] # (UN) Unit Number on this Device [0-0FFH] #H (UIN) Unit Info Name [1-16 Chars] # (MB) Max Buffers [0-0FFH] #H ##CHG9Do you want any/more @ DUIBs ?   /DEV"   NAM  UN r UIN"!q  MB z I_002nK(I_002) (DEV) Device Name [1-16 Chars] # (NAM) Device-Unit Name [1-14 Chars] # (PFD) Physical File Driver Required [Yes/No] # (NFD) Named File Driver Required [Yes/No] # (SDD) Single or Double Density Disks [Single/Double] # (SDS) Single or Double Sided Disks [Single/Double] # (EFI) 8 or 5 Inch Disks [8/5] # (SUF) Standard or Uniform Format [Standard/Uniform] # (GRA) Granularity [0-0FFFFH] #H (DSZ) Device Size [0-0FFFFFFFFH] # H (UN) Unit Number on this Device [0-0FFH] #H (UIN) Unit Info Name [1-16 Chars] # (RUT) Request Update Timeout [0-0FFFFH] #H (NB) Number of Buffers [nonrandom = 0/rand = 1-0FFFFH] #H (CUP) Common Update [Yes/No] # (MB) Max Buffers [0-0FFH] #H ##CHG9Do you want any/more @ DUIBs ?  4Ul$@SDEV"   NAM   PFD NFDr SDD!-DSINGLEDOUBLE SDS!lSSINGLEDOUBLE EFI.i858 SUF%b!SSTANDARDUNIFORM  GRA DSZ  UN i  UIN" q  RUTh  NB   CUP  MB z I_003T(I_003) (DEV) Device Name [1-16 Chars] # (NAM) Device-Unit Name [1-13 Chars] # (FD) File Drivers [0-0FFFFH Encoded] #H (FNC) Functions [0-0FFH Encoded] #H (FLG) Flags [0-0FFH Encoded] #H (GRA) Granularity [0-0FFFFH] #H (DSZ) Device Size [0-0FFFFFFFFH] # H (UN) Unit Number on this Device [0-0FFH] #H (INI) Initialize-I/O Proc Name [1-31 Chars] # (FIN) Finish-I/O Procedure Name [1-31 Chars] # (QUE) Queue-I/O Procedure Name [1-31 Chars] # (CAN) Cancel-I/O Procedure Name [1-31 Chars] # (UIN) Unit Info Name [1-16 Chars] # (RUT) Request Update Timeout [0-0FFFFH] #H (NB) Number of Buffers [1-0FFFFH] #H (STP) Service Task Priority [0-255] #D (CUP) Common Update [Yes/No] # (MB) Max Buffers [0-0FFH] #H ##CHG9Do you want any/more @ DUIBs ?  y (Fa%GcDEV"   NAM  FD ' FNC FLGuO GRA DSZ` UN :  INI1 i-  FIN10 b-  QUE1 a-  CAN1 b-  UIN"U q  RUT  NB g  STP W CUPw  MB `z ICUHLP44444444Three screens define the interface between this single interrupt terminal controller and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the number of terminals on this terminal controller. This parameter specifies the number of bytes in the driver's data area pointed to by the USER$DATA$PTR field of the TSC data structure. This parameter specifies the number of bytes of stack needed collectively by the user supplied procedures in this device driver. This parameter specifies the public name of this controller's user-written terminal initialization procedure. This parameter specifies the public name of this controller's user-written terminal finish procedure. This parameter specifies the public name of this controller's user-written terminal setup procedure. This parameter specifies the public name of this controller's user-written terminal output procedure. This parameter specifies the public name of this controller's user-written terminal answer procedure. This parameter specifies the public name of this controller's user-written terminal hangup procedure. This parameter specifies the public name of this controller's user-written terminal utility procedure. This parameter specifies the encoded interrupt level used by this controller. The interrupt task uses this value to associate itself with the correct interrupt level. This parameter specifies the public name of this controller's user-written terminal check procedure for the interrupt level. Three screens define the interface between this single interrupt terminal controller and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the number of terminals on this terminal controller. This parameter specifies the number of bytes in the driver's data area pointed to by the USER$DATA$PTR field of the TSC data structure. This parameter specifies the number of bytes of stack needed collectively by the user supplied procedures in this device driver. This parameter specifies the public name of this controller's user-written terminal initialization procedure. This parameter specifies the public name of this controller's user-written terminal finish procedure. This parameter specifies the public name of this controller's user-written terminal setup procedure. This parameter specifies the public name of this controller's user-written terminal output procedure. This parameter specifies the public name of this controller's user-written terminal answer procedure. This parameter specifies the public name of this controller's user-written terminal hangup procedure. This parameter specifies the public name of this controller's user-written terminal utility procedure. This parameter specifies the encoded interrupt level used by this controller. The interrupt task uses this value to associate itself with the correct interrupt level. This parameter specifies the public name of this controller's user-written terminal check procedure for the interrupt level. Three screens define the interface between this double interrupt terminal controller and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the number of terminals on this terminal controller. This parameter specifies the number of bytes in the driver's data area pointed to by the USER$DATA$PTR field of the TSC data structure. This parameter specifies the number of bytes of stack needed collectively by the user supplied procedures in this device driver. This parameter specifies the public name of this controller's user-written terminal initialization procedure. This parameter specifies the public name of this controller's user-written terminal finish procedure. This parameter specifies the public name of this controller's user-written terminal setup procedure. This parameter specifies the public name of this controller's user-written terminal output procedure. This parameter specifies the public name of this controller's user-written terminal answer procedure. This parameter specifies the public name of this controller's user-written terminal hangup procedure. This parameter specifies the public name of this controller's user-written terminal utility procedure. This parameter specifies the first encoded interrupt level used by this controller. The interrupt task uses this value to associate itself with the correct interrupt level. This parameter specifies the public name of this controller's user-written terminal check procedure for the first interrupt level. This parameter specifies the second encoded interrupt level used by this controller. The interrupt task uses this value to associate itself with the correct interrupt level. This parameter specifies the address of this controller's user-written terminal check procedure for the second interrupt level. Three screens define the interface between this double interrupt terminal controller and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the number of terminals on this terminal controller. This parameter specifies the number of bytes in the driver's data area pointed to by the USER$DATA$PTR field of the TSC data structure. This parameter specifies the number of bytes of stack needed collectively by the user supplied procedures in this device driver. This parameter specifies the public name of this controller's user-written terminal initialization procedure. This parameter specifies the public name of this controller's user-written terminal finish procedure. This parameter specifies the public name of this controller's user-written terminal setup procedure. This parameter specifies the public name of this controller's user-written terminal output procedure. This parameter specifies the public name of this controller's user-written terminal answer procedure. This parameter specifies the public name of this controller's user-written terminal hangup procedure. This parameter specifies the public name of this controller's user-written terminal utility procedure. This parameter specifies the first encoded interrupt level used by this controller. The interrupt task uses this value to associate itself with the correct interrupt level. This parameter specifies the public name of this controller's user-written terminal check procedure for the first interrupt level. This parameter specifies the second encoded interrupt level used by this controller. The interrupt task uses this value to associate itself with the correct interrupt level. This parameter specifies the public name of this controller's user-written terminal check procedure for the second interrupt level. Three screens define the interface between this Multibus II terminal controller and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the number of terminals on this terminal controller. This parameter specifies the number of bytes in the driver's data area pointed to by the USER$DATA$PTR field of the TSC data structure. This parameter specifies the number of bytes of stack needed collectively by the user supplied procedures in this device driver. This parameter specifies the public name of this controller's user-written terminal initialization procedure. This parameter specifies the public name of this controller's user-written terminal finish procedure. This parameter specifies the public name of this controller's user-written terminal setup procedure. This parameter specifies the public name of this controller's user-written terminal output procedure. This parameter specifies the public name of this controller's user-written terminal answer procedure. This parameter specifies the public name of this controller's user-written terminal hangup procedure. This parameter specifies the public name of this controller's user-written terminal utility procedure. This parameter specifies the priority of the TSC task which receives Multibus II messages. This parameter specifies the public name of this controller's user-written terminal check procedure for the interrupt level. Three screens define the interface between this Multibus II terminal controller and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the number of terminals on this terminal controller. This parameter specifies the number of bytes in the driver's data area pointed to by the USER$DATA$PTR field of the TSC data structure. This parameter specifies the number of bytes of stack needed collectively by the user supplied procedures in this device driver. This parameter specifies the public name of this controller's user-written terminal initialization procedure. This parameter specifies the public name of this controller's user-written terminal finish procedure. This parameter specifies the public name of this controller's user-written terminal setup procedure. This parameter specifies the public name of this controller's user-written terminal output procedure. This parameter specifies the public name of this controller's user-written terminal answer procedure. This parameter specifies the public name of this controller's user-written terminal hangup procedure. This parameter specifies the public name of this controller's user-written terminal utility procedure. This parameter specifies the priority of the TSC task which receives Multibus II messages. This parameter specifies the public name of this controller's user-written terminal check procedure for the interrupt level. Three screens define the interface between this random access driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the encoded interrupt level used by this controller. The interrupt task uses this value to associate itself with the correct interrupt level. This parameter specifies the initial priority of the device's interrupt task. The actual priority of the iRMX 286 interrupt task changes because the Nucleus adjusts an interrupt task's priority according to the interrupt level that it services. This parameter specifies the number of bytes of stack needed collectively by the user supplied procedures in this device driver. This parameter specifies the number of bytes in the driver's data area pointed to by the USER$DATA$PTR field of the driver data structure. This parameter specifies the number of units supported by the driver. Units are assumed to be numbered consecutively, starting with zero. This parameter specifies the public name of this controller's user-written device initialization procedure. This parameter specifies the public name of this controller's user-written device finish procedure. This parameter specifies the public name of this controller's user-written device start procedure. This parameter specifies the public name of this controller's user-written device stop procedure. This parameter specifies the public name of this controller's user-written device interrupt procedure. This parameter specifies how long (in milliseconds) the system should wait for an interrupt from the line printer before resuming control. Three screens define the interface between this random access driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the encoded interrupt level used by this controller. The interrupt task uses this value to associate itself with the correct interrupt level. This parameter specifies the initial priority of the device's interrupt task. The actual priority of the iRMX 286 interrupt task changes because the Nucleus adjusts an interrupt task's priority according to the interrupt level that it services. This parameter specifies the number of bytes of stack needed collectively by the user supplied procedures in this device driver. This parameter specifies the number of bytes in the driver's data area pointed to by the USER$DATA$PTR field of the driver data structure. This parameter specifies the number of units supported by the driver. Units are assumed to be numbered consecutively, starting with zero. This parameter specifies the public name of this controller's user-written device initialization procedure. This parameter specifies the public name of this controller's user-written device finish procedure. This parameter specifies the public name of this controller's user-written device start procedure. This parameter specifies the public name of this controller's user-written device stop procedure. This parameter specifies the public name of this controller's user-written device interrupt procedure. This parameter specifies how long (in milliseconds) the system should wait for an interrupt from the line printer before resuming control. Three screens define the interface between this MBII full message passing random access driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the fixed priority of the message task. This parameter specifies the number of bytes of stack needed collectively by the user supplied procedures in this device driver. This parameter specifies the number of bytes in the driver's data area pointed to by the USER$DATA$PTR field of the driver data structure. This parameter specifies the number of units supported by the driver. Units are assumed to be numbered consecutively, starting with zero. This parameter specifies the public name of this controller's user-written device initialization procedure. This parameter specifies the public name of this controller's user-written device finish procedure. This parameter specifies the public name of this controller's user-written device start procedure. This parameter specifies the public name of this controller's user-written device stop procedure. This parameter specifies the public name of this controller's user-written device driver procedure which processes messages. This parameter specifies how long (in milliseconds) the message task should wait for a message from the controller. This parameter specifies the maximum number of controller messages that the Comm System will queue at the port for the message task. An increment of one in queue length will increase the incremental memory requirements for the port object by five bytes. This parameter specifies the instance of the specified board ID. Boards with the same name are assumed to have instance IDs allocated in contiguous ascending order starting from a value of one for the instance of the board with the lowest slot id. amoung them. This parameter specifies the 10 character board name present in the MBII interconnect header record. NOTE: To avoid automatic conversion to upper case, enclose the board ID. in quotes. The quotes will not be included in the character count. Three screens define the interface between this MBII full message passing random access driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the fixed priority of the message task. This parameter specifies the number of bytes of stack needed collectively by the user supplied procedures in this device driver. This parameter specifies the number of bytes in the driver's data area pointed to by the USER$DATA$PTR field of the driver data structure. This parameter specifies the number of units supported by the driver. Units are assumed to be numbered consecutively, starting with zero. This parameter specifies the public name of this controller's user-written device initialization procedure. This parameter specifies the public name of this controller's user-written device finish procedure. This parameter specifies the public name of this controller's user-written device start procedure. This parameter specifies the public name of this controller's user-written device stop procedure. This parameter specifies the public name of this controller's user-written device driver procedure which processes messages. This parameter specifies how long (in milliseconds) the message task should wait for a message from the controller. This parameter specifies the maximum number of controller messages that the Comm System will queue at the port for the message task. An increment of one in queue length will increase the incremental memory requirements for the port object by five bytes. This parameter specifies the instance of the specified board ID. Boards with the same name are assumed to have instance IDs allocated in contiguous ascending order starting from a value of one for the instance of the board with the lowest slot id. amoung them. This parameter specifies the 10 character board name present in the MBII interconnect header record. NOTE: To avoid automatic conversion to upper case, enclose the board ID. in quotes. The quotes will not be included in the character count. Three screens define the interface between this MBII interrupt driven random access driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the encoded interrupt level used by this controller. The interrupt task uses this value to associate itself with the correct interrupt level. This parameter specifies the initial priority of the device's interrupt task. The actual priority of the iRMX 286 interrupt task changes because the Nucleus adjusts an interrupt task's priority according to the interrupt level that it services. This parameter specifies the number of bytes of stack needed collectively by the user supplied procedures in this device driver. This parameter specifies the number of bytes in the driver's data area pointed to by the USER$DATA$PTR field of the driver data structure. This parameter specifies the number of units supported by the driver. Units are assumed to be numbered consecutively, starting with zero. This parameter specifies the public name of this controller's user-written device initialization procedure. This parameter specifies the public name of this controller's user-written device finish procedure. This parameter specifies the public name of this controller's user-written device start procedure. This parameter specifies the public name of this controller's user-written device stop procedure. This parameter specifies the public name of this controller's user-written device interrupt procedure. This parameter specifies how long (in milliseconds) the system should wait for an interrupt from the device before resuming control. This parameter specifies the maximum number of queue elements in the PCB/PSB queue in shared-memory. It should be one more than the maximum number of PCBs or PSBs that can be outstanding in the queue. This parameter specifies the absolute address of the shared-memory queue in dual-port memory. It must begin at an even address. The number of bytes of memory needed for the queue is calculated as follows: (Max_queue_elements * 32) * 2) + 6 This parameter specifies the I/O port address of the flag byte used by the driver to signal the controller. Three screens define the interface between this MBII interrupt driven random access driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the encoded interrupt level used by this controller. The interrupt task uses this value to associate itself with the correct interrupt level. This parameter specifies the initial priority of the device's interrupt task. The actual priority of the iRMX 286 interrupt task changes because the Nucleus adjusts an interrupt task's priority according to the interrupt level that it services. This parameter specifies the number of bytes of stack needed collectively by the user supplied procedures in this device driver. This parameter specifies the number of bytes in the driver's data area pointed to by the USER$DATA$PTR field of the driver data structure. This parameter specifies the number of units supported by the driver. Units are assumed to be numbered consecutively, starting with zero. This parameter specifies the public name of this controller's user-written device initialization procedure. This parameter specifies the public name of this controller's user-written device finish procedure. This parameter specifies the public name of this controller's user-written device start procedure. This parameter specifies the public name of this controller's user-written device stop procedure. This parameter specifies the public name of this controller's user-written device interrupt procedure. This parameter specifies how long (in milliseconds) the system should wait for an interrupt from device before resuming control. This parameter specifies the maximum number of queue elements in the PCB/PSB queue in shared-memory. It should be one more than the maximum number of PCBs or PSBs that can be outstanding in the queue. This parameter specifies the absolute address of the shared-memory queue in dual-port memory. It must begin at an even address. The number of bytes of memory needed for the queue is calculated as follows: (Max_queue_elements * 32) * 2) + 6 This parameter specifies the I/O port address of the flag byte used by the driver to signal the controller. Three screens define the interface between this general device and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the encoded interrupt level used by this controller. The interrupt task uses this value to associate itself with the correct interrupt level. This parameter specifies the initial priority of the device's interrupt task. The actual priority of the iRMX 286 interrupt task changes because the Nucleus adjusts an interrupt task's priority according to the interrupt level that it services. Three screens define the interface between this general device and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies the encoded interrupt level used by this controller. The interrupt task uses this value to associate itself with the correct interrupt level. This parameter specifies the initial priority of the device's interrupt task. The actual priority of the iRMX 286 interrupt task changes because the Nucleus adjusts an interrupt task's priority according to the interrupt level that it services. Three screens define the interface between this terminal driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies a unique name for this unit information table. A DUIB uses the "Unit Info Name" to point to this particular unit information table. This parameter specifies the default connection flags for the terminal. The flags are encoded as follows: bits meaning 0-1 Line editing control 2 Echo control 3 Input parity control 4 Output parity control 5 Output control character recognition control 6-7 OSC control sequence control 8 Reserved This parameter specifies the default terminal flags. The flags are encoded as follows: bits meaning 0 Reserved - must be set to 1 1 Line protocol indicator 2 Terminal type indicator 3 Modem indicator 4-5 Read parity control 6-8 Write parity control 9 OSC control 10 Terminal axes sequence control 11 Horizontal axes control 12 Vertical axes control 13-15 Reserved This parameter specifies the initial input baud rate of this terminal. Specify a value of one if you want the controller to ascertain the initial baud rate automatically. This parameter specifies the initial output baud rate of this terminal. Specify a value of one if you want the controller to ascertain the initial baud rate automatically. This parameter specifies the number of lines to scroll when an operator enters the scrolling output control character. (Control-W is the default) Three screens define the interface between this terminal driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies a unique name for this unit information table. A DUIB uses the "Unit Info Name" to point to this particular unit information table. This parameter specifies the default connection flags for the terminal. The flags are encoded as follows: bits meaning 0-1 Line editing control 2 Echo control 3 Input parity control 4 Output parity control 5 Output control character recognition control 6-7 OSC control sequence control 8 Reserved This parameter specifies the default terminal flags. The flags are encoded as follows: bits meaning 0 Reserved - must be set to 1 1 Line protocol indicator 2 Terminal type indicator 3 Modem indicator 4-5 Read parity control 6-8 Write parity control 9 OSC control 10 Terminal axes sequence control 11 Horizontal axes control 12 Vertical axes control 13-15 Reserved This parameter specifies the initial input baud rate of this terminal. Specify a value of one if you want the controller to ascertain the initial baud rate automatically. This parameter specifies the initial output baud rate of this terminal. Specify a value of one if you want the controller to ascertain the initial baud rate automatically. This parameter specifies the number of lines to scroll when an operator enters the scrolling output control character. (Control-W is the default) Three screens define the interface between this random access driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies a unique name for this unit information table. A DUIB uses the "Unit Info Name" to point to this particular unit information table. This parameter specifies the size in bytes of a single track of a volume on the unit. If the device controller supports reading and writing across track boundaries and your driver is a random-access driver, place a zero in this field. For Message-based devices this parameter must be set to zero. For Winchester disk drives and flexible disk drives, this parameter specifies the maximum number of times the Basic I/O System should retry an operation before returning an E$IO$SOFT exception code. This parameter specifies the number of sectors per cylinder and whether the controller should perform automatic and concurrent seek operations. value meaning 0 - The I/O system never requests a seek operation. Instead it expects the device to perform implied "seeks" when read/write on the unit begins on a cylinder which is different from the one associated with the current position of the read/write head. 1 - The I/O system automatically requests a seek operation before performing a read or write. other - The number of sectors in a cylinder on the unit. The I/O system automatically performs a seek when a read/write on the unit begins on a cylinder which is different from the one associated with the current position of the read/write head. Three screens define the interface between this random access driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies a unique name for this unit information table. A DUIB uses the "Unit Info Name" to point to this particular unit information table. This parameter specifies the size in bytes of a single track of a volume on the unit. If the device controller supports reading and writing across track boundaries and your driver is a random-access driver, place a zero in this field. For Message-based devices this parameter must be set to zero. For Winchester disk drives and flexible disk drives, this parameter specifies the maximum number of times the Basic I/O System should retry an operation before returning an E$IO$SOFT exception code. This parameter specifies the number of sectors per cylinder and whether the controller should perform automatic and concurrent seek operations. value meaning 0 - The I/O system never requests a seek operation. Instead it expects the device to perform implied "seeks" when read/write on the unit begins on a cylinder which is different from the one associated with the current position of the read/write head. 1 - The I/O system automatically requests a seek operation before performing a read or write. other - The number of sectors in a cylinder on the unit. The I/O system automatically performs a seek when a read/write on the unit begins on a cylinder which is different from the one associated with the current position of the read/write head. Three screens define the interface between this general device driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies a unique name for this unit information table. A DUIB uses the "Unit Info Name" to point to this particular unit information table. Three screens define the interface between this general device driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies a unique name for this unit information table. A DUIB uses the "Unit Info Name" to point to this particular unit information table. Three screens define the interface between this terminal driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies a name that uniquely identifies this device-unit to the I/O System. If you want the Extended I/O System to logically attach this device during initialization, specify it in the Logical Names screen. This parameter specifies the unit number of the device-unit associated with this device-unit information block. This parameter specifies the "Unit Info Name" of the unit information table that fills the needs of this DUIB. This parameter specifies the maximum number of buffers that the Extended I/O System can allocate for this device's I/O. Three screens define the interface between this random access driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies a name that uniquely identifies this device-unit to the I/O System. If you want the Extended I/O System to logically attach this device during initialization, specify it in the Logical Names screen. This parameter specifies whether or not the Physical file driver is required. Two good reasons exist for not changing the "Yes" default value. First, the Human Interface ATTACHDEVICE command, the EIOS LOGICAL$ATTACH$DEVICE system call, and the BIOS A$PHYSICAL$ATTACH$DEVICE system call require you to select the file type at run time. Second, there is no code savings if you specify "Yes" to NFD parameter and "No" to PFD, or vice versa. This parameter specifies whether or not the Named file driver is required. Two good reasons exist for not changing the "Yes" default value. First, the Human Interface ATTACHDEVICE command, the EIOS LOGICAL$ATTACH$DEVICE system call, and the BIOS A$PHYSICAL$ATTACH$DEVICE system call require you to select the file type at run time. Second, there is no code savings if you specify "Yes" to NFD parameter and "No" to PFD, or vice versa. For flexible disk drives, this parameter specifies the recording density of this flexible disk. The recording density is either single or double. For flexible disk drives, this parameter specifies the number of recording surfaces on the flexible disk. This parameter specifies the form factor of the disk drive. The form factor is either 5.25 or 8 inch. For flexible disk drives this parameter specifies the format that the controller should expect on track zero. Choose the option "Standard" if you want track zero to be single density with 128-byte sectors (regardless of how the remaining tracks are formatted). Choose the option "Uniform" if you want all tracks on a disk to have the same format. This parameter specifies the minimum number of bytes that the device reads or writes in one operation. This value is called device granularity. This parameter to specifies the device storage capacity in bytes. For Winchester disk drives and flexible disk drives, use the following: DSZ = [cylinders - alts] * # of heads * sectors per track * device granularity This parameter specifies the unit number of this device-unit. The unit numbers for the device begin with zero and increase sequentially. This parameter specifies the "Unit Info Name" of the unit information table that fills the needs of this DUIB. This parameter specifies the number of clock ticks that the driver should wait (during a pause in activity) before updating the attached files on the device. This parameter specifies the number of buffers this device has for blocking and deblocking I/O requests. A value of 6 is appropriate for a unit that has a granularity of 512 bytes. Specify "Yes" for this parameter if you want the driver to update the attached files on this device at the fixed interval you specified on the "BIOS" screen. Specify "No" if you do not want to update attached files on this device at fixed intervals, but prefer to update attached files based only on the time interval you specified for the "Request Update Timeout" parameter. You should not specify "No" for this parameter and 0FFFFH for the "Request Update Timeout" parameter. This parameter specifies the maximum number of buffers that the Extended I/O System can allocate for this device's I/O. Three screens define the interface between this general device driver and the I/O system. The device information table, the unit information table and the device unit information block (DUIB). This parameter provides a means of associating the device and all the units and DUIBs which belong to it. The ICU "knows" which unit information and device-unit information screen relate to a particular device driver by the name you enter in the "DEV" parameter. This parameter specifies a name that uniquely identifies this device-unit to the I/O System. If you want the Extended I/O System to logically attach this device during initialization, specify it in the Logical Names screen. This parameter specifies which file drivers can be used to interface to this device-unit. Setting bit number "i" implies that the corresponding file driver can attach this device-unit. bit meaning 0 Physical 1 Stream 3 Named This parameter specifies which I/O functions are supported by this device-unit. Setting bit number "i" implies taht the corresponding I/O function is supported by this device-unit. bit meaning 0 Read 1 Write 2 Seek 3 Special 4 Attach 5 Detach 6 Open 7 Close This parameter specifies the various characteristics of flexible disks. bit bit values and meanings 0 0 = bits 1-7 are undefined 1 = bits 1-7 are defined as follows 1 0 = single density 1 = double density 2 0 = single sided 1 = double sided 3 0 = 8-inch diskettes 1 = 5.25-inch diskettes 4 0 = standard format diskette 1 = not a standard format diskette 5-7 Reserved; must be set to zero This parameter specifies the device granularity, in bytes. The minimum number of bytes of information that the device reads or writes on one operation. This parameter specifies the device storage capacity in bytes. For Winchester disk drives and flexible disk drives, use the following: DSZ = [cylinders - alts] * # of heads * sectors per track * device granularity This parameter specifies the unit number of the device-unit. The unit numbers for the device begin with zero and increase sequentially. This parameter specifies the public name of the initializaton I/O procedure associated with this unit. This parameter specifies the public name of the finish I/O procedure associated with this unit. This parameter specifies the public name of the queue I/O procedure associated with this unit. This parameter specifies the public name of the cancel I/O procedure associated with this unit. This parameter specifies the "Unit Info Name" of the unit information table that fills the needs of this DUIB. This parameter specifies the number of clock ticks that the driver should wait (during a pause in activity) before updating the attached files on the device. This parameter specifies the number of buffers this device has for blocking and deblocking I/O requests. A value of 6 is appropriate for a unit that has a granularity of 512 bytes. This parameter specifies the priority of the I/O system service task for the device. Specify "Yes" for this parameter if you want the driver to update the attached files on this device at the fixed interval you specified on the "BIOS" screen. Specify "No" if you do not want to update attached files on this device at fixed intervals, but prefer to update attached files based only on the time interval you specified for the "Request Update Timeout" parameter. You should not specify "No" for this parameter and 0FFFFH for the "Request Update Timeout" parameter. This parameter specifies the maximum number of buffers that the Extended I/O System can allocate for this device's I/O.