Creating and managing jobs in a project

Creating jobs automatically

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 the job settings for metadata import or metadata enrichment jobs from the Job's page. You can only do this from the project's Assets page.

In Cloud Pak for Data, jobs are created for:

• 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 Creating a metadata import job.

• 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 Relationship Analysis for Metadata Enrichment Assets when the metadata enrichment is created
  • A job for relationship analysis with the job type Relationship Analysis for Metadata Enrichment Assets when the metadata enrichment is created
  • A publish job with the job type Publish Metadata Enrichment Assets when you publish metadata enrichment results

  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 for files in a project with deprecated Git integration

You can't create jobs directly in JupyterLab or RStudio. To create jobs for Notebooks or scripts that are created in JupyterLab or RStudio in a project with deprecated Git integration, you must push the files from the IDE to the Git repository associated with your project and then sync the repository files with the project. Any Notebooks, scripts, or RShiny apps that are pushed to a GIT repository with a size of zero bytes are considered invalid and are not synced with the project.

You can create jobs after you have synced your GIT files to create project assets:

• From the Notebook viewer for Notebooks. See Creating jobs in the Notebook viewer.
• From the project Assets page for Notebooks and scripts. See Creating jobs for the Assets page.

Creating jobs from the Assets page

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

In a project with default Git integration, you need to create a code-based job for non-listed assets by selecting a file from your local Git branch. See Creating jobs for code files.

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 Create 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.

   Note: Scheduling jobs within git-based projects is unsupported.

   If you define a start day and time without selecting Repeat, the job will run exactly one time at the specified day and time. If you select Repeat, the job will run at the timestamp indicated in the Repeat section between the start and end dates of the schedule.

   You can't change the time zone; the schedule uses your web browser's time zone setting. 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.

6. Optionally set 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 from the job's action bar. You can start a scheduled job based on the schedule and on demand.
• Delete the job by clicking 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 SPSS Modeler
• 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 code-based jobs
• Creating jobs for Pipelines

Parent topic: Working in projects