Re: WDSC can't see files anymore in Verify

I'm not the original poster of those 3 reasons for using Verify, however when an object's authority has changed, you may not be able to replace it with a compile. In those situations I've always had to manually delete the object then compile (we have one or two programs where I work like that, so it's not very common).

-Kurt

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Bryce Martin
Sent: Thursday, January 14, 2010 8:46 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] WDSC can't see files anymore in Verify

I understand #1 if you have an undersized server, I haven't really had
much problems with #2, but #3 has me perplexed. In what situation would
the program object be locked? Even if someone is actively using the
program you can compile a new version. Then, if all conditions being met,
the next time they run the program they will have the new version. How
does #3 happen?


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
01/13/2010 05:50 PM
Please respond to
Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>


To
"wdsci-l@xxxxxxxxxxxx" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] WDSC can't see files anymore in Verify






I use verify for these reasons:
1. Less server workload
2. SQLRPGLE
3. Program objects that are locked cannot be compiled, but Verify will
check for syntax errors.