re: using particular user .. yes - it would be much more efficient to do the list of commands in a REXX script on the host rather than issuing 'rexec' for each, if that's all the client is doing. Ideally - a single command (pass parms to effect behavior) is all you want to issue with the rexec client to accomplish a particular task.
re: agents .. as Alan says - we want to see the debug on the REXECD server -- to try and see why agents aren't getting started. Hoping to find a clue as to why they aren't. Scott Rohling On Fri, Jul 15, 2011 at 2:42 PM, Tom Duerbusch <duerbus...@stlouiscity.com>wrote: > I duplicated the RXAGENT1 to make the RXAGENT2 in the directory and added > the info in the DTCPARMS. > > They do have the LINK REXECD 191 191 RR in the directory. > > When I force REXECD, TCPIP automatically brings it back up. No attempt is > made to bring up the agents. > > The only problem I have with using REXECD with a particular user, which is > solved by using the agents, is that I have a list of commands that I'm > sending off to be executed and some of them fail with "Unable to autolog > user" message. In other words, the machine didn't finish logging off before > the next remote command was being issued. I might bypass this problem by > executing a rexx program instead of individual commands. > > Tom Duerbusch > THD Consulting > > >>> Scott Rohling <scott.rohl...@gmail.com> 7/15/2011 3:01 PM >>> > Only RXAGENT1 is supplied .. which makes me then wonder if these agents > are built as they should be -- doing a LINK REXECD 191 191 RR for their A > disk, etc? Did you model RXAGENT2 on 1? What you show seems correct.. > so > searching for clues :) Does the REXECD console show it is attempting to > start -- any error msgs? Is RACF installed - if so, is REXECD authorized > to autolog? > > These agent ids are only for anonymous requests.. any trouble using REXECD > for a particular user? > > Just a note that don't set SECUSER on these guests to watch -- you'll mess > up the message interactivity between them. > > Any errors at all you are seeing would be good clues.. > > Scott Rohling > > On Fri, Jul 15, 2011 at 1:43 PM, Tom Duerbusch > <duerbus...@stlouiscity.com>wrote: > > > I'm having a brain check. > > > > I've enabled REXEC which is working well. > > And I thing I enabled the server machines RXAGENT1 and RXAGENT2. > > > > How I read the documentation, both these agent machines should fire up > when > > the REXECD server is started. > > My agent machines don't automatically start. > > And when I try to send a command to the guest server, I get back a > message > > about an agent server not being available. > > > > My DTCPARMs seem to be correct: > > > > :nick.REXECD > > :Parms. > > :Anonymous.yes > > :ESM_Enable. > > :ESM_Validate. > > > > :Nick.RXAGENT1 :type.server :class.rexec_agent > > :For.REXECD > > > > :Nick.RXAGENT2 :type.server :class.rexec_agent > > :For.REXECD > > > > I don't see anything in the TCPIP configuration file about the RXAGENTx > > machines. > > > > Just what am I missing? > > > > Tom Duerbusch > > THD Consulting > > (Sorry officer. I just thought you wanted to race....) > > >
