COPYEXT, COPYLBR, COPYLIST, FOLD-COPY-NAME, OLDCOPY

From: apknight (apknight_at_gmail.com)
Date: 03/14/05 

Date: 13 Mar 2005 18:04:35 -0800

I can't have MF COBOL COMPILER.. but I must study MF COBOL..
ㅠ.ㅠ

so.. I have many question ^_^... ( so often found me here )

I found followed Text.. cobol lnaguage reference

In addition to Compiler directives which provide flagging and modify
the reserved word list, the following directives may impact either the
syntax or the semantics described in this section.

    * COPYEXT - specifies the filename extension to be used for
locating copy files.

    * COPYLBR - specifies that library-names are equivalent to .lbr
files.

    * COPYLIST - causes the result of a COPY statement to be included
in the listing file.

    * FOLD-COPY-NAME - allows the Compiler to find a copy library
member when the library name on disk and the text-name in the COPY
statement do not use the same upper-case and lower-case letters for
the library member name.

    * OLDCOPY - changes the handling of COPY statements to match the
ANS'68 and OS/VS COBOL LANGLVL(1) rules.

.................................................................
What is .lbr file?, and COPYLIST is automated set by COPY Statement?

One More... FOLD-COPY-NAME'S value is TRUE/FALSE ? or Y/N? or other? (
needs..example)

Relevant Pages

  • Re: Itanium Port Question
    ... the HP COBOL compiler does not insert padding into a data ... ALIGNMENT qualifier and/or compiler directives are used to modify this ... structures are written directly to an RMS file where disk space was at ...
    (comp.os.vms)
  • Re: invoking a method
    ... Okay, having actually done maintenance on compilers including written more than one, I'll state why I don't think your idea will work, at least, not in the context of Cobol. ... Now, I will admit I have not worked on anyone else's Cobol compiler so I don't know how they work, I will offer some thoughts on the subject based on how I suspect they work. ... I may be wrong on this point but considering the way Cobol reference manuals show Cobol syntax, I have a reasonable belief that this would be the way it would be done. ... But the high probability is that it would be an extreme effort to be able to implement such a thing, since I suspect that Cobol compilers tend to be keyword driven, thus allowing them to implement the "implicit call" function would require potentially a significant rewrite or even a reengineering of the parsing routines of the compiler. ...
    (comp.lang.cobol)
  • Re: invoking a method
    ... Okay, having actually done maintenance on compilers including written more than one, I'll state why I don't think your idea will work, at least, not in the context of Cobol. ... I was suggesting it for if I were developing my own language; a language that is not COBOL. ... I may be wrong on this point but considering the way Cobol reference manuals show Cobol syntax, I have a reasonable belief that this would be the way it would be done. ... Presumably the parser for a Cobol Compiler is going to presume some fixed syntax, i.e. a specific DIVISION having certain contexts. ...
    (comp.lang.cobol)
  • Re: I need help!!
    ... Most COBOL environments have utilities available to create standard ... but you will still have to deal with the packed fields. ... If you DON'T have a COBOL compiler available you should still try and get ... I would also look at converting the ...
    (comp.lang.cobol)
  • Re: Next project, C programming problem.
    ... writting with fopenit will be Stream. ... > If it is COBOL, then you really do need properly delimited records since ... The COBOL source files are the data my program needs to work with. ... otherwise the padding blew the COBOL compiler ...
    (comp.os.vms)