LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (May 1999)Back to main CICS-L pageJoin or leave CICS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Thu, 6 May 1999 08:16:48 -0600
Reply-To:   CICS List <CICS-L@UGA.CC.UGA.EDU>
Sender:   CICS List <CICS-L@UGA.CC.UGA.EDU>
From:   "Grinsell, Don" <Dgrinsell@STATE.MT.US>
Subject:   Re: TCT
Content-Type:   text/plain; charset="iso-8859-1"

Doug,

Are you currently using Autoinstall in your 2.1.2 TOR? I have a very simple autoinstall program that uses a KSDS to associate VTAM id's with fixed terminal id's. The majority of our users do not need a specific CICS terminal id, but there were a few applications that did. We implemented our program to look for the VTAM ID in our file, if it's found we assign the fixed termid, if it's not, we generate an id. I can send you the source if you'd like. As to the second part of your question, you do not need to define the TCT entries in the AOR. Use the Shippable attribute in the TOR and all is handled. You may need an XICTENF exit if you do START based on termid in the AOR...this exit will route the request back to the TOR in the case of a terminal not found condition. I can supply a simple version of that code as well.

Regards,

Donald Grinsell CICS Systems Programmer State of Montana 406-444-2983

-----Original Message----- From: Pereira, Doug [mailto:DUPereira@AVONDALE.COM] Sent: Thursday, May 06, 1999 6:02 AM To: CICS-L@UGA.CC.UGA.EDU Subject: TCT

Hello Everyone,

Let me see it I can explain our problem properly. We're at CICS 2.1 heading toward 4.1 and have questions on exactly how to handle the TCT. A number of our current applications rely on checking a fixed terminal id assigned to a particular user and until we can actually change the program this must remain.

We use VTAM/SWITCH for initial mainframe access and when necessary assigned a logical terminal address to a user. This logical address is associated with a CICS terminal id in the current 2.1 TCT.

With the new setup we would like to have a 4.1 TOR addressing either a 2.1 AOR or a 4.1 AOR depending on where the transaction resides. A user will get into the 4.1 TOR, initiate a transaction that will either run in the 2.1 or 4.1 AOR. Eventually all transactions will be in the 4.1 but believe it or not we still have a number of macro programs hanging around. (Is it true that CICS 2.1 will not work after this year? Our systems manager seems to think it will run forever.)

Our problem is the TCT. Where should it reside? If it must be in the 4.1 TOR will the terminal id be passed to the AOR's? Can anyone give any hints as to the proper TCT setup for these regions.

Thanks in advance for your help.

Doug Pereira Avondale Industries


Back to: Top of message | Previous page | Main CICS-L page