The problem with SET SECUSER is that it changes to who messages are
delivered:
If you issue SET SECUSER REXECD MAINT messages sent to REXECD are directly
delivered to MAINT.
REXECD runs a program that intercept messages, but when they are delivered
to MAINT
When using SET OBSERVER such message
After a restart of TCPIP, yep, I got that. I have too frequent of restarts.
06:00:37 DTCIPI030W STARTANEWLIFE: VICTIM REXECD, REASON RESTARTING YO
BEEN RESTARTED
06:00:37 AUTO LOGON *** REXECD USERS = 60BY TCPIP
On Wednesday, 07/20/2011 at 10:18 EDT, Tom Duerbusch
duerbus...@stlouiscity.com wrote:
My manuals (z/VM 5.2) do not show a method of recycling REXECD using the
OBEYFILE command. It does show it for about a dozen other servers, but
not for
REXECD.
Searching the archives, I found very
Thanks Alan
I was somewhat confused with the Planning and Customization manual, with the
section:
Starting and Stopping TCP/IP Servers
It lists many of the servers and how to stop them, usually with SMSG.
It didn't list REXECD which was part of my questioning Kris' post.
Apparently, I was in
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 = 62BY TCPMAINT
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
On Friday, 07/15/2011 at 03:43 EDT, 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
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
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
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
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
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
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.comwrote:
OK, got it.
For REXECD:
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
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
: REXEC and RXAGENT1
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
16 matches
Mail list logo
