|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] 1) Was this program working prior to V5R1? 2) Is this your first trigger program? 3) Please post your *ENTRY or your programs initial PI, whichever method you are using. And also post the datastructures used to make up these variables. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Roger Vicker, CCP" <rvicker@vicker.com> Sent by: rpg400-l-admin@midrange.com 04/02/2002 03:43 PM Please respond to rpg400-l To: RPG400 <rpg400-l@midrange.com> cc: Fax to: Subject: Trigger parameters blank filled. Hello, I am using a system at V5R1M0 with current Cum PTF and trying to create a new trigger program in RPGLE. My problem is that when the trigger fires the first parameter (the buffers) is blank filled and the second parm (buffer length) is zero. I've tried compiling DFTACTGRP(*YES) and DFTACTGRP(*NO) ACTGRP(*CALLER) with no difference. I've tried using procedure definitions and *ENTRY PLIST. The program is compiled with CRTBNDRPG To add the trigger I use ADDPFTRG FILE(FILELIB/FILE) TRGTIME(*AFTER) TRGEVENT(*INSERT) PGM(PGMLIB/TRIGGER) Shouldn't the parms always have something at least? Thanks. Roger Vicker, CCP -- *** Vicker Programming and Service *** Have bits will byte *** www.vicker.com *** Where bribes are cheerfully accepted. _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
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.