Re: Observation on QZRCSRVS jobs -- MIDRANGE-L

× 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.

My WRKODBCJOB can be used for "seeing" the serviced user profile.

If you prompt it you can cnage the default behaivour of looking for QZDASONINT jobs and look for the jobs in question.

Bryan

http://home.roadrunner.com/~jbmmdietz/wrkodbcjob.html

James H. H. Lampert said the following on 10/26/2009 4:51 PM:

I just got through debugging a library list issue with a server job generated from a Java Toolbox call.

One of the things that made it a challenge was that even though the joblog showed the user profile from which we connect, the job still shows up in WRKACTJOB as being under QUSER.

And even though it gets its initial library list from that user's default *JOBD, the job's definition attributes show it as using QZBSJOBD.

Makes me kind of feel like I've been "down the rabbit-hole" on this one.

Also makes me kind of glad I didn't switch our client-server products from their proprietary communication protocols (which go to great lengths to run their child-server jobs completely under the correct user profile) to the Toolbox.

--
JHHL

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.