|
IBM kept telling people to look in the job logs for QZDASOINIT jobs (the ODBC server jobs) for errors relating to SQL package corruption and "failed to extend" errors, debug messages, and so forth. Some really annoying person kept pointing out that even if an interesting message were found, in a really common case where there was no way to relate the ODBC server job to any particular client computer so one could not call the person and determine the application context that created the condition. IBM kept saying that the software vendor could send a certain kind of message to the AS/400 through each ODBC data source. The 400 would reply with the job name, user name, and job number. This information could be written into a log file. The same annoying person said that this would be fine but searching log files on 1,000 or so PCs scattered all over the place was not practical. In an effort to make the annoying person shut up, IBM coded the ODBC server jobs to query the client-side client access code and request the machine's name or IP address then report the answer in the job log and the QHST files. The messages that you see in QHST can help to relate a specific ODBC server job (a QZDASOINIT job) to a specific client machine. Of course, if the client machine is running terminal server ... well never mind. Richard Jackson mailto:richardjackson@richardjackson.net http://www.richardjacksonltd.com Voice: 1 (303) 808-8058 Fax: 1 (303) 663-4325 -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of oliver.wenzel@cibavision.Novartis.com Sent: Tuesday, August 22, 2000 8:13 AM To: MIDRANGE-L@midrange.com Subject: CPIAD12 - what is it ?? Hello, ever since going to V4R3 on our 620, I'm getting this CPIAD12 message in QHST quite often. It says something like (rough translation from german) : Servicing userprofile xxx from client 170.60.24.75. I see no negative effects from this message - but would like to know what it means and why/when it is sent? Thx, Oliver +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.