Path: utzoo!mnetor!uunet!husc6!hao!gatech!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!uiucdcs!uxc.cso.uiuc.edu!uicsrd.csrd.uiuc.edu!hoefling
From: hoefling@uicsrd.csrd.uiuc.edu
Newsgroups: comp.sys.apollo
Subject: Re: Fooling Fortran
Message-ID: <11400005@uicsrd.csrd.uiuc.edu>
Date: 27 Jan 88 16:06:00 GMT
References: <11400004@uicsrd.csrd.uiuc.edu>
Lines: 30
Nf-ID: #R:uicsrd.csrd.uiuc.edu:11400004:uicsrd.csrd.uiuc.edu:11400005:000:685
Nf-From: uicsrd.csrd.uiuc.edu!hoefling    Jan 27 10:06:00 1988


Well, the (800) 2APOLLO help line came up with a real solution this time.

It is straightforward and I wonder why it took so many calls and so long
for them get it.  Anyway, here is a way to pass back a status value to
the c-shell:

%include '/sys/ins/base.ins.ftn'
%include '/sys/ins/pgm.ins.ftn'

      call pgm_$set_severity(<severity-code>)
      call pgm_$exit
      end

where <severity-code> is one of:

pgm_$ok
pgm_$true
pgm_$false
pgm_$warning
pgm_$error
pgm_$output_invalid
pgm_$internal_error
pgm_$program_faulted

Any other value for the <severity-code> causes the status variable in the
c-shell to get the value 0.  So, you can't use it to return just any old
value.

Jay