PID Failed

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
kommven
Charter Member
Charter Member
Posts: 125
Joined: Mon Jul 12, 2004 12:37 pm

PID Failed

Post by kommven »

Job shows PID Failed.
However was running very fine until a week before when we last ran it.

Tried all of the following, nothing works:
1. Cleared &PH& Directory
2. Unlock user on TCL. (This clears locks indeed but locks are created again on job run)
3.Deleted and redeployed job from version control
4. Ran ds.reindex
5 Ran DS.Checker
6. Stopped and Restarted DataStage Server.

Important to note is that the job runs perfect by itself but shows this error when called from a sequence.
Also shows this log message:
From previous run
DataStage Job 1085 Phantom 14706
Program "DSD.RUN": Line 2166, Variable previously undefined. Zero length string used.
Program "DSD.RUN": Line 2166, Variable previously undefined. Zero length string used.
Program "DSD.RUN": Line 2166, Variable previously undefined. Zero length string used.
Program "DSD.RUN": Line 2166, Variable previously undefined. Zero length string used.
Program "DSD.RUN": Line 2166, Variable previously undefined. Zero length string used.
Program "DSD.RUN": Line 2166, Variable previously undefined. Zero length string used.
Program "DSD.RUN": Line 2166, Variable previously undefined. Zero length string used.

Help Appreciated.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Is it called with exactly the same parameters from the sequence? Is it a multi-instance job and is it called up with an instance name?
kommven
Charter Member
Charter Member
Posts: 125
Joined: Mon Jul 12, 2004 12:37 pm

Post by kommven »

Yes it is called wth the same parameters.
Tried calling the sequence for different parameter sets but still aborts for the same job for the same error.
Most of the Job parameters are PROJDEF.

Also the job is not a multiple instance job.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

The error message from DSD.RUN looks like it comes from a "reset" of a job sequence, not a Parallel job, ist that right? Or is this the log of the aborted PX job?
kommven
Charter Member
Charter Member
Posts: 125
Joined: Mon Jul 12, 2004 12:37 pm

Post by kommven »

Thats Right, DSD Run appears when the sequence resets the job prior to running it.
Post Reply