×
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.
On Fri, Mar 3, 2017 at 11:10 AM, Rob Berendt <rob@xxxxxxxxx> wrote:
How did you resolve this back in 2014?
https://archive.midrange.com/pctech/201405/msg00013.html
Never did. Had the user on the Windows 7 PC go get the file from the IBM
i.
Did you try
MD '/QNTC/MYWIN7PC'
Then
WRKLNK '/QNTC/MYWIN7PC/*'
Sometimes you have to build that initial link. Maybe even put it in your
startup.
The link is already there. Only to the PC, not to any of the shares. A MD
of one of the shares results in:
Message ID . . . . . . : CPFA09C
Date sent . . . . . . : 03/03/17 Time sent . . . . . . :
12:30:19
Message . . . . : Not authorized to object. Object is
/QNTC/JLCROSBY/IRECOVERY.
Cause . . . . . : You do not have the correct authority for object
/QNTC/JLCROSBY/IRECOVERY or for one of the directories in the object
path.
Recovery . . . : Contact your security officer, the object owner, or
other
authorized person to obtain the correct authority to use object
/QNTC/JLCROSBY/IRECOVERY or the directories in the object path, and try
your
request again. If the object name is *N, it could not be determined which
of
the objects authority was not sufficient.
The System i Security Reference, SC41-5302, contains authority
information
for the operation.
midrange.com
