|
I could be really off base here, but.... IIRC in RPGII, an O without Add, would 'create' the file new if it didn't exist, (i think, even without the 'new' keyword on the file ocl statement). I don't remember what happened if the file already existed, but something tells me it might have overlayed the file on the first write. I DON'T believe that simply opening and closing the file cleared it - 'clearing' a file wasn't something that the 36 and 34 were at all familiar with. you deleted and rebuilt files on those boxes. CLRPFM was later added to SSP to help migrating packages slowly to 400 techniques, but only as an afterthought. If such a technique existed, i'm would have though that it would have been in all the techy mags, and widely used in utilites librarys as a way of clearing files. you could have just written a generic rpg program that opened and closed the file, called from a procedure that recieved the files name: (my syntax could be rusty): clrpfm filename procedure clrpfm: // load clrpfm // file name-generic label-?1? // run rpgII pgm clrpfm H FGENERIC O F 1 1 DISK C SETON LR OGENERIC D LRNLR O 1 ' ' but, i could be wrong...... ;) -----original message-------- >I must be missing something here because >no one else has mentioned this, but >.... Why don't you simply open the file >for output, and then close it? When Jon speaks, I look carefully before answering. It was my recollection that O in RPG/400 + did not clear the output file like it did on S/3/32/34/36. So I tested it: fmastest o e disk C SETON LR This did not clear my file. So I went hunting through The RPG Reference, V5R1, but could not find a specific reference. The S/36 manual wasn't very helpful either. Hm. --buck
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.