× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Jerry,

How about the following for:

<code>
PGM                                                     
DCL        &JOB        *CHAR   10                       
DCL        &USER       *CHAR   10                       
DCL        &NBR        *CHAR   6                        
DCL        &TRIGGER    *CHAR   26                       
                                                        
RTVJOBA    JOB(&JOB) USER(&USER) NBR(&NBR)              
                                                        
CHGVAR     &TRIGGER VALUE(&JOB *TCAT &USER *TCAT &NBR)  
                                                        
CRTPF      QTEMP/TEST   RCDLEN(133)                     
                                                        
ADDPFTRG   FILE(QTEMP/TEST) TRGTIME(*AFTER) +           
           TRGEVENT(*INSERT) PGM(FTPERRORS) +           
           TRG(&TRIGGER) TRGLIB(QGPL)                   
                                                        
RMVPFTRG   FILE(QTEMP/TEST) TRGTIME(*AFTER) +           
           TRGEVENT(*INSERT) TRG(&TRIGGER) TRGLIB(QGPL) 
                                                        
ENDPGM
<code>

I must confess however, that on my V5R1 system, the above RMVPFTRG fails.  The
text states something to the effect that if TRG is not *ALL, than TRGTIME and
TRGEVENT must be *ALL.  What I find troubling is the fact that IBM provides the
following example which seems to contradict this statement:

"TRG(ABC) TRGTIME(*BEFORE) TRGEVENT(*INSERT) - The trigger named ABC is removed
if the trigger time is *BEFORE and the triggered event is *INSERT.  If the 
trigger
time and triggered event do not match, trigger ABC will not be removed."

As I am at V5R1, I suspected I might be missing a PTF but a quick search does
reflect any V5R1 PTF's for RMVPFTRG.  What OS level are you at?  If V5R2 or 
V5R3,
does my sample behave differently?

Sorry to be answering your question with a question...

Regards,

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 12:13 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: CPF32C6 - Trigger operation not successful.


Thanks Michael (Rooney):

Your idea to 'specify a TRG value generated by your CLP' wouldn't provide 
me with a known value should I desire to remove that specific trigger - I 
wouldn't know its specific name. But that concept led me to a possible 
solution. 

Your suggestion would mean doing a DSPFD to an *outfile. 

 DSPFD FILE(MYFILE) TYPE(*TRG) OUTPUT(*OUTFILE) OUTFILE(MYLIB/MYOUTFILE) 

>From the outfile I can read the records and they provide the information 
that helps me determine if a specific trigger is applied.

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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.