Task Load

Purpose

The Task load process is used to populate the Code Pipeline repository with Tasks and Components. Tasks can be loaded at any level (even production). It is the responsibility of the caller to make sure that Task information loaded reflects the actual location and status of the physical components.

Description

The Task load process consists of one TASK LOAD call, zero or more TASK LOADPART calls, and one TASK LOADEND call. The information for the Task is not committed to the repository until a successful TASK LOADEND call is made.

Version Sequence Issues

Loading Tasks through the ECI has consequences for versioning, in that these tasks are inherently not based upon any existing versions in the repository.

ECI loaded tasks are considered to be mutable (for example, Code Pipeline cannot guarantee the integrity of the task with relation to other tasks), and so the strict versioning sequence rules do not apply.

Example

This example adds two tasks to an existing assignment. You must review and ensure that:

• The STEPLIB DD is only required if the runtime configuration authorized LOADLIB, default name ISPW.AUTHLINK, is not in the LINKLIST.
• The runtime JCL must be set to an appropriate value.
• The keyword values must be set appropriately.