Status: AVAILABLE |
In order to read or download ibm cobol reference manual ebook, you need to create a FREE account.
Download Now! |
eBook includes PDF, ePub and Kindle version
| ✔ Register a free 1 month Trial Account. |
| ✔ Download as many books as you like (Personal use) |
| ✔ Cancel the membership at any time if not satisfied. |
| ✔ Join Over 80000 Happy Readers |
Search support or find a product: Search Our apologies No results were found for your search query. Tips To return expected results, you can: Reduce the number of search terms. Each term you use focuses the search further. Check your spelling. A single misspelled or incorrectly typed term can change your result. If so, follow the appropriate link below to find the content you need. Our apologies Search results are not available at this time. Please try again later or use one of the other support options on this page. No results were found for your search query. If so, follow the appropriate link below to find the content you need. IBM Doc Buddy also aggregates mainframe content including blogs, videos, IBM Knowledge Center topics, and Thought Leader opinions. The app is available in both Apple App Store and Google Play. IBM Doc Buddy also aggregates mainframe content including blogs, videos, IBM Knowledge Center topics, and Thought Leader opinions. The app is available in both Apple App Store and Google Play. Scripting appears to be disabled or not supported for your browser. Enable JavaScript use, and try again. When you sign in to comment, IBM will provide your email, first name and last name to DISQUS. That information, along with your comments, will be governed by By commenting, you are accepting the. Subject to IBM's valid intellectual\nproperty or other legally protectable rights, any functionally equivalent product, program,\nor service may be used instead of the IBM product, program, or service. The evalu-\nation and verification of operation in conjunction with other products, except those\nexpressly designated by IBM, are the responsibility of the user.\n \n IBM may have patents or pending patent applications covering subject matter in this\ndocument. The furnishing of this document does not give you any license to these\npatents. Object-oriented\nCOBOL is not supported on VM.
http://sunn-tech.com/mmag/library/upload/products/file/1605846484659943397.xml
\n \n Use this book in conjunction with the IBM COBOL Programming Guide for your plat-\nform.\n \n IBM Extensions\n IBM extensions generally add to language element rules or restrictions. In the hard-\ncopy, published book, IBM extensions appear in gray ink. Either identifier-1 or literal-1 must be coded.\n3 The item 1 fragment is optional; it can be coded or not, as required by the application. If item 1\n \n is coded, it can be repeated with each entry separated by one or more COBOL separators.\nEntry selections allowed for this fragment are described at the bottom of the diagram.\n \n 4 The operand identifier-3 and associated TO key word are required and can be repeated with\none or more COBOL separators separating each entry. Each entry can be assigned the key\nword ROUNDED.\n \n 5 The ON SIZE ERROR phrase with associated imperative-statement-1 are optional. If the ON\nSIZE ERROR phrase is coded, the key word ON is optional.\n \n 6 The END-STATEMENT key word can be coded to end the statement. It is not a required\ndelimiter.\n \n 7\n \n DBCS Notation\n Double-Byte Character Strings (DBCS) in literals, comments, and user-\n \n defined words are delimited by shift-out and shift-in characters. However, all such\norganizations are requested to reproduce this section as part of the introduc-\ntion to the document. Those using a short passage, as in a book review, are\nrequested to mention COBOL in acknowledgment of the source, but need not\nquote this entire section.\n \n COBOL is an industry language and is not the property of any company or\ngroup of companies, or of any organization or group of organizations.\n \n No warranty, expressed or implied, is made by any contributor or by the\nCOBOL Committee as to the accuracy and functioning of the programming\nsystem and language. Moreover, no responsibility is assumed by any contrib-\nutor, or by the committee, in connection there with.\n \n Procedures have been established for the maintenance of COBOL.
http://alitosi.com/userfiles/creation-pcut-ct1200-manual.xml
Inquiries\nconcerning the procedures for proposing changes should be directed to the\nExecutive Committee of the Conference on Data Systems Languages.\n \n The authors and copyright holders of copyrighted material:\n \n FLOW-MATIC (Trademark of Sperry Rand Corporation),\nProgramming for the UNIVAC (R) I and II, Data\nAutomation Systems copyrighted 1958, 1959, by\nSperry Rand Corporation; IBM Commercial Translator,\nForm No. F28-8013, copyrighted 1959 by IBM; FACT, DSI\n27A5260-2760, copyrighted 1960 by Minneapolis-Honeywell,\n \n have specifically authorized the use of this material in whole or in part, in the\nCOBOL specifications. The\nPICTURE SYMBOL phrase allows a PICTURE clause currency symbol to repre-\nsent a currency sign value that is different from the currency symbol, and not\nrestricted to a single character. The extensions also allow multiple currency symbols and currency sign\nvalues to be defined. A character-\nstring is delimited by separators.\n \n A separator is a string of one or two contiguous characters used to delimit character\nstrings. All user-defined\nwords (except for section-names, paragraph-names, segment-numbers, and level-\nnumbers) must contain at least one alphabetic character. Segment numbers and level\nnumbers need not be unique; a given specification of a segment-number or level-\nnumber can be identical to any other segment-number or level-number. The following are the rules for forming user-defined words from multi-byte char-\nacters:\n \n Table 2 (Page 1 of 2). The only double-byte\nEBCDIC characters allowed are: A - Z, a - z,\n0 - 9, and the hyphen (-). The hyphen cannot\nappear as the first or last character.\n \n A user-defined word can consist of both single-\nbyte or multiple-byte (including double-byte)\ncharacters. If a character exists in both single-\nbyte and multiple-byte forms, its single-byte and\nmulti-byte representations are not equivalent.\n \n Continuation\nRules\n \n Words cannot be continued across lines.
http://eco-region31.ru/bosch-oven-manuals-online
The classification of a specific occurrence of a COBOL word is\ndetermined by the context of the clause or phrase in which it occurs.\n \n 4 COBOL Language Reference \n\n \n Table 2 (Page 2 of 2). The same word, in a different context, can appear in a program as a\nuser-defined word or a system-name. You can specify SELF only in source program positions that are\nexplicitly listed in the syntax diagrams.\n \n SUPER\n A special object identifier you can use in the Procedure Division of a method\nonly as the object identifier in an INVOKE statement. When used in this way,\n \n Character-Strings\n \n Reserved Words\n A reserved word is a character-string with a predefined meaning in a COBOL source\nprogram. Within each format, such words appear in uppercase on the main path.\n \n Optional Words\n Optional words are reserved words that can be included in the format of a clause,\nentry, or statement in order to improve readability. The resolution of the method to be invoked ignores any methods\ndeclared in the class definition of the currently-executing method and methods\ndefined in any class derived from that class. For the EBCDIC collating sequence, the\ncharacter is X'FF'; for other collating sequences, the actual character used\ndepends on the collating sequence indicated by the locale. For the EBCDIC collating sequence, the\ncharacter is X'00'; for other collating sequences, the actual character used\ndepends on the collating sequence. NULL\ncan be used only where explicitly allowed in the syntax format. NULL has the\nvalue of zero.\n \n INVOKE,\n \n Figurative Constants\n \n than the ALL literal. When a figurative constant, other than the ALL literal is used,\nthe word ALL is redundant and is used for readability only. The figurative constant\nALL literal must not be used with the CALL, INSPECT, STOP, or\nSTRING statements.
http://elipseradiologiadigital.com/images/c15-romahome-manual.pdf
\n \n symbolic-character\n Represents one or more of the characters specified as a value of the symbolic-\ncharacter in the SYMBOLIC CHARACTERS clause of the SPECIAL-NAMES para-\ngraph.\n \n The singular and plural forms of ZERO, SPACE, HIGH-VALUE, LOW-VALUE, and\nQUOTE can be used interchangeably. When a numeric literal appears in a syntax diagram,\nonly the figurative constant ZERO (ZEROS, ZEROES) can be used. Figurative con-\nstants are not allowed as function arguments except in an arithmetic expression, where\nthey are arguments to a function.\n \n The length of a figurative constant depends on the context of the program. In such cases, the\nADDRESS OF special register is similarly redefined.\n \n The ADDRESS OF special register is implicitly defined USAGE IS POINTER.\n \n Special Registers\n \n Special Registers\nSpecial registers are reserved words that name storage areas generated by the com-\npiler. Their primary use is to store information produced through specific COBOL fea-\ntures. You must not reference the DEBUG-ITEM\nspecial register if your program uses more than three levels of subscripting or\nindexing.\n \n Part 1. COBOL Language Structure 11 \n\n \n LENGTH OF\n The LENGTH OF special register contains the number of bytes used by an identifier.\n \n LENGTH OF creates an implicit special register whose content is equal to the current\nbyte length of the data item referenced by the identifier.\n \n Note: For DBCS data items, each character occupies 2 bytes of storage.\n \n LENGTH OF can be used in the Procedure Division anywhere a numeric data item\nhaving the same definition as the implied definition of the LENGTH OF special register\ncan be used. LENGTH supports nonnu-\nmeric literals in addition to data names.\n \n Special Registers\n \n LINAGE-COUNTER\n A separate LINAGE-COUNTER special register is generated for each FD entry con-\ntaining a LINAGE clause.
The supported\nuser return code values are determined by the operating system, and might not\ninclude the full range of RETURN-CODE special register values. An embedded apos-\ntrophe must be represented by a pair of apostrophes (''). The maximum\nlength of a nonnumeric literal is 160 characters.\n \n The enclosing quotation marks are excluded from the literal when the program is com-\npiled. The\nmaximum length of a nonnumeric literal with multi-byte characters is limited only by\nthe available positions in Area B on a single source line.\n \n Under MVS and VM, with the DBCS compiler option, the characters X'0E'\nand X'0F' in a nonnumeric literal will be recognized as shift codes for DBCS charac-\nters. That is, the characters between paired shift codes will be recognized as DBCS\ncharacters. The\nmove and comparison rules for nonnumeric literals with double-byte characters are the\nsame as those for any nonnumeric literal.\n \n The length of a nonnumeric literal with double-byte characters is its byte length,\nincluding the shift control characters. The\nuse of statements that operate on a byte-to-byte basis (for example, STRING and\nUNSTRING) can result in strings that are not valid mixtures of EBCDIC and double-byte\ncharacters. You must be certain that the statements use DBCS characters. An even number of hexadecimal digits must be specified.\nThe maximum length of a hexadecimal literal is 320 hexadecimal digits.\n \n The continuation rules are the same as those for any nonnumeric literal. You can specify\nany character except X'00', which is the null string automatically appended to the end\nof the literal. If included, it must be the leftmost character of\nthe literal. If a decimal point is included, it is treated as an\nassumed decimal point (that is, as not taking up a character position in the literal).\nThe decimal point can appear anywhere within the literal except as the rightmost\ncharacter.
BABYBASKETSONLINE.COM/userfiles/files/Canon-eos-30d-manual.pdf
\n \n The value of a numeric literal is the algebraic quantity expressed by the characters in\nthe literal. The size of a numeric literal in standard data format characters is equal to\nthe number of digits specified by the user.\n \n Numeric literals can be fixed-point numbers.\n \n 24 COBOL Language Reference \n\n \n DBCS Literals\n Table 5 lists the formats and rules for DBCS literals. If you specify a DBCS\nliteral in a VALUE clause for a data item, the length of the literal must not\nexceed the size indicated by the data item's PICTURE clause. PICTURE character-strings are\ndelimited only by the separator space, separator comma, separator semicolon, or sepa-\nrator period.\n \n A chart of PICTURE clause symbols appears in Table 12 on page 180.\n \n Comments\n A comment is a character-string that can contain any combination of characters from\nthe character set of the computer. Anywhere a space is used as a\nseparator, or as part of a separator, more than one space can be used.\n \n The IBM COBOL character set does not include a tab character (ASCII\ncode 9). A closing apostrophe must be immediately followed by a separator (space,\ncomma, semicolon, period, or right parenthesis). Apostrophes must appear as bal-\nanced pairs. A closing quotation mark must be immediately followed by a sepa-\nrator (space, comma, semicolon, period, right parenthesis, or pseudo-text delim-\niter). Quotation marks must appear as balanced pairs. A\nclosing pseudo-text delimiter must be immediately followed by a separator (space,\ncomma, semicolon, or period). Pseudo-text delimiters must appear as balanced\npairs. They are subdivided into clauses and\nstatements. If optional clauses or state-\nments are used, they must be written in the sequence shown in their formats. Entries are constructed\nin the Identification, Environment, and Data Divisions.\n \n Clauses\n A clause is an ordered set of consecutive COBOL character-strings that specifies an\nattribute of an entry.
It specifies an\naction to be taken by the object program. Statements are constructed in the Procedure\nDivision. The effect may be\ndependent on the LINECOUNT compiler option. For example:\n \n OBJECT-COMPUTER.It must be followed by a space or\nseparator period.\n \n DECLARATIVES and END DECLARATIVES\n DECLARATIVES and END DECLARATIVES are key words that begin and end the\ndeclaratives part of the source program.\n \n In the Procedure Division, each of the key words DECLARATIVES and END DECLAR-\nATIVES must begin in Area A and be followed immediately by a separator period; no\nother text may appear on the same line. This will\nresult in two consecutive nonnumeric literals instead of one continued nonnumeric\nliteral.\n \n Area B\n \n Entries, Sentences, Statements, Clauses\n The first entry, sentence, statement, or clause begins on either the same line as the\nheader or paragraph-name it follows, or in Area B of the next nonblank line that is not a\ncomment line. Successive sentences or entries either begin in Area B of the same line\nas the preceding sentence or entry or in Area B of the next nonblank line that is not a\ncomment line.\n \n Within an entry or sentence, successive lines in Area B may have the same format, or\nmay be indented to clarify program logic. The output listing is indented only if the input\nstatements are indented. Indentation does not affect the meaning of the program. The\nline being continued is a continued line; the succeeding lines are continuation lines.\nArea A of a continuation line must be blank.\n \n If there is no hyphen (-) in the indicator area (column 7) of a line, the last character of\nthe preceding line is assumed to be followed by a space.\n \n If there is a hyphen in the indicator area of a line, the first nonblank character of this\ncontinuation line immediately follows the last nonblank character of the continued line\nwithout an intervening space.
\n \n If the continued line contains a nonnumeric literal without a closing quotation mark, all\nspaces at the end of the continued line (through column 72) are considered to be part\nof the literal. The continuation line must contain a hyphen in the indicator area, and the\nfirst nonblank character must be a quotation mark. The continuation of the literal\nbegins with the character immediately following the quotation mark.\n \n If the last character on the continued line of a nonnumeric literal is a single quotation\nmark in column 72, the continuation line must start with two consecutive quotation\nmarks. The quotation mark with the following space terminates\nthe continued line. Only the characters within the quotation marks are counted as\npart of the literals. A level-number that must begin in Area A is a 1- or 2-digit\ninteger with a value of 01 or 77. The comment may be written anywhere in Area A and Area B of that\nline, and may consist of any combination of characters from the character set of the\ncomputer. A comment line may be placed anywhere in the program following the Iden-\ntification Division header.\n \n Multiple comment lines are allowed. A blank\nline may appear anywhere in a program.\n \n 38 COBOL Language Reference \n\n \n For Classes and Methods\n Names declared in a class definition are global to all the methods contained in that\nclass definition. All names declared in methods are implicitly local.\n \n Scope of Names\n \n Scope of Names\n \n A COBOL resource is any resource in a COBOL program that is referenced via a user-\ndefined word. You can use names to identify COBOL resources. This section\ndescribes COBOL names and their scope. It explains the range of where the names\ncan be referenced and the range of their usability and accessibility.\n \n Types of Names\n In addition to identifying a resource, a name can have global or local attributes. An\nobject-oriented class-name is always global.
BABETRAVELLING.COM/ckfinder/userfiles2/files/Canon-eos-30d-manual-download.pdf
\n \n object-oriented class Working-Storage\n Object-oriented class Working-Storage data items are always global to the methods\ncontained in the class definition. They are accessible from any contained method.\n \n Scope of Names\n \n If you specify library-name with a literal, it is treated as the actual path name. If you\nspecify library-name with a user-defined word, the name is used as an environment\nvariable and the value of the environment variable is used for the path names(s) to\nlocate the COPY text. The\nstorage associated with a data item or a file connector can be external or internal to\nthe program in which the resource is declared.\n \n A data item or file connector is external if the storage associated with that resource is\nassociated with the run unit rather than with any particular program within\nthe run unit. An external resource can be referenced by any program in the\nrun unit that describes the resource. References to an external resource from different\nprograms using separate descriptions of the resource are always to the\nsame resource. In a run unit, there is only one representation of an external resource.\n \n A resource is internal if the storage associated with that resource is associated only\nwith the program that describes the resource.\n \n External and internal resources can have either global or local names.\n \n A data record described in the Working-Storage Section is given the external attribute\nby the presence of the EXTERNAL clause in its data description entry. Any data item\ndescribed by a data description entry subordinate to an entry describing an external\nrecord also attains the external attribute. References to data and\nprocedures can be either explicit or implicit. This section contains the rules for quali-\nfication and for explicit and implicit data references.
\n \n Uniqueness of Reference\n Every user-defined name in a COBOL program is assigned by the user to name a\nresource for solving a data processing problem. To use a resource, a statement in a\nCOBOL program must contain a reference which uniquely identifies that resource. To\nensure uniqueness of reference, a user-defined name can be qualified, subscripted, or\nreference-modified.\n \n When the same name has been assigned in separate programs to two or more occur-\nrences of a resource of a given type, and when qualification by itself does not allow the\nreferences in one of those programs to differentiate between the identically named\nresources, then certain conventions that limit the scope of names apply. The con-\nventions ensure that the resource identified is that described in the program containing\nthe reference. The higher-level names are called qual-\nifiers, and the process by which such names are made unique is called qualification.\n \n Qualification is specified by placing one or more phrases after a user-specified name,\nwith each phrase made up of the word IN or OF followed by a qualifier (IN and OF are\nlogically equivalent).\n \n In any hierarchy, the data name associated with the highest level must be unique if it is\nreferenced, and cannot be qualified.\n \n You must specify enough qualification to make the name unique; however, it is not\nalways necessary to specify all the levels of the hierarchy. If you do not explicitly code a data attri-\nbute, the compiler assumes a default value.\n \n For example, you need not specify the USAGE of a data item. If it is omitted and the\nsymbol N is not specified in the PICTURE clause, the default is USAGE DISPLAY,\nwhich is the implicit data attribute.\n \n If, however, you specify USAGE DISPLAY in COBOL coding, it becomes an\nexplicit data attribute.
\n \n Identical Names\n When programs are directly or indirectly contained within other programs, each program\ncan use identical user-defined words to name resources. A paragraph-name need not be qualified when referred to within the section in\nwhich it appears. A paragraph-name or section-name appearing in a program cannot\nbe referenced from any other program.\n \n References to Data Division Names\n \n Simple Data Reference\n The most basic method of referencing data items in a COBOL program is simple data\nreference, which is data-name-1 without qualification, subscripting, or reference modifi-\ncation. File-name-2 must\nbe unique within this program.\n \n Duplication of data-names must not occur in those places where the data-name cannot\nbe made unique by qualification.\n \n In the same program, the data-name specified as the subject of the entry whose level-\nnumber is 01 that includes the EXTERNAL clause must not be the same data-name\nspecified for any other data description entry that includes the EXTERNAL clause.\n \n In the same Data Division, the data description entries for any two data items for which\nthe same data-name is specified must not include the GLOBAL clause.\n \n Data Division names that are explicitly referenced must either be uniquely defined or\nmade unique through qualification. Unreferenced data items need not be uniquely\ndefined. The highest level in a data hierarchy must be uniquely named, if referenced.\nThis is a data item associated with a level indicator (FD or SD in the File Section) or\nwith a level-number 01. The number of subscripts in such a refer-\nence must equal the number of dimensions in the table whose element is being\nreferenced. That is, there must be a subscript for each OCCURS clause in the hier-\narchy containing the data-name including the data-name itself.\n \n When more than one subscript is required, they are written in the order of successively\nless inclusive dimensions of the data organization.
See the third example on\npage 54. However,\nthe table element length of the table being referenced and of the table that the index-\nname is associated with should match. Otherwise, the reference will not be to the\nsame table element in each table, and you might get run-time errors.\n \n Uniqueness of Reference\n \n The lowest permissible occurrence number represented by a subscript is 1. The\nhighest permissible occurrence number in any particular case is the maximum number\nof occurrences of the item as specified in the OCCURS clause.\n \n Subscripting Using Data-Names\n When a data-name is used to represent a subscript, it can be used to reference items\nwithin different tables. These tables need not have elements of the same size. The\nsame data-name can appear as the only subscript with one item and as one of two or\nmore subscripts with another item. A data-name subscript can be qualified; it cannot\nbe subscripted or indexed. An index associated with an index-\nname acts as a subscript, and its value corresponds to an occurrence number for the\nitem to which the index-name is associated.\n \n The INDEXED BY phrase, by which the index-name is identified and associated with its\ntable, is an optional part of the OCCURS clause. There is no separate entry to\ndescribe the index associated with index-name. At run time, the contents of the index\ncorresponds to an occurrence number for that specific dimension of the table with\nwhich the index is associated.\n \n The initial value of an index at run time is undefined, and the index must be initialized\nbefore it is used as a subscript. The SEARCH statement\nprovides facilities for producing serial and non-serial searches. The value of the\nsubscript used is the same as if the index-name or data-name had been set up or down\nby the value of the integer. The leftmost position is assigned\nthe ordinal number one. This unique data item is considered an\nelementary data item without the JUSTIFIED clause.
\n \n When a function is reference-modified, the unique data item has the class and category\nof alphanumeric. This is achieved using a technique known as windowing,\nwhich removes the assumption that all 2-digit year fields represent years from 1900 to\n1999. Instead, windowing enables 2-digit year fields to represent years within any\n100-year range, known as a century window.\n \n For example, if a 2-digit year field contains the value 15, many applications would inter-\npret the year as 1915. A windowed year\nconsists of 2 digits, representing a year within the century window.\n \n Part 1. COBOL Language Structure 59 \n\n \n Millennium Language Extensions and Date Fields\n \n Expanded Date Field\n An expanded date field is a date field that contains an expanded year. An expanded\nyear consists of 4 digits.\n \n Note: The main use of expanded date fields is to provide correct results when these\nare used in combination with windowed date fields; for example, where migration to\n4-digit year dates is not complete. If all the dates in an application use 4-digit years,\nthere is no need to use the millennium language extensions.\n \n Year-Last Date Field\n A year-last date field is a date field whose DATE FORMAT clause specifies one or\nmore Xs preceding the YY or YYYY. These con-\ntained programs can reference some of the resources of the programs that contain\nthem. A class definition consti-\ntutes a compilation unit.\n \n Class\n The entity that defines common behavior and implementation for zero, one, or\nmore objects. The objects that share the same implementation are considered to\nbe objects of the same class.\n \n Method\n Procedural code that defines one of the operations supported by an object, and\nthat is executed by an INVOKE statement on that object.\n \n Instance Data\n Data defining the state of an object. The instance data introduced by a class is\ndefined in the Working-Storage Section of the Data Division of the class definition.
\nThe state of an object also includes the state of the instance variables introduced\nby bases classes that are inherited by the current class. A separate copy of the\ninstance data is created for each object instance.\n \n Subclass\n A class that inherits methods and instance data from another class. When two\nclasses in an inheritance relationship are considered together, the subclass is the\ninheritor or inheriting class; the super-class is the inheritee or inherited class.\n \n Metaclass\n A special type of class whose instances are called class-objects.It cannot be\na figurative constant.\n \n PGMNAME\n(LONGMIXED)\n \n Program-name must be specified as a\nliteral. It cannot be a figurative constant.\n \n The name can be up to 160 characters in\nlength.\n \n Program-name can consist of any character\nin the range X'41' to X'FE'.\n \n Program-name must be specified as a\nliteral. It cannot be a figurative constant.\n \n The name can be up to 160 characters in\nlength.\n \n Wherever alphabetic characters are allowed,\nyou can use multi-byte characters.\n \n For information on the PGMNAME compiler option and how the compiler processes\nthe names, see the IBM COBOL Programming Guide for your platform.\n \n RECURSIVE\n An optional clause that allows COBOL programs to be recursively reentered.\n \n You can specify the RECURSIVE clause only on the outermost program of a com-\npilation unit. Recursive programs cannot contain nested subprograms.\n \n PROGRAM-ID Paragraph\n \n PROGRAM-ID Paragraph\n The PROGRAM-ID paragraph specifies the name by which the program is known and\nassigns selected program attributes to that program. It is required and must be the first\nparagraph in the Identification Division.\n \n program-name\n A user-defined word that identifies your program. If the RECURSIVE clause is not\nspecified, an active program cannot be recursively reentered.