[daip] AIPS question

[Eric Greisen]

John Cartwright writes:
 > 
 > Hi Eric,
 > Thanks for yoru response.  I find that if I set "DOCRT -1"
 > in LISTR the runfile will initiate a print job.  What I would 
 > like LISTR to do is to write everything (optype='scan' so I can get a
 > summary of the sources, times, visibilities, etc) to the screen (and
 > thereby write to a message file) without being prompted by LISTR to 
 > show each new screen.  I then write out the messages to an output .txt
 > file and pick off the important pieces of information with a perl script.
 > I could, of course, tell LISTR to write its output to a separate file,
 > but doing so would create a multitude of files and I want to keep
 > my file structure simple--with a single message output file for all
 > aspects of the reduction.  Any ideas?

        When a listing program writes to the screen it does NOT write
to the message file.  With DOCRT > 0, the output is ephemeral and is
destroyed.  You can use OUTPRINT to select a single output file that
is not actually printed.  This will contain all tasks' output
including PRTMSG.

 > 
 > Thanks,
 > John Cartwright
 > 
 > On Wed, 22 Mar 2000, Eric Greisen wrote:
 > 
 > > John Cartwright writes:
 > > 
 > >  > I have an AIPS question.  I would like to include LISTR in a runfile,
 > >  > but when I do that it causes the runfile to choke because it queries me
 > >  > every time it fills the page, i.e., "Type Q to stop, just hit RETURN to
 > >  > continue".  Is there some way of disabling this so that LISTR just spits
 > >  > out its entire output in one go?
 > > 
 > >          You are clearly asking LISTR to do an interactive display of
 > > its output - namely to the CRT rather than the printer.  Either set
 > > DOCRT=-1 for printed output, suitable to a batch-like operation, or
 > > look at a few pages of LISTR on the CRT with interactive choice of
 > > when to terminate it.
 > > 
 > > Eric
 > >