× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Mark Bauman wrote:
    <snip>

> NOTE:  I just saw Neil's message in response to your subsequent posting
> on the midrange.  Neil has posted an excellent note that also answers
> your questions - only in better detail than I was planning to do.
> However, there is one small correction.  Neil writes:
> 
> Excerpts from mail: 7-Aug-97 Re: Trigger PC Job Neil Palmer@NxTrend.com
> (7133*)
> 
> >  It appears the RUNRMTCMD for a PC running CA/400 will ONLY
> > work with an SNA connection.  The TCP option is for Unix systems only.
> > (You COULD connect to the PC via AnyNet).
> 
> CA/400 is shipped with server remote command support that will run over
> TCP/IP or over SNA. The TCP/IP CA/400 remote command daemon is written
> to Winsock and is started by CA/400 with a program called CWBRXD.EXE.
> You DO NOT need to use *SNA on the RUNRMTCMD to connect to the PC if you
> have your CA/400 connected via TCP/IP.  The information unit Neil
> extracted from IBM Technical Q&A support also has it incorrectly stated.
> 
> By the way, for the SNA CA/400 remote command daemon, run the
> AREXECDW.EXE or AREXECDN.EXE
> 
> (I don't use CA/400  so I asked CA/400 developers for the above information)
> 

I had misread the RUNRMTCMD help text, but it is written rather
awkwardly.  Mark, maybe you can pass this note on to the appropriate
department and have them reword the confusing help text.
I would rewrite the following paragraph of the help text as shown below:

                                                                  
  The target portion of this function can be an rexecd (remote        
  executing) daemon if you specify *TCP for the address type, or an   
  arexecd (APPC executing) daemon if you specify *SNA for the address 
  type.  If you want to run a command on a Client Access/400 client   
  that supports the arexecd (APPC) daemon, you will need to specify
*SNA   for the address type.      


ACTUAL HELP TEXT (V3R2) BELOW:

                     Run Remote Command - Help                        
                                                                      
  The Run Remote Command (RUNRMTCMD) command allows AS/400 users to   
  run a command on a remote system that is running the target portion 
  of this function.                                                   
                                                                      
  The target portion of this function can be an rexecd (remote        
  executing) daemon if you specify *TCP for the address type, or an   
  arexecd (APPC executing) daemon if you specify *SNA for the address 
  type.  If you want to run a command on a Client Access/400 client   
  that supports this function, you will need to specify *SNA for the  
  address type.                                                       
                                                                      
  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.                           

-- 
... Neil Palmer                                      AS/400~~~~~      
... NxTrend Technology -Canada       ____________          ___  ~     
... Markham,  Ontario,  Canada       |OOOOOOOOOO| ________  o|__||=   
... Phone: (905) 731-9000 x238       |__________|_|______|_|______)   
... url:http://www.NxTrend.com        oo      oo   oo  oo   OOOo=o\   
... mailto:NPalmer@NxTrend.com     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.