Known Problems and Solutions in Cadence Job Monitor
This document describes the known issues with Cadence® Job Monitor and suggests the workarounds for these issues. Each issue is identified by a Cadence Change Request (CCR) number.
Related Topics
CCR 72452: cdsqmgr should give warning if hostname is invalid in config
Problem: cdsqmanager does not display a warning if there is an invalid host name in the configuration file. However, it ignores any invalid hosts.
There is no workaround available.
CCR 71543: More clear message when cannot find current working dir
Problem: When the job manager cannot find the current working directory, it executes the job using a temporary directory. It also reports the following error in the email sent to the requestor of the job:
PS: Failed to open given output file; stdout output included in this report
PS: Failed to open given error file; stderr output included in this report
even though no output or error file was specified for the job.
Solution: None. The job is executed as expected. You can ignore the error message.
CCR 37670: Job Monitor does not accept 00 in min as start time
Problem: In the Run form, if you type 00 in the minute part of the Start Time field, when you click OK, you get the following error:
Invalid start time specified.
Correct the problem and try again.
Solution: To specify 00 minutes, instead of typing in the minutes, select the minute part of the field and use the scroll bar to set the minutes.
CCR 25677: Stack trace on NT when selected an empty month
Problem: In the Run form, the Start Date field erroneously lets you select an empty month, (by selecting the empty item after Dec). When this happens, a stack trace is displayed in the window in which you started the job monitor.
Solution: None. This is only a display problem. The month defaults to the current month and the job runs as expected.
CCR 6914: Job Properties cut off when description is too long
Description: If the description in the Job Properties window is too long, the complete description is not displayed.
There is no workaround available.
Return to top