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....) >
