|
Carl: It's not clear exactly what you want to do. Do you want the command-processing program to be able to determine where the command came from? Do you want to look from some other job into a server job that's executing that command and extract info about the remote system? Hmmm... I'm not sure it matters. Seems to me that the way to do this is via an exit program on the QIBM_QTMX_SERVER_REQ exit point. The remote IP address is passed by the server into the exit program. You can then stash that address along with the remote command itself, if you wish, wherever you choose so the info is available to the command when it runs or to any other job. Tom Liotta midrange-l-request@xxxxxxxxxxxx wrote: > 9. RE: What REMOTE system started the RUNRMTCMD (Carl Galgano) > >Don, my purpose was to not have to change every program to pass the >parameter. Anyone know the API to do this? >cjg > >-----Original Message----- >[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Fisher, Don > >I believe there are APIs that will do what you want. However, the simplest >thing might be to pass the calling system name as a parameter to the program >being executed. The name can be retrieved on the calling system with >RTVNETA. > ><clip> >How can I determine in a CL program what system has initiated the RUNRMTCMD >command. <clip> -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 x313 Fax 253-872-7904 http://www.powertechgroup.com __________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.