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.
I tried this, no luck. There must be some other side-effect of that tickbox that causes the problem. Ascential Support said "but there is something else that the Manager changes" when I enquired about the registry setting (I did look myself but somehow didn't spot that key).
Update:
Just for completeness sake, I also changed the extension of the DSExport value from xml to dsx as well as changing the "XML Format" value, and this fixed it! This is surprising to me, since dscmdexport has no reason to read the default export file name that DS Manager uses.
Last edited by PhilHibbs on Thu Mar 03, 2005 12:35 pm, edited 2 times in total.
Yes. It wasn't obvious to me that that particular key was used for an export either. I did a registry export, unticked the property, did another registry export, and then compared the two registry exports.
There was one other key that changed. I didn't mention it because I didn't think it would make a difference, but ...
"DSExport" key (appears to contain the last used export file name). The file extension in this changed from xml to dsx.
Those were the only two registry settings that changed within the [HKEY_CURRENT_USER\Software\Ascential Software\DataStage Client\Manager] branch.
I notice that your backup script is written in MS batch language, I don't know how you would solve this problem in that context. Anyone know of a good command-line registry edit program? I suppose you could use
I recently worked at a site that renamed the exiting export file, then exported. They rely on nightly Windows backups if they ever need to go back more that two nights. They've never needed to thus far.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ray.wurlod wrote:I recently worked at a site that renamed the exiting export file, then exported. They rely on nightly Windows backups if they ever need to go back more that two nights. They've never needed to thus far.
That would not avoid this problem, because when the XML box is ticked, the dscmdexport command always prompts about the existing file, even if the file did not exist before running it.
That's not the default but if you've made sure that option is defaulting to on and it's still not working, I don't see what else you could do. There's nothing to change in the registry in that case.
-craig
"You can never have too many knives" -- Logan Nine Fingers
I know the problem.
I had it in datastage version 8.0.1, and the solution is:
In designer tool, Tools > Options > Prompting > Unmark this check boxes.
Now try again.
Solved?