Adding an application

Procedure to add a new application structure (including responses, functions, and task codes).

To define dialogs, maps, and process modules, see descriptions of ADSC, MAPC, and IDD later in this appendix.

Enter basic information about the application on a Main Menu screen:

• An application name
• A dictionary name/node (where applicable)

Select the Add activity from the action bar to register the application in the dictionary and check it out (reserve it) to the programmer.

Add required components on appropriate ADSA screens:

• Add responses and functions by using the Response/Function List screen as described under "Adding Responses and Functions" later in this table.
• Further define responses by using the Response Definition screen, as described in "Adding a Response" later in this table.
• Further define functions by using the appropriate Function Definition screen, as described in "Adding a Function" later in this table.
• Add task codes by using the Task Codes screen, as described in "Adding a Task Code" later in this table.

Optionally make additional specifications on other ADSA screens.

For more information on available ADSA screens, see the CA ADS Reference Guide.

Create a load module for the application by selecting the Compile activity from the action bar on the Main Menu.

For an example of using ADSA to add an application, see Chapter 8, "Defining an Application Structure Using ADSA".

Modifying an application

Procedure to modify an existing application structure (including responses, functions, and task codes).

This procedure cannot be used to modify an application name1.

To modify dialogs, maps, and process modules, see descriptions of ADSC, MAPC, and IDD later in this appendix.

Display the application definition (if not already displayed) by entering the following information on the application Main Menu screen:

• The application's name
• A dictionary name/node (when applicable)

If the application has been released (after having been added), check the application out through the Check out option under the Modify activity on the action bar.

Modify application specifications, as necessary, on appropriate ADSA screens:

• Add and select responses and functions by using the Response/Function List screen, as described later in this table.
• Add, modify, or delete responses by using the Response Definition screen, as described later in this table.
• Add, modify, or delete functions by using the Function Definition screens, as described later in this table.
• Add, modify, or delete task codes by using the Task Codes screen, as described later in this table.

Recompile the application load module by selecting the Compile activity from the action bar on the Main Menu.

For an example of using ADSA to modify an application, see chapter 10.Modifying the Application Structure Using ADSA.

Deleting an application

Procedure to delete an application structure (including responses, functions, and task codes).

To delete dialogs, maps, and process modules, see descriptions of ADSC, MAPC, and IDD later in this appendix.

Enter the following information on the application Main Menuscreen:

• The application name
• A dictionary name/node (when applicable)

Choose the Delete application option from the Delete activity on the action bar on the Main Menu.

After you press [Enter], ADSA displays a confirmation window so that the request to delete the application can be confirmed or rescinded.

Confirm or reject the deletion.

For an example of using ADSA, see Chapter 8, "Defining an Application Structure Using ADSA".

Adding response and function relationships

Procedure to add an application response and function relationships to an application.

Do not confuse application responses with dialog response processes₂.

Display the Response/Function List screen by entering a 2 opposite the Screen prompt on the Main Menu.

Enter the following information on the Response/Function List screen:

• The response name
• An associated activity key (optional)
• The name of the function invoked by the response3
• The type of function (declaration, premap, response, default response)
• The program or dialog name
• A nonblank character to indicate which responses and functions need further definition

For an example of using ADSA to add responses and functions, see Steps 4 through 6 in Chapter 8, "Defining an Application Structure Using ADSA" of this manual.

Enhancing the response definition

Procedure to further define an application response to an application.

Do not confuse application responses with dialog response processes.

Select responses for further definition by entering a nonblank character next to the responses on the Response/Function List screen

Display the Response Definition screen by pressing [PF5] from the Response/Function List screen

Enter the following information on the Response Definition screen:

• The response type (local or global)
• The control command (optional) used to invoke the associated function

For an example of using ADSA to further define responses, see Steps 4 and 5 in Chapter 8, "Defining an Application Structure Using ADSA" of this manual.

Modifying a response

Procedure to modify an application response.

This procedure cannot be used to modify a response name4.

Do not confuse application responses with dialog response processes5.

Display the responses and functions on the Response/Function List screen.

Make any changes required.

Optionally select the response to be modified by placing a nonblank character next to the response and pressing [PF5] to access the Response Definition screen.

Modify any specifications on the Response Definition screen, including:

