Hi,

I was asked by IBM Support to submit an RFE and here it is:

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=54665

Regards,

Hans Chr.


On Thu, Jun 5, 2014 at 10:25 PM, Del Hoobler <hoobler AT us.ibm DOT com> wrote:

> Hi Hans,
>
> I agree with you. Please open a PMR.
>
> Del
>
> ----------------------------------------------------
>
> "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 06/05/2014
> 05:45:50 AM:
>
> > From: Hans Christian Riksheim <bullhcr AT GMAIL DOT COM>
> > To: ADSM-L AT vm.marist DOT edu
> > Date: 06/05/2014 05:46 AM
> > Subject: Re: SQL-backup with no config file
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
> >
> > Hi,
> >
> > thanks for the answer.
> >
> > I may have explained the problem poorly. New try.
> >
> > If we have in a sqlful.bat script:
> >
> > tdpsqlc backup * full /configfile=someconfig.cfg
> >
> > and the file "someconfig.cfg" does not exist, the command runs along
> with
> > default config and returns with rc=0.
> >
> > Problem with that is if "somconfig.cfg" once existed and pointed to an
> > MSSQL-instance ie. "SQLSERVER NODE\INSTANCE" and somebody deletes this
> file
> > the schedule will run fine and the missing backup of NODE\INSTANCE will
> go
> > undetected. I just happened to find that out in our environment where
> such
> > a configfile was deleted more than a year ago. Luckily no restore of
> that
> > instance was needed in that period.
> >
> > I understand that specifying the instance in the backup script is one
> > solution but I also think it would be a lot safer if the tdpsqlc command
> > returned an error if /configfile points to a non existent config file.
> That
> > would also be consistent with how TSM behaves elsewhere. For example
> "dsmc
> > -optfile=file" will fail with rc=12 if "file" does not exist.
> >
> > Maybe this is PMR/RFE material.
> >
> > Regards
> >
> > Hans Chr.
>