There is a way to run a batch job with the user profile that has the special
authorities.
I use it for /QNTC processing.
See this article...
http://www.itjungle.com/mpo/mpo071703-story02.html
It allows your job to swap user profiles and do what you need to do and then
set the profile back again.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan
Cassidy
Sent: Tuesday, June 23, 2015 5:35 PM
To: Midrange Systems Technical Discussion
Subject: RE: Accessing a Windows share folder using QNTC
Thanks everybody for the replies.
I think this will give y'all another reason to avoid QNTC. (And if you can
shops with big dot-net oriented departments like mine)
Chris, I thought about creating the program to run under the Owner profile
(it's a unique user profile to be used for special functions, and I think
created for this present task. ) BUT we need to run this with the Start-up
program at IPL. ...(We IPL nightly here, I don't know why). So we need the
startup program, which runs under its own user-id, to be able to kick off
this create.
Meantime I discovered this paragraph on the link that Gary posted:
10. Now sign on the System i with a user ID (usually with administrator
authority on the Windows Server) that has the proper authorities to the
specific shares to be accessed on the Windows Server and run WRKLNK QNTC.
Type a 5 next to QNTC and press the Enter key. If you do not see the name of
the Windows Server, verify Steps 2, 3, 4, and 7. If you configure Steps 5
and 6, verify those steps also. If assistance is required with Steps 4, 5,
and 6 (if the DNS is other than the System i DNS) you can refer to
www.microsoft.com/support, call Microsoft Support, or we can assist under a
consulting agreement
I've suggested now doing the following:
#1. Change the program that creates this link to submit itself to its own
job queue as the last step, but after it puts that job queue on hold.
#2. Create that job queue and put it on hold.
#3. Submit the program to that job queue.
#4. Change the start-up to release that job queue.
When the start-up runs, it will hit step #4 above and release the job that
runs the program, completely under the appropriate user-ID. The program
itself will put the job queue back on hold before submitting the next job to
it.
(This is my first brush with QNTC.. Yuck!)
I will report back.
Thanks everybody!
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris
Bipes
Sent: Tuesday, June 23, 2015 4:58 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Accessing a Windows share folder using QNTC
I find if you create the program to run under Owner Profile and change the
Owner to the appropriate profile, You alleviate most security issues.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
What happens when you submit when you are signed on as the user in the
USERID parm?
Running a job with USERID(userid) is not the same thing as running a job as
that user.
--
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.
----------------------------------------------------------------------------
----
Confidentiality Notice: This email may contain confidential information or
information covered under the Privacy Act, 5 USC 552(a), and/or the Health
Insurance Portability and Accountability Act (PL 104-191) and its various
implementing regulations and must be protected in accordance with those
provisions. It contains information that is legally privileged, confidential
or otherwise protected from use or disclosure. This e-mail message,
including any attachments, is for the sole use of the intended recipient(s).
Any unauthorized review, use, disclosure or distribution is prohibited. You,
the recipient, are obligated to maintain it in a safe, secure and
confidential manner. If you are not the intended recipient, please contact
the sender by reply e-mail and destroy all copies of the original message.
Thank you.
----------------------------------------------------------------------------
----
--
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
