On Tuesday, 05/06/2008 at 08:01 EDT, David Boyes <[EMAIL PROTECTED]> wrote: > > Routing DFSMS to some other filepool that VMSYS is very very easy: > > If you know how, or why it should be this way. I do, you do -- most > people haven't got any idea to even think of trying this. Lying to APPC > to work around a hardcoded file reference like this is just ugly.
It's not a lie, David. In fact, on other platforms you MUST provide a side file to provide the metadata APPC needs. Because VM implements a cluster of virtual machines as well as a cluster of VM instances (APPC Collection), we can take liberties with default metadata. :nick.<tpn> :luname.*IDENT 0 (moral equivalent) :security.same :tpn.<tpn> It has always been the architecture of APPC/LU 6.2 that applications make symbolic references to resource managers. The local system (LU) performs a local lookup. This is just as "arca Again, a communications protocol that has been in place for decades. So, the point is that you can EASILY redirect SFS connections. Yes, you have to know how to do it or the book must tell you to do it. Now, the DFSMS situation is a little different since I don't think you can choose the filepool name at install, or easily change it later. The fully-qualified name of the config file should be specifiable in some way. Alan Altmark z/VM Development IBM Endicott
