(j3.2006) Do these questions need interps?
Van Snyder
Van.Snyder
Fri Oct 30 16:26:39 EDT 2015
There were several questions in 15-226 that were deleted without answers
in 15-226r1 and subsequent revisions.
Do the answers appear somwehere, or do they need interps, or could we
clarify them otherwise?
[229:7+ 9.6.4.8.3p22+ 229:19-21 9.6.4.8.3p28] Is input (via an input
list) permitted to the parent data transfer statement's internal file?
Is output (via an internal file) permitted to the parent data transfer
statement's internal file? 9.6.4.8.3p28 does not address these
questions.
[232:10-12 9.7.1p3] If the input operation completed successfully, does
the variable in the SIZE= specifier become defined?
[233:16-19 9.8.1p1] Is it permitted to reference a unit that is not
connected?
[236:1-29.10.1p3] What value is assigned to, e.g., POS= or SIZE= if
INQUIRE is executed while asynchronous I/O is in progress? Should
INQUIRE be a wait operation in this case?
[238:33-35 9.10.2.14] An ID= specifier is prohibited in a child data
transfer statement. What happens if an ID= specifier appears in an
INQUIRE statement and the unit is the "unit" argument of a defined I/O
subroutine?
[239:9-15 9.10.2.17] A REC= specifier is prohibited in a child data
transfer statement. What happens if a NEXTREC= specifier appears in
an INQUIRE statement and the unit is the "unit" argument of a defined
I/O subroutine?
[240:10-15 9.10.2.22] A POS= specifier is prohibited in a child data
transfer statement. What happens if a POS= specifier appears in an
INQUIRE statement and the unit is the "unit" argument of a defined I/O
subroutine?
[239:15 9.10.2.17] Is the order of completion of the pending data
transfers important to determining the value assigned to the variable in
a NEXTREC= specifier?
[239:18 9.10.2.18] What value is assigned to the variable in the NUMBER=
specifier if several units are attached to the file?
[243:35-37 9.11.14p1(1)] To which list item does this description apply?
All of the ones for which input has not yet occurred?
More information about the J3
mailing list