'!j  p  r5*3+/# Q*+FS3!#$r%G&j'c)`*+-d.O//tD0.12o384,d5G6%7>c8.9Ft:;j<=T?1@AKB> DEjFphHpIjBKpLGMJCOGPJQRUZW)X3Y[,]:`bbcdef&ic)k*SmXo<q rtuCw x zz{}{~"g  W7GGO?$?cFFG6G}GćDGORG9! ,16=I?ʼn ω## +D OD&Gmsd<nPhh *̝Y%v2͡502h*ĦG qghS\ ũTHIS COMMAND ALLOWS THE OPERATOR TO REPLACE THE COMMAND CHARACTER WITH ANOTHER CHARACTER. IF THE COMMAND CHARACTER IS NOT REPLACED, ICU80 USES THE ESCAPE CHARACTER AS THE COMMAND CHARACTER. THIS COMMAND IS USED TO ENTER THE CHANGE MODE. CHANGE IS USED TO CREATE A NEW DESCRIPTION FILE OR TO EDIT AN EXISTING DESCRIPTION FILE. IT IS POSSIBLE TO APPEND THE NAME OF A PARAMETER IN THE DESCRIPTION FILE TO THE CHANGE COMMAND. IF THIS IS DONE EDITING WILL BEGIN AT THE PARAMETER SPECIFIED. IF A MATCH IS NOT FOUND OR IF NO PARAMETER IS SPECIFIED EDITING WILL BEGIN WITH THE FIRST ENTRY IN THE DESCRIPTION FILE. FOR A COMPLETE DESCRIPTION OF THE PARAMETER SPECIFICATIONS USED WITH THE CHANGE COMMAND PLEASE REFER TO THE ICU80 USERS GUIDE. THIS COMMAND CAUSES ICU80 TO ENTER THE GENERATE MODE. GENERATE IS USED AFTER A DESCRIPTION FILE HAS BEEN CREATED. IT WILL PRODUCE THE CONFIGURATION OBJECT, CAM OBJECT AND THE SUBMIT FILE CONTAINING THE LINK AND LOCATE COMMANDS REQUIRED FOR BUILDING THE iRMX 80 SYSTEM. THIS COMMAND PRODUCES A LISTING OF THE DESCRIPTION FILE. THE LISTING PRODUCED IS FORMATTED WITH EACH LINE CONTAINING THE PARAMETER NAME FOLLOWED BY THE CURRENT VALUE. THE LISTING MAY BE DIRECTED TO ANY LEGAL ISIS DEVICE/FILE BY APPENDING THE DEVICE/FILENAME TO THE LIST COMMAND. (e.g. LIST :LP:) IF NO DEVICE IS SPECIFIED THE LISTING WILL DEFAULT TO :CO:. THIS COMMAND IS USED TO EXIT ICU80 WITHOUT SAVING THE NEWLY-CREATED DESCRIPTION FILE. THE INPUT DESCRIPTION FILE IS NOT MODIFIED. THIS COMMAND IS USED TO EXIT ICU80. THE NEWLY-CREATED DESCRIPTION FILE WILL BE SAVED IN THE OUTPUT FILE SPECIFIED UPON INITIATION. KEY MEANING ? Request explanation. (CC) ? Request explanation. CARRIAGE RETURN End of input. (CC) B Backup to previous line. (CC) C Return to command mode. (CC) I Insert preceding present prompt. (CC) D Delete current list element. (CC) R Insert comment preceding present prompt. (CC) F parm Search for the listed parameter and display it. Where (CC) is the control character. THE CONFIG FILE NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II COMPATIBLE DEVICE/FILE NAME IS ACCEPTABLE. THIS IS THE NAME OF THE RELOCATABLE OBJECT FILE REPRESENTING THE CONFIGURATION MODULE. IT IS CREATED BY ICU80. THE SUBMIT FILE NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II COMPATIBLE DEVICE/FILE NAME IS ACCEPTABLE. THIS IS THE NAME OF THE SUBMIT FILE THAT CAN BE EXECUTED TO BUILD THE APPLICATION SYSTEM DEFINED BY THE DESCRIPTION FILE. THIS FILE IS CREATED BY ICU80. THE CAM FILE NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II COMPATIBLE DEVICE/FILE NAME IS ACCEPTABLE. THIS IS THE NAME OF THE RELOCATABLE OBJECT FILE REPRESENTING THE CAM MODULE. IT IS CREATED BY ICU80. THE LINKOBJ FILE NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II COMPATIBLE DEVICE/FILE NAME IS ACCEPTABLE. THIS IS THE NAME OF THE FILE TO WHICH THE iRMX 80 APPLICATION SYSTEM'S LINKED OBJECT CODE WILL BE DIRECTED WHEN THE SUBMIT FILE IS EXECUTED. IT IS ONLY USED IN THE SUBMIT FILE. THE LINKMAP FILE NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II COMPATIBLE DEVICE/FILE NAME IS ACCEPTABLE. THIS IS THE NAME OF THE FILE TO WHICH THE LINK MAP FOR THE APPLICATION SYSTEM WILL BE DIRECTED WHEN THE SUBMIT FILE IS EXECUTED. IT IS ONLY USED IN THE SUBMIT FILE. THE LOCOBJ FILE NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II COMPATIBLE DEVICE/FILE NAME IS ACCEPTABLE. THIS IS THE NAME OF THE FILE TO WHICH THE LOCATED OBJECT CODE FOR THE APPLICATION SYSTEM WILL BE DIRECTED WHEN THE SUBMIT FILE IS EXECUTED. IT IS ONLY USED IN THE SUBMIT FILE. THE LOCMAP FILE NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II COMPATIBLE DEVICE/FILE NAME IS ACCEPTABLE. THIS IS THE NAME OF THE FILE TO WHICH THE LOCATE MAP FOR THE APPLICATION SYSTEM WILL BE DIRECTED WHEN THE SUBMIT FILE IS EXECUTED. IT IS ONLY USED IN THE SUBMIT FILE. THE CAMOBJ FILE NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II COMPATIBLE DEVICE/FILE NAME IS ACCEPTABLE. THIS IS THE NAME OF THE FILE TO WHICH THE LOCATED OBJECT CODE FOR THE CAM MODULE WILL BE DIRECTED WHEN THE SUBMIT FILE IS EXECUTED. IT IS ONLY USED IN THE SUBMIT FILE. NOTE -- THIS FILE IS ONLY INCLUDED IF IT IS REQUESTED THAT THE CAM BE LOCATED SEPARATELY FROM THE REST OF THE APPLICATION SYSTEM. THE CAMMAP FILE NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II COMPATIBLE DEVICE/FILE NAME IS ACCEPTABLE. THIS IS THE NAME OF THE FILE TO WHICH THE LOCATE MAP FOR THE CAM MODULE WILL BE DIRECTED WHEN THE SUBMIT FILE IS EXECUTED. IT IS ONLY USED IN THE SUBMIT FILE. THE LOADABLE FILE NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II COMPATIBLE FILE NAME IS ACCEPTABLE; HOWEVER, NO DEVICE NAME CAN BE SPECIFIED. THIS IS THE NAME OF THE FILE THAT WILL BE LOADED BY THE BOOT LOADER SYSTEM. THE BOOT LOADER SYSTEM FILE NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II COMPATIBLE DEVICE/FILE NAME IS ACCEPTABLE. THE PUBLICS OF THIS FILE WILL BE LINKED WITH LOADABLE SYSTEM WHEN THE SUBMIT FILE USED TO CREATE THE LOADABLE SYSTEM IS EXECUTED. THE LOW RAM ADDRESS PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THIS IS THE LOWEST (SMALLEST) ADDRESS OF A CONTIGUOUS WORK SPACE AREA PROVIDED FOR THE BASIC INTERPRETER. THE HIGH RAM ADDRESS PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THIS IS THE HIGHEST (LARGEST) ADDRESS OF A CONTIGUOUS WORK SPACE AREA PROVIDED FOR THE BASIC INTERPRETER. THE BQCONC TASK STACK SIZE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THE BQCONC TASK PROVIDES BASIC WITH ITS CONTROL C FUNCTIONALITY. THE BQBAS TASK STACK SIZE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. BQBAS IS THE BASIC TASK. THE BUFFER SIZE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THIS IS THE SIZE OF THE BUFFER (IN BYTES). THIS SPACE WILL BE RESERVED IN THE CAM MODULE. THE CONTROLLER TASK STACK SIZE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THE STACK SIZE FOR iRMX 80-SUPPLIED CONTROLLER TASKS SHOULD BE 104. THE CONTROLLER STACK RESIDES IN THE CAM MODULE. THE DISKIO TASK STACK SIZE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THE DIRECTORY SERVICES TASK STACK SIZE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THE EXTRA PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 255 INCLUSIVE IS ACCEPTABLE. THIS PARAMETER IS USED FOR FORTRAN TASKS THAT USE FLOATING-POINT OPERATIONS. ITS FUNCTION IS TO INCREASE THE TASK DESCRIPTOR SIZE BY THE INDICATED NUMBER. IF SOFTWARE FLOATING-POINT ROUTINES ARE USED, 18 EXTRA BYTES MUST BE ADDED; IF THE iSBC 310 UNIT IS USED, 13 EXTRA BYTES ARE REQUIRED. THE RQTOV PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. ITS VALUE SPECIFIES THE NUMBER OF SYSTEM TIME UNITS THE DFS SYSTEM WILL WAIT BEFORE RETURNING AN ERROR CODE IF A DRIVE BEING ACCESSED DOES NOT RESPOND. NOTE -- THIS PARAMETER IS ONLY RELEVANT TO 80/10-BASED SYSTEMS. THE RQMOTM PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THIS PARAMETER SPECIFIES THE NUMBER OF SYSTEM TIME UNITS TO BE DELAYED BY THE MOTOR ON OPERATION OF THE DISKIO SERVICE. THIS VALUE SHOULD BE EQUIVALENT TO ONE SECONDS' WORTH OF SYSTEM TIME UNITS. FOR EXAMPLE, IF YOUR SYSTEM TIME UNIT IS 20MS, RQMOTM SHOULD BE 50. NOTE -- THIS PARAMETER IS ONLY RELEVANT TO 80/10-BASED SYSTEMS USING MINI- DISKETTE DRIVES. THE USER TASK STACK LENGTH PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THIS WILL CREATE A STACK OF THE INDICATED SIZE FOR THE CURRENT TASK. NOTE -- ANY TASK WRITTEN IN FORTRAN THAT USES FORTRAN I/O STATEMENTS AND/OR STOP OR PAUSE STATEMENTS MUST INCLUDE AN EXTRA 800 (DECIMAL) BYTES OF STACK FOR I/O ROUTINES. THE STACK SIZE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THIS NUMBER REPRESENTS THE SIZE OF THE STACK FOR THE TASK CURRENTLY BEING SPECIFIED. THE EXTENSION/DFS SERVICE STACK SIZE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THIS NUMBER OF BYTES WILL BE RESERVED FOR THE CURRENT TASK STACK. THE RQTCNT PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THIS PARAMETER IS RELEVANT ONLY IN 80/10-BASED SYSTEMS. ITS VALUE SPECIFIES THE NUMBER OF CLOCK TICKS IN A SYSTEM TIME UNIT. FOR EXAMPLE, TO MAINTAIN A 50MS TIME QUANTUM, A SYSTEM USING A 25MS CLOCK SHOULD SPECIFY A VALUE OF 2 FOR RQTCNT. THE iSBC 310 OFF BOARD ADDRESS PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: RELOCATABLE OR ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. SPECIFYING RELOCATABLE WILL CAUSE THE FORTRAN FLOATING POINT RECORD TO BE LINKED AND LOCATED WITH THE REST OF THE SYSTEM. SPECIFYING AN ABSOLUTE ADDRESS WILL CAUSE THE FPR TO BE LOCATED SEPARATELY AT THE INDICATED ADDRESS BEFORE BEING LINKED WITH THE REST OF THE SYSTEM. THE SYSTEM CODE ADDRESS PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: RELOCATABLE OR ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THIS IS THE ADDRESS AT WHICH THE CODE SEGMENT WILL BEGIN WHEN THE APPLICATION SYSTEM IS LOCATED. IT IS ONLY USED IN THE SUBMIT FILE. NOTE -- A BOOT LOADER SYSTEM'S CODE SEGMENT MUST BE LOCATED AT 40H. THE SYSTEM DATA ADDRESS PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: RELOCATABLE OR ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. THIS IS THE ADDRESS AT WHICH THE DATA SEGMENT WILL BEGIN WHEN THE APPLICATION SYSTEM IS LOCATED. IT IS ONLY USED IN THE SUBMIT FILE. THE CAM MODULE ADDRESS PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: NO, RELOCATABLE OR ANY NUMBER BETWEEN 0 AND 65535 INCLUSIVE IS ACCEPTABLE. NO -- NO CAM MODULE WILL BE CREATED. RELOCATABLE -- THE CAM MODULE WILL BE LINKED AND LOCATED WITH THE REST OF THE SYSTEM. ANY NUMBER -- THE CAM MODULE WILL BE LOCATED AT THIS ADDRESS BEFORE BEING LINKED WITH THE REST OF THE SYSTEM. THE USER TASK PRIORITY PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 255 IS ACCEPTABLE. THIS NUMBER REPRESENTS THE PRIORITY OF THE CURRENT USER TASK. 255 IS RESERVED FOR THE IDLE TASK. THE TASK PRIORITY PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 255 IS ACCEPTABLE. THIS NUMBER REPRESENTS THE PRIORITY OF THE CURRENT iRMX 80 SERVICE/EXTENSION TASK. 255 IS RESERVED FOR THE IDLE TASK. THE DIRECTORY SERVICES PRIORITY PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 255 IS ACCEPTABLE. THE DISKIO PRIORITY PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 255 IS ACCEPTABLE. THE CONTROLLER TASK PRIORITY PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 255 IS ACCEPTABLE. NOTE -- CONTROLLER TASK PRIORITIES SHOULD RUN AT RELATIVELY HIGH PRIORITIES; SEE THE iRMX 80 USERS MANUAL. THE NUMBER OF DFS FILES PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: DYNAMIC OR ANY NUMBER BETWEEN 0 AND 255 IS ACCEPTABLE. DYNAMIC-- DYNAMIC BUFFER ALLOCATION WILL BE PERFORMED. THE FREE SPACE MANAGER MUST BE INCLUDED IN THE APPLICATION SYSTEM. ANY BYTE VALUE-- THIS IS GREATEST NUMBER OF SIMULTANEOUSLY OPEN DFS FILES TO OCCUR IN THE APPLICATION. THE BQBAS TASK PRIORITY PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 255 IS ACCEPTABLE. THIS IS THE PRIORITY OF THE TASK THAT RUNS AS THE BASIC INTERPRETER. THE BQCONC TASK PRIORITY PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 255 IS ACCEPTABLE. THE IS THE PRIORITY OF THE TASK THAT SUPPLIES BASIC'S CONTROL C FUNCTIONALITY. THE NUMBER OF USER FILES PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 255 IS ACCEPTABLE. THIS NUMBER SPECIFIES THE NUMBER OF USER FILES BEING USED IN THE BASIC SYSTEM. THIS PARAMETER IS ONLY RELEVANT IF USER I/O IS SUPPLIED. THIS VALUE DOES NOT INCLUDE DFS FILES. THE iSBC 204 STEP PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 255 IS ACCEPTABLE. THIS PARAMETER SPECIFIES THE STEP RATE (IN MS. - TRACK TO TRACK) OF A DRIVE ATTACHED TO A iSBC 204 CONTROLLER. THE iSBC 204 SETTLE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 255 IS ACCEPTABLE. THIS PARAMETER SPECIFIES (IN MS.) THE HEAD SETTLING TIME OF A DRIVE ATTACHED TO AN iSBC 204 CONTROLLER. THE CONTROL TABLE ELEMENTS PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 255 IS ACCEPTABLE. YOU MAY SPECIFY A SUBSTITUTE VALUE FOR ANY CONTROL COMMAND SIMPLY BY ENTERING THE NEW VALUE TO BE USED TO INDICATE THE CONTROL. A VALUE GREATER THAN 80H WILL CANCEL THE EFFECT OF THE CONTROL. THE ENTRY POINT PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY IDENTIFIER NAME IS ACCEPTABLE. THIS IS THE POINT TO WHICH CONTROL WILL BE PASSED WHEN THE TASK FIRST RECEIVES PROCESSOR CONTROL. THE USER TASK DEFAULT EXCHANGE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: NO VALUE OR ANY IDENTIFIER NAME IS ACCEPTABLE. THIS IS THE DEFAULT EXCHANGE TO BE USED BY THE CURRENT TASK. IF A DEFAULT EXCHANGE IS SPECIFIED, IT MUST BE DECLARED IN THE EXCHANGE LIST IN ORDER TO BE PROPERLY LINKED TO THE TASK DESCRIPTOR. THE CONTROLLER REQUEST EXCHANGE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY IDENTIFIER NAME IS ACCEPTABLE. YOU MUST SUPPLY YOUR OWN REQUEST EXCHANGE FOR THE CONTROLLER. THIS MEANS THAT THE DEFAULT EXCHANGE THAT YOU SPECIFY MUST ALSO BE INCLUDED IN THE EXCHANGE LIST. THE EXCHANGE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY IDENTIFIER NAME IS ACCEPTABLE. THIS IS THE LABEL OF THE EXCHANGE DESCRIPTOR BEING DESCRIBED. THIS ADDRESS, ONCE RESOLVED, WILL BE PART OF THE INITIAL EXCHANGE TABLE. NOTE -- INTERRUPT EXCHANGES CANNOT BE BUILT IN A LOADABLE SYSTEM; THEY MUST BE DECLARED IN THE BOOT LOADER SYSTEM. THE BUFFER NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY IDENTIFIER NAME IS ACCEPTABLE. THE IDENTIFIER DESCRIBING THE BUFFER WILL BE CREATED AS A PUBLIC VARIABLE RESIDING IN THE CAM MODULE. THE PRUN IDENTIFIER PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: COMMAND OR ANY IDENTIFIER NAME IS ACCEPTABLE. COMMAND -- THE BASIC SYSTEM WILL COME UP IN THE INTERPRETIVE MODE. ANY OTHER IDENTIFIER -- BASIC WILL BEGIN EXECUTING THE CODE BEGINNING AT THE ADDRESS INDICATED BY THE IDENTIFIER. FOR THIS REASON, THE IDENTIFIER SPECIFIED MUST BE A PUBLIC LABEL TO SOME BASIC PROGRAM. THE EXTERNAL CLOCK PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. THIS PARAMETER IS ONLY RELEVANT TO 80/10-BASED SYSTEMS. YES -- IT IS ASSUMED THAT AN EXTERNAL CLOCK SOURCE IS PROVIDED. NO -- IT IS ASSUMED THAT NO EXTERNAL CLOCK SOURCE IS PROVIDED. THE CONTROL TABLE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- A USER-DESCRIBED CONTROL TABLE WILL BE LINKED INTO THE SYSTEM. NO -- A DEFAULT CONTROL TABLE WILL DESCRIBE THE CONTROL VALUES. THE FREE SPACE MANAGER PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES-- THE TASKS AND EXCHANGES NEEDED TO INCLUDE THE FSM IN THE APPLICATION SYSTEM WILL BE AUTOMATICALLY INCLUDED. NO-- THE FREE SPACE MANAGER WILL NOT BE INCLUDED. TASK DESCRIPTOR ADDRESS = RQFSMD. THE INTERRUPT PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- THE EXCHANGE WILL BE CREATED AS AN INTERRUPT EXCHANGE. NO -- THE EXCHANGE WILL BE CREATED AS A NON-INTERRUPT EXCHANGE. NOTE -- THIS PARAMETER IS ONLY RELEVANT TO SYSTEMS THAT ARE NOT LOADABLE. THE DISK FILE SYSTEM PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- THIS ASSUMES THAT SOME DFS SERVICES ARE TO BE INCLUDED IN THE APPLICATION SYSTEM. ALL OF THE SERVICES WILL BE PROMPTED FOR. NO -- IT IS ASSUMED THAT NO DISK FILE SERVICES ARE TO BE INCLUDED. TASK DESCRIPTOR ADDRESS = (DIRECTORY SERVICES) RQDRSD. THE ATTRIB PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- ANY TASKS AND EXCHANGES NEEDED TO USE THE ATTRIBUTE FUNCTION WILL BE INCLUDED IN THE APPLICATION SYSTEM. NO -- IT IS ASSUMED THAT NO ATTRIBUTE SERVICES ARE REQUIRED BY THE APPLICATION SYSTEM. TASK DESCRIPTOR ADDRESS = RQATBD. THE DELETE DFS SERVICE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- ANY TASKS AND EXCHANGES NEEDED TO USE THE DELETE FUNCTION WILL BE INCLUDED IN THE APPLICATION SYSTEM. NO -- IT IS ASSUMED THAT NO DELETE SERVICES ARE REQUIRED BY THE APPLICATION SYSTEM. TASK DESCRIPTOR ADDRESS = RQDELD. THE FORMAT DFS SERVICE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- ANY TASKS AND EXCHANGES NEEDED TO USE THE FORMAT FUNCTION WILL BE INCLUDED IN THE APPLICATION SYSTEM. NO -- IT IS ASSUMED THAT NO FORMAT SERVICES ARE REQUIRED BY THE APPLICATION SYSTEM. TASK DESCRIPTOR ADDRESS = RQFMTD. THE LOAD DFS SERVICE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- ANY TASKS AND EXCHANGES NEEDED TO USE THE LOAD FUNCTION WILL BE INCLUDED IN THE APPLICATION SYSTEM. NO -- IT IS ASSUMED THAT NO LOAD SERVICES ARE REQUIRED BY THE APPLICATION SYSTEM. TASK DESCRIPTOR ADDRESS = RQLODD. THE RENAME DFS SERVICE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- ANY TASKS AND EXCHANGES NEEDED TO USE THE RENAME FUNCTION WILL BE INCLUDED IN THE APPLICATION SYSTEM. NO -- IT IS ASSUMED THAT NO RENAME SERVICES ARE REQUIRED BY THE APPLICATION SYSTEM. TASK DESCRIPTOR ADDRESS = RQREND. THE OPEN DFS SERVICE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- ANY TASKS AND EXCHANGES NEEDED TO USE THE OPEN FUNCTION WILL BE INCLUDED IN THE APPLICATION SYSTEM. NO -- IT IS ASSUMED THAT NO OPEN SERVICES ARE REQUIRED BY THE APPLICATION SYSTEM. THE CLOSE DFS SERVICE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- ANY TASKS AND EXCHANGES NEEDED TO USE THE CLOSE FUNCTION WILL BE INCLUDED IN THE APPLICATION SYSTEM. NO -- IT IS ASSUMED THAT NO CLOSE SERVICES ARE REQUIRED BY THE APPLICATION SYSTEM. THE READ DFS SERVICE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- ANY TASKS AND EXCHANGES NEEDED TO USE THE READ FUNCTION WILL BE INCLUDED IN THE APPLICATION SYSTEM. NO -- IT IS ASSUMED THAT NO READ SERVICES ARE REQUIRED BY THE APPLICATION SYSTEM. THE WRITE DFS SERVICE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- ANY TASKS AND EXCHANGES NEEDED TO USE THE WRITE FUNCTION WILL BE INCLUDED IN THE APPLICATION SYSTEM. NO -- IT IS ASSUMED THAT NO WRITE SERVICES ARE REQUIRED BY THE APPLICATION SYSTEM. THE SEEK DFS SERVICE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- SEEK WILL BE INCLUDED IN THE BUILDING OF THE APPLICATION SYSTEM. NO -- SEEK WILL NOT BE INCLUDED. THE DISKIO DFS SERVICE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. THE TASKS AND EXCHANGES NECESSARY TO INCLUDE DISKIO IN THE APPLICATION SYSTEM ARE ALWAYS INCLUDED IN A SYSTEM THAT REQUESTS DFS. THE EXCEPTION IS WHEN A LOADABLE SYSTEM IS BEING CREATED. NO -- IF THE SYSTEM IS LOADABLE THEN THE DISKIO TASKS AND EXCHANGES WILL NOT BE INCLUDED. OTHERWISE, IF DFS IS REQUESTED, THEY WILL BE. NOTE -- THE ORDER OF THE DRIVES IN THE DEVICE CONFIGURATION TABLE (DCT) IS THE SAME AS THE ORDER THAT THEY ARE ENTERED UNDER THE 'DRIVE NAME' PROMPT; THE FIRST DRIVE ENTERED IS DRIVE 0 IN THE DCT, THE SECOND IS DRIVE 1, ETC.. TASK DESCRIPTOR ADDRESS = RQDIOD. THE BASIC PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- ALL OF THE TASKS AND EXCHANGES NEEDED TO CONFIGURE BASIC INTO THE SYSTEM WILL BE INCLUDED. ALSO, OTHER NEEDED INFORMATION WILL BE PROMPTED FOR. BQSMEM, BQEMEM, AND BQINIT ARE AUTOMATICALLY SUPPLIED. NO -- BASIC WILL NOT BE INCLUDED IN THE SYSTEM. TASK DESCRIPTOR ADDRESS - BQBAS = RQBASD; BQCONC = RQBQCD. THE USER I/O FOR BASIC PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- IT IS ASSUMED THAT THE USER IS SUPPLYING USER I/O. BQUIO WILL BE PROPERLY INITIALIZED. NO -- IT IS ASSUMED THAT NO USER-SUPPLIED I/O ROUTINES WILL BE USED. THE FORTRAN PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- IT IS ASSUMED THAT FORTRAN TASKS WILL BE INCLUDED IN THE SYSTEM; ANY NEEDED INFORMATION WILL BE PROMPTED FOR. NO -- FORTRAN TASKS WILL NOT BE INCLUDED IN THE APPLICATION SYSTEM. THE FORTRAN I/O PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- THE LIBRARIES NEEDED TO SUPPORT FORTRAN I/O OPERATIONS WILL BE LINKED INTO THE SYSTEM. NO -- LIBRARIES INDICATING NO FORTRAN I/O WILL BE LINKED INTO THE SYSTEM. NOTE -- ANY USER TASK THAT UTILIZES FORTRAN I/O STATEMENTS AND/OR STOP OR PAUSE STATEMENTS MUST INCLUDE AN EXTRA 800 (DECIMAL) BYTES OF STACK FOR I/O ROUTINES. THE FLOATING POINT MATH PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: SOFT, HARD, AND NO ARE THE ACCEPTABLE PARAMETER VALUES. SOFT -- THE SOFTWARE FLOATING POINT LIBRARIES WILL BE LINKED INTO THE SYSTEM. HARD -- THE HARDWARE FLOATING POINT LIBRARIES WILL BE LINKED INTO THE SYSTEM. NO -- LIBRARIES INDICATING THAT NO FLOATING POINT OPERATIONS WILL BE USED ARE LINKED INTO THE APPLICATION SYSTEM. THE BOOT LOADER SYSTEM PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- THE TASKS, EXCHANGES, AND SPECIAL LINK INFORMATION NEEDED TO CREATE A BOOT LOADER SYSTEM WILL BE INCLUDED. ANY SPECIAL BOOT- LOADER INFORMATION WILL BE PROMPTED FOR. NO -- IT IS ASSUMED THAT THE SYSTEM IS NOT A BOOT LOADER SYSTEM. NOTE -- SINCE INTERRUPT EXCHANGES CANNOT BE CREATED IN A LOADABLE SYSTEM, THE TERMINAL HANDLER INTERRUPT EXCHANGES (RQL6EX FOR INPUT AND RQL7EX FOR OUTPUT) MUST BE DECLARED AS PUBLIC INTERRUPT EXCHANGES UNDER THE 'EXCHANGE:' PROMPT WITHIN THE BOOT LOADER SYSTEM IF A TERMINAL HANDLER IS INCLUDED IN THE LOADABLE SYSTEM. TASK DESCRIPTOR ADDRESS = RQLDRD. THE LOADABLE SYSTEM PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE PARAMETER VALUES. YES -- THE NECESSARY MODULES NEEDED TO LINK A BOOT LOADER SYSTEM ARE INCLUDED IN THE LINK STATEMENT, AND ANY NEEDED INFORMATION IS PROMPTED FOR. NO -- IT IS ASSUMED THAT THE SYSTEM IS NOT TO BE LOADABLE. NOTE -- THE BOOT LOADER ALWAYS LOADS A LOADABLE FILE FROM THE FIRST ENTRY IN THE DEVICE CONFIGURATION TABLE (RQDCT). THE BASIC DISK PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II DEVICE NAME IS ACCEPTABLE. THIS IS THE DEVICE WHERE YOUR INTEL-SUPPLIED BASIC LIBRARIES WILL RESIDE. THIS INFORMATION IS USED TO BUILD THE SUBMIT FILE. THE FORTRAN DISK PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II DEVICE NAME IS ACCEPTABLE. THIS IS THE DEVICE WHERE YOUR INTEL-SUPPLIED FORTRAN LIBRARIES WILL RESIDE. THIS INFORMATION IS USED TO BUILD THE SUBMIT FILE. THE NUCLEUS DISK PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II DEVICE NAME IS ACCEPTABLE. THIS IS THE DEVICE WHERE YOUR INTEL-SUPPLIED NUCLEUS LIBRARIES WILL RESIDE. THIS INFORMATION IS USED TO BUILD THE SUBMIT FILE. THE EXTENSIONS DISK PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II DEVICE NAME IS ACCEPTABLE. THIS IS THE DEVICE WHERE YOUR INTEL-SUPPLIED EXTENSIONS LIBRARIES WILL RESIDE. THIS INFORMATION IS USED TO BUILD THE SUBMIT FILE. THE SBC TYPE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: 80/10, 80/10A, 80/10B, 80/20, 80/20-4, 80/24, 80/30, 544 AND 569 ARE ACCEPTABLE VALUES. YOU MUST SPECIFY THE TYPE OF BOARD YOUR SYSTEM IS TARGETED TO. THE TERMINAL HANDLER PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: FULL, MINIMAL, AND NONE ARE THE ACCEPTABLE VALUES. FULL -- THE NEEDED TASKS AND EXCHANGES FOR SUPPORTING THE FULL TERMINAL HANDLER WILL BE INCLUDED. MINIMAL -- THE NEEDED TASKS AND EXCHANGES FOR SUPPORTING THE MINIMAL TERMINAL HANDLER WILL BE INCLUDED. NONE -- THE TERMINAL HANDLER WILL NOT BE INCLUDED. NOTE -- IF A TERMINAL HANDLER IS TO BE INCLUDED IN A LOADABLE SYSTEM THE I/O INTERRUPT EXCHANGES MUST BE DECLARED AS PUBLIC INTERRUPT EXCHANGES UNDER THE 'EXCHANGE:' PROMPT WITHIN THE BOOT LOADER SYSTEM. FOR EXAMPLE, THE OUTPUT-ONLY VERSION MUST HAVE RQL7EX DECLARED, WHILE THE I/O VERSION ALSO REQUIRES RQL6EX FOR INPUT. TASK DESCRIPTOR ADDRESS = RQTHTD. THE I/O FUNCTION PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: OUTPUT AND I/O ARE THE ACCEPTABLE VALUES. OUTPUT -- THE TASKS AND EXCHANGES NEEDED TO SUPPORT A TERMINAL HANDLER WITH THIS FUNCTIONALITY WILL BE INCLUDED. I/O -- THE TASKS AND EXCHANGES NEEDED TO SUPPORT A TERMINAL HANDLER WITH THIS FUNCTIONALITY WILL BE INCLUDED. THE BAUD RATE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: SEARCH, 9600, 4800, 2400, 1200, 600, 300, 150 AND 110 ARE THE ACCEPTABLE VALUES SEARCH -- THIS PARAMETER IS ONLY RELEVANT TO APPLICATION SYSTEMS WHICH INCLUDE THE FULL I/O TERMINAL HANDLER, AND ARE NOT 80/10- BASED. SPECIFYING SEARCH WILL CAUSE THE TERMINAL HANDLER TO DETERMINE THE BAUD RATE OF YOUR SYSTEM. ANY OTHER VALUE FROM THE LIST -- THIS NUMBER SIMPLY SPECIFIES THE BAUD RATE OF THE TERMINAL TO BE USED WITH THE APPLICATION SYSTEM. THE DEBUGGER PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: NONE, ACTIVE, AND PASSIVE ARE THE ACCEPTABLE VALUES. NONE -- THE DEBUGGER WILL NOT BE INCLUDED IN THE SYSTEM. ACTIVE -- THE TASKS AND EXCHANGES NEEDED TO SUPPORT THE ACTIVE DEBUGGER WILL BE INCLUDED IN THE APPLICATION SYSTEM. PASSIVE -- THE TASKS AND EXCHANGES NEEDED TO SUPPORT THE PASSIVE DEBUGGER WILL BE INCLUDED IN THE APPLICATION SYSTEM. NOTE -- IF YOU ARE USING THE ACTIVE OR PASSIVE DEBUGGER, YOU MUST INCLUDE THE FULL I/O TERMINAL HANDLER IN YOUR SYSTEM. TASK DESCRIPTOR ADDRESS = RQDBGD. THE ANALOG HANDLER PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: NONE, INPUT, OUTPUT, AND I/O ARE THE ACCEPTABLE VALUES. NONE -- NO ANALOG HANDLER INFORMATION WILL BE INTRODUCED INTO THE SYSTEM. INPUT -- THE TASKS AND EXCHANGES NEEDED TO SUPPORT THE INPUT ANALOG HANDLER WILL BE INCLUDED IN THE APPLICATION SYSTEM. OUTPUT -- THE TASKS AND EXCHANGES NEEDED TO SUPPORT THE OUTPUT ANALOG HANDLERS WILL BE INCLUDED IN THE APPLICATION SYSTEM. I/O -- BOTH OF THE ABOVE WILL BE INCLUDED. TASK DESCRIPTOR ADDRESS - INPUT = RQAIHD; OUTPUT = RQAOHD. THE USER TASK NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY STRING OF ASCII CHARACTERS 1-6 BYTES IN LENGTH IS ACCEPTABLE, WITH THE EXCEPTION THAT THE SECOND BYTE CAN NOT BE 'Q' OR '?'. THIS NAME WILL BE ASSIGNED TO THE TASK IN THE INITIAL TASK TABLE. THE SCOPE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: LOCAL, PUBLIC, AND EXTERNAL ARE THE ACCEPTABLE VALUES. LOCAL -- THE ADDRESS OF THE EXCHANGE WILL BE KNOWN ONLY WITHIN THE CONFIGURATION MODULE. SPACE WILL BE RESERVED IN THIS MODULE. PUBLIC -- THE ADDRESS OF THE EXCHANGE WILL BE AVAILABLE OUTSIDE OF THE CONFIGURATION MODULE. SPACE WILL BE RESERVED IN THE CONFIGURATION MODULE. EXTERNAL -- THE ADDRESS OF THE EXCHANGE WILL BE SATISFIED AT LINK TIME. THE CONTROLLER TYPE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: 201, 202, 204 AND 206 ARE THE ACCEPTABLE VALUES. THESE CORRESPOND TO THEIR RESPECTIVE iSBC BOARD TYPES. YOU MUST SPECIFY ONE OF THE ABOVE TYPES. THE CONTROLLER BASE ADDRESS PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER BETWEEN 0 AND 255 WHICH IS A MULTIPLE OF 8 IS ACCEPTABLE (BASE ADDRESSES FOR 204 CONTROLLERS MUST BE A MULTIPLE OF 16). THIS IS THE BASE ADDRESS THAT YOU WILL ASSIGN TO YOUR CONTROLLER FOR COMMUNICATING OVER THE SERIAL I/O PORT. THE CONTROLLER INTERRUPT LEVEL PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER FROM 0 TO 7 IS ACCEPTABLE. THIS IS THE INTERRUPT LEVEL TO BE ASSIGNED TO THE CONTROLLER. AN INTERRUPT EXCHANGE WILL BE CREATED AT THIS LEVEL FOR THE CONTROLLER TASK. THE DRIVE NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY TWO ASCII CHARACTERS ARE ACCEPTABLE. THIS IS THE NAME THAT WILL BE USED IN MAKING LOGICAL REFERENCES TO THIS DRIVE (i.e., IT IS THE PATHNAME). NOTE -- THE DRIVES SPECIFIED HERE ARE ENTERED IN THE DEVICE CONFIGURATION TABLE IN EXACTLY THE SAME ORDER AS THEY ARE ENTERED HERE. FOR EXAMPLE, THE DRIVE THAT WILL BE USED BY THE BOOT LOADER IS THE FIRST ONE IN THE DCT, WHICH, IN TURN IS THE FIRST ONE ENTERED HERE. THE DRIVE UNIT NUMBER PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER FROM 0 TO 15 IS ACCEPTABLE. THIS PARAMETER SPECIFIES THE UNIT NUMBER FOR THE CONTROLLER WHEN SELECTING THE DRIVE. THE DRIVE SIZE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: STANDARD AND MINI ARE THE ACCEPTABLE VALUES. YOU MUST INDICATE WHETHER YOUR DRIVE IS STANDARD- OR MINI-SIZED BY ENTERING THE CORRECT PARAMETER VALUE. THE DRIVE TYPE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: SA800, SA400, SA850, MEMOREX 550, MEMOREX 552, CDC 9404, PERTEC FD200, GSI-110, WANGCO MOD 82, WANGCO MOD 765, AND SPECIAL ARE ACCEPTABLE VALUES. SPECIAL -- IT IS ASSUMED THAT THE DRIVE YOU HAVE IS NOT IN THE LIST. NEEDED PARAMETERS WILL BE PROMPTED FOR. IF THE TYPE OF DRIVE YOU ARE USING IS IN THE LIST, ENTER THE TYPE-- ANY ADDITIONAL NEEDED INFORMATION WILL BE PROMPTED FOR. THE iSBC 204 CHIP SELECT PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: 0 AND 1 ARE THE ACCEPTABLE VALUES. 0 -- THE INTEL-INSTALLED CHIP IS TO BE USED TO CONTROL THE DRIVE. 1 -- A USER-INSTALLED CHIP IS TO BE USED TO CONTROL THE DRIVE. THE iSBC 204 INDEX PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER FROM 1 TO 15 IS ACCEPTABLE. THIS PARAMETER SPECIFIES THE INDEX COUNT FOR THE DRIVE. THE iSBC 204 LOAD TIME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER FROM 0 TO 15 IS ACCEPTABLE. THIS PARAMETER SPECIFIES THE HEAD LOAD TIME FOR THE DRIVE. THE USER LINK INFORMATION PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY INPUT WILL BE ACCEPTED. HERE IS WHERE ANY USER-SUPPLIED MODULES, PUBLICS, ETC. WHICH ARE TO BE LINKED INTO THE APPLICATION SYSTEM ARE SPECIFIED. ANY INFORMATION SPECIFIED HERE WILL BE TAKEN VERBATUM AND HAVE APPENDED A COMMA AND AN AMPERSAND. THE INFORMATION IS THEN INCLUDED IN THE LINK STATEMENT OF THE SUBMIT FILE. THE COMMENT PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY INPUT WILL BE ACCEPTED. COMMENTS CAN BE INSERTED ANY WHERE IN THE DESCRIPTION FILE. A RESPONSE OF YES WILL CAUSE A CONFIGURATION MODULE TO BE CREATED. IF DFS IS TO BE INCLUDED IN THE APPLICATION SYSTEM, A CAM MODULE WILL AUTOMATICALLY BE GENERATED, UNLESS IT HAS BEEN SPECIFIED IN THE CONFIGURATION MODULE (CAM ADDRESS PARAMETER) THAT NO CAM MODULE IS TO BE CREATED. A RESPONSE OF YES WILL CAUSE A SUBMIT FILE TO BE GENERATED. THIS SUBMIT FILE, WHEN EXECUTED, WILL BE CAPABLE OF CREATING THE APPLICATION SYSTEM DEFINED IN THE DESCRIPTION FILE. IN THE CASE OF 80/10-BASED SYSTEMS OR OTHER SYSTEMS THAT HAVE IRREGULAR MEMORY CONFIGURATIONS, SOME MODIFICATIONS MUST BE MADE BY THE USER. INSTRUCTIONS ARE SUPPLIED WITH SUBMIT FILES FOR GENERATING 80/10-BASED SYSTEMS (THIS DOES NOT APPLY TO LOADABLE SYSTEMS). RQTHDIRQTHDITHISTKFpRQOUTXRQTHTDRQTHTDTHISTKFRQINPXRQOUTXRQWAKERQDBUGRQALRMRQTHDORQTHDOTHOSTK<RQOUTXRQTHTDRQTHTDTHOSTK<RQOUTXRQALRMRQFMGRRQFMGRFSMSTK@RQFSRXRQFSMDRQFSMDFSMSTK@RQFSRXRQFSAXRQADBGRQADBGDBGSTKXRQWAKERQDBGDRQDBGDDBGSTKXRQPDBGRQPDBGDBGSTKXRQWAKERQDBGDRQDBGDDBGSTKXRQAIH RQAIHAIHSTK:RQAIEXRQAIHDRQAIHDAIHSTK:RQAIEXRQAOH RQAOHAOHSTK8RQAOEXRQAOHDRQAOHDAOHSTK8RQAOEXRQPATRRQPATRATBSTKXRQATRXRQATBDRQATBDATBSTKXRQATRXRQPDELRQPDELDELSTKXRQDELXRQDELDRQDELDDELSTKXRQDELXRQPFMTRQPFMTFMTSTKXRQFMTXRQFMTDRQFMTDFMTSTKXRQFMTXRQPLD RQPLDLODSTKXRQLDXRQLODDRQLODDLODSTKXRQLDXRQPRNMRQPRNMRENSTKXRQRNMXRQRENDRQRENDRENSTKXRQRNMXRQPDIRRQPDIRDRSSTKHRQDIRXRQDRSDRQDRSDDRSSTKHRQDIRXRQDBUFRQPDSKRQPDSKDIOSTKHRQDSKXRQDIODRQDIODDIOSTKHRQDSKXRQBOOTRQBOOTLDRSTKXRQLDRDLDRSTKXRQLDRDFQ0LOK ITTIET RQCSTBQBAS BQBASBASSTKXBQEXCHRQBASDBQEXCH BASSTKXRQBASDBQCONCBQCONCBQCSTKHRQWAKERQBQCDBQCSTKHRQBQCD BQINITBQINITRQHD1V RQSETPBQINITRQHD4V RQSETPBQOPNX RQPOOLRQBABRQFSAXRQFSRX BQPRUNTHE EXTRA INTERRUPT PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE VALUES. YES -- THE LIBRARIES NEEDED TO UTILIZE THE 8085'S EXTRA INTERRUPTS ARE AVAILABLE. NO -- THE 8085 WILL BE TREATED AS AN 8080. THE BOARD TYPE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: 310 AND 332 ARE THE ACCEPTABLE VALUES. 310 -- THE LIBRARIES NEEDED TO SUPPORT THE iSBC 310 WILL BE INCLUDED. 332 -- THE iSBX 332 LIBRARIES WILL BE INCLUDED. THE BAD BLOCKS PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE ACCEPTABLE VALUES. YES -- THE LIBRARIES WHICH SUPPORT BAD BLOCK RECOVERY FOR A HARD DISK WILL BE INCLUDED IN THE SYSTEM AT LINK TIME. THIS SOFTWARE WILL FORMAT THE HARD DISK IN SUCH A WAY THAT BAD SECTORS WILL BE IDENTIFIED AND NOT ALLOCATED TO USER FILES. THIS SOFTWARE IS ISIS-COMPATIBLE. NO -- BAD BLOCK FORMATTING SOFTWARE WILL NOT BE INCLUDED IN THE SYSTEM. NOTE -- BAD BLOCK SOFTWARE IS ONLY RELEVANT IN SYSTEMS WHICH INCLUDE AN iSBC 206 AND A HARD DISK, ALTHOUGH THE SOFTWARE WILL RUN PROPERLY WITH ANY DISK CONTROLLER. THE DISADVANTAGE OF INCLUDING THE SPECIAL BAD BLOCK SOFTWARE IS THAT IT REQUIRES APPROXIMATELY 1000 MORE BYTES OF MEMORY THAN THE TYPICAL FORMAT SOFTWARE. THE TASK DESCRIPTOR NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY IDENTIFIER IS ACCEPTABLE. SPECIFYING A VALUE WILL CAUSE THE TASK DESCRIPTOR ASSOCIATED WITH THIS TASK TO BE DECLARED PUBLIC AT THE INDICATED IDENTIFIER. THIS IS USEFUL FOR DELETING AND SUSPENDING TASKS. NO VALUE SHOULD BE ENTERED IF THERE IS NO NEED TO HAVE THE TASK'S TASK DECRIPTOR DECLARED PUBLIC. THE SYSTEM TIME UNIT PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: | 80/20 | | | BOARD TYPE | 80/20-4 | 80/30 | 544 | 569 | 80/24 | | | _____________|_____________|_____________|_____________|____________ | | | | ACCEPTABLE | | 10, 25, | | VALUES | 10, 25, 50 | 50, 100 | 10, 25, 50 | 10, 25 OR ANY NUMBER BETWEEN 100 AND 65535. THIS PARAMETER SPECIFIES THE SMALLEST TIME UNIT REALIZED BY THE NUCLEUS. THE VALUE OF THIS PARAMETER IS SPECIFIED IN MILLISECONDS IF A NUMBER FROM THE TABLE IS SELECTED, OR IN A VALUE WITH WHICH THE 8253 WILL BE PROGRAMMED IF A NUMBER GREATER THAN 100 IS INPUT. NOTE -- THE DEFAULT VALUE OF 50mS IS RECOMMENDED. VALUES LESS THAN THIS WILL CAUSE THE PROCESSOR TO SPEND MOST OF ITS TIME SERVICING TIMER INTERRUPTS. THE EXCEPTION TO THIS IS THE 569 BOARD WHICH CANNOT SUPPORT A TIME UNIT OF MORE THAN 25mS AND MUST USE A VALUE OTHER THAN THE DEFAULT. THE COMMAND LINE INTERPRETER PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE ACCEPTABLE VALUES. YES -- THE CLI UTILITY IS TO BE INCLUDED IN THE APPLICATION SYSTEM. NO -- THE CLI WILL NOT BE INCLUDED. NOTE -- THE CLI REQUIRES A TERMINAL HANDLER TO BE PRESENT IN THE APPLICATION SYSTEM. THE COMMAND NAME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY IDENTIFIER NAME, UP TO SIX CHARACTERS, IS ACCEPTABLE. THIS PARAMETER SPECIFIES THE NAME OF THE USER TASK TO BE INVOKED VIA THE CLI. THE COMMAND EXCHANGE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY IDENTIFIER IS AN ACCEPTABLE VALUE. THIS PARAMETER SPECIFIES THE NAME OF THE EXCHANGE TO WHICH THE MESSAGE FOR THE ASSOCIATED COMMAND WILL BE SENT. THE CLI INPUT EXCHANGE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY IDENTIFIER IS AN ACCEPTABLE VALUE. THIS PARAMETER SPECIFIES THE NAME OF THE EXCHANGE THAT THE CLI WILL USE FOR INPUT FROM A TERMINAL HANDLER. NOTE -- IT IS NOT REQUIRED THAT THE iRMX 80 TERMINAL HANDLER BE INCLUDED FOR USE BY THE CLI IF A USER T. H. HAS BEEN PROVIDED. THE CLI OUTPUT EXCHANGE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY IDENTIFIER IS AN ACCEPTABLE VALUE. THIS PARAMETER SPECIFIES THE NAME OF THE EXCHANGE THAT THE CLI WILL USE FOR OUTPUT TO A TERMINAL HANDLER. NOTE -- IT IS NOT REQUIRED THAT THE iRMX 80 TERMINAL HANDLER BE INCLUDED FOR USE BY THE CLI IF A USER T. H. HAS BEEN PROVIDED. THE COPY UTILITY PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE VALUES. YES -- THE COPY UTILITY WILL BE INCLUDED FOR USE BY THE CLI. NO -- THE COPY UTILITY WILL NOT BE INCLUDED. NOTE -- IN ORDER TO USE THE COPY UTILITY, THE DFS EXTENSIONS OPEN, CLOSE, READ, WRITE, ATTRIB AND DELETE MUST BE INCLUDED IN THE SYSTEM CONFIGURATION. THE COPY UTILITY BUFFER SIZE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY NUMBER IS AN ACCEPTABLE VALUE. THIS PARAMETER SPECIFIES THE SIZE OF THE BUFFER TO BE USED BY COPY IN MAKING TRANSFERS BETWEEN FILES. NOTE -- IT IS RECOMMENDED THAT THE LENGTH OF THE BUFFER BE DIVISIBLE BY 128. THE FORMAT UTILITY PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE VALUES. YES -- THE FORMAT UTILITY WILL BE INCLUDED FOR USE BY THE CLI. NO -- THE FORMAT UTILITY WILL NOT BE INCLUDED. NOTE -- IN ORDER TO USE THE FORMAT UTILITY, THE DFS FORMAT COMMAND MUST BE INCLUDED IN THE SYSTEM CONFIGURATION. THE DIRECTORY UTILITY PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE VALUES. YES -- THE DIRECTORY UTILITY WILL BE INCLUDED FOR USE BY THE CLI. NO -- THE DIRECTORY UTILITY WILL NOT BE INCLUDED. NOTE -- IN ORDER TO USE THE DIRECTORY UTILITY, THE DFS EXTENSIONS OPEN, READ AND CLOSE MUST BE INCLUDED IN THE SYSTEM CONFIGURATION. THE DELAYED WAITS PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE VALUES. NO -- DELAYED WAITS ARE NOT USED BY THE APPLICATION SYSTEM. YES -- THE DELAYED WAITS FUNCTIONALITY WILL BE INCLUDED IN THE NUCLEUS CONFIGURATION. THIS ALLOWS USE OF THE RQISND PRIMITIVE. THE ACCEPT MESSAGE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE VALUES. NO -- ACCEPT MESSAGE IS NOT USED BY THE APPLICATION SYSTEM. YES -- THE ACCEPT MESSAGE FUNCTIONALITY WILL BE INCLUDED IN THE NUCLEUS CONFIGURATION. THIS ALLOWS USE OF THE RQACPT PRIMITIVE. THE INTERRUPTS PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE VALUES. NO -- INTERRUPTS ARE NOT USED IN THE APPLICATION SYSTEM. YES -- INTERRUPT FUNCTIONALITY WILL BE INCLUDED IN THE NUCLEUS CONFIGURATION. THIS ALLOWS USE OF THE RQDLVL AND RQELVL PRIMITIVES. THE INTERRUPT SERVICE ROUTINE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE VALUES. NO -- INTERRUPT SERVICE ROUTINES ARE NOT USED BY THE APPLICATION SYSTEM. YES -- INTERRUPT SERVICE ROUTINE FUNCTIONALITY WILL BE INCLUDED IN THE NUCLEUS CONFIGURATION. THIS ALLOWS USE OF THE RQSETV AND RQENDI PRIMITIVES. THE DELETE TASK PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE VALUES. NO -- THE APPLICATION SYSTEM DOES NOT DELETE ANY TASKS. YES -- THE DELETE TASK FUNCTIONALITY WILL BE INCLUDED IN THE NUCLEUS CONFIGURATION. THIS ALLOWS USE OF THE RQDTSK PRIMITIVE. THE SUSPEND/RESUME PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: YES AND NO ARE THE ACCEPTABLE VALUES. NO -- THE APPLICATION SYSTEM DOES NOT SUSPEND OR RESUME ANY TASKS. YES -- THE SUSPEND/RESUME FUNCTIONALITY WILL BE INCLUDED IN THE NUCLEUS CONFIGURATION. THIS ALLOWS USE OF THE RQSUSP AND RQRESM PRIMITIVES. RQWAKERMXCLIRQCLICLISTKRQCLIDRQCLIDRQCLRX  CLIIOEXCH  WRITERESPEXCH CLISTK COMMANDTABLEFMTUTLFMTUTLFMUSTKRQFMUXRQFMUDRQFMUDRQFMUX  FMTIOEXCH FMUSTKFORMATRQFMUXRQCOPYRQCOPYCPYSTKRQCPYXRQCPYDRQCPYDRQCPYX  COPYIOEXCH CPYSTKCOPY RQCPYXDIRECT DIRECTORYDIRSTKRQDRUXRQDIRDRQDIRDRQDRUX DIRSTKDIRECTRQDRUXRQL7EXRQL6EXTHE SYSTEM DISK PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: ANY ISIS-II DEVICE NAME IS ACCEPTABLE. THIS IS THE DEVICE WHERE YOUR INTEL-SUPPLIED SYSTEM LIBRARIES WILL RESIDE. THIS INFORMATION IS USED TO BUILD THE SUBMIT FILE. THE RUBOUT TYPE PARAMETER CAN ASSUME ANY OF THE FOLLOWING VALUES: CRT OR TTY ARE THE ACCEPTABLE PARAMETER VALUES. THIS INFORMATION IS USED TO SPECIFY THE TYPE OF RUBOUT USED BY THE TERMINAL HANDLER. CRT -- TYPING A RUBOUT WILL CAUSE THE TERMINAL HANDLER TO ECHO A SEQUENCE CONSISTING OF 'BACKSPACE, SPACE, BACKSPACE,' LEAVING THE CURSOR POSITIONED ONE SPACE TO THE LEFT OF ITS LAST POSITION. THIS TYPE OF RUBOUT IS INTENDED PRIMARILY FOR THOSE SYSTEMS USING CRT'S. TTY -- TYPING A RUBOUT WILL CAUSE THE TERMINAL HANDLER TO ECHO THE LAST CHARACTER ENTERED. NO BACKSPACING WILL TAKE PLACE. THIS TYPE OF RUBOUT IS INTENDED PRIMARILY FOR THOSE SYSTEMS USING TELETYPES.