RE: Starting a remote command without hard coding a password

Is using SAVRSTLIB over all the libraries directly out of the question?

SAVRSTLIB LIB(LIB1 LIB2 LIB3 LIB5 LIB999)
          RMTLOCNAME(REMOTE1)            

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Dave Odom
Sent: Thursday, November 10, 2005 1:54 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Starting a remote command without hard coding a password


A problem from a colleague of mine but a good solution could also help
me.

Thanks in advance,

Dave Odom

Colleague wrote:

>>I'm trying to write a CLP to refresh the data on our test partition
(not
environment, but partition).  I've written each library's SAVLIB to a
SAVF
in a special library and done the SAVRSTLIB to get that lib moved to
test.
Now I'm trying to figure out to start the restores on the test
partition
from the program on the production partition.  I can do RUNRMTCMD from
prod
to test (or vice versa, for that matter, with consistent lack of
results),
but ONLY if I hardcode a password (otherwise CPF1269, reason code
2021).
RUNRMTCMD allows specifying *CURRENT for user profile, like STRPASTHR
does,
but it does not accept it without a password, at least not in my
environment.  I just spent 45 minutes or so talking to Support Line
and
nothing they suggested worked.  Have any of you hotshot communication
people out there succeeded in doing something like this?  My test
command
looks like this:
RUNRMTCMD CMD(DSPLIBL OUTPUT(*PRINT)) RMTLOCNAME(B1050A8D *SNA)
RMTUSER
(*CURRENT)
The QAPPNRMT configuration list on both sides specifies Secure Loc
*YES.

All suggestions (at least those related to this question and not some
anatomical impossibility) greatly appreciated.  Support Line suggested
possibly issuing the command thru ftp or SQL, but I don't see how to
get
around the pwd requirement, like STRPASTHR does.<<