CA ADS Application Compiler (ADSA) › Application Compiler Session › Invoking the Application Compiler

Invoking the Application Compiler

The application developer can invoke the application compiler from any of the three ways described below.

From CA IDMS/DC or DC/UCF

By specifying the appropriate CA IDMS/DC or DC/UCF task code, the application developer can invoke the application compiler. Task codes are defined at system generation and can vary from site to site. The default task code for the application compiler is ADSA.

Note: To use the application compiler under the transfer control facility (TCF), specify ADSAT, the TCF version of the application compiler task code. The TCF task code for the dialog compiler is ADSCT and for the mapping facility is MAPCT.

When invoked, the application compiler displays a blank Main Menu screen on which the application developer can begin a new session or resume a suspended session.

From Another TCF Task

By specifying the appropriate CA IDMS/DC or DC/UCF task code in conjunction with the SWITCH command from another task executing under the transfer control facility, the application developer can invoke the application compiler.

If a new session is requested, the application compiler displays a blank Main Menu screen on which the application developer can begin a new session or resume a suspended session.

If an old session is requested, the application compiler resumes its most recently suspended session under the transfer control facility.

From the TCF Selection Screen

The application compiler can be invoked by keying any nonblank character, except the underscore (_), next to the appropriate task code or descriptor, as follows:

• Keying a nonblank character next to the appropriate task code invokes the application compiler. A blank Main Menu screen on which the application developer can begin a new session or resume a suspended session is displayed.
• Keying a nonblank character next to the descriptor of a suspended application compiler session invokes the application compiler and resumes the suspended session at the Main Menu screen. The descriptor consists of the appropriate task code, the application name, and the application version number.

The transfer control facility enables the application developer to transfer from one CA IDMS/DC or DC/UCF task to another. For example, the application developer can transfer between the application compiler, IDD, MAPC, and the dialog compiler. When control is transferred from a task, the current session of that task is suspended, if necessary. A task can have several suspended sessions.

Note: In a multiple dictionary environment, be sure to begin the application compiler session in the correct dictionary. The dictionary name can be specified in the Dictionary name field on the Main Menu screen. For more information about the transfer control facility, see the CA IDMS Common Facilities Guide.

TCF Selection Screen

Sample selections on the transfer control facility Selection screen are shown below:

                                CA, INC.
     TRANSFER CONTROL FACILITY               *** SELECTION SCREEN ***



 _ SUSPEND TCF SESSION   (PF9)           DBNAME..:           DBNODE..:
 _ TERMINATE TCF SESSION (PF3)           DICTNAME: TSTDICT   DICTNODE:

          *TCF TASKCODES*                           *SUSPENDED SESSIONS*
 SELECT ONE TO START A NEW SESSION          SELECT ONE TO RESUME AN OLD SESSION
                                                   TASKCODE        DESCRIPTOR
 _ TCF                                            _ADSCT           MPKDIA1 0001
 _ SYSGENT    SYSGEN COMPILER                     _ADSAT           MPKAPP1  001
 _ MAPCT      MAP DEFINITION                      _ADSAT           MPKAPP1  002
 _ ADSCT      DIALOG GENERATOR                    _ADSCT           MPKDIA2 0001
 X ADSAT      APPLICATION GENERATOR
 _ ASF
 _ ASFT
 _ IDDT       IDD COMMAND MODE
 _ SSCT       SUBSCHEMA COMPILER
 _ SCHEMAT    SCHEMA COMPILER
 _ IDDMT      IDD MENU MODE
 _ OLQ        OLQ COMMAND MODE
 _ OLQT       OLQ COMMAND MODE