Re: Starting a remote command without hard coding a password

[Evan Harris <spanner@xxxxxxxxxx>]

Hi Dave

Without going down the remote command track, I can think of two possibilities:

1. Create a remote data queue and pipe the command you want to run 
over the data queue to a server job on the target system
2. Create a file on the target system and add a new record trigger 
that calls your restore process; update the file via DDM from the source system

Regards
Evan Harris

At 08:53 a.m. 11/11/2005, you wrote:
> 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.<<
> --