dscmdexport command line problem
Moderators: chulett, rschirm, roy
dscmdexport command line problem
Hi,
I'm trying to create a batch file that will be execute each night. This batch file will be execute from a Windows client computer.
Here is my Dos command:
dscmdexport /H=myunixserver /U=myuser /P=mypassword PROJECTNAME FILENAME > logfile
This command works perfectly... the only thing is, the dscmdexport prompt me a dialog box that require somebody to press a Yes or No button...
The message on the dialog box is: File xxx already exists Do you want to replace it ?
Dialog title: DataStage Repository Interface
But the file doesn't already exist (I have the date and the hour in the filename...).
We are using Datastage 6.2.
Is anybody seen that before.
Thanks.
Math.
I'm trying to create a batch file that will be execute each night. This batch file will be execute from a Windows client computer.
Here is my Dos command:
dscmdexport /H=myunixserver /U=myuser /P=mypassword PROJECTNAME FILENAME > logfile
This command works perfectly... the only thing is, the dscmdexport prompt me a dialog box that require somebody to press a Yes or No button...
The message on the dialog box is: File xxx already exists Do you want to replace it ?
Dialog title: DataStage Repository Interface
But the file doesn't already exist (I have the date and the hour in the filename...).
We are using Datastage 6.2.
Is anybody seen that before.
Thanks.
Math.
-
- Premium Member
- Posts: 224
- Joined: Tue Sep 24, 2002 7:32 am
- Location: Denver, CO USA
-
- Premium Member
- Posts: 1044
- Joined: Wed Sep 29, 2004 3:30 am
- Location: Nottingham, UK
- Contact:
Re: dscmdexport command line problem
No, I hadn't seen it before you started this thread, but I am seeing it now! I am using DS 7.0.2 and I have exactly this problem on my desktop PC, but not on my laptop, or on anyone else's PC. No matter what filename I use, it pops up a "DataStage Repository Interface - File c:\QA.dsx already exists. Do you want to replace it?" dialog box. If I then look in explorer, sure enough the file is there, zero bytes, timestamp of a few seconds ago.mtardif wrote:Hi,
I'm trying to create a batch file that will be execute each night. This batch file will be execute from a Windows client computer.
Here is my Dos command:
dscmdexport /H=myunixserver /U=myuser /P=mypassword PROJECTNAME FILENAME > logfile
This command works perfectly... the only thing is, the dscmdexport prompt me a dialog box that require somebody to press a Yes or No button...
The message on the dialog box is: File xxx already exists Do you want to replace it ?
Dialog title: DataStage Repository Interface
But the file doesn't already exist (I have the date and the hour in the filename...).
We are using Datastage 6.2.
Is anybody seen that before.
Thanks.
Math.
I have raised this with Ascential, they say that they have only heard of this problem once before, and were unable to recreate it. Was that you, or is there a third lucky winner out there somewhere?
(p.s. I know, the OP hasn't been seen around here for a while, so consider that an open question to the crowd)
Phil Hibbs | Capgemini
Technical Consultant
Technical Consultant
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA
I know what the problem is! I've run into it before...
Check the current default for the Manager's 'Export DataStage Components' screen. If you have 'Export as XML Document' checked, it will stop and prompt you with this strange little question. This in spite of the fact that you are not creating an .xml export.
Check the current default for the Manager's 'Export DataStage Components' screen. If you have 'Export as XML Document' checked, it will stop and prompt you with this strange little question. This in spite of the fact that you are not creating an .xml export.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Hi,
the most simple solution would be to rename or delete the file in your bat file before running the dscmdexport command.
I suppose something like would do, just replace the DSExport.dsx withthe name you use.
IHTH,
the most simple solution would be to rename or delete the file in your bat file before running the dscmdexport command.
I suppose something like
Code: Select all
del /Q/S DSExport.dsx
IHTH,
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
No, you are missing the point. You can only create a .dsx export from the command line. However, in your client software on the machine you are doing the export from, the 'Export as XML' option is checked. This causes the stupid error you are seeing!PhilHibbs wrote:I wish I was creating an XML export, it would be very useful.
Go into the 'Export DataStage Components' gizmoski and uncheck it. You'll be fine after that. I swear.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 1044
- Joined: Wed Sep 29, 2004 3:30 am
- Location: Nottingham, UK
- Contact:
I use DS Manager every day, and I only use the xml export option, so that would require me to un-check it at the end of every day to ensure that the backup worked. That kind of error-prone manual tedium is what I automated the backup to avoid!chulett wrote:Go into the 'Export DataStage Components' gizmoski and uncheck it. You'll be fine after that. I swear.
Nope, the error occurs whether or not the file existed before running dscmdexport.roy wrote:the most simple solution would be to rename or delete the file in your bat file before running the dscmdexport command.
Phil Hibbs | Capgemini
Technical Consultant
Technical Consultant
Ok, then I can only see a couple of solutions. No amount of 'renaming' will help, as you've found. So...
1) Find out where that option is stored in the registry (assuming it is) and somehow automagically turn it off and then back on again during your backup.
2) Run the backup from a different machine.
How much of a possibility is #2?
1) Find out where that option is stored in the registry (assuming it is) and somehow automagically turn it off and then back on again during your backup.
2) Run the backup from a different machine.
How much of a possibility is #2?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 1044
- Joined: Wed Sep 29, 2004 3:30 am
- Location: Nottingham, UK
- Contact:
That is my current workaround! It's only saving the problem up for later, though.chulett wrote:Ok, then I can only see a couple of solutions. No amount of 'renaming' will help, as you've found. So...
1) Find out where that option is stored in the registry (assuming it is) and somehow automagically turn it off and then back on again during your backup.
2) Run the backup from a different machine.
How much of a possibility is #2?
I have looked in the registry and I can't find it, and I've asked Ascential for this informaton.
Phil Hibbs | Capgemini
Technical Consultant
Technical Consultant
If you do come up with a solution, post it back here. I'm sure there would be plenty of people looking for a generic solution to this issue.
In my mind, something to first determine the current setting is needed. If the option is found to be set, unset it and then put it back at the end of the backup. If it's not set, then do nothing. That would be cool.
In my mind, something to first determine the current setting is needed. If the option is found to be set, unset it and then put it back at the end of the backup. If it's not set, then do nothing. That would be cool.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Phil,
I did a quick change/compare to isolate the registry entry. It is here:
"1"=xml, "0"= dsx
I'm sure you're aware of the usual disclaimers/warnings associated with editing the Windows registry.
Please do let us know what solution you come up with.
Thanks,
Mike
I did a quick change/compare to isolate the registry entry. It is here:
Code: Select all
[HKEY_CURRENT_USER\Software\Ascential Software\DataStage Client\Manager]
"XML Format"="1"
I'm sure you're aware of the usual disclaimers/warnings associated with editing the Windows registry.
Please do let us know what solution you come up with.
Thanks,
Mike