Re: TSAF - Supported Links

2008-07-21 Thread Kris Buelens
TSAF's connections are rather old, it was well positioned at the 9370
and 9221 age with their integrated adapters, but nowadays 
If you can get a CTC connection between the systems, use an IFSC link,
that's even simpler than TSAF:
  CP ACTIVATE ISLINK rdev
on both sides, and you're done.

BEWARE: SFS resource names (and alike) must be unique.  Assure it is
before you issue the ACTIVATE command, otherwise you're in trouble.
Use Q RESOURCE to find all resource names; alls those that are not
LOCAL must be unique.

2008/7/21 Fox Blue [EMAIL PROTECTED]:
 Dear all,

 I have two z/VM running on different CPCs. They are joined in a CSE complex.
 The DASD is shared but spool not since I do not have VM/Pass Through
 facility. I want to connect now both systems via TSAF as I need to
 interconnect IUCV and SFS services.

 After reading the Connectivity Guide (GC24-6118-02) I found out that TSAF
 would be the right component for doing this. As far as I can understand the
 setting up of TSAF is quite straight forward.

 Nevertheless I would need some explanation about the IEEE 802.3 LAN
 subsystem on rack-mounted processors. This is in my opinion a quite vague
 description of a feature. What does it mean? Does that mean that the OSA
 Express2 adapters on my z990s are not supported for TSAF? Aside from CTCs
 and since I do not have VTAM, Token Ring and BSC stuff, the Ethernet link
 would be the easiest solution.

 I would need some confirmation on this. Thank you very much in advance.

 Best regards,
 Fox




-- 
Kris Buelens,
IBM Belgium, VM customer support


Re: TSAF - Supported Links

2008-07-21 Thread Florian Bilek
Hello Kris, 

Thanks for that information. I will have a look on ISFC. First, I have to

get me some CTCs ;-) 

Best regards, 
Fox


Re: TSAF - Supported Links

2008-07-21 Thread Rob van der Heij
On Mon, Jul 21, 2008 at 10:45 AM, Florian Bilek [EMAIL PROTECTED] wrote:

 Thanks for that information. I will have a look on ISFC. First, I have to
 get me some CTCs ;-)

For modern configurations, that takes just a foot of fiber to connect
two spare chpids. Find an old gray haired person to talk about 3088
where the I/O configuration drawings even X for selected connection
and o for broken ...

A null modem for those with such heritage. And the neat thing is
that our foot of fiber actually is 256 null modem cables. We don't do
cross wires, so you configure one chpid as male and the other as
female (the political correct term is CTC and CNC).

PS A friend of mine used to say that RS232 stands for Recommended
Soldering: 2 to 3, 3 to 2

Rob


Re: TSAF - Supported Links

2008-07-21 Thread Alan Altmark
On Monday, 07/21/2008 at 02:57 EDT, Fox Blue [EMAIL PROTECTED] 
wrote:
 After reading the Connectivity Guide (GC24-6118-02) I found out that 
TSAF
 would be the right component for doing this. As far as I can understand
 the setting up of TSAF is quite straight forward.
 
 Nevertheless I would need some explanation about the IEEE 802.3 LAN
 subsystem on ?rack-mounted processors?. This is in my opinion a quite
 vague description of a feature. What does it mean? Does that mean that 
the OSA
 Express2 adapters on my z990s are not supported for TSAF?

Oh, dear.  I guess we need to clean that up.  Our first error is letting 
you conclude that TSAF would be the right component without having 
alerted you to ISFC.  We compounded it by describing hardware that no 
longer exists.  To answer your question, the IBM ES/9221 and its 
predecessor, the IBM 9370, were rack-mounted machines with integrated 
network and terminal adapters, as well as having internal dasd.

TSAF is still a wonderful alternative for connecting second level systems 
together or to a first level system since it can use virtual CTCs (ISFC 
cannot).  However, TSAF cannot drive an OSA.

If you would, please submit a Reader's Comment Form describing your 
confusion.  (That is, send a note about it to mhvrcfs at us.ibm.com.)

Alan Altmark
z/VM Development
IBM Endicott