Re: Error in TRIGGER (CLE) pgm

[Jeff Young <cooljeff913@xxxxxxxxx>]

Make the trigger an RPGLE program and compile with the keyword FIXNBR(*ZONED *INPUTPACKED)  Note that the *INPUTPACKED value will cause the field to be set to ZERO.


 
Jeff Young 
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2 
IBM  Certified Specialist- e(logo) server i5Series Technical Solutions Designer V5R3
IBM  Certified Specialist- e(logo)server i5Series Technical Solutions Implementer V5R3 


  
 





----- Original Message ----
From: "MKirkpatrick@xxxxxxxxxxxxxxxxx" <MKirkpatrick@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Friday, September 7, 2007 4:17:13 PM
Subject: Error in TRIGGER (CLE) pgm


I have created a simple trigger to INSERT a row into another file when a 
change on one of my fields occurs.  When this trigger get executed, I am 
receiving an error in the CLE pgm.  Upon review of the stmt in the CLE 
pgm, I have determined that it is being caused by *blanks in a packed 
field. (old s/36 stuff).  Knowing that the best solution would be to clean 
up the data and fix the pgms that are causing the bad data to be written, 
is there another way of getting around this issue and use the SQL trigger?
Thanks.




This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.  Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone this email or any information contained in this email.  If you have received this email in error, please advise the sender by replying to this email, and delete this email immediately.  Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Western Dental Services, Inc.  Finally, the recipient should check this email and any attachments for the presence of viruses. Western Dental Services, Inc. accepts no liability for any damage caused by any virus transmitted by this email.