Jeff,
 
    Have you  set an InstPw  in LOCAL  SYSVARS?  If so,  LISTSERV will
leave the  SHIPMENT file in it's  reader, in USER hold.   According to
your LISTSERV (from  the INSTALL STATUS command), it  has received the
MEMO_1.5k  SHIPMENT, and  sent it  to you.   It would  appear in  your
reader as MEMO15K  UPDATE (not the usual UPD15K MEMO,  and no, I don't
know why Eric named it that).
 
    The  CODE_1.5k SHIPMENT  doesn't  show up  in  the INSTALL  STATUS
output,  so it  hasn't  arrived yet  I  only got  mine  at 11:30  this
morning, due to  a power failure.  If yours comes  via RUTVM1 (I don't
know if it does), then it may be on the way.
 
Phil,
 
    There should  have been a copy  of either LISTINST MEMO  or UPD15J
MEMO in the package you received.   Due to the large number of changes
between  1.5i  and   1.5j,  Eric  simply  updated   and  reissued  the
Installation Guide,  and sent it out  as both of those  files.  If you
didn't get a copy, let me know and I'll send you mine.
 
    There are  a few things you  need to do after  installing the 1.5j
update, including building a LOCAL SYSVARS file (by customizing SAMPLE
SYSVARS), ERASEing  LSV$PROF EXEC,  etc.  You shouldn't  need to  do a
NODESGEN, the upgrade process will take care of that itself.  The only
problem I've found is that LISTSERV  expects that all of its files are
on the A-disk.  If,  like me, you were taught to put  code and data on
separate disks,  be sure  that the  code disk is  an extension  of the
A-disk, and that  the MIG_* EXECs and  * FILE*s are on  the A-disk (as
well as the LISTs, of course).
 
Ross