DMIS S I R Entry

Dimensional Measuring Interface Standard
Standard Improvement Request

SIR No.
97-31
DMIS Release
3.0
SIR Type
Other
Severity
Documentation Deficiency
Status
Resolved
Date Submitted
March 6 1997
Date Validated
March 6 1997
Date In Process

Date Referred

Date Vote Pending

Date Closed
August 20 1998
Action
Clarifications
Submitted By
Dietmar May
Object Workshops, Inc.
PO Box 597
Whytheville VA 24382
USA
Phone: (540)223-1145
Fax: (540)223-1241
dcmay@object-workshops.com

Problem Topic
OUTPUT: When does it occur for xxx?

Problem Description
The following statements have OUTPUT formats, but do not indicate when output occurs: all FEATures, all TOLs, WKPLAN, SNSDEF/PROBE, CRGDEF, CALL, CLOSE, DISPLY, OPEN, TEXT/OUTFIL, TEXT/RES, DMIS.

References
None

Related SIRs
None

Suggested Resolution
--- Reasonable guesses as to the time of output have been attempted:

all FEATures --- during OUTPUT/
all TOLs --- during OUTPUT/
WKPLAN --- when exec'd
SNSDEF/PROBE --- during OUTPUT/
CRGDEF --- when exec'd
CALL --- when exec'd (but see example DMISMD)
CLOSE --- when exec'd
DISPLY --- when exec'd
OPEN --- when exec'd
TEXT/OUTFIL --- when exec'd TEXT/RES --- after response received
DMIS --- when exec'd

Support Documentation
None


Resolution

Warning!!

The following statement is only a resolution to a Standard Improvement Request (SIR) and is NOT part of the current DMIS standard, nor is it guaranteed to become part of the next revision of the DMIS standard even if voted and accepted by the DMIS National Standards Committee. This resolution is tentative because it may not be incorporated into the next version of the standard, it could be changed prior to the next release, or it could be changed as the result of the "public review and comment" period required for the next version of the standard. If you choose to use this tentative resolution, you do so at your own risk since at this time it is not part of the DMIS standard.

Resolved per 8/98 DNSC Meeting Oak Ridge, TN.
Added text to FEAT/, TOL/, SNSDEF/PROBE,WKPLAN, CRGDEF, CALL, CLOSE, DISPLY, OPEN, TEXT/OUTFIL, TEXT/RES, and DMIS.
Change example in DMISMN.
Global text change.

1) The following sentence is to be placed at the end of each of the FEAT/, TOL/, and SNSDEF/PROBE definition pages:

"The XXX statement is passed to the output file by execution of the OUTPUT statement."

2)The following sentence is to be placed at the end of the definition pages for; WKPLAN, CRGDEF, CALL, CLOSE, DISPLY, OPEN, TEXT/OUTFIL, TEXT/RES, and DMIS:

"The XXX statement is passed to the output file when executed."

3)Change the example for DMISMN on page 170, in the (DMIS OUTPUT FILE) area add the following line after the FILNAM line:

"CALL/EXTERN,DME,'9W3309.SUB'"

4)Additionally, a global change of any reference to " ...passed on to the output ..." or "... passed through to the output ..." or any similar occurrances, be changed to "... passed to the output...". This will provide phrase consistency.

Attachments
None

Notes

Added by Mike Holloway, hkm@ornl.gov on 7/31/1998

Discussion of this SIR found in Gaithersburg meeting minutes of 4/10/97.

I generally concur with the resolutions. The statement that is in the standard for statements that are output when executed is:

The XXX statement is passed on to the output file when executed.

This seems to be the case for those indicated above as "when exec'd". See also section 3.13.

The example for DMISMD is actually on the next page under DMISMN. This example does not show the output of the CALL statement. This should be added to the example.

The TEXT/RES,... statement is put in the output file when the TEXT/QUERY,... statement is executed. It is not very clear, but it would seem that the 'text' in the TEXT/RES output would be the response to the TEXT/QUERY. The label is used to associate the response with the query.

For output of FEAT and TOL data, refer to sections 3.10.5 and 3.13 and the description of OUTPUT.

Added by Interpretation Sub-Committee, gph5@chrysler.com on 8/4/1998

The following sentence is to be placed at the end of each of the FEAT/, TOL/, and SNSDEF/PROBE definition pages:

"The XXX statement is passed on to the output file by execution of the OUTPUT statement."

The following sentence is to be placed at the end of the definition pages for; WKPLAN, CRGDEF, CALL, CLOSE, DISPLY, OPEN, TEXT/OUTFIL, TEXT/RES, and DMIS:

"The XXX statement is passed on to the output file when executed."

Change the example for DMISMN on page 170, in the (DMIS OUTPUT FILE) area add the following line after the FILNAM line:

"CALL/EXTERN,DME,'9W3309.SUB'"

Added by DNSC, rui@ornl.gov on 8/6/1998

The following sentence is to be placed at the end of each of the FEAT/, TOL/, and SNSDEF/PROBE definition pages:

"The XXX statement is passed to the output file by execution of the OUTPUT statement."

The following sentence is to be placed at the end of the definition pages for; WKPLAN, CRGDEF, CALL, CLOSE, DISPLY, OPEN, TEXT/OUTFIL, TEXT/RES, and DMIS:

"The XXX statement is passed to the output file when executed."

Change the example for DMISMN on page 170, in the (DMIS OUTPUT FILE) area add the following line after the FILNAM line:

"CALL/EXTERN,DME,'9W3309.SUB'"

Additionally, any reference to " ...passed on to the output ..." or "... passed through to the output ..." or any similar occurrances, be changed to "... passed to the output..." for consistency.

Return to SIR List