|
Possible Causes |
Possible Solutions |
|---|---|
|
System resources fully used |
N/A |
|
nodename.LOG > 500 blocks |
Use SCHEDULE SET DEBUG OFF or SCHEDULE STOP |
|
History log > 2500 blocks |
Use SCHEDULE CLOSE LOG [/SUMMARIZE] |
|
Database fragmented; deletes > 200 |
Use SCHEDULE OPTIMIZE DATABASE to compress database |
|
Many interface requests at the same time |
N/A |
|
Job Management Manager default transition |
N/A |
|
New scheduler joining cluster |
N/A |
|
NSCHED priority has been lowered |
See system manager |
|
NULL keys are not present in the jobs database |
Shutdown JM Manager cluster wide and execute the DCL command $ CONVERT/FDL=NSCHED$DATA:VSS_STANDARD.FDL NSCHED$DATA:VSS.DAT NSCHED$DATA:VSS.DAT |
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |