ADSM-L

Re: [ADSM-L] 3494 Partitioning

2009-02-17 13:27:08
Subject: Re: [ADSM-L] 3494 Partitioning
From: Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 17 Feb 2009 13:25:58 -0500
-----Nick Laflamme wrote: -----

>Can anyone refer me to the parameters options for partitioning a
>3494 ATL? It's easy to find that a 3494 can support two VTS
>partitions; I'm questioning how we add TSM on AIX to the existing
>z/OS non-VTS use and a VTS partition for z/OS.
>
>We have new 3592s to coexist with the z/OS's 3590s, so there's no
>question of sharing drives or volumes. I simply can't verify that
>we can set up a another partition for this new image.
>
>I have a copy of SG24-4409, the Redbook on partitioning 3494s. It
>doesn't address the question and, worse, it hasn't been updated
>in a decade.
>
>(I miss the 3584s I used at former sites. Sniff.) (Then again,
>someone said a single 3584-L23 is about $300,000, so I guess I
>understand why they didn't go that route right away.)

We have a 3494 shared between a VTS used by z/OS, a group of
native tape drives used by z/OS, and a TSM server with two types
of tape drives. Our experience matches that of other respondants;
a new 'partition' is really just a pair of previously unused
category numbers.

We did have a little trouble with z/OS when we first migrated
TSM from z/OS to its current host (mainframe Linux). The z/OS
system has an exit routine that is called when a volume is
inserted into the 3494. The return code from the exit tells
z/OS whether to assign one of its own category codes to the
volume. We had to update the exit routine to get z/OS to stop
grabbing TSM volumes before TSM tried to check them in.

<Prev in Thread] Current Thread [Next in Thread>