× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Chris:

Ever used ALIAS?  It deals rather nicely with the "member problem".

Richard Jackson
mailto:richardjackson@richardjackson.net
http://www.richardjacksonltd.com
Voice: 1 (303) 808-8058
Fax:   1 (303) 663-4325

-|-----Original Message-----
-|From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
-|Behalf Of Chris Bipes
-|Sent: Wednesday, October 18, 2000 12:39 PM
-|To: 'RPG400-L@midrange.com'
-|Subject: RE: Accessing files In QTEMP
-|
-|
-|The more problems comes into play if you need to create LF's over the
-|member.  You have to be sure you only create it over your member.
-| If it get
-|created over all member you will not be able to delete any
-|members from any
-|jobs until the LF is deleted.  If your application uses imbedded SQL you
-|will be screwed by multiple members.  Multiple member make the job
-|processing more complex IMHO.
-|
-|It is just as easy to do a keyed delete as a remove member at job
-|end/cleanup.  It the job bombs, you have to track and clean up members or
-|records.  I think it is easier to see if job/user/number is on the system
-|and active or on queue, if not delete records.  Gee is the job for member
-|xxx active or on queue?  What job is processing member xxx?  Can I delete
-|this member?
-|
-|A nightly job that reads this file by job/user/number as IP with a level
-|break can check the status of a job and see if it is on jobq /
-|active / outq
-|or not on the system.  If it is not on system or outq status, delete the
-|records.  I prefer to delete records as they are processed not in a final
-|clean up.
-|
-|But I guess since I LOVE the RPG Cycle, I am a dinosaur.
-|
-|
-|
-|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
-|
-|Living in the days of RPG Cycle, and LOVING it!
-|
-|-----Original Message-----
-|From: D.BALE@handleman.com [mailto:D.BALE@handleman.com]
-|Sent: Wednesday, October 18, 2000 10:37 AM
-|To: RPG400-L@midrange.com
-|Subject: RE: Accessing files In QTEMP
-|
-|
-|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
-|+---
-|| 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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.