We are trying to make Automation point from CA work with a TN3270 session with
a VM guest, The last step is to assign an LU name to the session. Don't see a
way to do that in the VM world. Easy enough with MVS.
Any ideas?
Thanks
Bobby Bauer
Center for Information Technology
National Institutes
LU names are a SNA thing. They don't apply with TCPIP sessions.
What are they trying to do - identify the session somehow?
We are trying to make Automation point from CA work with a TN3270 session with
a VM guest, The last step is to assign an LU name to the session. Don't see a
way to do
On Wednesday, 12/15/2010 at 02:37 EST, Bauer, Bobby (NIH/CIT) [E]
baue...@mail.nih.gov wrote:
We are trying to make Automation point from CA work with a TN3270
session with
a VM guest, The last step is to assign an LU name to the session. Don?t
see a
way to do that in the VM world. Easy
If you are connecting through an OSA-ICC (or IDG9074) type connection you can
assign an LU name in the OSA-ICC (or IDG9074) definition and then put that in
the TN3270 software session setup on the PC.
Paul Feller
AIT Mainframe Technical Support
From: The IBM z/VM Operating System [mailto:ib
]
Sent: Wednesday, December 15, 2010 2:54 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: LU name?
LU names are a SNA thing. They don't apply with TCPIP sessions.
What are they trying to do - identify the session somehow?
We are trying to make Automation point from CA work with a TN3270 session
is to assign an LU name to the
session. Don't see a way to do that in the VM world. Easy enough with
MVS.
Any ideas?
Thanks Bobby Bauer Center for Information Technology National
Institutes of Health Bethesda, MD 20892-5628 301-594-7474
--
Dave Jones
V/Soft Software
www.vsoft-software.com
Ah. Digging a bit: the product allows the CA automation tool to drive a session
and pick up console output.
As somebody else noted, the only place in this scenario you would supply a
LUname is if the CA product were talking to a ICC non-SNA console assigned to
the guest - the LUname is used in
