DSXchange

Have not (yet) used CCMigration.exe so can not advise.

Indeed.

Best practice tip #Rnd(42): never have Director log or monitor open nor Designer design area open when exporting/importing that job.

Is this a one-off exercise or an ongoing requirement?

The SQL that is actually executed is usually obtainable from the job log.

The SQL that is designed is a property of the link on which it occurs. This SQL may include job parameter references.

The miracle of Search!

Thank you for posting the resolution. This will aid future searchers.

Not enough information. I can aver that the rules are the same for Data Sets. The actual number of files is the product of the number of nodes in the configuration file and the number of resource disk directories for each node. But there may be more than this (a) if you are appending, particularly t...

What tool were you using to inspect the target?

Moderator: please move to server forum

CLEAR.FILE can hang. It attempts to take a special table-level lock, and will be thwarted if any other process has any record locked in the table (hashed file). For example if someone has the job log open in Director, or has a Monitor open, then such a lock exists.

I believe this is an Execute Command activity in a job sequence. If this is correct, simply use the regular command line (perhaps for gzip or compress). If anything needs to be parameterized, you need to put that and the remainder of the command into the Parameters field.

To clarify that further, Windows IS supported for version 7.5.2, but only server and mainframe jobs.

A special version (7.5x2) was created to compile and run parallel jobs on Windows platforms.

To check whether the AppServer is running: /usr/IBM/WebSphere/AppServer/bin/serverStatus.sh server1 To check whether the ASB Agent is running: netstat -n | grep 31531 (there should be one listener) To check whether the Job Monitor app is running: netstat -n | grep 1340 (there should be two listeners)

Hashed files usually aren't used at all in parallel jobs. Can you please provide more information about precisely what you're doing and what you hope to achieve?

The after-job subroutine itself could start the other job. Depends really on what you actually want to accomplish, about which you have provided little information.

What actual commands are you using to request the jobs to stop. "Scripts" is not a useful start point for diagnosis.

The "$" character will cause DataStage to seek out an environment variable in the project. Is that how your project is set up?

Despite being a premium user, you have to request a password from the membership director.