Re: WDSC can't see files anymore in Verify

Thanks. Makes sense. I haven't every created a trigger. We try not to
use them here... I don't make the policy, I just have to follow it.


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



Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
01/14/2010 01:07 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






#3 is related to trigger programs. If a table has any locks, the trigger
program cannot be replaced.




date: Thu, 14 Jan 2010 09:46:22 -0500
from: Bryce Martin <BMartin@xxxxxxxxxxxx>
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.