|
I might suggest SQL stored procedures.... You could CONNECT to the remote system, then call a stored procedure, or UDF to execute your program, returning the output parms in a result set. Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-898-7863 or ext. 1863 -----Original Message----- From: Vern Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx] Sent: Thursday, May 06, 2004 8:28 AM To: Midrange Systems Technical Discussion Subject: Re: RUNRMTCMD Mike, this won't work as is because parameters are passed with pointers. Besides, you are not passing the parameters to a CALL, you are passing a command string that is interpreted on the remote system. The pointers on the remote system have nothing to do with those on the local one. Usually, as Don said, you need an external mechanism to pass data between systems. However, you might still be able to make this work without setting up things like data queues or message queues or whatever. According to the help for RUNRMTCMD, "When the command is sent to the remote system, the local system waits for the command to complete and the output from the remote command will be placed in a spooled file." You could have your remote program put anything into a spooled file, then extract them on the local machine. Maybe? HTH Vern At 08:02 AM 5/6/2004, you wrote: >I need to run an RPG program on a remote 400 from a source 400. I also need >to pass parameters for the call and have parameters returned. I have >researched the RUNRMTCMD command in the archives, but all of the past >messages seem to revolve around PC remote calls. > >Here is my situation: >I have a process that runs on my source 400. If the process fails, it needs >to run a program on the remote 400 that will run a different process. The >end message depends on the success or failure of the processes. I need to >pass parameters and receive parameters on the remote call. _______________________________________________ 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.