《ISO-1989-2002.pdf》由会员分享,可在线阅读,更多相关《ISO-1989-2002.pdf(887页珍藏版)》请在三一文库上搜索。
1、ICS 35.060 Ref. No. ISO/IEC 1989:2002/Cor.2:2006(E) ISO/IEC 2006 All rights reserved Published in Switzerland INTERNATIONAL STANDARD ISO/IEC 1989:2002 TECHNICAL CORRIGENDUM 2 Published 2006-06-15 INTERNATIONAL ORGANIZATION FOR STANDARDIZATION ORGANISATION INTERNATIONALE DE NORMALISATION INTERNATIONA
2、L ELECTROTECHNICAL COMMISSION COMMISSION LECTROTECHNIQUE INTERNATIONALE Information technology Programming languages COBOL TECHNICAL CORRIGENDUM 2 Technologies de linformation Langages de programmation COBOL RECTIFICATIF TECHNIQUE 2 Technical Corrigendum 2 to ISO/IEC 1989:2002 was prepared by Joint
3、Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 22, Programming languages, their environments and system software interfaces. The defect reports associated with these changes are contained in Record of Response 2 for ISO/IEC 1989:2002. The related defect report number is i
4、ndicated in brackets at the end of each change item. DR-23, for example, is a reference to Defect Report 1989/001. NOTE Page numbers in various PDF versions might differ slightly from the page numbers shown in these change descriptions. 1. Page 58, 7.2.19.3, Turn Directive, add the following as new
5、general rule 3a: “If specified within a statement, the TURN directive does not apply to any phrase of that statement. That TURN directive applies to any succeeding statement in the sequence of source lines, whether or not that succeeding statement is within the scope of the statement in which the TU
6、RN directive is specified. ” DR-21 2. Page 58, 7.2.19.3, Turn Directive, general rule 4, delete the second sentence (beginning “If specified within a statement .”). DR-21 3. Page 58, 7.2.19.3, Turn Directive, general rule 6, delete the last sentence (beginning “If specified within a statement .”). D
7、R-21 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/02/2007 07:32:53 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 1989:2002/Cor.2:2006(E) 2 IS
8、O/IEC 2006 All rights reserved 4. Page 97, 8.4.2.11.2, Data-address-identifier, syntax rule 4, add the following note under the rule: “NOTE The effect of this rule, along with 8.4.2.11.3, Data-address-identifier, general rule 2, is to produce a restricted data-pointer.” DR-18 5. Page 112, 8.5.2.7, N
9、ational category, delete item 3. DR-35 6. Page 176, 11.2.2, CLASS-ID paragraph, syntax rules: add a new rule as follows: “10) A given parameter-name shall not appear more than once in a USING clause.” DR-32 7. Page 180, 11.5.2, INTERFACE-ID paragraph, syntax rules: add two new rules as follows: “6)
10、A given interface-name shall not appear more than once in an INHERITS clause. 7) A given parameter-name shall not appear more than once in a USING clause.” DR-32 8. Page 185, 11.8.5.1, ENTRY-CONVENTION, General format: change to read “ ENTRY-CONVENTION IS COBOL entry-convention-name-1 ” DR-30 9. Pag
11、e 185, 11.8.5.3, ENTRY-CONVENTION, General rules: move the note from Rule 2 to Rule 1, and then replace Rule 2 with the following 3 rules: “2) When COBOL is specified, the naming convention and mapping of method-names and program- names are as specified in 8.3.1.1.1, User-defined words; other aspect
12、s of the entry convention are implementor-defined. 3) When entry-convention-name-1 is specified, the meaning of the entry convention is implementor- defined. 4) When ENTRY-CONVENTION is not specified, the entry convention used is as follows: a. If a class definition includes the INHERITS clause, the
13、 entry convention is inherited from the first class specified in the INHERITS clause. b. If an interface definition includes the INHERITS clause, the entry convention is inherited from the first interface specified in the INHERITS clause. c. In all other cases, the entry convention is COBOL. ” DR-30
14、 10. Page 245, 13.9.2, Constant entry, replace syntax rule 3 with the following: “Data-name-1 and data-name-2 may be qualified and subscripted. All subscripts of data-name-1 and data- name-2 shall be literals.” DR-23 11. Page 356, 13.16.55, TYPE clause, general rule 3: replace with the following: “I
15、f a VALUE clause is specified in the data description of the subject of the entry, the content of the literal associated with that VALUE clause is used for the initial value associated with the subject of the entry. When the description of type-name-1 includes an implicit PICTURE clause derived from
16、 a VALUE clause, that implicit PICTURE clause becomes part of the description of the subject of the entry. ” DR-22 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/02/2007 07:32:53
17、MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 1989:2002/Cor.2:2006(E) ISO/IEC 2006 All rights reserved 3 12. Page 393, 14.5.12.1.4, Exception objects, Second paragraph (beginning “If an exception object is raised by a RAISE statement .”), add the following as a ne
18、w sentence at the end of the paragraph: “If there is no associated declarative, execution continues as specified in the RAISE statement” DR-25 13. Page 396, 14.5.12.1.5, Exception-names and exception conditions, Table 14, entry for EC-RAISING-NOT-SPECIFIED: delete “EC-IMP or” from the description. D
19、R-28 14. Page 454, 14.8.17.2, GOBACK statement: add the following new syntax rules: “2) Exception-name-1 shall be a level-3 exception-name as specified in 14.5.12.1, Exception conditions. If exception-name-1 is a level-3 exception-name for EC-USER, exception-name-1 shall be specified in the RAISING
20、phrase of the procedure division header of the source element in which this GOBACK statement is contained. 3) Identifier-1 is a sending operand. 4) Identifier-1 shall be an object reference, subject to the following constraints: a) If the data description entry of identifier-1 specifies a class-name
21、, the class identified by that class-name or one of the superclasses of that class is specified in the RAISING phrase of the procedure division header of the source element containing this GOBACK statement and the presence or absence of the FACTORY phrase is the same in the data description entry of
22、 identifier-1 as in the RAISING phrase of the procedure division header of the containing source element. b) If the data description entry of identifier-1 specifies an interface-name, the interface referenced by that interface-name shall conform to an interface specified in the RAISING phrase of the
23、 procedure division header of the source element containing this GOBACK statement. c) If the data description entry of identifier-1 specifies an ACTIVE-CLASS phrase, the class of the object containing the GOBACK statement or one of the superclasses of that class is specified in the RAISING phrase of
24、 the procedure division header of the source element containing this GOBACK statement. d) Identifier-1 shall not be a universal object reference. 5) The LAST phrase may be specified only in a declarative procedure. ” DR-33 15. Page 459, 14.8.19.3, INITIALIZE statement: delete “or table format” from
25、general rule 5c1b. DR-29 16. Page 459, 14.8.19.3, INITIALIZE statement: add a new general sub-rule as 5c1c to read: “A table format VALUE clause is specified in the data description entry of the elementary item and that VALUE clause specifies a value for the particular occurrence of the elementary d
26、ata item.” DR-29 17. Page 495, 14.8.28.3, RAISE statement, replace general rules 1 through 3 with the following two general rules: “1) If exception-name-1 is specified, the associated exception condition is raised and EXCEPTION- OBJECT is set to null. If there is no applicable declarative and the ex
27、ception condition is non-fatal, processing continues with the statement following the RAISE statement. 2) If identifier-1 is specified, EXCEPTION-OBJECT is set to reference the object referenced by identifier- 1. If there is no applicable declarative, processing continues with the statement followin
28、g the RAISE statement. ” DR-25 18. Page 567, 15.2, Arguments, rule 8, change “usage” to “class” DR-39 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/02/2007 07:32:53 MDTNo reprodu
29、ction or networking permitted without license from IHS -,-,- ISO/IEC 1989:2002/Cor.2:2006(E) 4 ISO/IEC 2006 All rights reserved 19. Page 592, 15.23, EXCEPTION-FILE function, Returned values: add a new entry between sub-items a and b as follows: “a1) The returned value is two alphanumeric spaces when
30、 the last exception status indicates an EC-I-O exception condition that originates from one of the following statements: a RAISE statement an EXIT statement with a RAISING phrase that specifies an EC-I-O exception-name a GOBACK statement with a RAISING phrase that specifies an EC-I-O exception-name
31、” DR-27 20. Page 593, 15.24, EXCEPTION-FILE-N function, Returned values: add a new entry between sub-items a and b as follows: “a1) The returned value is two national spaces when the last exception status indicates an EC-I-O exception condition that originates from one of the following statements: a
32、 RAISE statement an EXIT statement with a RAISING phrase that specifies an EC-I-O exception-name a GOBACK statement with a RAISING phrase that specifies an EC-I-O exception-name ” DR-27 21. Page 809, E.26, ENTRY-CONVENTION clause: replace the first sentence with the following sentence: “The ENTRY-CO
33、NVENTION clause specifies how a runtime element is to receive control.” DR-30 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 04/02/2007 07:32:53 MDTNo reproduction or networking perm
34、itted without license from IHS -,-,- ICS 35.060 Ref. No. ISO/IEC 1989:2002/Cor.1:2006(E) ISO/IEC 2006 All rights reserved Published in Switzerland INTERNATIONAL STANDARD ISO/IEC 1989:2002 TECHNICAL CORRIGENDUM 1 Published 2006-06-15 INTERNATIONAL ORGANIZATION FOR STANDARDIZATION ORGANISATION INTERNA
35、TIONALE DE NORMALISATION INTERNATIONAL ELECTROTECHNICAL COMMISSION COMMISSION LECTROTECHNIQUE INTERNATIONALE Information technology Programming languages COBOL TECHNICAL CORRIGENDUM 1 Technologies de linformation Langages de programmation COBOL RECTIFICATIF TECHNIQUE 1 Technical Corrigendum 1 to ISO
36、/IEC 1989:2002 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 22, Programming languages, their environments and system software interfaces. The defect reports associated with these changes are contained in Record of Response 1 for ISO/IEC 1989:2002.
37、The related defect report number is indicated in brackets at the end of each change item. DR-1, for example, is a reference to Defect Report 1989/001. 1. Page 1, Scope, third paragraph, third bullet, change “classes” to “classes and interfaces”. DR-10 2. Page 68, 8.3.1.1.1, User-defined words, last
38、paragraph (beginning “When a CALL statement, a CANCEL statement, .”), item 1, change in part to read: “. determined by the entry convention indicated by the description of the program to be called, as specified in 12.2.7.3, REPOSITORY paragraph, General rule 10.” DR-8 3. Page 166, 9.3.12, Parameteri
39、zed classes, third paragraph, first sentence, change in part to read: “When a class is specified as the parameterized class in an EXPANDS phrase in the REPOSITORY paragraph, .” DR-10 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=IHS Employee
40、s/1111111001, User=Wing, Bernie Not for Resale, 04/02/2007 07:32:53 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 1989:2002/Cor.1:2006(E) 2 ISO/IEC 2006 All rights reserved 4. Page 166, 9.3.13, Parameterized interfaces, third paragraph, first sentence, change in p
41、art to read: “When an interface is specified as the parameterized interface in an EXPANDS phrase in the REPOSITORY paragraph, a new interface .” DR-10 5. Page 176, 11.2.2, CLASS-ID paragraph, Syntax rules, syntax rule 4, delete the second sentence (beginning “Class-name-2 shall not be the name .”) D
42、R-10 6. Page 206, 12.2.7.3, REPOSITORY paragraph, General rules, general rule 1, add a second paragraph as follows: “If class-name-1 is a class described with the USING phrase, class-name-1 may be specified only in the REPOSITORY paragraph.” DR-10 7. Page 207, 12.2.7.3, REPOSITORY paragraph, General
43、 rules, general rule 7, add a second paragraph as follows: “If interface-name-1 is an interface described with the USING phrase, interface-name-1 may be specified only in the REPOSITORY paragraph.” DR-10 8. Page 286, 13.16.22.3, FORMAT clause, General rules, delete general rule 2)c)3.d (beginning “I
44、f the literal is a fixed-point numeric .”) and general rule 2)c)3.e (beginning “If the literal is a floating-point numeric .”). DR-3 9. Page 356, 13.16.55.3, TYPE clause, General rules, general rule 1, delete the note that immediately follows the rule. DR-17 10. Page 359, 13.16.56.2, TYPEDEF clause,
45、 Syntax rules, add a new syntax rule after syntax rule 1 as follows: “2) The description of the subject of the entry, including its subordinate items, shall not contain a TYPE clause that directly or indirectly references this type definition.” DR-17 11. Page 396, Table 14 Exception-names and except
46、ion conditions, entry for EC-OO-RESOURCE, in the Description column, delete “or expand the object”. DR-10 12. Pages 407 and 408, 14.7.2.2, Elementary items, first paragraph, replace item 2 and its subitems a, b, c, d, and e with the following: “2) If the returning item in the activated element is de
47、scribed with an ACTIVE-CLASS phrase, the conformance rules are the same as the conformance rules for a SET statement specified in the activating element with the following operands: a) A receiving operand that is the returning item in the activating element. b) A sending operand that is an object reference described as follows: a) If the activated method is invoked with a class-name, the sending object reference is described with that same class-name and an ONLY phrase. b) If the activated method is invoked with the predefined object reference SELF or SUPER, the sendin
链接地址:https://www.31doc.com/p-3776702.html