RE: runrmtcmd network connection

["Hatzenbeler, Tim" <thatzenbeler@xxxxxxxxxxxxx>]

I did see the net use archives... I just thought it was for older operating
system before mapped drives were allowed to re-connect durring startup....

I will pursue this direction...

thanks, tim

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [SMTP:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CWilt@xxxxxxxxxxxx
> Sent: Tuesday, March 16, 2004 6:47 AM
> To:   midrange-l@xxxxxxxxxxxx
> Subject:      RE: runrmtcmd network connection
> 
> The remote command is run separately from whomever may or may not be
> logged
> onto the PC.
> 
> Basically, the drive isn't mapped during the execution of the remote
> command.
> 
> There should lots of info in the archive about this; also I think IBM has
> this documented in the KB.
> 
> As I recall, you need to be calling a batch file that includes the net use
> commands to map the drive.
> 
> 
> HTH,
> Charles
> 
> 
> > -----Original Message-----
> > From: Hatzenbeler, Tim [mailto:thatzenbeler@xxxxxxxxxxxxx]
> > Sent: Monday, March 15, 2004 7:28 PM
> > To: 'midrange-l@xxxxxxxxxxxx'
> > Subject: runrmtcmd network connection
> > 
> > 
> > I'm stumped...
> > 
> > I have a PC, that I send commands to, via runrmtcmd, via an 
> > *ip connection
> > with a user name and password...
> > 
> > And it works fine... However, when I try to do a DIR command 
> > of a mapped
> > drive letter, thats mapped to the 400's IFS I get Access denied..
> > 
> > But if I walk over to that PC, I can get to that drive via a 
> > DOS prompt or
> > the Explorer Program...
> > 
> > So the PC is connected... But I'm assuming, the profile of 
> > the connected
> > runrmtcmd call is not authorized to the mapped drives... Is 
> > there a way
> > around this?
> > 
> > Thanks, tim 
> > This e-mail message, including any attachments, is for the 
> > sole use of the
> > intended recipient(s) and may contain confidential or privileged
> > information.  Any unauthorized review, use, disclosure or 
> > distribution is
> > prohibited.  If you are not the intended recipient, please contact the
> > sender by reply e-mail and destroy the message.
> > _______________________________________________
> > 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.
> > 
> _______________________________________________
> 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.
> 
This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential or privileged
information.  Any unauthorized review, use, disclosure or distribution is
prohibited.  If you are not the intended recipient, please contact the
sender by reply e-mail and destroy the message.