RE: [sqr-users] SQE Error logging in mainframe environment

["Sengupta, Rajib \(Contractor\)" <Rajib.Sengupta@conagrafoods.com>]

I had implemented this successfully in different OS/390 environments using 
SYSPRINT, SYSTERM and SYSERR.
Thanks,
Rajib


Rajib Sengupta
Systems Analyst and Team Lead
Peoplesoft Financial Consultant
Conagra Business Systems


-----Original Message-----
From: sqr-users-bounces+rajib.sengupta=conagrafoods.com@sqrug.org
[mailto:sqr-users-bounces+rajib.sengupta=conagrafoods.com@sqrug.org]On
Behalf Of Gunjala Pradeep (XFF3PXG)
Sent: Wednesday, March 23, 2005 12:43 PM
To: sqr-users@sqrug.org
Subject: [sqr-users] SQE Error logging in mainframe environment


Hello Esteemed List,
Please share your ideas or best practices you have implemented. We run
our SQRs in mainframe environment using JCL and database is DB2 on
OS/390. We are tryingn to desing a good error logging or capturing
mechanism in our SQRs those would write enough information to SYSOUT, so
that operaters and developers can easily figureout the nature of error. 
As far as DB2 errors are concerned we are thinking to customize
SQL-ERROR SQC to have more detailed information like in which procedure
it failed etc...But as far as file related errors, or runtime errors or
environment errors are concerned, how do we capture them and write them
to SYSOUT. I am sure many of you might have implemented some error
logging mechanism, please share your ideas and experiences. 
Thank you.
- Pete

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users