That is kind of what I was hoping for, but I don't think that would work, at least if I'm only trying to change the newer systems.
Perhaps I'm just too frighten to make a "simple" change that will affect 1,000 or so users, without testing. That is why I would perfer to make a change only on the newer systems. But if I make a change on all other systems to select a non-EDS logmode and then change the VM/VTAM books to be EDS devices, I should get what I want. I'm trying to keep from modifying the old systems. Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 10/10/2006 11:17 AM >>> Hello Tom, Very interesting problem. Are you planning on adjusting the base model you are using for your autoinstalled terminals? Each CICS has a grplist that would have the terminal definitions required for that CICS. Ed Martin Aultman Health Foundation 330-588-4723 [EMAIL PROTECTED] ext. 40441 > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of Tom Duerbusch > Sent: Tuesday, October 10, 2006 12:10 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: VTAM Cross Domain problem/question > > What I want to be able to do is, on a CICS by CICS basis, setup whether > that system can handle EDS. My understanding of the negoiation of the > bind, is when there are conflicts, they step down to the lowest common > attributes. I would rather not make changes to our current production > systems, but rather to the systems that need EDS. But I think those two > conditions are in direct conflict with each other. > > What are some good ways of making this type of change? > > Thanks > > Tom Duerbusch > THD Consulting