• The response type (global or local)
• The control command used to invoke the function

For an example of using ADSA to modify a response, see Steps 2 and 3 in Chapter 11, "Modifying the Application Structure Using ADSA".

Deleting a response

Procedure to delete an application response from an application.

Do not confuse application responses with dialog response processes6.

Display the responses and functions on the Response/Function List screen.

Select the response to be deleted by placing a nonblank character next to the response and pressing [PF5] to access the Response Definition screen.

Display the response definition (if not already displayed) on the Response Definition screen as described above in "Modifying a response" earlier in this table.

Place a nonblank character next to the Drop prompt

For an example of using the Response Definition screen, see "Step 5: Further define application responses" in Chapter 8, "Defining an Application Structure Using ADSA".

Enhancing the dialog function definition

Procedure to further define a dialog functions to an application7.

Display the responses and functions on the Response/Function List screen.

Select the function to be defined by placing a nonblank character next to the function and pressing [PF5].

Display the Function Definition (Dialog) screen by pressing [PF5] from the Response/Function List screen.

Enter the following information on the Function Definition screen:

• A description of the function
• Valid responses for this function.

For an example of using ADSA to further define functions see "Step 6: Further define application functions in Chapter 8, "Defining an Application Structure Using ADSA" of this manual.

Enhancing the menu function definition

Procedure to further define a menu function to an application.7

Display the responses and functions on the Response/Function List screen.

Select the menu function to be defined by placing a nonblank character next to the function and pressing [PF5].

Display the Function Definition (Menu) screen by pressing [PF5] from the Response/Function List screen.

Enter the following information on the Function Definition screen:

• A description of the function
• Specify heading text to be displayed on the runtime menu:

1. Enter the number of heading lines after the Heading lines prompt.
2. Enter the heading text in lines below the Heading line text prompt.

Identify the valid responses for this function.

• Display the second page of the Function Definition (Menu) screen by pressing [PF8] from page 1.
• Enter a nonblank character next to each response that is valid for the menu.

Customize the menu display for a menu function9:

• Optionally change the way in which responses are displayed on the runtime menu:

1. Optionally change the sequence of responses by typing new sequence numbers for the responses to be moved.
2. Optionally suppress the display of a valid response by entering zeros over the sequence number for the response; the response remains available from the menu even though it is not displayed.

   For an example of changing the response sequence for a menu function, see "Menu functions" in Chapter 8, "Defining an Application Structure Using ADSA".

For an example of using ADSA to further define functions see "Step 6: Further define application functions in Chapter 8, "Defining an Application Structure Using ADSA" of this manual.

Modifying a function

Procedure to modify an application function.

This procedure cannot be used to modify a function name10.

Display the responses and functions on the Response/Function List screen.

Make any changes required.

Optionally select the function to be further modified by placing a nonblank character next to the function and pressing [PF5] to access the Function Definition screen.

Modify any specifications on the Function Definition screen, including:

• Description
• Associated dialog
• Default response
• Valid responses

For an example of using ADSA to modify a function, see "Step 4: Modify the ADDDEP function" in Chapter 11, "Modifying the Application Structure Using ADSA".

Deleting a function

Procedure to delete a function and all responses that invoke that function.

Display the function definition (if not already displayed) on the Function Definition screen as described above in "Modifying a function" earlier in this table.

Place a nonblank character next to the Drop prompt

For an example of using the Function Definition screen, see "Step 6: Further define application functions" in Chapter 8, "Defining an Application Structure Using ADSA".

Adding a task code

Procedure to add an entry point to the application.

Display the Task Codes screen by selecting 5 from the Main Menu.

Add the task code:

• Enter a task code below the Task code heading
• Enter a function name below the corresponding Function heading.

For an example of using ADSA to define a task code, see "Step 7: Define a task code" in Chapter 8, "Defining an Application Structure Using ADSA".

Modifying a task code

Procedure to modify the name or entry-point function for an application.

Display the Task Codes screen by selecting 5 from the Main Menu.

Erase the task code from the screen by pressing the ERASE EOF key or typing spaces over the task code.

For an example of using the Task Codes screen, see "Step 7: Define a task code" in Chapter 8, "Defining an Application Structure Using ADSA".