CA ADS Runtime System › Initiating the CA ADS Runtime System › How to Define Runtime Tasks

How to Define Runtime Tasks

Tasks that initiate the CA ADS runtime system are defined at CA IDMS/DC or DC/UCF (DC/UCF) system generation to activate program ADSORUN1. The task codes are specified by means of the system generation TASK statement and are associated with CA ADS in one of the following ways:

• By means of the ADSTASK clause of the system generation ADSO statement.
• By means of the application compiler Task Codes screen. At runtime, a task code defined on the Task Codes screen directly initiates the application for which it is defined.

  A task code specified on the Task Codes screen can be used to initiate the runtime system only if one of the following conditions is met:

  • If the task code specified on the Task Codes screen is also defined in the system generation TASK statement
  • If the default ADSTASK task code (ADS) is entered in conjunction with the task code specification on the Task Codes screen
• By means of a task code invoking a mainline dialog (provided the task code invokes ADSORUN1).

  At runtime, the named dialog is directly initiated as the first dialog in an application consisting of a series of dialogs.

Note: For more information on the system generation TASK statement, see the CA IDMS System Generation Guide.

When the user initiates a CA ADS application, the runtime system loads the required load modules into storage and sets up control blocks and record buffers for the application.

More information:

CA ADS Application Compiler (ADSA)