of course, this is exactly the way I use to connect to zVSE, but on VM
vtam you need non-SNA definitions for each session which uses a separate
device number each. To this device I dial from the SCEXIT. And VM VTAM
only accepts 3-digit device numbers. So if you reach 4096 sessions (a
bit less because the vm-vtam user needs some devices for himself e. g.
mdisks) you cannot define more sessions to vm-vtam. It has nothing to do
with the zVSE. This is cross-domain business with virtual ctcs as you
mentioned.
kind regards
Franz Josef Pohlen
Am 19.10.2010 15:01, schrieb Frank M. Ramaekers:
Exactly.
Frank M. Ramaekers Jr.
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of Lim Ming Liang
Sent: Tuesday, October 19, 2010 7:51 AM
To: [email protected]
Subject: Re: how to change the name of VTAM-NSS
A virtual CTCA between the VM/VTAM and zVSE/VTAM ?
Regards Lim ML
On 19/10/10 8:12 PM, Frank M. Ramaekers wrote:
Can't you connect to your z/VSE CICS's via VTAM CDRM CDRSC instead of
using a CUU for each session?
Frank M. Ramaekers Jr.
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]]
On
Behalf Of Franz Josef Pohlen
Sent: Monday, October 18, 2010 11:43 PM
To: [email protected]
Subject: how to change the name of VTAM-NSS
Hi listers,
my customer uses VM-TN3270E, SCEXIT and Dial to VM-VTAM to connect to
his CICS-TS in zVSE. Now he is going to reach the 4096 devices limit
in
his vm-vtam, because the Non-SNA resources support only 3-digit device
numbers. We want to create a 2nd GCS and VTAM with its own segments to
avoid any storage complaints. I know how to build a new GCS, but how
can
I build a new VTAM NSS VTAM2 instead of VTAM.
_____________________________________________________
This message contains information which is privileged and confidential and is
solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any
review, disclosure,
copying, distribution, or use of the contents of this message is strictly
prohibited. If you have
received this in error, please destroy it immediately and notify us at
[email protected].
