DSXchange

Data Sets don't migrate. Why would you want to? You normally overwrite them each run anyway. There is a post by kali recently on the question of how to migrate Data Sets, but no useful reply. I don't know of a reliable way to move them. Can't help with your second point, as I still have not played w...

Hi Gurus, can we invoke the functions like DSGetJobInfo from the command prompt. But these are functions, can we call these functions from command prompt or else these functions are used only in processing stages. cheers; saama No, in exactly the same way that you can't call SQL functions other tha...

Should be just UPDATE queries, except that you have to determine the column names. These tables are fully documented, so you can do so readily with a LIST.DICT command.

Not in a server job, it won't!

The documentation means that DataStage supports OCCURS n TIMES but does not support OCCURS 0 TO n TIMES DEPENDING ON column

While ever you have OCCURS DEPENDING ON in your copybook, the CFF stage is not going to be able to handle it. Prior to version 8.0, anyway.

It's a mainframe job. Unfortunately there is no function such as the one you seek in mainframe jobs. You have Len() to determine the length, and I think - without checking - that you have Str() which can generate repeated strings. So something like Str("*",Len(MyString)) might do it for you.

From Director client you can use the Cleanup Resources tool. For an individual parallel job you can set the APT_PM_SHOW_PIDS environment variable. Or you can get in to the DataStage environment on the server in a project directory and execute the DS.TOOLS menu. Invoke the sub-menu to work with proce...

Can you use TOAD or sqlplus with SQL Server?!!

Somewhere in the MQ Series documentation, I would guess.

Please post the exact warning.

Check that you are providing the correct pathname for dsrecords and the correct pathname for the xyz.ds file - that is, the Data Set control file.

You can set the default in Director using Options from the Tools menu.

But that default is only for jobs started from that particular Director client by that particular user - it becomes a Registry entry on the client PC.

Just don't break any confidences or non-disclosure agreements!

I know of no work in the field of neural net or any other "automatic" mechanism to do what you suggest. Maybe there's a PhD in it?

These are totally unrelated to the first set of errors. What is the nature of "some workaround"? Is this being run from DataStage or wholly within QualityStage? If from DataStage, do you get the warnings when running the QualityStage job within QualityStage only? (For example, if you don't, you've n...

It's not DataStage. The message shows that the ODBC driver manager was successfully loaded, and the SQL Server driver was successfully loaded using the libssclient20 library. So the problem is outside the ODBC driver - maybe the network but I'd be checking the database server first.