Error handling in RPG IV. (and SQL v. RPG db access)

  I'm currently doing some (further) investigation into using
  referential integrity and triggering on our files. (Stop! Don't
  flame me, I know they're different things!) I've established that
  using an embedded SQL to update a file is actually quite manageable
  - if the INSERT breaks an R/I constraint, you just get a negative
  return flag.

  What I'm interested in, first of all, is how I might use the *PSSR
  error handling routine to prevent a termination level error trashing
  my program if I break a constraint. When the routine is called, how
  do I get it to return to the point just after it was called if I
  deem the error to be 'handleable'?

  Also, a colleague told me of anecdotal evidence that embedded SQL is
  cool for fiddling around with large blocks of records, but gets
  blown out of the water (performance wise) by RPG when doing record
  by record work. Anybody else have this experience?

  TIA

  Tim Lennon.
  A/P Thomas Miler & Co., London.
  lennontc@mutual.co.uk
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *