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. On Wed, Jun 4, 2014 at 5:33 PM, Angela Robertson <aprob...@us.ibm.com> wrote: > Hi, > > There is an APAR for this issue -> IC98441. Here's the link to track -> > http://www.ibm.com/support/docview.wss?uid=swg1IC98441 > > In addition to the fixing levels listed in the APAR link, we are also > planning to to include this APAR in the DP SQL 7.1.0.1 interim fix. This is > targeted for delivery in late June. However, this is subject to change at > the discretion of IBM. Angela > ---------------------------------------------------------------- > Angela Robertson > IBM Software Group > Durham, NC 27703 > aprob...@us.ibm.com > ---------------------------------------------------------------- > > "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> wrote on 06/02/2014 > 07:50:08 AM: > > > From: Hans Christian Riksheim <bull...@gmail.com> > > To: ADSM-L@vm.marist.edu > > Date: 06/02/2014 07:51 AM > > Subject: [ADSM-L] SQL-backup with no config file > > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> > > > > I noticed that if someone(usually a DBA) accidentally renames or deletes > a > > tdpsql_XXXX.cfg file the command still runs and just uses the default > > config. it will return with no errors. > > > > Example: > > > > Someone has deleted a configfile which points to a specific instance. > > > > tdpsqlc backup * full /configfile=tdpsql_INSTANCE.cfg will backup the > > default server instance if the config file is missing with rc=0. > > > > Would it be possible to have the command end in error if /configfile > points > > to a non existent config file? > > > > Regards > > > > Hans Chr. > > >