I am out of the office until 15/10/2010.
I am currently out of the office, with no immediate access to my mail.
I shall endeavour to respond to mail on a daily basis.
If it is urgent then please contact Helena Hetherington and/or Colm
Feighoney for all ITS ITS&A / DiP matters.
For matters relati
tyvm, David Boyes, et al:
Some progress:
I noticed Level 1 TCPIP did not have a NICDEF/SPECIAL for VSWITCH which
explains why Level 2 TCPIP cannot connect to Level 1 TCPIP via VSWITCH..
It had a SPECIAL for OSALAN, but OSALAN was not DEFINED in Level 1.
So I defined OSALAN in Level 1, coupled
It's just clever code on the server, depending on authorizations and privileges.
Even my ancient VMSERVE from the Download Library can be readily programmed to
do it. File output is easy, MSG output not so easy because of the indeterminate
end of the messages from service machines you don't cont
Here it is... When the server gets something from TOM like cmd MSG OP CMD Q
T it will change it to FOR TOM CMD MSG OP Q T. I think that just might
work
On Wed, Oct 13, 2010 at 11:51 AM, Mike Walter wrote:
> Ah... well that's a slightly different situation. I do not recall any way
> USERA t
Ah... well that's a slightly different situation. I do not recall any way
USERA to issue a message to a server, which then relays it to another
server
and spontaneously re-routes the output back to USERA.
If nothing else were happening during that timeframe, USERA could SET
OBSERVER ON for th
What does your level 1 vswitch show? It needs to show both your level 1
TCPIP stack (10.13.13.18) and any addresses registered from your 2nd leve
l
system, such as your level 2 TCPIP stack (10.13.13.26). For now, leave
the linux guests out of the testing because they are in a different subne
Let¹s back up a bit.
What you are essentially doing is creating a setup like this:
Company network --> vswitch -> level 1 network stack
+-> level 2 network stack
The TCP stacks (both level 1 and level 2) need:
1) unique IP addressess
2) the same network mask
3) the sa
Maybe I should have been more clear. BOB is not a pearson, but another
service machine (maybe PROP, or RSCS) that will respond to the sender as he
sees it.
I.E. MSG OP CMD Q V DASD and PROP will return the output of Q V DASD to me.
If I send via my server machine the response is returned to the ser
Or... if security allows, add a new privclass for MSGNOH as privclass 'M'
(e.g. in SYSTEM CONFIG, include: MODIFY CMD MSGNOH PRIVclass ACBM )
and then authorize the servers that need it to enter: CP MSGNOH bob MSG
FROM you: message test here
Someone needs to decide which is worse, authorizing s
I have NICDEFed to my level 1 switch from my level 2 machine (ZVM54SVM)
and can display my level 2 switch now with "q lan" from Level 2:
Adapter Owner: VLINUX3 NIC: D000.P00 Name: LNXVSW1
RX Packets: 341673 Discarded: 0 Errors: 0
TX Packets: 24165 Discarded: 0
CP SEND CP serverid MSG BOB HI
where your userid is the SECUSER for serverid
Mark Wheeler
UnitedHealth Group
Date: Wed, 13 Oct 2010 09:57:13 -0700
From: tehue...@gmail.com
Subject: Forwarding program or mod?
To: IBMVM@LISTSERV.UARK.EDU
Hi,
I seem to remember a program or mod that a
Hi,
I seem to remember a program or mod that allowed the 'FROM' part of a
command to be changed...
Example .. I do MSG serverid CP MSG BOB HI .. Then the serverid would invoke
the 'mod' and CP MSG BOB HI.
But to BOB it would look like the message came from me NOT from the server
machine.
Or is i
On Wed, 13 Oct 2010 11:04:29 -0400, George Henke/NYLIC
wrote:
>ty, Brian.
>
>OSA2LAN is defined in the 1st Level Dircectory profile of my 2d Level
>machine.
The SPECIALs do not define OSA2LAN, they create the virtual device
addresses and attempt to automatically COUPLE to an existing OSA2LAN a
If you are logged onto the 2nd level guest user itself -- and have a console
and also logged into the 2nd level system (say as MAINT) - then you can use
the PA1 key - which will take you to the 1st level system CP. You can
issue the COUPLE - and then you will see ...MORE in the status area. Aft
ty, Brian.
OSA2LAN is defined in the 1st Level Dircectory profile of my 2d Level
machine.
There is an OSALAN on the 1st Level machine and a VSWITCH as well.
As you noted in a previous email, I could just NICDEF from 2nd Level to
the 1st Level VSWITCH, but I was not clear how I would distinguis
I think the you are probably issuing the COUPLE command from the wrong
place. You need to issue it from your 2nd level guest userid as a comman
d
to your 1st level system to COUPLE to an OSA2LAN defined in your 1st leve
l
system. The best time to do this is after you logon to your 2nd level
I have defined the OSA2LAN as Dave Jones suggested, though probably not
how:
I defined a SPECIAL in the profile of the Level 2 machine and also in the
profile of TCPIP Level 2:
SPECIAL 9012 QDIO 3 SYSTEM OSA2LAN
But I still get a failure at TCPIP startup:
09:45:12 DTCQDI001I QDIO device OSA90
17 matches
Mail list logo
