DSXchange

My "step by step instructions for bouncing DataStage SE" is never to do so except to change the configuration or to upgrade.

Your original post specified UNIX server, yet you complain that the help is only for UNIX servers. What's the deal with that?

Client authentication is actually managed by the DataStage RPC daemon (dsrpcd). However, how it does this internally is knowledge denied to us, the great unwashed. I suspect even the ATS group (advanced technical support) in IBM would have to ask Engineering.

Server jobs don't need them. Parallel jobs need them to determine whether the table is partitioned and, if so, how. Server jobs simply operate in sequential mode, whether or not the table is partitioned.

Never, except to change configuration or upgrade.

Yes.

Locks are held for a reason. Locks held by defunct processes may safely be released using appropriate tools - there is no need to restart the server. Locks held by valid users should be released by those users.

Oracle is different from the rest of the world.

Your record lacks a record delimiter. DataStage is informing you of that fact. You could try setting or unsetting the Final Delimiter property. Otherwise use a local message handler to demote the message to informational.

The Hashed File Calculator (on your DataStage CD, in the unsupported utilities folder) will generate either CREATE.FILE or mkdbfile command.

If you need "everything before the ':' character", then a Field() function is a better solution, as it does not restrict you to a fixed size substring.

Shouldn't there be 17 syllables?

Maybe you could use the SDKSequences hashed file, which you can increment with the KeyMgtGetNextValue() function and which you can reset using a Routine or Execute Command activity.

How - precisely - is the StartLoop activity defined?

Can you post the generated job control code (inside Code tags please)?

There is no magic bullet. You need to do some detective work. Find out where the "hot spots" are - monitor the stage processes, use stage tracing (in particular generation of statistics) and analyze the results. Look at %CPU in the Monitor.

Change the line terminator in the Sequential File stage to "DOS style".

Encrypted environment variable job parameters are first supported in DataStage 7.5. You work it out.

"That would be an ecclesiastical matter."

-- Father Jack (Father Ted)