DSXchange

Tell the DS Admin that you NEVER kill processes associated with DataStage jobs. There are proper ways to stop jobs and remove their processes; kill -9 is not among them. So, the job is locked, and the lock is owned by a process that no longer exists (a "defunct" process). Your DS Admin is ...

Anything with RT_ prefix is a run-time table; there are also RT_CONFIGnnn and RT_LOGnnn. No, you can't delete them. RT_STATUSnnn contains the status information for job number nnn and its active stages and resources, which you view in Director (in status and monitor views). RT_BPnnn contains the sou...

Let me get this straight. Run 1 - the Data Set was not created. Run 2 - the Data Set could not be deleted. Is that right? Probably the Data Set stage is set to overwrite, and the "error" is spurious. What does your official support provider have to say? Is the error fatal, or does Run 2 fi...

Is there any OCCURS clause in the COBOL FD on which the CFF stage bases its operation?

Oooh, no, I don't think we can ignore it. Tell us what you did to castigate this "someone"!

JobA and Job2 started within the same second. Please post your actual job sequence design. Also please post the logged startup and execution times of all five jobs (including the job sequence).

On a single machine ("SMP" environment) you may as well use Entire, because it comes at no cost, via shared memory. In a multiple machine environment ("MPP", cluster, grid) there can be a substantial cost moving records to all nodes, so you tend to avoid Entire (other than for sm...

Craig's memory is accurate. The actual folder is Utilies, and there's a sub-folder in there called Unsupported, and within that one for the HFC.

Job logs are not stored in files - they are stored in database tables.

Try refreshing the Director client (View > Refresh).

Don't link them together. There ought to be no link from Job2 to Job3.

No, only the membership director can. You are not yet showing up as a premium member.

The other thread also gave the algorithm for the routine, if memory serves.

It can not be done with a job design containing only passive stage types*. You need at least one active stage type.

* unless run multiple times, appending to the target and sorting the target in an after-job subroutine.

Handle the null explicitly - maybe convert it to a "high date" timestamp.

They use the same dynamic configuration files that any grid configuration would use. The basis is a "standard" configuration file, and there are some environment variables that need to be set. I can not remember off the top of my head which ones they are.