|
True that may be however the API will perform much faster (& IMO better ) for this type of application. Thanks, Tommy Holden -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Donald Whittaker Sent: Monday, November 14, 2005 12:32 PM To: RPG programming on the AS400 / iSeries Subject: RE: RE: [WDSCI-L] Wdsc issues Now: On RPG400-L I do use QjoRetrieveJournalEntries, but I've been doing this for years. I was going to let Mike get his feet wet before I pushed him in the rest of the way... Thanks, Don Whittaker --- Holden Tommy <Tommy.Holden@xxxxxxxxxxxxxxxxx> wrote: > If you are using RPG why not use the Journaling > APIS?? > > http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/apis/jc1.htm > > > > Thanks, > Tommy Holden > > > -----Original Message----- > From: rpg400-l-bounces@xxxxxxxxxxxx > [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of > Donald Whittaker > Sent: Monday, November 14, 2005 9:54 AM > To: RPG400-L@xxxxxxxxxxxx > Subject: Was: RE: [WDSCI-L] Wdsc issues Now: On > RPG400-L > > Mike, > What I do in these cases is clone QADSPJR4 and > dump > the entries to that clone. The RPG program I use to > read the cloned file has numerous D-specs defining > externally described data structures, one for each > entry type I am dumping, using the QASYxxJ4 name as > the EXTNAME (no need to clone these files; the RPG > compiler will use the existing files to pick up the > structure). > The program logic reads a QADSPJR4 record, checks > the entry type, and moves the data to the > appropriate > DS. > > Hope that helps, > > Don Whittaker > > --- "Smith, Mike" <Mike_Smith@xxxxxxxxxxxxxxxx> > wrote: > > > Thanks Donald. I found out the these were related > > to the DSPJRN command > > this weekend. Now I'm trying to put it together, > > but I'm not sure if > > I'm missing something very simple here or not. Is > > there an easy way to > > map the QADSPJRN file to the specific QASYxxJ4 > data > > structures, or am I > > going to have to individually map each field. Its > > probably staring me > > right in the face, I'm just not seeing it. > > > > Michael Smith > > iSeries.mySeries. > > > > > > -----Original Message----- > > From: Donald Whittaker > > [mailto:donald_whittaker@xxxxxxxxx] > > Sent: Friday, November 11, 2005 5:59 PM > > To: Websphere Development Studio Client for > iSeries > > Subject: RE: [WDSCI-L] Wdsc issues > > > > > > You would need to do a DSPJRN to an outfile. > You > > can specify which journal entry types you want > > (there > > are, of course, numerous selection criteria). > > DSPJRN > > will dump all of the entries into the > > "generic-format" > > of QADSPJRN/QADSPJR4. This is "generic" in the > > sense > > that the entry-specific data is lumped into one > big > > herking field, unlike the entry-specific QASYxxJ4 > > files that list these in separate columns. Hence > my > > suggestion to then use the QASYxxJ4 files as > > externally described DS's. > > There are a couple of API's you can use to > > retrieve > > the journal entries if you would rather do it that > > way. > > Maybe this would work for you. > > Don Whittaker > > > > --- "Smith, Mike" <Mike_Smith@xxxxxxxxxxxxxxxx> > > wrote: > > > > > Don, Thanks for the reply. As I read your reply > I > > > started thinking > > > about what I was doing. I took off qualifying > > > (qtemp) on my Select > > > statements and that resolved my initial compile > > > issue. > > > I'm definitely trying to avoid the 'ugly' so > your > > > point about using > > > QSYS/QADSPJRN or QSYS/QADSPJR4) is definitely > > worth > > > looking at. Yours > > > was a very timely response-btw. > > > However, I'm not sure I know how to use these > > files. > > > I know when I do a > > > DSPAUDJRNE I get a bunch of QASYxxJ4 files > > > populated, but what is going > > > to populate the files (QADSPJRN,QADSPJR4)??? > > > > > > Michael Smith > > > iSeries.mySeries. > > > > > > > > > > > > > __________________________________ > > Yahoo! FareChase: Search multiple travel sites in > > one click. > > http://farechase.yahoo.com > > -- > > This is the Websphere Development Studio Client > for > > iSeries (WDSCI-L) > > mailing list To post a message email: > > WDSCI-L@xxxxxxxxxxxx To subscribe, > > unsubscribe, or change list options, > > visit: > > http://lists.midrange.com/mailman/listinfo/wdsci-l > > or email: WDSCI-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the > > archives > > at http://archive.midrange.com/wdsci-l. > > > > -- > > This is the Websphere Development Studio Client > for > > iSeries (WDSCI-L) mailing list > > To post a message email: WDSCI-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: > > http://lists.midrange.com/mailman/listinfo/wdsci-l > > or email: WDSCI-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the > > archives > > at http://archive.midrange.com/wdsci-l. > > > > > > > > __________________________________ > Yahoo! Mail - PC Magazine Editors' Choice 2005 > http://mail.yahoo.com > -- > This is the RPG programming on the AS400 / iSeries > (RPG400-L) mailing > list > To post a message email: RPG400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/mailman/listinfo/rpg400-l > or email: RPG400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/rpg400-l. > > > -- > This is the RPG programming on the AS400 / iSeries > (RPG400-L) mailing list > To post a message email: RPG400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/mailman/listinfo/rpg400-l > or email: RPG400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/rpg400-l. > > __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.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.