error handling in ims

I would appreciate suggestion on how to handle unespected errors (for
example database return codes) in cobol/ims. Intentional abend?
Logging error? Rollback? Display? Format with error description?
Thanks
Piero

In article <cbf8aea2.0504220549.4e74b5e5@posting.google.com>,
piero <pietro_crincoli@yahoo.it> wrote:
>I would appreciate suggestion on how to handle unespected errors (for
>example database return codes) in cobol/ims. Intentional abend?
>Logging error? Rollback? Display? Format with error description?

These are all possibilities... don't forget the standard:

When in danger, when in doubt -
Run in circles, scream and shout.

DD

My suggestions are:

A) (most important) check with the user or user group to see what THEY want

B) see what (if anything) is your "shop standard" (and who gets called with 
what
information at 2 a.m. when this happens)

--
Bill Klein
wmklein <at> ix.netcom.com
"piero" <pietro_crincoli@yahoo.it> wrote in message
news:cbf8aea2.0504220549.4e74b5e5@posting.google.com...
>I would appreciate suggestion on how to handle unespected errors (for
> example database return codes) in cobol/ims. Intentional abend?
> Logging error? Rollback? Display? Format with error description?
> Thanks
> Piero

My suggestions are:

A) (most important) check with the user or user group to see what THEY want

B) see what (if anything) is your "shop standard" (and who gets called with 
what
information at 2 a.m. when this happens)

--
Bill Klein
wmklein <at> ix.netcom.com
"piero" <pietro_crincoli@yahoo.it> wrote in message
news:cbf8aea2.0504220549.4e74b5e5@posting.google.com...
>I would appreciate suggestion on how to handle unespected errors (for
> example database return codes) in cobol/ims. Intentional abend?
> Logging error? Rollback? Display? Format with error description?
> Thanks
> Piero