I don't think so, Bryan. At least, I've never figured out how to do it. The QZDASOINIT job's JOBD is configured from the prestart job entry and is already an active job when the user connects. The job does a profile swap from QUSER to the user's profile but doesn't pick up any of the JOBD or other attributes from the user's profile. The profile swap only changes the user for security purposes. The job continues to "belong" to QUSER.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bryan Dietz
Sent: Monday, November 28, 2011 3:03 PM
To: Midrange Systems Technical Discussion
Subject: Re: ADO Connection to iSeries
If there is a jobd attached to the user profile that library list should be used when you connect.
I have seen cases where if the user was not authorized to a library on the jobd's library list then the jobd's library list would not be in effect. Check the audit log for AF(authorization) failures.
Thanks the the kind words on the utility.
Bryan
Michael Naughton said the following on 11/28/2011 12:06 PM:
Bryan - thank you! What a great utility -- it's been _very_ helpful.
I've confirmed that I can get a job to run using my test user profile, but Dan was right -- the job's library list doesn't change. I'm going to look into how to change it on the connection string -- I'm not using a DSN, so I can't do it there.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
