|
Be careful. If the file is created in the current run on a busy machine, the QADBxxx files may not be updated immediately (updates a separate task in a different subsystem). -----Original Message----- From: Pytel, Alexei [SMTP:pytela1@midas-kapiti.com] Sent: Friday, August 21, 1998 4:48 AM To: MIDRANGE-L@midrange.com Subject: RE: DSPFFD with KeyList Why you need DSPFFD output at all ? There is one of system database directory files (QADBxxxx) which contains all field information for all files on system. You may use such file or one of the logicals built over it. Best regards, Alexei Pytel > -----Original Message----- > From: VENU YAMAJALA [SMTP:venu_yamajala@goodyear.com] > Sent: Thursday, August 20, 1998 9:50 PM > To: MIDRANGE-L@midrange.com > Subject: DSPFFD with KeyList > > Hi All, > > I want to retreive (random retreival) the database fields' > information > from DspFfd command in an RPGLE pgm. > > I need some suggestions/help. In my driver CL pgm I am doing a DSPFFD > of one database file to an outfile in QTEMP library. Say QTEMP/DSPxxx. > I want > to build a key for this outfile and use the keyed file in my called > RPG. I am > confused with the sequence of steps I need to do. I am doing > > OvrDbf Qtemp/DSPxxx SHARE(*YES) > OpnQryF (Qtemp/DSPxxx) KEYFLD(WHLIB WHFILE WHFLD) OPENSCOPE(*JOB) > > Call RPG1 > > In my RPG1, I will be doing some CHAIN to this file. So I need to > define the > file in the F specs. I defined it as QADSPFFD (template of DSPFFD). > > I am missing something here. The QADSPFFD in the F spec cannot be > defined as > Keyed (it is giving a compile error!!). If I dont define it as keyed, > I cannot > do a CHAIN. Next problem is I need this QADSPFFD to point to the > dynamically > built keyed OpnQryF file. I am missing something here. > > Can anybody help me or is there any work-around. Thanx in advance for > any help > or suggestions. > > Rgds, > Vg > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | 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.