CA ADS Runtime System

CA ADS applications are executed using the CA ADS runtime system. To execute a CA ADS Batch application, initiate the CA ADS Batch runtime system.
idmscu19
CA ADS applications are executed using the CA ADS runtime system. To execute a CA ADS Batch application, initiate the CA ADS Batch runtime system.
For more information about the CA ADS Batch runtime system, see the
CA ADS Batch Using section
.
This article describes the following information:
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.
For more information on the system generation TASK statement, see the
CA IDMS System Generation section
.
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.
How to Start a CA ADS Application
After signing on to DC/UCF, the user can initiate the CA ADS runtime system by responding to the ENTER NEXT TASK CODE prompt, as follows:
  • By entering the task code that directly initiates an application
  • By entering the task code specified in the ADSTASK clause of the system generation ADSO statement, followed either by a task code defined for an application or by the name of a mainline dialog
  • By entering only the task code specified in the ADSTASK clause of the system generation ADSO statement
Task Application Table
In either of the first two cases, the CA ADS runtime system responds by checking the Task Application Table (TAT) for the specified task code. If the specified task code is in the TAT, the runtime system begins execution of the application with the function associated with the task code or with a signon function if one is specified for the application. The TAT is updated by the application compiler by using information entered on the Task Codes screen.
The TAT table can also be updated online using ADSOTATU, or in batch using ADSOBTAT.
If the specified task code is not in the TAT, the runtime system checks for a mainline dialog whose name matches the task code. If the dialog exists, the runtime system begins execution of the dialog. If the dialog does not exist, the runtime system terminates abnormally.
If the user enters only the task code specified in the ADSTASK clause of the system generation ADSO statement, the runtime system responds by displaying the Dialog Selection screen.
The Dialog Selection screen displays a menu of the mainline dialogs available to the user. The user selects a dialog, and the runtime system begins execution of the dialog.
Dialog Selection Screen
CA ADS RELEASE nn.n                                              PAGE:   1                  DIALOG SELECTION FOR USER: ENTER DIALOG NAME:             OR SELECT ONE BELOW _ ADSA                _ ADSOTATU                _ ASFADSGD              _ ASFOOAKD - OLQ                 _ RQERDQ PA1 - PAGE FORWARD PA2 - PAGE BACK CLEAR - EXIT CA ADS
The user initiates a dialog from the Dialog Selection screen by entering a nonblank character in the response field corresponding to the applicable dialog, or by entering the name of the dialog in response to the ENTER DIALOG NAME prompt.
Initiating the CA ADS Runtime System
Syntax and syntax rules for the statement used to initiate the CA ADS runtime system are shown below.
Use these statements in response to the DC/UCF prompt:
ENTER NEXT TASK CODE
Syntax
►►─┬─ 
ads-task-code
 ───────────────────────────────────────────────────────────►─    │    ├─ 
ads-task-code
 ─┬┬────────────────────────────┬─┬──────────────────┬──────    │                 │└─┬───────────┬ 
dialog-name
 ─┤ └─ NODe=
node-name
 ─┘    │                 │  └─ DIAlog= ─┘              │    │                 └─ 
application-task-code
 ─────┘    │    └─ 
idms-dc/ucf-task-code
 ─┬──────────────────┬──────────────────────────────                              └─ NODe=
node-name
 ─┘ ─►────────────────────────────────────────────────────────────────────┬───────►◄   ────┬────────────────────────┬───────┬─────────────────────┬────────┤       └─ DBName=
database-name
 ─┘       └─ TRACE= ──┬─ ALL ─┬─┘        │                                                    └─ CTL ─┘          │                                                                       │   ────┬────────────────────────┬──────────────────────────────────────┘       └─ DBName=
database-name
 ─┘
Parameters
  • ads-task-code
    Specifies the task code defined in the ADSTASK clause of the system generation ADSO statement.
    Ads-task-code
    must be defined in a system generation TASK statement to invoke program ADSORUN1. The default task code is ADS.
  • DIAlog=
    dialog-name
    Specifies the name of a mainline dialog to begin execution as the first dialog in an application.
    There is no space between the keyword DIAlog and = or between = and
    dialog-name
    .
  • application-task-code
    Specifies a task code defined for an application by means of the Task Codes screen.
    If no signon function is specified, the function associated with the task code begins execution as the first function in the application. If a signon function is specified, the function associated with the task code begins execution after an acceptable signon is entered.
  • idms-dc/ucf-task-code
    Specifies either a task code defined for an application by means of the Task Codes screen or the name of a mainline dialog.
    Idms-dc/ucf-task-code
    must be defined in a system generation TASK statement to invoke program ADSORUN1.
  • NODe=
    node-name
    Specifies the node that controls the data dictionary in which the definitions and load modules for the requested application are stored.
    Node-name
    must be defined at DC/UCF system generation.
    There is no space between the keyword NODe and = or between = and
    node-name
    .
  • DBName=
    database-name
    Specifies the database accessed by the application.
    Database-name
    must be defined at system generation.
    There is no space between the keyword DBName and = or between = and
    database-name
    .
  • TRACE=
    Specifies that the CA ADS trace facility is to be used for the application.
    There is no space between the keyword TRACE and = or between = and ALL or CTL.
Example 1: Specifying a Task Code that Directly Initiates an Application
The following statement initiates the run-time system with the system-generated task code REPORTS. Because REPORTS is defined in the TAT and no signon function is specified for the application that REPORTS initiates, the runtime system begins execution of the function associated with REPORTS.
REPORTS
Example 2: Specifying the Run-Time System Task Code Without an Application Task Code
The following statement initiates the run-time system with the default task code ADS. The system displays the Dialog Selection screen.
ADS
Example 3: Specifying the Run-Time System Task Code with an Application Task Code
The following statement initiates the run-time system with the default task code ADS and specifies the application task code TESTAPPL:
ADS TESTAPPL DBNAME=TESTDB
The DBNAME clause is included to specify that the database to be accessed by the application is TESTDB. If the clause were not included in this statement, the application would access the system's current database or the dbname set by a DCUF SET DBNAME command.
Runtime System Initiating Statement
►►─┬─ 
ads-task-code
 ───────────────────────────────────────────────────────────►─    │    ├─ 
ads-task-code
 ─┬┬────────────────────────────┬─┬──────────────────┬──────    │                 │└─┬───────────┬─
dialog-name
 ─┤ └─ NODe=
node-name
 ─┘    │                 │  └─ DIAlog= ─┘              │    │                 └─ 
application-task-code
 ─────┘    │    └─ 
idms-dc/ucf-task-code
 ─┬──────────────────┬──────────────────────────────                              └─ NODe=
node-name
 ─┘ ─►────────────────────────────────────────────────────────────────────┬───────►◄   ────┬────────────────────────┬───────┬─────────────────────┬────────┤       └─ DBName=
database-name
 ─┘       └─ TRACE= ──┬──ALL ─┬─┘        │                                                    └──CTL ─┘          │                                                                       │   ────┬────────────────────────┬──────────────────────────────────────┘       └─ DBName=
database-name
 ─┘