Re: VMRPC placement in z/VM 5.2
Hello Mats, The Programmer's Reference citation is correct. The VMRPC TXTLIB part is built on the TCPMAINT 492 test-build disk, and should then also reside on the client-code disk (TCPMAINT 592) when TCP2PROD is used to place files into production. The various client 'run-time' files are copied from the 492 disk to the 592 disk when a 'wildcard' CATALOG file entry (similar to the one that follows) is processed by TCP2PROD: BLD3Z BLD2Z * * = = The CATALOG file entries you cited are in place to specifically propagate the VMRPC TXTLIB to the MAINT 493 /193 disks, to ensure it is available f or use whenever the (CMS) DMSVSMAS module is built (without requiring a separate access of the TCPMAINT 592 disk beforehand). Regards, Mark Cibula, z/VM TCP/IP Development and Support
VMRPC placement in z/VM 5.2
When installing z/VM 5.2 I found a discrepancy between the documentation and the actually installation. The manual says that the VMRPC TXTLIB should be on TCPMAINT 592 and the tcp2prod exec place it on the MAINT 193 Where is the right place for VMRPC TXTLIB? The 5VMTCP20 CATALOG file BLD3Z BLD10Z VMRPCTXTLIB== DMSVSMAS BLD3Z BLD11Z VMRPCTXTLIB== DMSVSMAS Manual z/VMTCP/IP Programmer's Reference Version 5 Release 1.0 Chapter 5. Remote Procedure Calls subchapter Compiling, Linking, and Running an RPC Program To compile, link and run an RPC program: 1 Access the TCP/IP Client-code disk (usually TCPMAINT 592), which contains the header files for RPC and the VMRPC TXTLIB, after the disk that contains the Language Environment header files (usually the Y-disk). Regards Mats Westlund HP Sverige AB
