Cecelia, Let me see what I can do to accommodate this ... I may be able to make the ATTACH "configurable". Please call CA VM Support to open an issue ...
Thanks, JR JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Dusha, Cecelia Ms. WHS/ITMD Sent: Monday, January 08, 2007 06:23 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Sharing an IBM ATL Across Systems I need to be able to share an IBM ATL across various systems (first level and guestOSs). I set up VM:Tape Shared Tape Allocation Manager (STAM) on all of the systems (first level and guestOSs). I then attached the tape drives using: CP ATTACH 300-303 BFSDEV MULTIUSER NOASSIGN CP ATTACH 300-303 BFSTST MULTIUSER NOASSIGN >From first level system: Q TAPES TAPE 0300 ATTACHED TO BFSDEV 0300 R/W NOASSIGN MULTIUSER TAPE 0300 ATTACHED TO BFSTST 0300 R/W NOASSIGN MULTIUSER TAPE 0301 ATTACHED TO BFSDEV 0301 R/W NOASSIGN MULTIUSER TAPE 0301 ATTACHED TO BFSTST 0301 R/W NOASSIGN MULTIUSER TAPE 0302 ATTACHED TO BFSDEV 0302 R/W NOASSIGN MULTIUSER TAPE 0302 ATTACHED TO BFSTST 0302 R/W NOASSIGN MULTIUSER TAPE 0303 ATTACHED TO BFSDEV 0303 R/W NOASSIGN MULTIUSER TAPE 0303 ATTACHED TO BFSTST 0303 R/W NOASSIGN MULTIUSER vmtape stam du * 4 WBF1 BDEV BTST BIFL 300 A,ON ON ON ON BFSDEV 301 A,ON ON ON ON BFSDEV 302 A,ON ON ON ON BFSDEV 303 A,ON ON ON ON BFSDEV Ready; T=0.01/0.01 06:06:49 VM:Tape STAM is viewing the tapes as being allocated to BFSDEV. If another system in the group requests a tape drive, it is placed in wait until one of the drives is released from BFSDEV and BFSTST. If a tape drive is not attached to either BFSDEV or BFSTST a tape can be mounted on either of my two first level systems... The VM:Tape System Administrator's Guide in chapter 19 section "Guest Systems Under VM" says, "VM requires that a tape drive be attached to a guest operating system as a dedicated device. If devices are to be shared between two or more guest operating systems in the same CPU, a device must be attached to multiple operating systems. If the device has an additional channel path, it can be defined to VM as two separte devices - one with the primary device address, and one with the additional channel address. Each of these two devices can then be attached to a different guest operating system." I thought the "CP ATTACH raddr system MULTIUSER NOASSIGN" would enable me to have VM:Tape STAM functional across all first level and guestOSs... Did I miss a parameter on the CP ATTACH statement? I reviewed the options, but could not determine what would be missing from the CP ATTACH statement... Or maybe there needs to be a specific option set on the guestOS for VM:Tape STAM? vmtape stam do VMTSTC369I CYCLE=10, NLIMIT=1, DLIMIT=3, DUCOUNT=1. VMTSTC369I VARYSYS=HERE, DEVSTAT=UCB, TRACE=NO. VMTSTC369I DURLSE=NO, RELUNLD=NO. Ready; T=0.01/0.01 06:17:43 Please advice. Thank you. Cecelia Dusha
