|
>> I'm not too familiar with this method since my shop doesn't use all of the ILE techniques. This isn't really an ILE technique. It was added because the iSeries COBOL compilers were not fully ANSI compliant under the revised interpretation of the standard. i.e. If an output file doesn't exist it will be created by opening/writing it. The support is minimal and it is not recommended to use it for anything other than compatibility reasons (e.g. if you want identical code to run on multiple platforms). The reason it is not recommended is that creating a file on an iSeries carries a much heavier overhead than creating a file on (say) a Unix box. This is because all files on the iSeries are databases and that is a little more complex to build than a simple flat or ISAM file. The method suggested for iSeries is to create the file permanently and then if you need it to be "emptied" on each use, run a CLRPFM from a CL prior to the program or run the CLRPFM via QCMDEXC within the COBOL prior to opening the file. I believe it is possible to control the location of the created file, but I suspect only via an OVRDBF - and if you're going to do that you might as well do it properly. Jon Paris Partner400 www.Partner400.com www.RPGWorld.com
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.