DSXchange

Hi
I am getting the following warning while I am creating the File set.

File_Set_9: When checking operator: No nodes with disk in "export" resource pool; using default disk pool instead

Can anybody explain why and how to fix it.

thanks
nivas

Hope this post helps

--Rich

You don't actually need to "fix" anything. It's just DataStage alerting you to the fact that you're running a configuration file that doesn't include a pool name of "export" so it's using the default pool (which must always exist) instead. It does not affect operation of your job.

If you don't like it as a warning, create a message handler to demote the message to informational or suppress it altogether. Or make sure that all of your configuration files include an "export" pool.

Thanks Richdhan and Ray.
Ray could you please suggest how do I create message handler

thanks
Nivas

Hi nivas,

Select the warning and collect the message ID and
Director-->Tool-->Message Handler Management.
you can proceed the same via administrator for project level message handler.

Example of the message text canbe given for identifying the log.

You could rather refer the FAQ about Message handler post by vincent

IHTH
-Kumar

Hi Kumar

Ray suggested me to create/customise message handler either suppress the warning or to make the warning informational. So I am trying to do that. I was not able to find " Director-->Tool-->Message Handler Management".
I the administrator also I was not able to proceed how do I do that I need to do. Please advice.

thanks
Nivas

kumar_s wrote:Hi nivas,

Select the warning and collect the message ID and
Director-->Tool-->Message Handler Management.
you can proceed the same via administrator for project level message handler.

I think that this functionality is limited to DataStage 7.5; you might still be on 7.1.

It make more sense to correct the configuration as Ray suggested instead of putting in an explicit handler; I would recommend you add the new pool

Here's a handy trick (though you need to be on 7.5): you can right mouse click on the warning message itself, and create a message handler from the context menu. Neat!