|
Joe, Good eyeballs :) Things like that can bite you in the a**. There are probably some environments that can use this feature, however I avoid it like the plague! The *only* time I have ever hard-coded library names was for API copybooks in QSYSINC. Terry > -----Original Message----- > From: Joe Pluta [mailto:joepluta@PlutaBrothers.com] > Sent: Wednesday, July 24, 2002 12:11 PM > To: cobol400-l@midrange.com > Subject: A little shudder here > > > Just a note... I just figured out (relearned, perhaps?) the > library name > syntax for file definitions. My program wasn't compiling > until I realized > it had a hardcoded library name in it. Now I know that > LIBRARY-FILENAME is > the syntax. > > Hardcoded library names. <<shudder>> > > Joe > > _______________________________________________ > This is the COBOL Programming on the iSeries/AS400 > (COBOL400-L) mailing list > To post a message email: COBOL400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/cobol400-l > or email: COBOL400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/cobol400-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
