RE: Function Opinion

That's exactly why I suggested not naming your module the same as the end 
program, or service, program.  Doing that alone, should avoid you having 
do the physical slapping.
Then the person should look at the original final object to see what 
modules make it up, where the original modules source is, etc.

Then again, a good change management tool should assist greatly...

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Bill Hopkins" <BHopkins@xxxxxxxxxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
10/16/2003 01:59 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
cc

Subject
RE: Function Opinion






" Also helps to beat into submission those who clobber your program with 
> CRTBNDRPG when they should have used CRTRPGMOD and then either CRTPGM or 


> CRTSRVPGM, (or the UPD... variant.)"

Well in the defense of the company I'm working for now. They just got the 
"How to compile Doc" from their vendor for their PKMS version that they 
moved up to 5 months ago( I had already written one ) but of course was 
still getting asked which way to do it daily.  Not to hard to figure when 
modules end in MR if RPGLE, srv end in SR if service RPGLE, modules end in 

MC if C, srv end in SC if service C,but they do the above all the time. 

Their fault for not knowing what the vendor's 
program name standards were or figuring it out?

Vendors lack of training on product?

Vendors not suppling needed docs? 

Or all of the above?

Crap like this keeps me employed. Scary :)

Bill Hopkins 
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.