ADSM-L

Re: Adding new DB & RecLog volumes whilst TSM server is running (on OS390)

2004-04-07 07:56:51
Subject: Re: Adding new DB & RecLog volumes whilst TSM server is running (on OS390)
From: Joni Moyer <joni.moyer AT HIGHMARK DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 7 Apr 2004 07:56:09 -0400
Paul,

You should be able to allocate & format the volume dynamically and then add
it to your TSM server.  You shouldn't have to stop/start the server at all.
(At least I never have...)  Then you should be able to define the new db or
log volume to your tsm server.  If you have any questions about how we do
this, just let me know.  Good luck!!!


********************************
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
joni.moyer AT highmark DOT com
********************************



             Paul Van De
             Vijver
             <Paul.Van.De.Vijv                                          To
             er AT HONDA-EU DOT COM>          ADSM-L AT VM.MARIST DOT EDU
             Sent by: "ADSM:                                            cc
             Dist Stor
             Manager"                                              Subject
             <[email protected]         Adding new DB & RecLog volumes
             .EDU>                     whilst TSM server is running (on
                                       OS390)

             04/07/2004 07:29
             AM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






Hi,

TSM Server (Version 5.1.8.0) running on OS390 2.10 (in the near future
Z/OS)

Up to now I always halted the TSM Server to define & format  additional
volumes
See example JCL below :

        //ALLOCAT  EXEC PGM=IDCAMS
        //SYSPRINT  DD  SYSOUT=*
        //SYSIN     DD  *
            DEFINE CLUSTER(NAME(ADSM.DB06) LINEAR MB(2341) VOL(ADSM21))
        /*

        //ADSMFMT  EXEC PGM=DSMFMT,DYNAMNBR=300,COND=(0,NE,ALLOCAT),
        //         PARM='/ADSM.DB06'
        //OPT       DD  DSN=ADSM.ANRSERV.OPTIONS,DISP=SHR
        //DSMAMENG  DD  DSN=TIVSM.V5R1M0.SANRMSG(ANRMENU),DISP=SHR
        //SYSPRINT  DD  SYSOUT=*
        //SYSTERM   DD  SYSOUT=*
        //*

Because the TSM Server options file (//OPT) is in exclusive use by the TSM
started task
I have to stop the TSM Server before being able to execute the format job.

Up to now there was no real problem with halting the server for a few
minutes to do this, but it is becoming
more and more difficult (even impossible) to find a moment where I can
stop the server (due to API-clients
which are accessing the server randomly) without causing archive/restore
problems.

I think this problem should be solved by simply using another options file
name (which is a copy from the original one)
for the format job (and TSM Server keeps running in the meantime).

Can I do this ? Or do I forget something and MUST I stop the TSM Server ?

Thanks for any info.

Best regards,

Paul Van de Vijver
Honda Europe NV
Belgium


The information contained in this communication is confidential and may be
legally privileged. It is intended solely for the use of the individual or
the entity to whom it is addressed and others authorised to receive it. If
you have received it by mistake, please let the sender know by e-mail reply
and delete it from your system.
If you are not the intended recipient you are hereby notified that any
disclosure, copying, distribution or taking any action in reliance of the
contents of this information is strictly prohibited and may be unlawful.
Honda Europe NV is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its
receipt.