DSXchange

Whenever i use a Folder stage to get the path of the source file i am
getting an error like
DSD.UVOpen Unable to open folder C:\.
DSD.UVOpen Unable to open folder C:\.|
Can any one tell me what is the reason for the same.

And one more thing When is it advisable to go for a folder stage?

Check the path of the folder.
Folder stage is used when you have a directory that has been identified, where source files with perhaps a pre decided extension (maybe some thing like ".csv") will be used.
This makes life simpler as you dont have to know the name of the file that has to be processed.

I agree.
You are on UNIX, but getting a Windows pathname in the error message. This strongly suggests that a default value is being used for the folder's pathname.
If you're loading the folder name from a job parameter, check (in the log, in the "job start" event) that the parameter value has been correctly set.

I am facing the problem only if i am using the path as C:\
If i give the path like C:\Foldername It works fine. Is there any thump rule that we should not the path as C:\ or D:\

So, you're on Windows after all!

I'm not aware of any restriction on using C:\, although it's never a good idea to write things into the root of a file system, in case it becomes full.

What happens of you use C:\. (with a "current directory" dot as the final piece of the pathname)?

Well, the only 'restriction' I am aware of is the fact that the root directory of any drive is the only one with a limit to the number of entries it can contain. Don't recall the actual number, and this may be a thing of the past, but it certainly was an issue Back In The Day.

Besides, as Ray mentions - if it hurts when you do something, don't do it!

Just a stab...

The FOLDER stage barfs (technical term) if the folder it is looking at has folders in it.

You can only use the FOLDER stage on folders that contain only files, no other folders.

Does that help any?

-Craig

Hi,
I do believe seeing this restriction in the manuals when I last looked (was long ago) if my memory serves me it specifically states not to use on directories containing directories.
besides usually it has a limit on max file size depending on your config, theese limitations are more then enough for me to always use alternative solutions and avoid using this stage.
there are posts here on how to get the same functionality using basic vie openpath, another way is to issue a dir command and redirect the output to a seq file which is easy to handle using a regular sequential file stage.

IHTH,