

                              IAS Readme File


This  system  has  been  successfully built on an IAS v3.1 system using the
F4P compiler, with the following restrictions:

* Background processing is not available from the shell. 

While no attempt has yet been made  to  build  it  using  the  FOR  or  F77
compilers,  there  is  no  reason  to believe that any problems will occur.
What follows below is the procedure followed in bringing up the  system  on
the IAS system, and follows closely the procedure in [307,30]toolgen.cmd. 

 1. Use  BRU  to  dump  the  contents of [307,31] and [307,37] from the SIG
    tape to a disk (known as DD0:). 

 2. Select a disk for  the  read-only  directories  (known  as  DD1:);  the
    default is LB0:. 

 3. Select  a  disk  for  the  readwrite  directories  (known as DD2:); the
    default is LB0:. 

 4. Select a group for the Tool's UIC's (known  as  GGG);  the  default  is
    105. 

 5. Create the following UIC's with the appropriate protection masks:

    DD1:[GGG,1]  /SY:RWE/OW:RWE/GR:RE/WO:RE
    DD1:[GGG,2]  /SY:RWE/OW:RWE/GR:RE/WO:RE
    DD1:[GGG,6]  /SY:RWE/OW:RWE/GR:RE/WO:RE

    DD2:[GGG,3]  /SY:RWE/OW:RWE/GR:RWE/WO:RWE
    DD2:[GGG,4]  /SY:RWE/OW:RWE/GR:RWE/WO:RWE
    DD2:[GGG,5]  /SY:RWE/OW:RWE/GR:RWE/WO:RWE

 6. SET DEFAULT DD1:[GGG,1]

 7. MCR PIP *.*=DD0:[307,31]*.*
    MCR PIP /NV=DD0:[307,37]ASM.PRE,*.F,*.FF,*.MAC,*.CMD,*.TKB,SYMBOLS. 
    MCR PIP /NV=DD0:[307,37]FINISH.IAS

 8. If  either DD1: or DD2: are not LB0:, getdir.mac will need to be edited
    to reflect that fact.  Be sure to change the appropriate branch of  the
    conditional code for IAS. 

    If  GGG  is  different from 105, getdir.mac must have all references to
    105 converted to the group number selected. 

 9. If you are using the FOR compiler with the  FPP  OTS  modules,  or  are
    using F4P/F77, then
        MCR PIP LD.FF=LDFP.FF
        MCR PIP LD.TKB=LDFP.TKB
    else
        MCR PIP LD.FF=LDNOFP.FF
        MCR PIP LD.TKB=LDNOFP.TKB


                                    -1-


                              IAS Readme File


10. If you are using F4P/F77, then
        MCR PIP FC.FF=FCF4P.FF
        If  the  compiler is installed under a name different from "$$$F4P"
        or "...F4P", then fc.ff must be edited.  Change the  occurrence  of
        3HF4P  to  3HXXX,  where  XXX  is  the  three-character name of the
        installed task "$$$XXX" or "...XXX". 
    else
        MCR PIP FC.FF=FCFOR.FF
        If the compiler is installed under a name different  from  "$$$FOR"
        or  "...FOR",  then fc.ff must be edited.  Change the occurrence of
        3HFOR to 3HXXX, where  XXX  is  the  three-character  name  of  the
        installed task "$$$XXX" or "...XXX". 

11. MCR PIP PRIM.FF=PRIMPST.FF
    If  your timezone is different from Pacific, then you must edit prim.ff
    to reflect that fact.  Perform the  substitution  that  corresponds  to
    your time zone:

    Eastern   TZONE(1)/80  becomes  TZONE(1)/69
    Central   TZONE(1)/80  becomes  TZONE(1)/67
    Mountain  TZONE(1)/80  becomes  TZONE(1)/77

12. If  you  wish  to  cause  a new version of a file be created whenever a
    tool opens a file at WRITE access, add the following line to  the  file
    asm.pre:
    
    NEWVER=0
    
    By  default,  whenever  a  file  is opened at write access, the current
    highest version is overwritten. 

13. Modify the file symbols. to reflect your local compiler and  task-build
    options.  Four lines must be added to the file:

    a. the definition for your timezone string - e.g. 
       DEFINE(TIME_ZONE,"XXX")
       Replace the string XXX with one of EST, CST, MST, PST. 
    b. the definition of your generic compiler - e.g. 
       DEFINE(FORT_COMP,YYY)
       Replace  the  string  YYY  with one of FOR or F4P.  (F77 is the same
       generic type as F4P.)
    c. the definition of your compiler's installed name - e.g. 
       DEFINE(COMP_NAME,"ZZZ")
       Replace the string ZZZ with the installed  name  of  your  compiler,
       "$$$ZZZ" or "...ZZZ". 
    d. whether  you  want  the  task  builder  to  build the tasks with the
       floating point save area - e.g. 
       DEFINE(FLOAT_PT,WWW)
       Replace the string WWW  with one of  YES  or  NO.   This  definition
       should jive with the decision made at step 9 above. 

