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





Perhaps I misunderstand the use of the user parm. Wouldn't you need the USER'S credentials.  Especially  when accessing a /QNTC share?


Sent from my Verizon Wireless 4G LTE smartphone

-------- Original message --------
From: CRPence <crpbottle@xxxxxxxxx>
Date: 06/23/2015 6:27 PM (GMT-05:00)
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Accessing a Windows share folder using QNTC

On 23-Jun-2015 14:17 -0600, paultherrien wrote:
On 23-Jun-2015 13:52 -0600, Alan Cassidy wrote:
<<SNIP>>
But we need to create this share every day with a job to be
included in the Startup. We tried SBMJOB with USER(USERID) to run
the program that creates the /QNTC subdirectory that accesses the
Windows share. Nonetheless, the program backfires with this
message:

Not authorized to object. Object is /QNTC/10.11.12.14/ABC. (I used
MKDIR to "create" the link in QNTC.


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.


   First a clarification, the Submit Job (SBMJOB) has a User (USER)
parameter, as in the OP, not USERID().  Second, in what way is SBMJOB
USER(userid) "not the same thing as running a job as that user"?  Is
that solely an allusion to the *CURRENT default values?  Seems anything
in that regard would not interfere with /authorization/, especially
unlikely affecting to the request merely to Make Directory (MKDIR).?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.