[daip] 31DEC99 install

[Patrick P. Murphy]

On Fri, 14 Apr 2000 15:58:56 -0400 (EDT), Shami Chatterjee
   <shami at spacenet.tn.cornell.edu> said: 

SC> I decided that I needed to upgrade, so I've just finished building
SC> 31DEC99 at Cornell (without errors), and run FILAIP, POPSGN.

What version were you using when you ran FILAIP?  If it wasn't 31DEC99,
then certain files would not have been created.

SC> I've changed the VERSION definitions so that TST and CVX point to
SC> 31DEC99.

If you did this after running FILAIP/POPSGN, then this explains why:

SC> AIPS 1: ZOPEN: FILE TSTMEM:MED000000;        NOT FOUND

as the TSTMEM area ($AIPS_VERSION/$ARCH/MEMORY/) is version-specific.
Here's what to do from the command line, assuming a bourne or korn or bash
flavor shell:

    bash$ $CDTST
    AIPS_VERSION=/wherever/31DEC99              (you have to see this!)
    bash$ mkdir $TST/$ARCH/TEMPLATE
    bash$ export DA00=$TST/$ARCH/TEMPLATE
    bash$ export DA01=/tmp
    bash$ $LOAD/FILAIP.EXE

    (disks 35, cat entries -100; interactive 8, batch 2; tape drives 4)
    (these are my suggested values)

    bash$ $LOAD/POPSGN.EXE
    0 POPSDAT TST
    >
    ...
    bash$ unset DA01; . /wherever/LOGIN.SH      (to restore sanity)

This will create and initialize the memory file that was missing, and also
set you up with a good template area for that architecture.  You can
delete the MSD001000.001\; file in /tmp after you're done with this little
exercise. 

SC> (Also, XAS fails over shared memory - this is an old problem and I'll
SC> just use my older working XAS instead.)

Why does it fail?  If AIPS and XAS are both running on the same host, it
should work.  If you have a sun system and are running the stock openwin
based X server, AND you have a resolution greater than 1152x900, then you
need to modify /etc/system with this line near the end:

set shmsys:shminfo_shmmax=10485760

This increases the max size of a shared memory segment to 10Megs, up from
the Sun-imposed default of 1 Meg.  On 1280x1024 screens, XAS's size for
each 8-bit image plane is over 1024x1024, hence it wants to be able to use
a larger shared memory segment.

If you are trying to use shared physical memory between XAS on one host
and AIPS on another, that won't work :-)  But you probably knew that
anyway. 

SC> I took a stab at running SYSETUP:

You can't run SYSETUP until you have set up the template area.

SC> (While ELLA is a SUL, there is no TEMPLATE area under SUL either.)

The template areas can be shared among all similarly-byte-ordered
systems.  So you can make $TST/SUL/TEMPLATE be a symlink to
$TST/SOL/TEMPLATE or vice versa, and also have SGI, HP and IBM areas point
to it.  If you have ALPHA, LINUX, AXLINUX etc. then they need to be
separate.  

SC> * Is this expected behavior? Or what else do I need to do? 

See above.  I think it was just a case of doing things in slightly
different order.  

SC> * Also, do I need to register this system in some way?

Eventually; don't worry about it for now.  I need to work on allowing the
(somewhat botch of a) registration scheme allow non-"15" versions.  When
I've fixed it, I'll send out a note to the bananas list.

SC> * Does the cron job have to be enabled before I can proceed?

You probably want to get the MNJ key first.  I'll attach it in a separate
message. 

				- Pat
-- 
  Patrick P. Murphy, Ph.D.            Division Head, Charlottesville Computing
  (804) 296-0372, 296-0236                National Radio Astronomy Observatory
  Home: http://www.goof.com/~pmurphy/   Work: http://www.cv.nrao.edu/~pmurphy/
   "Linux is Inevitable."  "Why?"  "Because it's alive!" - John MadDog Hall