× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2008

Re: Change the job log settings on QZDASOINIT

Thanks Eric. I'll take a look at that as well. The client application is running Windows NT and an older version of the Hit ODBC driver which may or may not have those options but it is certainly worth a look.

Pete

DeLong, Eric wrote:
Pete,

Can you just change the ODBC Datasource definition to use logging options? Open the datasource, which should be using an IBM odbc driver, and select the diagnostic tab. There should be an option on that panel called "Print Joblog at disconnect".

Eric

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Pete Helgren
Sent: Monday, February 11, 2008 11:07 AM
To: Midrange Systems Technical Discussion
Subject: Change the job log settings on QZDASOINIT


I have a problem with an application that uses ODBC to connect to DB2 for i5/OS. For the customer, the quickest fix is to stop and start the application, which disconnects from the System i and then restarts the connections. However, the information in the QZDASOINIT connection job is lost. The job log isn't retained. I am pretty sure that this is because of the way the prestart job is defined but I am not sure. Anyone have a quick pointer on how to get a job log retained when a QZDASOINIT job is ended?

Thanks,

Pete


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.