(j3.2006) Note 8.30 in F2008

[Van Snyder]

Since an ERROR STOP statement "initiates" error termination, is it
possible that another image could execute an ERROR STOP statement before
it gets killed?  If so, the same question applies to ERROR STOP: What is
"the" stop code that is used as exit status?

On Sun, 2013-06-23 at 03:26 -0500, Bill Long wrote:
> While we're looking at this section, another question about converting 
> <stop-code> values to process exit codes - what if some images execute 
> STOP and others execute STOP 1  (or some other inconsistent 
> combination)?  Right now we (Cray) tell people that they cannot rely on 
> the exit status value if they have different stop codes.
> 
> Cheers,
> Bill
> 
> On 6/23/13 3:10 AM, Bill Long wrote:
> >
> >
> > On 6/10/13 9:50 PM, Malcolm Cohen wrote:
> >
> >>>    Did we really mean that for ERROR STOP, where the default
> >>> exit status would seem more naturally to be the value corresponding to
> >>> "abort", such as 1, and not 0.
> >>
> > ...
> >
> >>
> >> You have a good point for "ERROR STOP" without a numeric stop-code,
> >> and I would
> >> suggest that the recommendation here should be a "nonzero
> >> processor-dependent
> >> value that indicates abnormal termination".
> >>
> >
> > Is this something that needs a paper/feature request, or is it in the
> > category of corrections from the Editor?
> >
> >> Another thing is that these recommendations ought to be in normative text
> >> anyway.
> >>
> >
> > This seems more clearly an Editorial issue.
> >
> > Cheers,
> > Bill
> >
> >
>