And what would you want in data-name-1? A DDNAME,like the PL/I? A data set name? A partial data set name (with some magic for full expansion)? Something else?
What do you feel, with your selected option for data-name-1, would be some example uses for this? Again, for me, just because something is in COBOL 2014, doesn't naturally mean it should get Enterprise COBOL development resources assigned to it. Clearly, unlike in 1985, the number of "sites" using COBOL on Linux/Unix/Windows is greater than the number of Mainframe sites. COBOL 2014 and future developments of the COBOL Standard will reflect this. As you've pointed out previously, with XML, Json and UNBOUNDED, IBM is happy to be COBOL-85-with-extesnsions-from-2002-2014-plus-our-own. So, good choices from 2002/2014, yes. What is it that would make the ability to use a data-name in the ASSIGN good? On Tue, 10 Jan 2017 23:01:59 +0000, Frank Swarbrick <[email protected]> wrote: >For whatever its worth, the latest COBOL Standard offers the following syntax, >which I believe meets this requirement at the language level: > > >SELECT file-name-1 ASSIGN USING data-name-1. > > >"3) The ASSIGN clause specifies the association of the file connector >referenced by file-name-1 to a physical file identified by device-name-1, >literal-1, or the content of the data item referenced by data-name-1. > >3b) When the USING phrase of the ASSIGN clause is specified, the file >connector referenced by file-name-1 is associated with a physical file >identified by the content of the data item referenced by data-name-1 in the >runtime element that executes the OPEN, SORT, or MERGE statement." > > >Someone want to open an RFE? > > >Frank ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
