Of course, if you're calling DLTLIB from one subprocedure and ADDLIBLE from
another, and trapping the error in a high-level subproc, that could be your
issue.
-Bob Cozzi
www.i5PodCast.com
Ask your manager to watch i5 TV
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [
mailto:rpg400-l-bounces@xxxxxxxxxxxx] On
Behalf Of Bob Cozzi
Sent: Tuesday, May 08, 2007 8:57 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: ON-ERROR catches CPF2103 but not CPF2110
Aaron,
Both messages are sent as ESCAPE messages, and both are severity 40 so it
shouldn't matter which one is issued. It may be that a second message is also
being issued in one case, but not the other and that second message is
triggering the on-error.
Are you using QCMDEXC or system() to perform the CL commands?
If you're using QCMDEXC check to see if you have CALLP(e) on one of the calls
but not the other. The (E) extender doesn't play nice with MONITOR.
-Bob Cozzi
www.i5PodCast.com
Ask your manager to watch i5 TV
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [
mailto:rpg400-l-bounces@xxxxxxxxxxxx] On
Behalf Of albartell
Sent: Tuesday, May 08, 2007 8:48 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: ON-ERROR catches CPF2103 but not CPF2110
I am doing some RPG unit testing which entails creating/deleting libraries
on the fly from RPG. If I execute DLTLIB LIB(MYLIB) and MYLIB doesn't
exists then CPF2110 is thrown, but the ON-ERROR clause I have wrapping the
DLTLIB call doesn't catch the error and instead immediately ends the
program. On the other hand if I do an ADDLIBLE LIB(MYLIB) when MYLIB
_doesn't_ exist a CPF2103 is thrown and the ON-ERROR clause _does_ catch the
error.
Any thoughts?
Aaron Bartell
http://mowyourlawn.com
midrange.com
