DSXchange

Tell your network administrator person that there is a problem with "get service by name". He/she will understand and should be able to fix it. It's not a DataStage issue. It's to do with being able to find a service, by name, when a request for that service arrives. That there's an entry in the /et...

And Version Control supports the notion of a Custom Folder, which it "knows" has to be promoted/migrated.

We still have the technology...

:evil: What the heck do you think the Dependencies tab is there for ?!!! Are you talking about the Package Wizard in Manager? Won't work for PX. It is a pain in the arse to ensure that custom stages and buildops along with their associated table definitions are migrated. But it's NOT that hard. 5 m...

How about a small change to the wording on the Forum index for the DataStage forum, encouraging users to search the archives before posting a question?

But don't be disheartened by that. :D As Ken says, he was in a foul mood at the time. (That said, everything in his post is correct.) Lay your hands on the Kimball book (search this Forum for details) to see how to design and implement DW properly. Here's a couple of best practices to get you under ...

When I was young ( ) and the IBM 360/20 was new ( ) the A margin was at column 8 and the B margin was at column 12.
That's it. No arguments.
<gruff>
(Should be more of it. Bring back the rope!)
</gruff>

Only that it's not a DataStage problem. Your mail server hates your mail client. It's probably a configuration issue on the mail server, to tell it that it has to recognize this client (or sender ID).

Have you specified the starting character column for 01 items correctly?
If not, and line 3 is your first 01 level item, this could generate this error.

Gosh, almost word for word the answer I was going to give!

What the heck do you think the Dependencies tab is there for ?!!! The old style of propagation (released jobs) could use it, so can Version Control. I second Ken's condemnation of your client. They are, purely and simply, wrong. Tell them: It's no big deal to ensure that Routines on which a job dep...

Do they all have the same record (line) layout? If so you can create a multi-instance job with the file name and hashed file name parameterized, and fire off all instances out of a job control that uses a loop of some kind to deliver parameter values to the separate instances. If they have differing...

Well, you can do it by inspecting the job log, using the DataStage functions for that. When the batch or job sequence starts a child job, it logs a "job run request" event. DSR_WHEREUSED is to support the Manager's where-used analysis of where particular job components are used in a project, it's no...

1. None that you would notice, unless their derivation expressions are hugely complex. But the same would be true with more columns or more complex expressions elsewhere in the Transformer stage (or anywhere else for that matter). More complexity = more CPU cycles = more elapsed time. 2. No practica...

Duplicate post. Please go back and delete the other one (with no replies). A metadata mismatch is a warning, rather than an error. It indicates that the metadata in your job design does not match the metadata in the table being referred to. In one place the length (precision) is 8, in the other it i...

You may get an error event logged if you reset the job (rather than recompiling it). Otherwise you can search in the &PH& directory on the server. The usual cause for aborting an Aggregator stage is that it needs more memory than is available for it to allocate. Try sorting your data by the column(s...