-db_cs option is deprecated

snt_ds · Post by **snt_ds** » Thu Dec 18, 2008 10:59 am

Hi,

I have one datastage job which is called multiple times in same sequence to load different datasets to the same table.

The sequence is getting aborted in the any of the jobactivity with the following status

EDMInsDSErrorLog.REJ_LKP_PACE_BOS_ERRMSG has finished, status = 99 (Not running)

This is running without any issues in DS 7.5.1

I can see something strange in the log.

main_program: -db_cs option is deprecated

Could you please let me know,what this message indicates?Is this message is fatal?

Thanks in Advance

chulett · Post by **chulett** » Thu Dec 18, 2008 11:09 am

I wouldn't worry about the 'deprecated' message, sounds like your problem is the job is not a multi-instance job and you are trying to start it while it is already running.

snt_ds · Post by **snt_ds** » Thu Dec 18, 2008 11:33 am

Thanks Chulett for your reply.

Job is in multiinstance which is called multiple times in nonmultiinstance
sequence job.

The same job is working fine in DEV and QA but failing in preprod.

Is this has anything to do with complier options.Thanks.

chulett · Post by **chulett** » Thu Dec 18, 2008 11:57 am

No. That "99" says it is not in the right state, i.e. the job has to be compiled and "not running". Double-check your logs, I'm still betting something is calling it while it is already running.

snt_ds · Post by **snt_ds** » Thu Dec 18, 2008 3:06 pm

Hi chulett,

The individual job is a multiinstance job and each time a different invocation id is passed from sequence.

There is nothing descriptive in the log other than

EDMOraDSErrorLog.REJ_ERR_PACE_POS_COLUMN_NOT_DERIVED_MFACTBOS_ERRMSG has finished, status = 99 (Not running)

Strange thing is that sometimes sequence will complete successfully.Most
of the time it fails.

Is there any problem if job runs on four node?

Thanks for time.

chulett · Post by **chulett** » Thu Dec 18, 2008 3:13 pm

Wait... so is the job actually starting and processing some rows before it ends with that message? I thought it was failing to start but a closer reading of the message implies it was running and then 'finished' with that status.

If so, then I'm barking up the wrong tree.

snt_ds · Post by **snt_ds** » Thu Dec 18, 2008 3:37 pm

Thanks for your reply chulett.

I couldn't read your entire message as i am not a premium member now.

I came accross a post in dsxchange which has a suggession below regarding the same issue.

Is Log Auto-purging enabled for either the Project or Jobs ?
If so, please disable and retest. If this solves your problem then there is a patch that you can request.

I disabled auto purging in my project which solved this issue.But i dont know anything about the patch to apply for?

My jobs are being migrated to ds 8.0.1 from 7.5.1.There is no problem
running this in old version.

Thanks for all your suggessions.

chulett · Post by **chulett** » Thu Dec 18, 2008 3:48 pm

Ask whomever wrote that there was a patch for the patch number. Post the question in their thread or explain the issue to your support provider and let them figure out what patch is applicable.