RE: CPF32C6 - Trigger operation not successful.

Jerry,

Perhaps they ran out of numbers?  Seriously though, I agree. It is a little
odd that the ADD/CHG/RMVPFTRG commands only returns CPF32C6.  It would be
nice to have additional "warning" messages indicating that such a trigger
already exists (ADDPFTRG) or didn't exist (RMVPFTRG).  It is a pain to
have to use the second-level message text or retrieve the prior message
to programmatically determine the true cause of CPF32C6.

Michael Rooney
Citigroup International       







-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of
GKern@xxxxxxxxxxxxxxxx
Sent: Tuesday, June 22, 2004 9:37 AM
To: midrange-l@xxxxxxxxxxxx
Subject: CPF32C6 - Trigger operation not successful.


Is there a reason why CPF32C6 is the only CPF message that can be 
monitored for regarding the adding or removing of triggers to a physical 
file? I find the message ambigous and it really doesn't tell me what I 
need to know. 

Why aren't  threre two additonal CPF messages, one specifically to 
indicate that an attempted addpftrg failed (ie...the trigger has been 
already added to the pf) and one to indicate that a rmvpftrg failed (ie... 
the specific trigger isn't applied to the PF).

Or am I missing something here? 

Regards, Jerry

Gerald Kern
IBM Certified AS/400 RPG IV Developer & RPG IV Programmer
MIS Project Leader, Lotus Notes/Domino Administrator
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.