Step 5: Further Define the Application Responses

Defining an Application Structure Using ADSA › Instructions › Step 5: Further Define the Application Responses

Step 5: Further Define the Application Responses

You further define each application response by using the Response Definition screen. A sample Response Definition screen is shown below:

Sample screen

Response Definition Application name: XXXAPPL Version: 1 Response name: ADD Drop response (/) _ Function invoked: ADDDEP Description . . . . ____________________________ Security class: 0 Response type. . . . . . . 2 1. Global 2. Local Response execution . . . . 2 1. Immediate 2. Deferred Assigned key . . . . . . . PF04 Control command. . . . . . 1 1. Transfer 2. Invoke 3. Link 4. Return 5. Return continue 6. Return clear 7. Return continue clear 8. Transfer nofinish 9. Invoke nosave 10. Link nosave Enter F1=Help F3=Exit F4=Prev F5=Next

Screen prompts

Certain information will be presented to you when this screen is displayed:

Application name— The name of the application will be displayed.
Version— The version number of the application will be displayed.
Response name— The name of the response as listed on the Response/Function List screen will be displayed. At runtime, the user can enter the response name on the screen to select the response.
Function invoked— The name of the function as listed on the Response/function List screen will be displayed. This is the function that the response invokes at runtime. For example, the ADD response invokes the ADDDEP function at runtime.
Assigned key— The key assigned to this response on the Response/Function List screen will be displayed. At runtime, the user can press the specified control key to select the response.

When you define a response on the Response Definition screen, you typically enter information after the following prompts:

Description— You can type a one-line description for each response. At runtime, the description is displayed on each menu from which the response is available.
Security class— You can assign a security class to this response. Applicable to online applications only, security class specifies the DC/UCF security class in the range 1 to 256, assigned to the application. Zero (0) is defined as always unsecured. See your security administrator about the security class conventions being used at your site.
For more information on security classes, refer to the CA ADS Reference Guide.
Response type— (Applies at definition time only) The default response type, 2 (local), specifies that you must explicitly make the response valid for any functions that use the response. You assign this response type to responses that are not used by many functions in the application. For example, it is easier to define ADD as a local response because you add it to only one function definition (DEPTMENU).
A response that is available from many application functions is typically defined as a 1 (global) response. A global response is added to each function definition as the function is defined. You later deselect the global response from the few functions that do not use the response. For example, you define BACK as a global response because it is used by all but one function in the application. When defining functions, it is easier to deselect BACK from one function than to explicitly select it for all other functions.

Note: It is often useful to list the global responses before local responses on the Response/Function List screen so that they are available for all function definitions.
Response execution—You can specify whether the invoked function is immediately executable or deferred.
For more information on immediate and deferred execution, see CA ADS Reference Guide.
Control command— You must specify the control command (for example, Transfer or Link) the response uses to invoke the specified function at runtime. For prototype applications, which don't perform any significant processing, you typically use the default control command, 1 (Transfer). When this command is used to pass control to another function, the runtime system frees resources being held for the original function.
For more information on control commands, see CA ADS Reference Guide.

Responses for Department application

The table below summarizes the specifications you will make for each of the five responses in the Department application. You can define these responses in any order, although it is often useful to define the global responses first. In the sample definition session shown in this chapter, these responses are defined in the order presented below.

Response name	Description	Control key	Function invoked	Response type
BACK	Return to menu	CLEAR	POP	Global
EXIT	Terminate application	PF9	QUIT	Global
ADD	Add a new department	PF4	ADDDEP	Local
MOD	Modify a department	PF5	MODDEP	Local
DEL	Delete a department	PF6	DELDEP	Local

To begin defining application responses, access the Response Definition screen by pressing [PF5] from the Response/Function List screen and define an application response.

The first two responses, BACK and EXIT, are used by most functions in the application. To make the functions easier to define later, you will define BACK and EXIT as global responses. When you define functions in ADSA, a global response is automatically available from each function. You can selectively remove a global function from functions when you define the functions.

You define the BACK response as shown:

Defining the BACK response

Response Definition Application name: XXXAPPL Version: 1 Response name: BACK Drop response (/) _ Function invoked: POP Description . . . . return to menu Response type. . . . . . . 1 1. Global 2. Local Response execution . . . . 2 1. Immediate 2. Deferred Assigned key . . . . . . . CLEAR Control command. . . . . . 1 1. Transfer 2. Invoke 3. Link 4. Return 5. Return continue 6. Return clear 7. Return continue clear 8. Transfer nofinish 9. Invoke nosave 10. Link nosave Enter F1=Help F3=Exit F4=Prev F5=Next

After you press [Enter], ADSA adds the response definition if there are no errors, and then redisplays the Response Definition screen.

Defaults

ADSA fills in default values for the following Response Definition screen prompts if you have not entered another value:

Response type returns the default value of 2 (Local). BACK is defined as a global response because it is available from many functions in the Department application. To specify that this response is global, overtype 2 with 1.
Response execution returns the default value of 2 (Deferred)
Control command returns the default value of 1 (Transfer).

When you press [Enter], the screen will redisplay with a confirming message if the definition is correct, or an error message if an error has been encountered.

Note: If you press [Enter] after providing information, the screen will redisplay. If you press [PF5] after providing information and there are no errors, the appropriate Function Definition screen will be displayed. Since BACK and EXIT are responses that invoke system functions, the Function Definition screen will not be displayed.

Press [PF5] and define the EXIT response in the same way:

Defining the EXIT response

Response Definition Application name: XXXAPPL Version: 1 Response name: EXIT Drop response (/) _ Function invoked: QUIT Description . . . . terminate application Security class: 0 Response type. . . . . . . 1 1. Global 2. Local Response execution . . . . 2 1. Immediate 2. Deferred Assigned key . . . . . . . PF09 Control command. . . . . . 1 1. Transfer 2. Invoke 3. Link 4. Return 5. Return continue 6. Return clear 7. Return continue clear 8. Transfer nofinish 9. Invoke nosave 10. Link nosave Enter F1=Help F3=Exit F4=Prev F5=Next

These responses invoke system functions. You do not have to further define any system function.

Defining the ADD response

The ADD response invokes the function, ADDDEP. The response definition is as follows:

Response Definition Application name: XXXAPPL Version: 1 Response name: ADD Drop response (/) _ Function invoked: ADDDEP Description . . . . add department Security class: 0 Response type. . . . . . . 2 1. Global 2. Local Response execution . . . . 2 1. Immediate 2. Deferred Assigned key . . . . . . . PF04 Control command. . . . . . 1 1. Transfer 2. Invoke 3. Link 4. Return 5. Return continue 6. Return clear 7. Return continue clear 8. Transfer nofinish 9. Invoke nosave 10. Link nosave Enter F1=Help F3=Exit F4=Prev F5=Next

ADD is defined as a local response because it is available only from the DEPTMENU function in the Department application. You will make ADD valid for DEPTMENU when you define the DEPTMENU function in Step 6.

After you press [Enter], ADSA adds the response definition if there are no errors, and then redisplays the Response Definition screen.

When you are finished defining a response for the Department application, you define the function it invokes as described below. Pressing [PF5] will display the Function Definition screen.