Dear IAS User, This is a list of additional instructions/limitations for the IAS version of the LBL Software Tools Virtual Operating System. You should also consult [307,30]kitbld.cmd and [307,30]readme for more information during the build procedure. I apologize in advance for any errors in this document, as I do not have an IAS liscense, and have only spent 3 days putting this system up on an IAS v.3.0 site. If you have any problems with installation, feel free to contact me at: Joseph Sventek Computer Science & Mathematics Lawrence Berkeley Laboratory Berkeley, CA 94720 (415) 486-5205 In order to expedite the removal of files from FLX tapes, the Fast FLX (FFL) source code is contained on [307,30]. If you wish to build it for use, perform the following (the tape device is assumed as MM0: below. If yours differs, please modify appropriately.) MCR FLX /RS=MM0:[307,30]FFL.MAC/DO,FFLBLD.CMD/DO MCR MAC FFL,FFL/-SP=FFL If the tape device is not MM0:, edit fflbld.cmd to reflect this. MCR TKB @FFLBLD INSTALL/TASK=$$$FFL FFL FFL /UF/FO/SL=MM0:[307,30]*.*,[307,31]*.*,[307,32]*.*,[307,33]*.* Now you have the sources and build files for the Tools VOS on the current disk. Since the PDS indirect command file processor is rather primitive, it is necessary for much of what is done automatically on RSX to be done by hand on an IAS system. It may help to follow along in kitbld.cmd. 1. Decide which device to place the tools directories on, hereafter known as DDN. 2. As you may have gleaned from readme, the tools occupy 6 directories, the defaults being [105,1] through [105,6]. If you must use different directories, you will have to do some additional editing, listed below. 3. Now edit [307,31]sitepr.f. You MUST replace all occurrences of the string "ST0" with "DDN", where this is your tools device. If you have chosen to use a different group from 105, (referred to as GGG), you will have to replace all occurrences of "105," with "GGG,". 4. Now create the uic's on the appropriate disk and with the -1- appropriate protection. See readme for the protection masks needed for each directory. 5. Set default to DDN:[GGG,1] and copy the contents of [307,31] into it. 6. Execute the following MCR commands: MCR MAC @MACLIST MCR MAC TCSPWN=TCSPWN.IAS MCR MAC GETMSG=GETMSG.IAS MCR MAC ENBINT=ENBINT.IAS MCR PIP ASSEMBLE.OBS=*.OBJ MCR PIP SPAWN.F;2=SPAWNIAS.F/RE MCR PIP ADDR.F;2=ADDRIAS.F/RE MCR LBR RLIB/CR:400.:1024.:1024.=ASSEMBLE.OBS 7. Now compile the primitive functions which are written in Fortran. If your compiler is FOR, the following template tells you how to compile each file: FOR =.F/NOSN/NOVA/NOLO whereas if you use F4P, use the following template F4P =.F/NOTR/NOCK/CO:19. where you replace with the name of the file to be compiled. Those files which need to be compiled are sitepr.f, osprim.f, lib.f, spawn.f, dirprim.f. These object modules must now be placed in RLIB as in MCR LBR RLIB/RP=SITEPR,OSPRIM,LIB,SPAWN,DIRPRIM If the compiler is F4P or the Floating Point Library is to be used with FOR, execute the following command: MCR PIP LD.F=LDFP.F else MCR PIP LD.F=LDNOFP.F If the compiler is F4P, type the following command MCR PIP FC.F=FCF4P.F else MCR PIP FC.F=FCFOR.F Now compile fc.f and ld.f. If you have installed the compiler with a non-standard name, you will have to edit fc.f -2- before compiling to reflect this fact. i.e. You will have to modify the lines with "4Hf4p " or "4Hfor " to be the appropriate name for your installed compiler. 8. Now it is necessary to generate the template TKB command file which is used to task-build the tools. To do so, simply perform the following: MCR PIP TOOLS.TKB=TEMPLATE.TKB If the OTS library for the Fortran compiler is not in LB:[1,1]SYSLIB or you wish the tools to link to SYSRES, you must edit TOOLS.TKB. Simply uncomment the LIBR= line for the latter, or replace the first line with the appropriate filespec/lb line for the former. 9. Now task-build ld and fc as follows: a. Use an editor to create ld.tkb ld.tsk/cp/fp= ld.obj rlib/lb:.main. rlib/lb b. Now perform the following MCR PIP LD.TKB/AP=TOOLS.TKB MCR TKB @LD.TKB INSTALL/TASK=$$$LDS LD LDS -V FC REMOVE $$$LDS INSTALL/TASK=$$$FCS FC 10. Now build those tasks whose object modules must be placed in RLIB as follows FCS -V FIND.F MCR LBR RLIB/RP=FIND FCS -V CH.F MCR LBR RLIB/RP=CH FCS -V ED.F MCR LBR RLIB/RP=ED FCS -V RAT4.F MCR LBR RLIB/RP=RAT4 FCS -V DETAB.F MCR LBR RLIB/RP=DETAB 11. Now build all of the rest of the tools by executing @FLIST.CMD 11. Now remove FCS, install shl, fixup script files and build mail system -3- REMOVE $$$FCS INSTALL/TASK=$$$SHL SH If GGG != 105, then execute the following SHL -X FIXUP GGG,1 GGG,3 Now execute the following SHL -C "CAT MSGHLP >~MAIL/MSGHLP" MCR PIP *.*;*/PR/WO:RE If the tools disk is different from LB0:, then execute SHL -X MFIXUP DDN The following commands must be executed SHL -C "ISAM -D20 <~BIN/DICT >~BIN/DICTDX" COPY [307,32]*.* [GGG,6]*.* SHL -C "ADDR | SORT >~MAIL/ADDRESS" SHL -V MYMAIL.BLD MCR @MYMAIL REMOVE $$$SHL At this point, sh.tsk should probably be re-task-built multi-user, since it is the only installed task. If you create sh.tkb which is an image of ld.tkb with the ld. strings replaced by sh. and with the /mu switch placed after the task image, then sh.tsk will have the mu attribute. 12. The file tools.cmd shows the startup file for RSX. A similar file for use when bringing up the time-sharing executive should be done to assure that the system is available at all times. Good luck with this, and happy tool'ing. -4-