It would seem that for a "hot plug" CTC device. You would set it up to
test for the presence of the other one of the pair. If they are not both
present then dont do anything. Thus in your example when 0A00 became
available nothing would hapen as 0A01 was not available. Then when 0A01
became available you could then activate 0A00.
Ivan Warren wrote:
Have we seen this in practice?
Because of the way the CTC driver is structured, one address is input
and one is output if you're speaking IP over it. It's not like using
CTC for RSCS where each address is bidirectional. So if only one of
the pair is there, I'd say that it's broken and you shouldn't try to
use it as a network device. Now if it comes up later, it would be
nice to autodetect that and tell that you now had a CTC pair and try
to start the interface...but that might be a lot more trouble than
it's worth. If your CTCs are flapping, something's clearly pretty
wrong already.
Adam
Not 100% sure Adam.. Bastian may have a point here..
Assuming the CTC pair (comprising the link to a TCP/IP virtual machine
or as a hercules means to talk outside) could be defined dynamically at
run time, I see where a problem may exist.
1st, when running under VM, CTCs have to be defined one after the other
(CP DEFINE CTC 0A00#CP DEFINE CTC 0A01 - followed by the appropriate
'couple' commands)
2nd under hercules, you either attach both CTCs as a group such as
"attach 0A00.2 CTCI ..." or independently (attach 0A00 CTCI .. attach
0A01 CTCI ...)
In any case, the CRWs are going to be made pending and presented one
after the other.. Any hotplugging technology will then receive a report
for the 1st instance followed by a report for the 2nd instance.
So it's clearly a possibility for a time window to exist for only the
first of the 2 exposures to either 'exist' or be known to the operating
system aven though the second exposure will eventually get there.
I doubt using some time lapse will do either.. This definitely doesn't
cover the fact of manually defining each CTC independently and manually.
This is only an issue for devices that start to exist *AFTER* IPL
(hotplugged devices).
(just my $.02..)
--Ivan
--
Stephen Frazier
Information Technology Unit
Oklahoma Department of Corrections
3400 Martin Luther King
Oklahoma City, Ok, 73111-4298
Tel.: (405) 425-2549
Fax: (405) 425-2554
Pager: (405) 690-1828
email: stevef%doc.state.ok.us
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
