Failures scheduling background monitoring

[Michael Pokraka]

Mark,
The workitem 00000000 bit sounds suspicious. Have you tried scheduling
it by hand? I would suggest poking around SM37 to get it to run at least
one - it should fix up any oddities in SWWDHMIN.
Also, have a look at table SWWWIDH for any 'funny' entries. It contains
any due deadlines, as I understand it, this is where case-specific
monitoring will get it's next runtime from.
HTH
Cheers
Mike
 
On Wed, Jan 08, 2003 at 10:05:08AM -0000, Pyc, Mark wrote:
> G'day WFers,
>
> I hoping someone has some insights into error messages returned when trying
> to schedule the deadline monitoring job in 46C.
>
> When selecting the "Schedule backgr. job for case-specific deadline
> monitoring" option the following message is returned:
> Message no. WL 864
> Work item 000000000000: Background job RSWWDHEX cannot be scheduled (error
> 13)
> The specified error number should indicate possible reasons for the error.
> It is possible that the system is in an inconsistent state. The scheduled
> start of the specified background job must be compared with the minimum
> date/time of all work items in table SWWDHMIN. It may be necessary to delete
> the scheduled background job by hand and reschedule it by calling report
> RSWWDHEX.
>
> When selecting the "Optional: Schedule permanent deadline monitoring" option
> the following message is returned:
> Message no. WL 818
> Table SWWDHMIN cannot be written
>
> Debugging, searches of OSS and the archives have provided no real joy. Both
> messages complain about SWWDHMIN and ddic tools reveal nothing unusual about
> this table. No authorization failures are reported. I will report this to
> OSS as well, but I thought I'd try this avenue as well in case someone else
> has hit it...
>
> Many thanks,
> Mark