In a message dated 00-01-19 12:06:57 EST, you write:
We have a document which was scheduled in DAS last year.
Usually DAS schedules jobs for a period of 1 year. So now after 1 year the document shows an
‘EXPIRED’ status.
When I queried against the ds_pending_jobs table in the repository, it
gives
a job_status = ‘1006’.
Is there a way to schedule the same document for 1 more year ? We do not have the document on our desktops…nor is it stored as a shared document in the
repository. We can only find its traces in obj_m_documnets,
obj_x_documents
and ds_pending_jobs.
Hmmmm…
I had to do some experimenting on my own with this one. It appears that you cannot retrieve the document once it has expired. You cannot do a “Run Now”. You can change the expiration date, but it does not change the status of the document. It truly appears that if you do not have a separate copy of the document, you are stuck once it expires.
Have you talked to your IT folks about looking for an old copy of the document on a system backup? The document had to be created at some point…
Who “owns” the document? Why don’t they have an old copy of the document that was processed by DAS at some earlier date?
Who was on the distribution list for the document? Is there a chance that there is still a document waiting to be “retrieved from DAS” under someone’s BusObj user ID?
If not, here is a suggestion:
Be sure to test this idea in a second repository before doing anything on your production system. BusObj certainly does not want you updating the repository directly! This solution does appear to work, but my repository is sitting on my laptop and not being used for any production systems.
Proceed at your own risk. (I have to say that, it’s in my contract. )
First, get the document ID from the expired job. This can be found in the DS_PENDING_JOB table.
Next, submit a new document with the schedule / expiration date that you want for the expired document. Note the BATCH_ID for the new job.
Third, update the repository record for the new job with the document ID from the expired job. That should link the old document with the new schedule. The idea here is to use a “dummy” document to get a new schedule, and then update the new schedule record with the old document ID. That does, however, potentially leave an extra document (the new one) floating around in the repository.
Finally, once the document runs to completion retrieve it from the repository and store it offline (out of the repository) for future use!
Regards,
Dave Rathbun
Integra Solutions
www.islink.com
Listserv Archives (BOB member since 2002-06-25)