|
HTH Vern
I am just a little confused. Once rexecd is installed, do I still use the RUNRMTCMD in my CL? And do I need to run a service on my server to run rexecd?
-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg Sent: Thursday, September 09, 2004 4:40 PM To: Midrange Systems Technical Discussion Subject: RE: Can RUNRMTCMD run on a Windows Server?
A Windows server may already have the rexecd server - it might need to be installed. The Incoming Remote Command piece of iSeries Access is a type of rexecd, but you end up with a lot of extra stuff. You can minimize it but still get too much, if all you need is the rexecd ("d" stands for "daemon", which is Greek for servant, I think -- hence, server).
Vern
At 03:34 PM 9/9/2004, you wrote: >I will run the RUNRMTCMD in a CL on our iSeries > >-----Original Message----- >From: midrange-l-bounces@xxxxxxxxxxxx >[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CWilt@xxxxxxxxxxxx >Sent: Thursday, September 09, 2004 3:11 PM >To: midrange-l@xxxxxxxxxxxx >Subject: RE: Can RUNRMTCMD run on a Windows Server? > >Hector, > >Just Google for a REXEC daemon. That's what RUNRMTCMD uses and it is a >standard TCP/IP utility. It's all you need to install. > >Wait, are you running the RUNRMTCMD on the iSeries to the PC or vice >versa? >Either way REXEC is what you want to look for, either the client or a >server >(daemon) > >HTH, >Charles > > > > -----Original Message----- > > From: Hector Sanchez [mailto:Hector.Sanchez@xxxxxxxxxx] > > Sent: Thursday, September 09, 2004 3:53 PM > > To: midrange-l@xxxxxxxxxxxx > > Subject: Can RUNRMTCMD run on a Windows Server? > > > > > > I have used RUNRMTCMD on PCs in the past, but now have the need to run > > it on a server. Can this be done? And do I need to install Client > > Access on the server to make the command work? If Client Access is > > needed, is it possible to do a Selective Install for just the > > RUNRMTCMD? > > > > Hector Sanchez > > Driscoll Children's Hospital > > > > -- > > 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. > > >-- >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. > > > > >-- >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.
-- 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.
-- 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.