[daip] Fwd: Error starting AIPS 31DEC21
Eric Greisen
egreisen at nrao.edu
Wed Apr 14 16:42:23 EDT 2021
-------- Forwarded Message --------
Subject: Re: [daip] Error starting AIPS 31DEC21
Date: Wed, 14 Apr 2021 14:40:41 -0600
From: Eric Greisen <egreisen at nrao.edu>
Organization: National Radio Astronomy Observatory
To: Joseph D Gelfand <jg168 at nyu.edu>, ", daip"@nrao.edu
On 4/14/21 1:37 PM, Joseph D Gelfand via Daip wrote:
> Hello,
>
> Sorry to bother you, but when I attempt to start AIPS on my Linux
> machine, it "hangs" after I enter my AIPS ID, and returns the following
> message:
>
> AIPS 1: ZOPEN: LUN = 13 ALREADY OPENED IN FTAB
> AIPS 1: ACCOUNT: OPEN ERROR 1
> AIPS 1: ZABORS: signal 2 received
> AIPS 1: ABORT!
>
> If I enter a different AIPS ID, the same thing happens with a longer
> error message:
> ZMSGOP: FILE DA01:MSD1AO000.1AO; NOT FOUND
> MSGWRT ERROR 2 AT OPEN
> AIPS 1: ZOPEN: LUN = 13 ALREADY OPENED IN FTAB
> ZMSGOP: FILE DA01:MSD1AO000.1AO; NOT FOUND
> MSGWRT ERROR 2 AT OPEN
> AIPS 1: ACCOUNT: OPEN ERROR 1
> ZMSGOP: FILE DA01:MSD1AO000.1AO; NOT FOUND
> MSGWRT ERROR 2 AT OPEN
> AIPS 1: ZABORS: signal 2 received
> ZMSGOP: FILE DA01:MSD1AO000.1AO; NOT FOUND
> MSGWRT ERROR 2 AT OPEN
> AIPS 1: ABORT!
>
> Any advice as to how I can fix this problem? Thanks a lot, and hope all
> is well -- Yosi
The longer messages are just that that user number does not yet have a
message file.
LUN 13 is not used by anything in AIPS until the ACOUNT call so it
cannot be in use. Furthermore, any error in ACOUNT is ignored. So
there is something else causing the abort and probably the erroneous
already in use message. The suggestion is that your version of AIPS.EXE
is somehow corrupt. Did you run a MNJ recently? AIPS was relinked a
day or 2 ago. Perhaps you should
cd to $LOAD ($AIPS_ROOT/31DEC21/LNX64/LOAD)
ls -l AIPS* What are the dates and times on these?)
mv AIPS.EXE AIPS.EXE.old
and then run a MNJ again.
I'm sorry that I cannot think of anything more clever.
ERic Greisen
More information about the Daip
mailing list