DSXchange

Hi
This is the error i got Please its urgent
####################################################################################
# Step 2: File Control Insert with Status - New
####################################################################################
ApplicationID = 1
JobName : JsCFPCOMM_Set_File_Ctrl
DSProject : cfpprd010
BAPI: File Control Insert/Update Datastage job is started at: Wed Jun 30 20:30:25 EDT 2010
Waiting for job...
BAPI File Control Insert/Update Datastage job is completed at: Wed Jun 30 20:30:36 EDT 2010
DATASTAGE_PROJECT PARM= cfpprd010
JOB_NAME PARM= JsCFPCOMM_Set_File_Ctrl.TRSQFR
Successful parse of job status string...continue
JobStatus=Job Status : NOT RUNNING ~99~
DataStage Job Status is = 99

check whether job is in compiled state or not

but when i check in the director its in finished state only.

I guess the problem is with auto purging of job log. Bcoz in all other servers its auto purge action = older then 2 days.

But in this production server its last 2 runs.

???????????

Unfortunately, it's a "catch all status" so it could mean any number of things that the other status codes don't catch.

there is a known bug in 8.x with multi - instance jobs only, till fixpack 2 where this bug is claimed to be fixed. Even after that the issue may arise, sometimes.

Can you confirm whether the job is multi-instance and the exact version of datastage?

Do you have any document that lists what are the job codes and their numbers datastage will throw, IF any failure occurs. I will really appriciate if you send that document to my mail electajay@gmail.com.

Thanks in Advance.

chulett wrote:Unfortunately, it's a "catch all status" so it could mean any number of things that the other status codes don't catch. ...

All of that, including the filename where that is stored on your system, is in the post I linked.

The version we are using here is Datastage V 8.1.0.0 and its on zlinux.
Can you define how can we find out the datastage job is multiinstance or another instance.

Thanks for your reply

priyadarshikunal wrote:there is a known bug in 8.x with multi - instance jobs only, till fixpack 2 where this bug is claimed to be fixed. Even after that the issue may arise, sometimes.

Can you confirm whether the job is multi-instance and the exact version of datastage?

Hi,

1. Pls check this link for a list of job status codes

2. Check the job properties if it is a multi-instance job.

HTH
--Rich

You should know if a job is multi-instance or not as that is a deliberate design decision someone had to make, plus that shows in the description.

richdhan wrote:1. Pls check this link for a list of job status codes

Or just check the dsapi.h file as noted in the previous linked post for the complete list.