|
Mike, I use CRTBNDRPG to create the programs and never create a module for the program object, thus it doesn't need to be in the binding directory. This also means that it is not necessary to have a binding directory for each program, they can all use the same one to access the service programs. Or you can have several to group service programs if it makes sense. Scott Mildenberger > -----Original Message----- > From: Smith, Mike [mailto:Mike_Smith@RGCResources.com] > Sent: Friday, October 19, 2001 8:39 AM > To: 'rpg400-l@midrange.com' > Subject: RE: binding directories > > > scott, > i'm not sure i understand your last sentence. i'm a little > thick headed. > what i'm currently doing is i create module PGM1. Create a binding > directory with Module(pgm1) and the service programs(SRVPGM1 > and SRVPGM2) > Then as you have suggested, i have the binding directory in > the H spec. The > thing i am doing is doing this same thing for each program, so i have > SRVPGM1 and SRVPGM2 in numerous binding directories. > > are you suggesting that i don't need the module in the > binding directory? > > -----Original Message----- > From: Scott Mildenberger [mailto:Smildenber@Washcorp.com] > Sent: Friday, October 19, 2001 10:23 AM > To: 'rpg400-l@midrange.com' > Subject: RE: binding directories > > > Mike, > > I would put the service programs into a binding directory. > Then I would use > the H-spec in the programs to specify the binding directory > and activation > group info. Then all the compiles can be done with default > options and no > need to create the module objects for the programs. > > Scott Mildenberger > > > -----Original Message----- > > From: Smith, Mike [mailto:Mike_Smith@RGCResources.com] > > Sent: Friday, October 19, 2001 8:21 AM > > To: 'rpg400-l@midrange.com' > > Subject: binding directories > > > > > > I'm just looking for what other people are doing. > > assume i have > > pgm1 and srvpgm1 and srvpgm2 > > pgm2, srvpgm1, srvpgm2 > > pgm3, srvpgm1, srvpgm2, srvpgm3 > > pgm4, srvpgm1, srvpgm2 > > > > In this scenario, pgm1, pgm2, pgm3, pgm4 are all within the > > same system. > > > > would you typically, > > > > A. Not create binding directories at all. > > B. Create 1 binding directory for all of these and just add to the > > binding directory for additional programs > > C. Create a separate binding directory for each program. > > D. Other- please explain > > > > > > As i said, i'm just looking for how others are doing these > > kind of things, > > to better how i'm handling these types of things. > > > > > > Mike Smith > > Information Systems > > RGC Resources > > > > > > _______________________________________________ > > This is the RPG programming on the AS400 / iSeries (RPG400-L) > > mailing list > > To post a message email: RPG400-L@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > > or email: RPG400-L-request@midrange.com > > 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@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > 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@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. >
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.