|
----- Original Message ----- From: "Buck Calabro" <buck.calabro@aptissoftware.com> To: <rpg400-l@midrange.com> Sent: Monday, August 28, 2000 09:23 Subject: Re: explicit close > It's an interesting question: Do we have getCustName do the open (in case > the caller "forgot") or do we return a "not open" error and have the caller > perform the proper initialisation? I do the latter but I see the wisdom in > the former, in which case I would indeed have getCustName call the public > fileOpen procedure. I think this is one of those personal preference things. I'm just a lazy typist, so I hate having to put "CallP InitModule" in every calling program. If the SrvPgm takes care of it's own initialization, then it's more of a "black-box" and I don't have to think about it anymore. > >How the resources are closed depends > >upon the type of caller. If the caller > >is designed to run in a named or *NEW > >activation group, then I rely upon the > >destruction of the activation group to > >close the resources. However, if the > >caller runs in the *DFT ag, or QILE, > >then I handle resource clean up > >within the program itself. > > Sadly, this is a level of sophistication that many shops aren't ready for. > It seems pretty straightforward once you've done an application this way, > but that first step is a doosy! John, what sort of programmers are in your > shop? We have a broad mix of mostly inexperienced folks peppered with > S/36ers and a handful of S/38 - AS/400 folks. I find that beginners are OK > with explicit closes but the whole activation group thing gets by them. I'm > more than happy just to get service programs in production! At the present time, it's just me, myself, & I. Obviously, this gives me a tremendous amount of freedom. I'm able to pick and choose the technologies that I use without interference - as long as I continue to deliver a solution on time & budget. I sympathize with those of you who don't have the same opportunity. Regards, John Taylor Canada +--- | 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-2025 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.