DSXchange

So this job does run on multiple nodes? And you don't have time to test it over time running on a single node before it needs to go to production? Just want to make sure we're all on the same page. My "partitioning" comment was extremely generic. And would typically be more about the targe...

Just want to make sure I understand - you need to get yesterday's date from the UNIX command line?

If so, then this is the trick you'll find if you google:
Use your timezone. If that's not what you need then please clarify.

Was wondering about that. So what was the actual resolution - were they using 'special characters' in the password?

This is typically caused by (improper) partitioning, which can be tested by running the job on a single node.

They haven't posted here in almost four years. Perhaps you should contact support.

That is a completely different scenario than your original post.

Chuck.

Sorry, no idea. None of those variables come with a length specification. You should contact your official support provider to see what they have to say on the subject while you wait for a more helpful reply. Perhaps a patch is in order.

Support.

ps. $APT_DISABLE_COMBINATION isn't meant to "fix" anything, it merely stops operator combination so that the failing component can be isolated.

pps. What changed on Friday? Anything at the O/S, DataStage, SAP level you are aware of?

Looks more like a join to me.

.profile typically.

"the DB2 changed the pwd"? So this means a database password was changed and you also have a environment variable of type Encrypted you are trying to make hold the new (increased in length) password, yes?

There's nothing about Auto that 'spends time and effort' to determine the most efficient method to use for each stage and how it is being used in your job. Found a detailed discussion here that may help. Also thought this quote from it was worth putting here: Auto partitioning will guarantee that th...

I'm not sure there's an answer for that question as there are SO many factors that go into it. Never mind that one man's good is another man's great and yet another man's crap.

You'll have to wait for one of the Old Guard to come along for the gory details on this TCL syntax but from what I recall it is all about the category records in the table... as in only getting them or skipping them. I think it is escaping the back slashes so looking for anything that starts with tw...

I would imagine it's as much about what happens after the read as the reading itself. What makes you think the reading of the file is the bottleneck in your job?