14. Edit  the file tools.tkb to reflect local options.  All tools are built


                                    -2-


                              IAS Readme File


    using this file as the tail end of the task build command file. 

15. Assemble and compile the modules for the tools library  and  build  the
    library.    You   may   have   to   edit  the  file  f4pcompil.cmd  (or
    forcompil.cmd) if your Fortran compiler is installed with a name  other
    then F4P (or FOR). 

    MCR MAC @ASSEMBLE
    MCR PIP RLIB.OBS=*.OBJ
    MCR LBR RLIB.OLB/CR:400.:1024.:1024. 
    @F4PCOMPIL (or @FORCOMPIL)
    MCR LBR RLIB.OLB/RP=PRIM.OBJ,LIB.OBJ,IASPRIM.OBJ,RLIB.OBS
    MCR PIP RLIB.OBS;*/DE

    Do  not  be  alarmed  by modules replaced messages, as it is simply IAS
    modules replacing RSX modules. 
16. Now compile and task build the tools ld and fc,  which  permits  us  to
    automate the rest of the build procedure. 

    If compiler is F4P, then
        MCR F4P LD=LD.FF/NOTR/NOCK/CO:19./RO
        MCR F4P FC=FC.FF/NOTR/NOCK/CO:19./RO
    else
        MCR FOR LD=LD.FF/NOSN/NOVA/NOLO/RO
        MCR FOR FC=FC.FF/NOSN/NOVA/NOLO/RO

    MCR PIP LD.TKB/AP=TOOLS.TKB
    MCR TKB @LD.TKB
    Install LD.TSK as $$$LDX
    LDX -V FC
    Remove $$$LDX and install FC.TSK as $$$FCX

17. If  everything  went  OK  to  here,  we  can  now build the rest of the
    tools.  You need to check that the first two lines of the command  file
    toolbuild.cmd  is the correct way to turn off error checking by the PDS
    command file interpreter; I do not use IAS, and can only guess that  is
    similar  to  other DCL implementations.  The build procedure takes from
    one to two hours. 

    SET VERIFY
    @TOOLBUILD

18. We now have just a little bit of cleanup left to perform:

    MCR PIP DD2:[GGG,5]MSGHLP.=MSGHLP. 
    MCR PIP MSGHLP.;*/DE
    MCR PIP [GGG,6]S1.;1/RE=[GGG,1]SECT1.;0
    MCR PIP [GGG,6]S2.;1/RE=[GGG,1]SECT2.;0
    MCR PIP [GGG,6]S3.;1/RE=[GGG,1]SECT3.;0
    MCR PIP [GGG,6]S4.;1/RE=[GGG,1]SECT4.;0
    Install sh.tsk as "$$$SHX"
    SHX -V FINISH.IAS


                                    -3-


                              IAS Readme File


    MCR PIP [GGG,1]*.*;*/TR,[GGG,5]*.*;*/TR,[GGG,6]*.*;*/TR

19. You must edit tools.cmd if either  DD1:  or  DD2:  are  different  from
    LB0:,  or  if  GGG  is different from 105.  This the command file which
    you should execute when booting your system to  enable  the  tools  for
    general use. 

    Note:  I  do  not  now  remember whether it is necessary to build tools
    which are to used by multiple users from PDS (such as $$$SHL) with  the
    multi-user  switch  turned  on.   If  that  is  necessary,  perform the
    following:

    Install sh.tsk as $$$SHX
    SHX
    % ld -v hsh ?hsh.tkb
    % ed hsh.tkb
    : 1s;=;/mu=;
    : w
    : q
    % rm hsh.tsk; tkb @hsh.tkb
    % logout
    Remove $$$SHL and $$$SHX
    Reinstall hsh.tsk as $$$SHL

20. It is necessary  to  modify  the  account  database  (using  the  USERS
    utility)  for  all individuals who are going to use the tools.  Since I
    don't remember the exact octal bit masks,  I  can  only  give  you  the
    privileges needed, and you will have to map them to octal yourself. 
    
    TP1 - JP.PI
    TP2 - PR.RST, PR.CTC, PR.TEV, PR.CHN
    Job nodes >= 6

21. From  here  on in, you should be able to follow the directions found in
    [307,30]release.doc and [307,36]readme.msg. 
    
                                    Good Luck,
                                    
                                    
                                    Joe Sventek














                                    -4-

