GETTING OF THE AIR WITH RSX-11/IAS RUNOFF I. Building RUNOFF 1.0 RSX-11M 1.1 RSX -11M MAPPED SYSTEMS All command files follow the standard RSX-11M c onventions. 1. [100,10] should contain all source modules. 2. [100,20] should contain the file RNOASM.CMD. [1,24] will receive the object output files. 3. [100,30] wil l receive listing files. 4. [1,24] should contain the file RNOB LM.ODL 5. [1,24] should contain the file RNOBLM.CMD 6. [1,34] will receive the map output file. 7. [1,54] wil l receive the task image file. Procedure: 1. Use UFD to set up the proper UFDs, if necessary. Note that all comm and files must be changed if you do not do this. 2. Use FLX to move the files to their proper UICs. 3. Set t he UIC to [1,24] and assemble. SET /UIC=[1,24] MAC @[100,20]RNOASM 4. Use PIP to construct a concatenat ed object file for all RNO files: PIP>RNO. OBS=*.OBJ 5. Build a library containing the RNO object files: LBR>RNO/CR=RNO.OBS 6. Build the task image f ile. The map will go to [1,34] and the task image to [1,54] . TKB @[1,24]RNOBLM Alternatively, you may use the indirect MCR command file, PAGE 2 [1,24]RNO11MM.CMD, to perform the se steps after transferring the files to the proper UFDs (i.e. [1,24]R NO11MM.CMD will perform steps 3 through 6). You will probably have to edit the command files to match installation dependent conditions. 1.2 RSX-11M UNMAPPED SYSTEMS All command files follo w the standard RSX-11M conventions. 1. [100,10] should contain all source modules. 2. [100,20] should contain the file RNOAS M.CMD. [1,20] will receive the object output files. 3. [100,30] will receive listing files. 4. [1,20] shou ld contain the file RNOBLM.ODL 5. [1,20] should contain the fil e RNOBLU.CMD 6. [1,30] will receive the map output file. 7. [1,50] will receive the task image file. Procedure: 1. Use UFD to set up the proper UFDs, if necessary. Note that all command files must be changed if you do not do this. 2. Use FLX to move the files to their proper UICs. 3. Set the UIC to [1,20] and assemble. SET / UIC=[1,20] MAC @[100,20]RNOASM 4. Use PIP t o construct a concatenated object file for all RNO files: PIP>RNO.OBS=*.OBJ 5. Build a library containing the RNO object files: LBR>RNO/CR=RNO.OBS 6. Build the task image file. The map will go to [1,30] and the task image to [1,50]. TKB @[1,20]RNOBLU Altern atively, you may use the indirect MCR command file, [1,20]RNO11M U.CMD, to perform these steps after transferring the files to the prope r UFDs (i.e. [1,20]RNO11MU.CMD will perform steps 3 through 6). Yo u will probably have to edit the command files to match installation de pendent conditions. PAGE 3 2.0 RSX-11D All command files foll ow the standard RSX-11D conventions. 1. [311,25] should contain all source modules. 2. [311,25] should contain the file RNOMAC D.CMD. [11,25] will receive the object output files. 3. [211,25] will receive listing files. 4. [11,25] sh ould contain the file RNOBLD.ODL 5. [11,25] should contain the file RNOBLD.CMD 6. [111,25] will receive the map output file. 7. [11,1] will receive the task image file. Procedure : 1. Use UFD to set up the proper UFDs, if necessary. Note that all command files must be changed if you do not do this. 2. Use FLX to move the files to their proper UI Cs. 3. Set the UIC to [11,25] and assemble. SET /UIC=[11,25] MAC @[311,25]RNOMACD 4. U se PIP to construct a concatenated object file for all RNO fil es: PIP>RNO.OBS=*.OBJ 5. Build a library co ntaining the RNO object files: LBR>RNO/CR=RNO.OBS 6. Build the task image file. The map will go to [111,25] and the task image to [11,1]. TKB @[11,25]RNOBLD Alternatively, you may use the Batch input file, [11 ,25]RNO11D.BIS, to perform these steps after transferring the files to the proper UFDs (i.e. [11,25]RNO11D.BIS will perform steps 3 through 6). You will probably have to edit the files to match installation de pendent conditions. PAGE 4 3.0 IAS IAS users have the optio n of following the procedures for RSX-11D under MCR or of using the following PDS commands. All command files follow the standard IAS conventions. 1. [311,25] should contain all source modules. 2. [311,25] should contain the file RNOMACI.CMD. [11,25] will receive the object output files. 3. [211,25] wi ll receive listing files. 4. [11,25] should contain the file RN OBLD.ODL 5. [11,25] should contain the file RNOBLI.CMD 6. [111,25] will receive the map output file. 7. [11,1 ] will receive the task image file. Procedure: 1. Th e system manager should use SCI>CREATE to set up the proper U FDs, if necessary. Note that all command files must be change d if you do not do this. 2. Use COPY to move the files to their proper UICs. 3. Set the UIC to [11,25] and assemble. SET DEFAULT [11,25] PDS> @[311,25]RNOMACI 4. Use COPY to construct a concatenated object file for all RNO files: COPY *.OBJ RNO.OBS 5. Build a library containing the RNO object files: LIBRARIAN/ CREATE RNO RNO.OBS 6. Build the task image file. The map will go to [111,25] and the task image to [11,1]. PDS>@[11,25]RNOBLI Alternatively, you may use the Batch input file, [11,25]RNOIAS.BIS, or the PDS indirect comma nd file, [11,25]RNOIAS.CMD, to perform these steps after transferring the files to the proper UFDs (i.e. [11,25]RNOIAS.BIS and [11,25]RNOIAS.CMD will perform steps 3 through 6). You will probably have to edit the files to match installation dependent cond itions. PA GE 5 II. RUNOFF Documentation Runoff is documented in the file, RUNOFF.RNO which you should transfer to the same UFD as the source files. You may then ob- tain a copy of the RUNOFF manual, b y installing RUNOFF (RUNOFF has the task name ...RNO under RSX-11M/ D and $$$RNO under IAS, so it may be run as an MCR command (PDS Library Task under IAS), and then issuing one of the following command lines or equiva- lent: RSX-11M: MCR>RNO LP:=[100,10]R UNOFF RSX-11D: MCR>RNO LP:=[311,25]RUNOFF IAS: PDS>RNO LP:=[311,25]RUNOFF