If any addition, change, or deletion of job nets or groups are processed when the remaining file system space is insufficient, the schedule file for the user may be corrupted. If the schedule pattern information has been written at this time, it may also be lost. Also, output data and history information for jobs in operation cannot be written.
In such cases, terminate the Jobscheduler operation, carry out restoration of the following information files and take the appropriate action to ensure that a larger amount of file space will be available.
Restoring schedule files
For recovery of the schedule information file, see the "A.3.5 Restoring Schedule Files" section.
Restoring system information, schedule pattern information and project information files
The Jobscheduler carries out backup on system information files (sysfile.sys), schedule pattern information files (db_calendar_ex.default) and project information files ("name of project".jsp) in the following timings.
When a Jobscheduler service starts
The backup of information will be created in the jobschbackup directory under the database directory.
If a file space insufficiency has occurred while updating information, copy the file from the jobschbackup directory to the database directory.
Deleting unnecessary files from the backup directory
Files in the jobschbackup directory will never be deleted. Consequently, even if all schedule information for a project is deleted and schedule files for that project no longer exist in the database directory, these schedule files for that project still remain in the jobschbackup directory. Therefore, the system administrator should check the contents of the jobschbackup directory regularly, and delete schedule files for projects that are no longer using the Jobscheduler if any.
Deleting unnecessary files from the work directory
The files contained in the work directory in the database directory are work files that the Jobscheduler uses on a temporary basis. Normally, these files are deleted when they are no longer needed. However, the work files might remain if a job net is cancelled or delete operation is not performed in the corresponding exit program. Therefore, the system administrator should check the contents of the work directory regularly and delete work files with old dates.
When Delete job output file is selected in the Output File sheet of the Define Jobscheduler Startup Parameters window, all files under the work directory will be deleted at the time of Jobscheduler service startup.
Moving the database directory [Windows version]
The default database directory is MpWalker.JM\mpjobsch\jobdb (MpWalker.JM\mpjobsch\jobdb1-9 during subsystem operations) under the Systemwalker Operation Manager installation directory. The database directory can be changed as necessary. If the disk space is insufficient, move the database directory to a different drive. When operating subsystems, specify a different directory for each subsystem. Make the database directory settings using the Database sheet of the Define Jobscheduler Startup Parameters window.
Deleting the storage file of abended job nets [UNIX version]
Every time a job net is abnormally terminated, the job net information is added to the abended job net storage file (jobnetabend.log) under the database directory. Since these files are never deleted automatically, it should be regularly checked and deleted.
