parallel Jobs finished ok but with Phantom warning message

jane_jiang · Post by **jane_jiang** » Wed Sep 06, 2006 9:46 am

All,
I encounter a problem when I am running several DS sequences in parallel using the dsjob command. All the jobs in the DS sequence are finished ok but in the end(after the Summary of sequence run) it get a phantom warning message caused the DS sequence aborted:

DataStage Job 139 Phantom 11116
The variable "APT_MSG_FILELINE" is not in the environment.
The variable "APT_NO_JOBMON" is not in the environment.
The variable "APT_PERFORMANCE_DATA" is not in the environment.
The variable "APT_PM_PLAYER_MEMORY" is not in the environment.
The variable "APT_PM_PLAYER_TIMING" is not in the environment.
The variable "APT_PM_SHOWRSH" is not in the environment.
The variable "APT_PM_SHOW_PIDS" is not in the environment.
The variable "APT_RECORD_COUNTS" is not in the environment.
The variable "APT_SHOW_COMPONENT_CALLS" is not in the environment.
The variable "APT_STARTUP_STATUS" is not in the environment.
The variable "OSH_DUMP" is not in the environment.
The variable "OSH_ECHO" is not in the environment.
The variable "OSH_EXPLAIN" is not in the environment.
The variable "OSH_PRINT_SCHEMAS" is not in the environment.

If I kick off four parallel DS sequences using the dsjob command, sometimes there are two get warning and other two finish ok, sometimes there are three get warning, which is very random.
I notice in the files of &PH&, most of the them has the above "variable not in the environment" message, but seems the warning only happened in the parallel DS sequences for some reason.

Any body has any good advice on this?
Thanks in advance.

-Jane

ray.wurlod · Post by **ray.wurlod** » Wed Sep 06, 2006 4:08 pm

It's looking for environment variables that are usually set in the Administrator client. Perhaps the jobs have specified $ENV as the default value, which causes the (parallel) jobs to look in the executing user's environment for a replacement value. These environment variables are not applicable to server jobs. Prefer $PROJDEF to $ENV for the in-job default value unless you have good reason to design otherwise.