(j3.2006) 14-253 and 14-254

[John Reid]

Whitlock, Stan wrote:
> Hi, John ? I notice that in the J3 m205 area that 14-253 and 14-254 are
> identical.  Thanks                                  /Stan
>

Thanks for telling me about this, Stan. Unfortunately, the J3 server is 
down so I cannot check what happened and correct it. Here are the two 
documents that I meant to send.

Sorry about this.

John.
-------------- next part --------------
                                                           J3/14-253
To: J3
From: John Reid
Subject: Known inactive images
Date: 2014 Oct 9

Discussion
----------

The changes proposed here are based on a suggestion in my ballot.
I think we need a clear definition of what is meant by a "known"
failed or stopped image. And if we add the concept of a stalled image, 
as proposed in 14-250, I think we need a clear definition of what is 
meant by a "known" stalled image.

Edits to N2027:
---------------

[5:32+] Add
"<3.4.1>
<known failed image>
image known by the executing image to have failed (5.8)"

[5:32+] Add
"<3.4.2>
<known stalled image>
image known by the executing image to have stalled (5.9)"
Note. This assumes that the concept of stalled image, see 14-250 is
accepted and subclause 5.9 has been added. 

[14:7+] Add paragraph
"If the executing image detects that another image has failed by 
executing an image control statement whose STAT= specifier is assigned 
the value STAT_FAILED_IMAGE or invoking a collective or atomic 
subroutine whose STAT argument is set to STAT_FAILED_IMAGE, the other
image is known by the executing image to have failed."

[14:7+] Add to the end of the new paragraph "If the failure 
has occurred as described in the previous paragraph, the image ceases 
to be known as having failed after execution of the relevant END TEAM  
statement."
Note. This assumes that the concept of stalled image, see 14-250 is
not accepted. 

[14:7+] Add paragraph to end of 5.9:
"If the executing image detects that another image has stalled by 
executing an image control statement whose STAT= specifier is assigned 
the value STAT_STALLED_IMAGE or invoking a collective or atomic 
subroutine whose STAT argument is set to STAT_STALLED_IMAGE, the other
image is known by the executing image to have stalled."
Note. This assumes that the concept of stalled image, see 14-250 is
accepted and subclause 5.9 has been added. 

[25:31-35] Delete sentence "If the executing image ... failed."
Reason: Let's instead have a clear definition in 5.8.

[40:15+} Add
"{In 13.8.2.24 STAT_STOPPED_IMAGE, insert new paragraph after 
paragraph 1}
"If the executing image detects that another image has initiated normal
termination by executing a statement whose STAT= specifier is assigned 
the value STAT_STOPPED_IMAGE or invoked a collective or atomic 
subroutine whose STAT argument is set to STAT_STOPPED_IMAGE, the other
image is known by the executing image to have initiated normal
termination."
-------------- next part --------------
                                                           J3/14-254
To: J3
From: John Reid
Subject: NUM_IMAGES: remove FAILED argument
Date: 2014 Oct 9

Discussion
----------

In his ballot, Reinhold Bader says that we no longer need to return 
the number of failed images from NUM_IMAGES now that we have the 
intrinsic FAILED_IMAGES. Edits are proposed here.

Edits to N2027:
---------------

[29:13-14] Delete "the optional argument FAILED".

[29:20-22] Delete paragraph.

[37:3+] In the entry for NUM_IMAGES, delete "[FAILED]" thrice.

[39:1-2] Delete "[FAILED]" thrice.

[39:9-10] Delete paragraph for FAILED.

[39:14-15] Delete paragraph for FAILED.