Re: Another STRPCCMD question

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

Hi Nick,

Just in case it's useful...    there's a Windows command called 'NET' 
that can be used to establish network credentials.  For example:

   net use T: \\i520\klemscot bigboy /USER:klemscot

In this case, it maps drive letter T: on the PC to the network share 
named \\i520\klemscot (which happens to be my home directory on my 
System i 520).   It logs in as userid=klemscot, password=bigboy.

Once that has been run, the network connection has been mapped and you 
can access it as drive T: without any further need to specify 
userid/password.

You can invoke the 'net' command via STRPCCMD if you like.  I know of 
some System i folks who solve the "unmatched user/password" problem by 
create a "general access" account in i5/OS (a single profile shared by 
everyone), and then having a CL program that runs when users log on to 
create the drive mapping (as in the example above).   Then all of their 
software that needs to access the IFS uses the drive mapping.

Obviously it's not recommended to do this in an environment where 
security is important, since the password is hard-coded into the CL 
program -- and even if you keep the source code secure, it's sent over 
the network in plain text.  To say nothing about the fact that all users 
have access to the same stuff in the IFS, since they share a common profile.

So I don't really recommend this approach, I just want to point out that 
it's possible.

nickmart@xxxxxxxxxxxxxxx wrote:
> I think Eric and John E. have shed some light on the situation. We already
> had the share portion covered.
>
> In our case, the network userid and password are NOT the same as the i5
> profile. Once I mapped a drive to the IFS using the i5 user and password,
> the STRPCCMD worked as on other machines.
>
> Thanks to all who replied back to my posting and my apologies to David and
> the rest of the RPG list for posting this on that list instead of here
> where it belongs.
>
> Nick