Creating and managing jobs in a project

Automatically creating jobs

Some jobs are created automatically at the time the asset is created in a project. These jobs are listed on the Jobs page of the project. You can view the job run details, change job settings, run the job manually, and delete the job from the Jobs page. Note that you can't edit job settings for a metadata import or metadata enrichment job from the Jobs page. You can only do this from the project's Assets page.

Jobs are created in the following situations:

• DataStage flows. See Creating jobs in DataStage.

• DataStage flows for data quality rules. See Creating jobs for running data quality rules.

• Metadata import assets. See Metadata import jobs.

• Metadata enrichment assets. See Creating a metadata enrichment job.

  In addition, the following jobs are created automatically:

  • A job for primary key analysis with the job type Key Analysis for Metadata Enrichment Assets on the first request for an advanced primary key or relationship analysis
  • A job for relationship analysis with the job type Key Analysis for Metadata Enrichment Assets on the first request for an advanced primary key or relationship analysis
  • A publish job with the job type Publish Metadata Enrichment Assets when you publish metadata enrichment results for the first time

  You can view the job run details or delete the jobs but you cannot change any job settings or run such jobs manually.

Creating jobs from the Assets page

You can create a job to run an asset from the project's Assets page.

Required permissions

You must have an Editor or Admin role in the project.

To create jobs for a listed asset from the Assets page of a project:

1. Select the asset from the section for your asset type and choose New job from the Menu icon with the lists of options at the end of the table row.

2. Define the job details by entering a name and a description (optional).

3. If you can select Setting, specify the settings that you want for the job.

4. If you can select Configure, choose an environment runtime for the job. Depending on the asset type, you can optionally configure more settings, for example environment variables or script arguments.

   To avoid accumulating too many finished job runs and job run artifacts, set how long to retain finished job runs and job run artifacts like logs or notebook results. You can either select the number of days to retain the job runs or the last number of job runs to keep.

5. On the Schedule page, you can optionally add a one-time or repeating schedule.

   If you select the Repeat option and unit of Minutes with the value of n, the job runs at the start of the hour, and then at every multiple of n. For example, if you specify a value of 11 it will run at 0, 11, 22, 33, 44 and 55 minutes of each hour.

   If you also select the Start of Schedule option, the job starts to run at the first multiple of n of the hour that occurs after the time that you provide in the Start Time field. For example, if you enter 10:24 for the Start of Time value, and you select Repeat and set the job to repeat every 14 minutes, then your job will run at 10:42, 10:56, 11:00, 11:14. 11:28, 11:42, 11:56, and so on.

   You can't change the time zone; you must set your job schedule in your web browser's time zone. The schedule will be translated to the time zone of the compute node where your job runs.

   If you exclude certain weekdays, the job might not run as you would expect. The reason might be due to a discrepancy between the time zone of the user who creates the schedule, and the time zone of the compute node where the job runs.

   Note: Your scheduled job can appear differently if your web browser’s time zone is set to your local time zone following Daylight Savings Time (DST). For example, your scheduled job appears at 3:00PM Eastern Standard Time Zone (EST) daily corresponding to 8:00PM Coordinated Universal Time (UTC). When your local time zone changes to Eastern Daylight Time Zone (EDT), your scheduled job continues to run at 8:00PM (UTC) which will now appear as 4:00PM (EDT) daily.
   
   
   An API key is generated when you create a scheduled job, and future runs will use this API key. If you didn't create a scheduled job but choose to modify one, an API key is generated for you when you modify the job and future runs will use this API key.

6. (Optional): Select to see notifications for the job. You can select the type of alerts to receive.

7. Review the job settings. Then, create the job and run it immediately, or create the job and run it later.

Managing jobs

You can view all of the jobs that exist for your project from the project's Jobs page. With Admin or Editor role for the project, you can view and edit the job details. You can run jobs manually and you can delete jobs. With Viewer role for the project, you can only view the job details. You can't run or delete jobs with Viewer role.

To view the details of a specific job, click the job. From the job's details page, you can:

• View the runs for that job and the status of each run. If a run failed, you can select the run and view the log tail or download the entire log file to help you troubleshoot the run. A failed run might be related to a temporary connection or environment problem. Try running the job again. If the job still fails, you can send the log to Customer Support.
• Edit job settings by clicking Edit job, for example to change schedule settings or to pick another environment template.
• Run the job manually by clicking the Run icon from the job's action bar. You can start a scheduled job based on the schedule and on demand.
• Delete the job by clicking the Delete from the job's action bar.

Learn more

• Creating jobs in Data Refinery
• Creating jobs in DataStage
• Creating jobs with Data Privacy
• Creating jobs in IBM Match 360
• Creating jobs in the Notebook editor or Notebook viewer
• Creating jobs for running data quality rules
• Creating a metadata import job
• Creating a metadata enrichment job
• Creating jobs for Pipelines

Parent topic: Working in projects