|
Hmm.. good point. Looking at it though, it seems I would not have to change my program whatsoever to do this. All I would have to do is to change my data queue to a local data queue and create another data queue to go to the other system. Then I write another program to pull from the local data que and put it to the data queue on my other system. I think, though, that I will wait til I actually have a problem with the current setup before I do this. Regards, Jim Langston Chris Bipes wrote: > I would not have the trigger goto the ddm data queue. If your > communications is ever down, your trigger will fail. Use a local data queue > and a server program to read the local and send to remote. This way if the > two as400s are not talking, the transactions remain queued until you can > re-establish communications. Your applications will not crash because the > trigger will not crash. We have the trigger write to a file and have a > server read the file, send to remote, delete the record from the file after > confirming the remote received the transaction. Data queues are fast with > little overhead but have their limits. Long term storage, more than a few > minutes), and power failures are two of their weaknesses. > > Christopher K. Bipes mailto:ChrisB@Cross-Check.com > Sr. Programmer/Analyst mailto:Chris_Bipes@Yahoo.com > CrossCheck, Inc. http://www.cross-check.com > 6119 State Farm Drive Phone: 707 586-0551 x 1102 > Rohnert Park CA 94928 Fax: 707 586-1884 > > If consistency is the hobgoblin of little minds, only geniuses work here. > Karen Herbelin - Readers Digest 3/2000 > > -----Original Message----- > From: Jim Langston [mailto:jlangston@conexfreight.com] > Sent: Monday, June 12, 2000 8:35 AM > To: RPG400-L@midrange.com > Subject: Re: Data Queues > > Thank you, Booth and Jodi and other people who responded. > > This worked exactly as advertised, and is implemented. Was quite > an interesting project, and even though I am still working on some of > the finer points of my data, the transfer is going quite well. > > >From a Trigger triggered on *Insert to an external data queue to a > remote system. Ain't the AS/400 grand? > > Regards, > > Jim Langston > > boothm@earth.Goddard.edu wrote: > > > Here's some code I use that works: > > > > 0019.00 * DTAQ identification variables > > 0020.00 D DtaQ s 10 Inz('xx4030DQ') > > 0021.00 D DtaQLib s 10 Inz('*LIBL') > > 0022.00 D DtaQLen s 5 0 Inz(1024) > > 0023.00 D DtaQData S 1024 > > 0024.00 > > 0026.00 D DtaQDataDS ds > > 0027.00 D xxCONO > > > > 0042.00 C Movel DtaQDataDS DtaQData > > 0043.00 C call 'QSNDDTAQ' > > 0044.00 C parm DtaQ > > 0045.00 C parm DtaQLib > > 0046.00 C parm DtaQLen > > 0047.00 C parm DtaQData > > > > Good luck with it. > > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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.