ds_pending_job

Hi Listers

Wanted some information for ds_pending_job -

What do the various values in field job_error stand for. Manual which we have states the following

JOB_ERROR : indicates what is the error. It is translated when read to a format more readable for a human being. (a string instead of an integer) Example : The value 4 is translated to ëError executing scriptí…

Does any of you have the translation of all the values to errors ? It will be helpful.

Thanks in advance

Regards

Naveen Phutane
Tata Infotech Limited
Ph : 555 0450 / 6
Fax : 555 0459
Email : naveen.phutane@tatainfotech.com


Listserv Archives (BOB member since 2002-06-25)

Those should all be listed in the errors pdf files that come with BO… if you don’t have that, you can get it off their web site.

Good Luck,
Brent


Listserv Archives (BOB member since 2002-06-25)

I’m just a little confused about the documentation on the DS_PENDING_JOB table. Specifically the DAY_TIMING field. We have a job that is scheduled to run Weekly every Tuesday at 7:00 AM in looking at the repository it is given a value of 2068368. This translates to a binary of 111111000111110010000. Using the documentation given by Business Objects. The fourth bit (starting from the right at bit 0) is correctly displaying the Tuesday position. However bits 7 through 20 do not make any since to me at all.


Listserv Archives (BOB member since 2002-06-25)

Hi

We get the Day_Timing field in DS_PENDING_JOB table to make sense to us by joining it the table DAY_TIMING using the id’s, for example

select
DECODE(DAY_TIMING.DAY_TIMING, NULL, ‘To Be Defined’, DAY_TIMING.DAY_TIMING) DAY_TIMING
FROM
DS_PENDING_JOB,
DAY_TIMING
WHERE
DS_PENDING_JOB.DAY_TIMING=DAY_TIMING.ID(+)

Hope this helps.

Best Regards
Pushpanjali

I’m just a little confused about the documentation on the DS_PENDING_JOB table. Specifically the DAY_TIMING field. We have a job that is scheduled to run Weekly every Tuesday at 7:00 AM in looking at the repository it is given a value of 2068368. This translates to a binary of 111111000111110010000. Using the documentation given by Business Objects. The fourth bit (starting from the right at bit 0) is correctly displaying the Tuesday position. However bits 7 through 20 do not make any since to me at all.


Listserv Archives (BOB member since 2002-06-25)

On Wed, 5 Dec 2001 13:04:23 +0100, Rao, Pushpanjali (IndSys, GEPC) Pushpanjali.Rao@GEPC.GE.COM wrote:

Hi

We get the Day_Timing field in DS_PENDING_JOB table to make sense to us by joining it the table DAY_TIMING using the id’s, for example

select
DECODE(DAY_TIMING.DAY_TIMING, NULL, ‘To Be Defined’, DAY_TIMING.DAY_TIMING) DAY_TIMING
FROM
DS_PENDING_JOB,
DAY_TIMING
WHERE
DS_PENDING_JOB.DAY_TIMING=DAY_TIMING.ID(+)

Hope this helps.

Best Regards
Pushpanjali

I’m just a little confused about the documentation on the DS_PENDING_JOB table. Specifically the DAY_TIMING field. We have a job that is scheduled to run Weekly every Tuesday at 7:00 AM in looking at the repository it is given a value of 2068368. This translates to a binary of 111111000111110010000. Using the documentation given by Business Objects. The fourth bit (starting from the right at bit 0) is correctly displaying the Tuesday position. However bits 7 through 20 do not make any since to me at all.

We do not have a DAY_TIMING Table in our repository. We do have a DAY_TIMING Field within the DS_PENDING_JOB Table. What version of Business Objects are you using? We are at 5.1.2 running on HPUNIX/Oracle 8.1.6.x. What we are trying to accomplish here is to be able to display in a BO report what and when reports are scheduled to run on BCA. The documentation provided on the Business Objects Installation CD (1) under the Freeware directory does explain the DAY_TIMING Field. It does not seem to match what we are seeing in our repository.


Listserv Archives (BOB member since 2002-06-25)

(to_date(‘15/12/1970 00:00:00’, ‘DD/MM/YYYY HH24:MI:SS’) +(TABLE.COLUMN / (60 * 60 * 24))) This is the conversion from UTC (Universal Time convention) format.


bmaly (BOB member since 2003-03-17)