DSXchange

Oh, so this was a MPP setup?

DataStage is attempting to spot the actual PID of JobMonApp. Then it will pull the information, and push the information based on the XSD file within the java directory. This is why I find it critical that you verify that the "Environment variable setting:" have the correct value, which in...

Please provide the result from within the DataStage job, as I asked. The results CAN be different, despite using the same username to run jobs.

I guess you can recognise null values in such a file, when you find a zero length string between two TABs. The only way you can do this is if you trigger "APT_IMPEXP_ALLOW_ZERO_LENGTH_FIXED_NULL". It will not work otherwise. Bunny mentioned that he/she does not know about this, so I am aw...

This is one of many things that are different between Server jobs and Parallel jobs.

Orchestrate is the actual engine's name running Parallel jobs. OSH code = Orchestrate Code.

Solaris 2.10 (aka 5.10, aka 10) is not supported for DataStage 7.5a. Sorry.

SPARC 2.8, 2.9
Solaris is a 64bit OSs with 32 bit compatibility. DataStage is a 32bit application

Contact Ascential Support to get the official line on this.

It does sound like something in your job's OSH code or whatever triggered a latent bug. Did you save that job? Are you able to restore it and repeat the crazy CPU action?

If so, PLEASE hit Support with that.

I do support the concept of using buildops, but when you do not have an expert C/C++ staff, it would be a maintenance nightmare.

Plus migration of buildops have its own interesting set of problems.

There are advantages and disadvantages to everything, naturally.

Director.

dsjob.

Kim Duke's tools.

Those are the three options you have. What do you want to do with the information? Where do you want to see the information? Do you want a history? Do you just want someone to watch the jobs?

I am not quite clear on what you are trying to do.

When I am referring to Routines, I am referring to BASIC routines (yes, they can pass values to called PX jobs), and scripts are UNIX-level (Perl, KSH, C using the API, et cetera.)

Try it within DataStage. Do an ExecSH with that command.

Hmm, dang, was not able to test this on my computer, since I only have 7.1 right now. Hope someone else here could help you with this.

Sorry.

You could use the pivot stage. You also could use a multiple output from a transformer (or filter if you can use it to verify the qualifying information), and funnel the results.

This is exactly what I thought happened. The most proper way to insert values within SQL from a Datastage stream is to use the following format: INSERT INTO [table] (field1, field2, field3...) VALUES (ORCHESTRATE.INPUT_FIELD1, ORCHESTRATE.INPUT_FIELD2, ORCHESTRATE.INPUT_FIELD3...) Basically, you can...

FYI: Server jobs do not use JobMonApp. Do a search on this forum to learn more about JobMonApp. 1. Verify that absolutely nobody is using or setting $APT_ORCHHOME anywhere outside the dsenv file. 2. Within Director, check the job log, and verify that APT_ORCHHOME is exactly the same on runtime of th...