[daip] problems with AIPS (part 2)

[Eric Greisen]

On 07/31/2014 04:04 PM, Hector Bravo-Alfaro wrote:
>     Hi Eric, many thanks, the problem is almost fixed:
>
>>
>> It would be better to use daip at nrao.edu.  I have been away on vacation.
>>
>
>     Ok, I switch to this address.
>
>
>> The problem below is due to something going wrong with your message
>> file.  If you delete it, and start again, then all this nonsense will go
>> away.  The file is in your first AIPS data area and is named
>> MSDuuu000.uuu\;  where uuu is your user number in extended hex (base 36).
>>
>
>     In addition to the file linked to my user number (126)
> there is another one:
>
> MSD001000.001;
> MSD03I000.03I;
>
>      I only erased the 03I, can I erase both? I'm getting quite
> much less error messages after this, and tasks seem to be
> working fine. This is the output while running AIPS:

The .001 one is the dummy file used when you start up and that is good 
to keep.  It does not affect user 126.


> AIPS 1: ZDAOPN: DELAY 1
> AIPS 1: ZDAOPN: DELAY 2
> AIPS 1: ZFI2: DELAY 1
> AIPS 1: ZFI2: DELAY 2
> AIPS 1: ZFI2: REQUEST FOR BYTES 1025 THRU = 2048
> AIPS 1: ZFIO: OPER = READ LUN = 27 NREC =        2
> AIPS 1: ZFI2: BEYOND EOF = 0
> AIPS 1: ZERROR: IN ZFI2   ERRNO = 22 (Invalid argument)
> AIPS 1: UNABLE TO READ SAVE/GET FILE NAMED LASTEXIT.  CHECK $DA01:SG*
> AIPS 1: Loading a brand new POPS vocabulary
>>
>
>
>
>
>> The LASTEXIT issue is curious.  In that same first AIPS data area do an
>>
>> ls -l SGDuuu*
>>
>> and look at ownership etc.  The file SGDuuu000.uuu\; is a directory file
>> and the others are various named SAVE/GET files one of which is
>> LASTEXIT.   Inside AIPS use the verb SGINDEX to see what the directory
>> contains.

What did the above ls -l SGD* say?

The error messages above suggest that somehow you have a 0-byte file 
when they should look more like

primate<136>$ ll SGD**.010\;
-rw-rw-r-- 1 egreisen aipsuser  28672 Jul 14 14:31 SGD010000.010;
-rw-rw-r-- 1 egreisen aipsuser 562176 Jul 14 14:31 SGD010001.010;
-rw-rw-r-- 1 egreisen aipsuser 562176 May 31  2011 SGD010002.010;
-rw-rw-r-- 1 egreisen aipsuser 562176 Apr 25  2012 SGD010003.010;
-rw-rw-r-- 1 egreisen aipsuser 562176 Jan 21  2014 SGD010004.010;


It would probably be best to rm the SGD* files and start over.  It seems 
unable to save over the top of the damaged version.

Eric Greisen