OK, that makes sense to what I'm seeing now.

I never got into using OBEYFILE.
Back in the early '90s when VM first got IP, everytime I used OBEYFILE, I wiped 
out things that I didn't intend to.

Never went back to it again.

I never caught on to which groups of statements were considered "packets" of 
statements.  That is if you replaced one statement, the entire "packet" of 
statements were replaced.

Anyway, I'll get back to this after I schedule the cycle of TCPIP.

Thanks

Tom Duerbusch
THD Consulting

>>> Kris Buelens <kris.buel...@gmail.com> 7/18/2011 3:33 PM >>>
Alan explained here a while ago that you can use OBEYFILE to make TCPIP
restart servers after that they have been taken from the restart list due to
too frequent restarts.

2011/7/18 Tom Duerbusch <duerbus...@stlouiscity.com>

> When I reread Step 2....
> Yep, it does say a "list of tags....", it's not meant to be a sample entry.
>
> Now, I'm getting somewhere...
>
> I copied the entries from the IBM DTCPARMS.
>
> Now, things are being tried, at least.
>
>        15:14:43 AUTO LOGON  ***       REXECD   USERS = 62    BY TCPMAINT
> TCPIP   15:14:43 DTCMON442I CP FORCE RXAGENT1 ISSUED BY REXECD; RESULTS
> PENDING
>        15:14:43 USER DSC   LOGOFF AS  RXAGENT1 USERS = 61    FORCED BY
> TCPIP
> TCPIP   USER DSC   LOGOFF AS  RXAGENT1 USERS = 61    FORCED BY TCPIP
> TCPIP   15:14:43 DTCMON443I CP FORCE RXAGENT1 ISSUED BY REXECD; COMMAND
> SUCCESSFUL
> TCPIP   15:14:43 DTCMON442I CP FORCE RXAGENT1 ISSUED BY REXECD; RESULTS
> PENDING
> TCPIP   15:14:43 DTCMON443I CP FORCE RXAGENT1 ISSUED BY REXECD; COMMAND
> SUCCESSFUL
> TCPIP   15:14:43 DTCMON442I CP FORCE RXAGENT2 ISSUED BY REXECD; RESULTS
> PENDING
> TCPIP   15:14:43 DTCMON443I CP FORCE RXAGENT2 ISSUED BY REXECD; COMMAND
> SUCCESSFUL
>
>        15:15:14 AUTO LOGON  ***       RXAGENT1 USERS = 62    BY REXECD
>        15:15:14 USER DSC   LOGOFF AS  REXECD   USERS = 61
>
> What is now strange, is that I have to (x)autolog REXECD after I force it.
>  REXECD was being detected that it was down and autologed by TCPIP.  Now I
> have to do it.
> Also, after it autologs RXAGENT1, REXECD automatically logs off.
>
> I'll have TCPIP scheduled to be cycled and try this stuff again on
> Wednesday.
>
> My parms now look like:
>
> :nick.REXECD    :type.server  :class.rexec
> :nick.RXAGENT1  :type.server  :class.rexec_agent   :for.REXECD
>
> .*======================================================================
> .* Anonymous Remote Execution (REXEC) and Remote Shell (RSH) agents
> .*----------------------------------------------------------------------
> :nick.rexec_agent
>              :type.class
>              :name.Anonymous Remote Execution agent
>              :command.RXSNDIU
>              :runtime.C
>
>
> :Nick.REXECD:Type.Server:Class.rexec
>  :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
>
> Tom Duerbusch
> THD Consulting
>
>
> >>> Scott Rohling <scott.rohl...@gmail.com> 7/15/2011 7:29 PM >>>
> Well - I dug a bit deeper - looked at TCPRUN EXEC, etc..    :type. and
> .class do seem to be required to modify server entries.   In fact - the
> section in TCPIP Planning and Admin section on 'Customizing Servers' shows
> several examples all specify :type and :class.
>
> I think where we both were confused is in Step 2 of 'Configuring the REXEC
> Server'..  it shows what looks like a :nickname entry, but is actually a
> list of tags that are recognized for REXEC.  To modify those tags, you
> still
> need to create an entry using :nick, :type, and :class.
>
> So - not a bug..  maybe a candidate for a reader comment?  It's spelled out
> in the 'DTCPARMS File Format' section that:
>
> Every entry must include either a :Type.Server or a :Type.Class definition.
>
> Entries that define a server using a :Type.Server definition must also
> include a :Class. tag and value to identify the class to which that server
> belongs.
>
> It certainly slipped by me though in looking at your DTCPARMS entry!
>
> Scott Rohling
> On Fri, Jul 15, 2011 at 5:01 PM, Scott Rohling <scott.rohl...@gmail.com 
> >wrote:
>
> > Hmmph..  we didn't have REXECD enabled on my test system -- so I did so
> ..
> > and added the :nick.REXECD tag with Anonymous.YES to SYSTEM DTCPARMS.
> >
> > What I see on a debug is much like yours - but also with this:
> >
> > +++ Lookup_Details.OUT
> >   $ParmFile_Serve = IBM DTCPARMS E1
> >   $ParmFile_Class = IBM DTCPARMS E1
> > +++ Lookup_Details.OUT
> >   $ParmFile_Serve = IBM DTCPARMS E1
> >   $ParmFile_Class = IBM DTCPARMS E1
> >
> > Like you - my SYSTEM DTCPARMS is on D..  so it doesn't appear it's using
> > it.
> >
> >
> > The NAME SEARCH debug info got me thinking..   So I did this in my SYSTEM
> > DTCPARMS:
> >
> > :Nick.REXECD :Type.Server :Class.rexec
> >  :Parms.-d
> >  :Anonymous.YES
> >  :ESM_Enable.
> >  :ESM_Validate.
> >
> > Note that I added :Type.Server and :class.rexec
> >
> > Once I did this -- voila --  it found my entry in SYSTEM DTCPARMS,
> started
> > up RXAGENT1 and was happy.  Even the -d parm was honored and I get more
> > debug info from rexec itself.
> >
> > So - this looks like  bug - either doc or code...    but try changing
> your
> > :Nick.REXECD to include type and class.
> >
> > The NAMES file search seems to be looking for both the nickname AND the
> > Type tag.   To specify :type - you also have to specify :class.    I'm
> > guessing it should be searching on just :Nick.. and this is a workaround.
> >
> > Hope this helps.. please open a PMR!
> >
> > Scott Rohling
> >
> >
> >
> > On Fri, Jul 15, 2011 at 4:08 PM, Tom Duerbusch <
> duerbus...@stlouiscity.com 
> > > wrote:
> >
> >> I only have two of them, SYSTEM and IBM.  I'm updating SYSTEM.
> >> It is on the D drive for user REXECD which is above the E drive where
> the
> >> IBM is.
> >>
> >> But that got me looking at the IBM on.
> >> That set of parms are different then what is on the SYSTEM on.
> >>
> >> The subset of the IBM one is:
> >>
> >> :nick.REXECD    :type.server  :class.rexec
> >> :nick.RXAGENT1  :type.server  :class.rexec_agent   :for.REXECD
> >>
> >>
> >> .*======================================================================
> >> .* Remote Execution (REXEC) and Remote Shell (RSH) daemon
> >> .*----------------------------------------------------------------------
> >> :nick.rexec   :type.class
> >>              :name.Remote Execution daemon
> >>              :command.REXECD
> >>              :runtime.C
> >>
> >>              :anonymous.NO
> >>
> >>              :ESM_Enable.NO
> >>              :ESM_Validate.RPIVAL
> >>              :ESM_Racroute.RPIUCMS
> >>
> >> .*======================================================================
> >> .* Anonymous Remote Execution (REXEC) and Remote Shell (RSH) agents
> >> .*----------------------------------------------------------------------
> >> :nick.rexec_agent
> >>              :type.class
> >>              :name.Anonymous Remote Execution agent
> >>              :command.RXSNDIU
> >>              :runtime.C
> >>
> >> My SYSTEM one only has:
> >>
> >> :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
> >>
> >>
> >> Looking at the output from debug, it sure looks like I'm picking up the
> >> IBM DTCPARMS.
> >> But based on other items in my SYSTEM DTCPARMS file, I know that it is,
> >> being executed.
> >>
> >> Tom Duerbusch
> >> THD Consulting
> >>
> >> >>> Scott Rohling <scott.rohl...@gmail.com> 7/15/2011 4:52 PM >>>
> >> Which DTCPARMS are you updating?    Is a 'lower level' one perhaps
> >> overriding?    The order is userid, nodeid, SYSTEM, and lastly IBM
> >> DTCPARMS
> >> which should not be touched.
> >>
> >> Scott Rohling
> >>
> >> On Fri, Jul 15, 2011 at 3:11 PM, Tom Duerbusch
> >> <duerbus...@stlouiscity.com>wrote:
> >>
> >> > OK, got it.
> >> >
> >> > For REXECD:
> >> >
> >> > 'Access 198 D'
> >> > 'Access 591 E'
> >> > 'Access 592 F'
> >> > QUEUE "EXEC TCPRUN (DEBUG"
> >> >
> >> >
> >> > TCPRUN DEBUG:
> >> >
> >> > TCPRUN Level = 520
> >> > TIME IS 15:55:07 CDT FRIDAY 07/15/11
> >> > CONNECT= 00:14:44 VIRTCPU= 000:00.27 TOTCPU= 000:00.35
> >> > z/VM Version 5 Release 2.0, service level 0602 (64-bit)
> >> > Generated at 09/18/06 18:39:52 CDT
> >> > IPL at 08/08/10 16:51:42 CDT
> >> > USERID=REXECD   MACH=XA  STOR=32M VIRT=V XSTORE=NONE
> >> > IPLSYS=CMS      DEVNUM=00016
> >> > CMS Level 22, Service Level 602
> >> > --------------------------------------------------
> >> > +++ GetInternetData
> >> >  $TCPhost        = STLMP11
> >> >  $TCPstack       = TCPIP
> >> > DTCRUN1022I Console log will be sent to default owner ID: TCPMAINT
> >> > +++ Lookup_Details.IN
> >> >  How             = BYUSER
> >> >  Search_Value    =
> >> > +++ Namesearch:
> >> >  Target          = :NICK REXECD :TYPE SERVER
> >> >  NFopts          =
> >> >  $SearchResults. = @NICK REXECD
> >> >                    @TYPE SERVER
> >> >                    @CLASS REXEC
> >> > +++ Lookup_Details.IN
> >> >  How             = BYCLASS
> >> >  Search_Value    = REXEC
> >> > +++ Namesearch:
> >> >  Target          = :NICK REXEC :TYPE CLASS
> >> >  NFopts          =
> >> >  $SearchResults. = @NICK REXEC
> >> >                    @TYPE CLASS
> >> >                    @NAME Remote Execution daemon
> >> >                    @COMMAND REXECD
> >> >                    @RUNTIME C
> >> >                    @ANONYMOUS NO
> >> >                    @ESM_ENABLE NO
> >> >                    @ESM_VALIDATE RPIVAL
> >> >                    @ESM_RACROUTE RPIUCMS
> >> > +++ Lookup_Details.OUT
> >> > +++ Lookup_Details.OUT
> >> > +++ Query_Write
> >> >  @Diskwarn       = NO
> >> >  pctneed         = NO
> >> >  fm              =
> >> > DTCRUN1021R To cancel Remote Execution daemon startup, type any
> non-blan
> >> >            character and press ENTER. To continue startup, just press
> E
> >> > DTCRUN1011I Server started at 15:55:08 on 15 Jul 2011 (Friday)
> >> > DTCRUN1011I Running "REXECD"
> >> >
> >> >
> >> > OK, now I see the problem  "@ANONYMOUS NO ", so back to the DTCPARMS:
> >> >
> >> > :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
> >> >
> >> > What is wrong with my :Anonymous.yes?
> >> >
> >> > Tom Duerbusch
> >> > THD Consulting
> >> >
> >> > >>> Alan Altmark <alan_altm...@us.ibm.com> 7/15/2011 3:45 PM >>>
> >> > On Friday, 07/15/2011 at 04:42 EDT, Tom Duerbusch
> >> > <duerbus...@stlouiscity.com> wrote:
> >> > > This is what I get with debug on:
> >> > >
> >> > > rexec -d -l guest -p guest 205.235.227.74 cp ind
> >> > > REXEC Level 520, Internal version id MT04091
> >> > > parms is -d -l guest -p guest 205.235.227.74 ind
> >> >
> >> > Not seeing TCPRUN output created by (DEBUG option on TCPRUN.  Looking
> >> for
> >> > REXECD initialization.
> >> >
> >> > Alan Altmark
> >> >
> >> > Senior Managing z/VM and Linux Consultant
> >> > IBM System Lab Services and Training
> >> > ibm.com/systems/services/labservices
> >> > office: 607.429.3323
> >> > mobile; 607.321.7556
> >> > alan_altm...@us.ibm.com 
> >> > IBM Endicott
> >> >
> >>
> >
> >
>



-- 
Kris Buelens,
IBM Belgium, VM customer support

Reply via email to