Re: Quick question: File exception on update

James,

(Please bear with me to the end...)

There's a price to be paid for limiting your software to be able to run 
all the way back to V2R3.  The people at the newer releases miss out on 
new features.

By the way, what makes something Native?  That format has been there since 
day one of the i5.  Isn't that native?  It doesn't require any crippled 
run time environment like PASE.

And I looked up idiomatic.  Which says that you could have restated your 
sentence as "... I was looking for something in NATIVE, NoT readily 
understood from the meaning of its component words RPG."  Which is a 100% 
true and accurate description of the old fixed format RPG - not readily 
understood.  I don't even know why that would be desired.

Back to what you wanted... (hey, if you get to rant, so do I)
There have been articles in the past about catching these messages and 
then throwing your own.  Several of the people who have done so were 
dismayed by the fact that you could always tell that you manually threw 
the message back.  Like, maybe the 2nd level text wasn't handled well or 
some such thing.  I'd have to search the archives.

Would the following work (pseudocode, you translate it back to the "not 
readily understood form").
update(e) myfile;
if %status(myfile) = ThatTriggerError;
  // do another update without extender or indicator and let the system 
throw it up.
  update myfile;
EndIf;

Rob Berendt