|
John Carr wrote: > RE: CLEAR Opcode? > > >I have a program in which I am using a file as Input/Full procedural, I > >am only using one of the files fields as output within the RLU generated > >PRTF in my program. When I do the following: > > CLEAR TMISC <---- Record format name. > > K10 CHAIN FLTMISC 30 > >If my chain is a no hit, this field from the record format above isn't > >cleared out. But if I do this: > > CLEAR TMDES6 <---- Individual field within record format. > > K10 CHAIN FLTMISC 30 > >It is cleared out properly.. What gives? > > -Tim & Dana Truax-: > > Tim > > It doesn't work if your file is Input only. Only if its Update. > To get around this, Have an externally defined D/S (Using that file > as the defining file), and then do a CLEAR on the D/S name. > This will have the same effect. I can't justify why it doesn't > work for Input Only. > > P.S. It would work for your Printer File Format Name though. You can use *ALL in factor 2 of the CLEAR Op code to clear all fields. Somthing like CLEAR *ALL RECFMT This works for input only, output only or i/o files. Also, if you specify *NOKEY in factor 1, it will leave the key fields alone. There is a blurb in the manual that says you cant use *ALL under certain i/o conditions with certain i/o fields. ignore it. It clears the fields. Now IBM, do not go messing around to make the code work like the manual. -- Thank You. Regards Dave Mahadevan.. mailto:mahadevan@fuse.net +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: david@midrange.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.