|
Chris, >It can cause more problems that its worth.< How? Yes, there's more cleanup involved, but that is hardly a daunting task. >Also it is not ISO SQL compliant.< I'm not sure I'd lose sleep over this. Honestly, I don't know what the implications of this are for an application which will likely remain on the AS/400. Your idea of using a unique job identifier in the file's records is fine, as long as it doesn't force a major rewrite of an existing application. Just my .02 Dan Bale IT - AS/400 Handleman Company 248-362-4400 Ext. 4952 -----Original Message----- Multi members is NOT the way to go. It can cause more problems that its worth. Also it is not ISO SQL compliant. If you are generating a 10 char field for a member name, why not add it as a field and pass to the batch program for processing. You are then processing only the records that match and once a record is processed you can delete it. Re-use delete on the file keeps it from eating DASD beyond the largest number of records active at any one time. I use the interactive job name/user/number as my key, 26 characters. Add a sequence number in a data area in qtemp and the same job can submit multiple batches. 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: Saunders, Martin P [mailto:Martin.Saunders@capgemini.co.uk] Sent: Wednesday, October 18, 2000 7:30 AM To: 'RPG400-L@midrange.com' Subject: RE: Accessing files In QTEMP Use multi-member files instead. Add/Allocate members as necessary and pass the member name as a parameter to the next job. Members can be removed/deallocated at the end of the second job. Small amount of effort required to ensure unique member names for each user. Martin +--- | 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.