On 1/12/07, Peter Rothman [EMAIL PROTECTED] wrote:
Besides a lot of 'steam lining' I thought I would be 'clever' and changed
the GLOBALVs to 'PIPE var VarName 1 | var VarName'.
The EXECCOMM interface is known to be slow. With GLOBALV you only use
it once to set the variable, with the Pipeline
I will be out of the office starting 01/13/2007 and will not return until
01/20/2007.
I am out of the office until 1/22/2007. I am not checking e-mail or voice
messages during that time.
The GLOBALV solution often also requires two calls to EXECCOMM:
GLOBALV PUT in the calling exec and GLOBALV GET in the callee
If the variables contain one word only, one can indeed save a call to
EXECCOM:
'GLOBALV SET V1' content 'V2' content
But, in such cases one can also pass the
Rob van der Heij wrote:
Come on Sir. You're just repeating hearsay nonsense arguments. Yours
is almost as good as the one to replace the VM Toolsrun-based employee
directory by LDAP because the VM solution required updates to be
applied to all copies of the data spread over multiple VM system
I'm in the mist of converting from z/VM 5.1 to z/VM 5.2 and having an IP
problem.
The VM stack is connected to a vswitch. And as far as the VM side is
concerned, all is well, (FTP, PING, TN3270, etc).
My, more modern VSE guests (2.5 and above) are connected to the vswitch
and all seems to be
There was a problem outside of IBM's networks which cut off www.vm.ibm.co
m
from the outside world. It was resolved Friday night. B.
