DSXchange

How many CPUs does your system have and how many nodes are in your APT_CONFIG_FILE? Can you experiment on timing using multiple readers per node to see if you speed up reading your file (in order to test this, write to a PEEK stage instead of to the dataset)

You have two problem areas, and I'm not sure which you consider: a) reading from flat file and writing to a dataset b) reading the dataset. Is your mainframe file fixed length? If so, you might be able to improve your read performance by using multiple readers and most likely improve your dataset wr...

Open up a job monitor from the director after the job has run and set it to show instances. Does it show 2 instances for the transform stage?

Yes.

I don't know about 3:50am, my watch read 11:50am and the sun is shining...

Perhaps you specified the output dataset to run "sequentially", this would explain your issue as well. I doubt that rebooting the server would affect this particular problem, but it can't hurt it, either. Roy's suggestion of "Having you tried turning it off and on again?" certain...

It seems that the Lookup stage doesn't like the same column being used twice for the key. Duplicate your PL.A1 column and then use the original and duplicate for the lookup.

It should use the dsadm credentials, but evidently has not. What sort of information server datastage credentials setup do you have? Is it set up to share registry or does it have explicit defaults.

Yes, shell scripting would probably be the best way to do this.

In that case, how are you determining that there is only 1 partition in your dataset? I would use the Director -> Tools -> Dataset Management to examine the dataset.

If you are working in a distributed or grid environment and those nodes aren't available the job would fail. The only way for this to work dynamically is to have a program dynamically create a configuration file that is subsequently used by jobs.

That is an odd condition indeed and I don't know what could be the cause. Do you have existing PX jobs in an import file - if yes, I would import them and see if they can be opened or compiled; in which case it might be a client-based problem. I would suggest you also contact your support provider, ...

In the lookup stage, double-click on the Condition or right-mouse-click on the left pane and choose "conditions" and you will see a drop down box on the top left of the window that allows you to choose the link from which multiple rows can come.

Since the month can be m or mm you can't do a direct numeric or string comparison. I'd convert the number to a string using the following logice: 1. stage variable svTempStringDate = In.DecimalDate 2. stage variable svStringDate = IF LEN(svTempStringDate)=7 THEN svTempStringDate[1,4]:'0':svTempStrin...

Sort of. You would declare node pools, then call the job with the configuration file and then limit each stage separately as to which pool it should use.