Re: I seek overall advice.

I wouldn't change the default reply handling. Identify why the programs are
blowing up and fix it. The last thing you want is bad data - it sucks, but
fixing the programs is the only way out of that problem.

You can scan the CL source and change the hardcoded library names to *LIBL
(if that's appropriate). Make sure you have the correct library lists when
your users run those programs. Probably want to examine the job description
that's associated with the user profile.

The missing/unknown source is a tough one. You might be able to put the
programs in debug and read the code and try and match it up.

The only benefit to giving users *ALLOBJ authority is that you don't have to
worry about security problems. However, the downside is that any user at any
time could trash data. You need to change this pretty as soon as you can.

On 12/21/05 06:58 PM, "Grizzly M" <grizzlym@xxxxxxxxxxxxxxxxxxxxx> wrote:

> Not sure where this should be posted. Either this list, Midrange-L, or
> the CPF000-L list.
> 
> Can anyone make a suggestion as to what would be a good way to handle
> exception errors for RPG II programs? Up until May of 2005 the previous
> programmer here wrote and maintained program in RPG II. That drives me
> nuts. Regardless of that these programs seem to crash at least once a
> day. It happens so often that the users think that answering the break
> messages is actually a programming feature the previous programmer put
> in place. I think that is unreal. Is there a way to change the default
> break handling to do something other than present the message and allow
> the user to answer?
> 
> The other problems are as follow:
> 
> There are over 400 CL programs with hardcoded libraries.
> 
> There are over 400 programs that don't have the correct source members
> they were compiled from. The previous method of testing/implementation
> was to creating a new test library for each project, compile programs
> there, copy objects to the production library after testing,
> occasionally copy the source member to the production source library,
> and then delete the test library.
> 
> Finally, can anyone tell me the benefits of giving all of the users
> *ALLOBJ special authority and setting their group profile to QPGMR?
> What about the users that have *SYSOPR as their user class that aren't
> really system operators?
> 
> --
> 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.
> 
>