Task Center script type | Job Manager job type |
---|---|
DB2 command script | DB2 CLP script |
OS command script | Shell/Executable script |
Task type | Restrictions |
---|---|
MVS shell script | Not supported. |
Grouping | Not supported. |
OS command script | The script interpreters and command execution parameters are not supported. The default script interpreter is used instead. |
DB2 command script | Supported. |
Schedule type | Restrictions |
---|---|
Weekly | Only schedules set for 1 to 4 weeks are supported. |
Monthly | Only schedules set for 1 month and schedules set to a specific date or last date are supported. |
Yearly | Only schedules set for 1 year are supported. |
Expired (that is, schedules with a starting or ending time that is earlier than the current time) | Expired schedules will be imported but marked as inactive. |
Task action | Restrictions |
---|---|
Run task | Only the first Run task task action associated with the task will be imported. |
Enable schedule of | Not supported. |
Disable schedule of | Not supported. |
Delete this task | Not supported. |
To import tasks from the DB2 Task Center:
If the task is imported successfully, a new job is created for the imported task in the job manager with a job name that is identical to the task name of the imported task. The job name is prefixed by "TC_toolsdb_" where toolsdb is the name of the DB2 tools database. The script of the imported task is not modified.
If the imported task is associated with a schedule in the Task Center, a new schedule is created for the corresponding job by the job manager and the tools catalog database is associated with the schedule by default. The schedule date format for the imported task is converted to the job manager schedule format.
If the job that was generated from the imported task is not associated with a schedule, create a schedule and add the job to the schedule.