The channel does not actually exist in Hercules.? It started out
as an ESA/390 emulator so initially the channel subsystem was
implemented for subchannel I/O.? Later, support for S/370 was
added and the channel I/O commands were added as a wrapper to the
already existing channel subsystem.? The channel subsystem does
not report the channel busy.
There was an effort to emulate channels, but that did not make it
into Hercules.
So from Hercules stand point, it does not matter.
From the perspective of the guest operating system running in
Hercules, VM, it might care.
Harold Grovesteen
On 9/12/24 15:10, Mark A. Stevens via
groups.io wrote:
toggle quoted message
Show quoted text
On Thu, Aug 15, 2024 at 07:50 AM, Bob Polmanter wrote:
For example, you have port 30880 on the CTCE at 500
and at 600.? They need to be different ports, on both sides of
the CTCE definition.? So, I'd suggest using 30880 for address
500 and something like 30890 for address 600.? This isnt
XNET's rules; rather, this is required by CTCE to function
properly.
Bob,
?
A follow up question concerning use of channels/CTCE for XNET
vs. other applications, say RSCS.
?
I remember your documentation saying, I should only use XNET
on a channel once, so 500, but not 501, ... Is it "safe" to use
501 for RSCS, or other products, or does XNET keep the whole
channel too busy, when it is in use?
?
Thanks!
?
?... Mark S.
