All of this is true, but the dsmfmt program will work without the //OPT
dddef. It is not needed to format any of the volumes, DB, recovery or disk
cache volumes. It works without specifying //OPT, so why confuse the matter
with multiple option files.
> -----Original Message-----
> From: Brian L. Nick [mailto:BRIAN.NICK AT PHOENIXWM DOT COM]
> Sent: Monday, April 26, 2004 10:12 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Adding new DB & RecLog volumes whilst TSM server
> is running ( on OS390)
>
>
> Crude but simple way to do this. Stop the TSM server and
> create a copy of
> your .opt file .opt2 or .opt.batch and run the format job against the
> copied file. Just need to keep the copy option file up to date.
>
> - Brian
>
>
> Brian L. Nick
> Systems Technician - Enterprise Storage Solutions
> The Phoenix Companies Inc.
> 100 Bright Meadow Blvd
> Enfield CT. 06082-1900
>
> E-MAIL: Brian.Nick AT phoenixwm DOT com
> PHONE: (860)403-2281
>
>
>
> "Gee, Norman"
> <Norman.Gee AT LC DOT CA To:
> ADSM-L AT VM.MARIST DOT EDU
> .GOV> cc:
> Sent by: "ADSM: Subject: Re:
> Adding new DB &
> RecLog volumes whilst TSM server is running ( on OS390)
> Dist Stor
> Manager"
> <[email protected]
> .EDU>
> 04/26/2004 12:46
> PM
> Please respond to
> "ADSM: Dist Stor
> Manager"
>
>
>
>
> If you change it to disp=shr, then the TSM started task can't
> update the
> option file on the fly.
>
> > -----Original Message-----
> > From: Slag, Jerry B. [mailto:jslag AT STATE.ND DOT US]
> > Sent: Monday, April 26, 2004 7:37 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: Adding new DB & RecLog volumes whilst TSM server
> > is running ( on OS390)
> >
> >
> > Change the dd def to "disp=shr" in the TSM procedure - don't
> > let tsm have
> > exclusive control.
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On
> > Behalf Of
> > Gee, Norman
> > Sent: Monday, April 26, 2004 12:06 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: Adding new DB & RecLog volumes whilst TSM server
> > is running
> > ( on OS390)
> >
> >
> > Did you know that this job will still work with the dddef for //OPT
> > commented out or left out.
> > I discover this when I decided I did not want to shutdown my
> > TSM server
> >
> > -----Original Message-----
> > From: Paul Van De Vijver [mailto:Paul.Van.De.Vijver AT HONDA-EU DOT COM]
> > Sent: Wednesday, April 07, 2004 4:30 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Adding new DB & RecLog volumes whilst TSM server is
> > running (on
> > OS390)
> >
> >
> > 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.
> >
>
>
>
>
>
>
>
> **************************************************************
> *********************
> CONFIDENTIAL: This communication, including attachments, is
> intended only for
> the exclusive use of addressee and may contain proprietary,
> confidential
> and/or privileged information. If you are not the intended
> recipient, you are
> hereby notified that you have received this document in
> error, and any use,
> review, copying, disclosure, dissemination or distribution is strictly
> prohibited. If you are not the intended recipient, please
> notify the sender
> immediately by return e-mail, delete this communication and
> destroy any and
> all copies of this communication.
>
> **************************************************************
> *********************
>
|
