VOC pointer to letter-mapped Network Drive

#1

In UniData 7.2 I am trying to build a VOC pointer
to a file on a different computer (a mac) than the
computer hosting UniData (a PC) but I get:
errno=2: No such file or directory
Open directory file BP error.
Open file error.

The VOC pointer looks like:
001 DIR
002 M:
003 D_BP

Works fine when 002 is "C:" but no joy for "M:".

<understatement>
The UniData documentation is not helpful.
</understatement>

Anybody been down this road before?

Can I get there from here?

--
frosty

#2

Put the full pathname in rather then the mapped drive letter and it
should be fine

#3

Ditto - the UNC path should work. Remember the UDT process that you
are running likely doesn't have access to all of your maps. Do a !CMD
to get to the shell prompt - then you can see your mappings etc that
are available.

hth
Colin
Calgary, Canada

On Sep 14, 2:30*am, martin kent <postrelatio... (AT) googlemail (DOT) com> wrote:

Quote:

Put the full pathname in rather then the mapped drive letter and it
should be fine

#4

On 9/14/11 2:30 AM, martin kent wrote:

Quote:

Put the full pathname in rather then the mapped drive letter and it
should be fine

Thanks for the reply, Martin.

I have already tried this:
001 DIR
002 \\computername\sharename
003 D_BP

but got the same error.

--
frosty

#5

On 9/14/11 7:40 AM, Colin wrote:

Quote:

Ditto - the UNC path should work. Remember the UDT process that you
are running likely doesn't have access to all of your maps. Do a !CMD
to get to the shell prompt - then you can see your mappings etc that
are available.

hth
Colin
Calgary, Canada

Thanks, Colin.

At the command prompt, what command should I be using?
ipconfig? netstat? something else?

--
frosty

#6

On 9/14/11 7:40 AM, Colin wrote:

Quote:

Ditto - the UNC path should work. Remember the UDT process that you
are running likely doesn't have access to all of your maps. Do a !CMD
to get to the shell prompt - then you can see your mappings etc that
are available.

I type "m:" at the command line (D'Oh) and got:
"The system cannot find the drive specified."

That's what you meant by "mappings... that are available" ?

--
frosty

#7

John, I've never looked closely at this but the network mapping is
somehow related to the user, not just mapped to the system. Even if
you use the "net use" command or the GUI, sometimes you need to
logoff/on with your Windows user to activate the change. I'd welcome
feedback on this from someone with a clue about Windows
administration.

In D3, I "!net use X: //server/path" in the user-coldstart so that I
can do what you're talking about in Q-pointers (notes on this are in
the TL forum). This seems to keep the X: reference available for the
D3 server which is always logged-in under the same user. With U2 this
might be more challenging since all users come in via a different
Windows user, but you may want to start with putting a "net use"
command in the bat file used to boot the U2 processes and see if that
helps.

I don't have a clue about why the UNC path isn't working but I suspect
that's a permissions issue - and if you can't get to data via UNC then
the drive map is likely not to work as well.

Sorry I can't be more helpful but I hope this helps to point you in
the right direction.

Bill Haskett doesn't lurk here much anymore but I know he's had a lot
of experience with UD/Win admin in his complex environment, so he
might be able to help - and there's always the U2 forum...

Best,
T

frosty <frostyj (AT) bogus (DOT) invalid> wrote:

Quote:

On 9/14/11 2:30 AM, martin kent wrote:
Put the full pathname in rather then the mapped drive letter and it
should be fine

Thanks for the reply, Martin.

I have already tried this:
001 DIR
002 \\computername\sharename
003 D_BP

but got the same error.

#8

You need to write to a folder UNDERNEATH the sharename:

\\computername\sharename\folder

I spent AGES trying to figure that one out.

Cheers,

Brian

On 14/09/2011 4:37 p.m., frosty wrote:

Quote:

On 9/14/11 2:30 AM, martin kent wrote:
Put the full pathname in rather then the mapped drive letter and it
should be fine

Thanks for the reply, Martin.

I have already tried this:
001 DIR
002 \\computername\sharename
003 D_BP

but got the same error.

#9

On 9/14/11 12:13 PM, Brian Speirs wrote:

Quote:

You need to write to a folder UNDERNEATH the sharename:

\\computername\sharename\folder

I spent AGES trying to figure that one out.

Thanks for the tip, Brian. I've tested that scenario,
too... but now I know _not_ to test it with just the
computer name and share name. Which is progress.
Which is good. =`:^P

--
frosty

#10

Quote:

On 9/14/11 10:43 AM, Tony Gravagno wrote:
In D3, I "!net use X: //server/path" in the user-coldstart
so that I can do what you're talking about in Q-pointers

Thanks, Tony.

This looks promising. I couldn't see the remote folders
from the Win server until I furnished a User ID and
password to connect to \\server\share; if there is a way
to "stack" those credentials for "net use" to use...

On 9/14/11 1:47 PM, frosty wrote:

Here's a clue. From the uniData command prompt on the
Win server:

:!dir \\computername\sharename\foldername
Logon failure: unknown user name or bad password.

:!dir \\bogusname\bogusshare\bogusfolder
The network path was not found.

In the first case, the Win box is talking to the
Mac box with the share, and the Mac recognizes
the sharename, but the Win box hasn't provided
a legal User/Password pair.

--
frosty