Response Definition Screen

The Response Definition screen enables the application developer to provide extended specifications when defining responses. These specifications include:
idmscu
The Response Definition screen enables the application developer to provide extended specifications when defining responses. These specifications include:
  • Description
  • Security class
  • Response type
  • Response execution
  • Assigned key
  • Control command
The Response Definition screen is accessed by entering a nonblank character in the appropriate
Select
field on the Response/Function List screen and pressing [PF5].
Sample Screen
                              Response Definition  Application name:   TEST1      Version:    1  Response name:      QUIT                                Drop response (/) _  Function invoked:   QUIT  Description . . . . ____________________________            Security class:   1  Response type. . . . . . . 2   1. Global      2. Local  Response execution . . . . 2   1. Immediate   2. Deferred  Assigned key . . . . . . . PF01  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
Field Descriptions
  • Application Name
    Specifies the name of the current application, as specified on the Main Menu screen. This field is protected.
  • Version
    Specifies the version number, in the range 1 through 9999, of the current application.
  • Response Name
    Displays the name of the application response selected on the Response/Function List screen.
    This field can be modified by the user. The first character of the response name cannot be blank. If modified, the user should insure that the combination of response name, assigned key, and associated function must be unique within the application.
  • Drop Response
    Removes the response definition from the application. CA ADS does
    not
    drop the function associated with the dropped response.
  • Function Invoked
    Displays the function invoked by the current application response, as specified on the Response/Function List screen.
    This field is protected.
  • Description
    Specifies a 1- to 28-byte description of the current response. The response description is displayed with the associated response name on runtime menu and help screens. Note that the specified description is truncated to 12 characters on the short description menu screen.
  • Security Class
    Specifies the security class for the response. Valid security class values are 1 to 256. See your Security Administrator about the security class conventions being used at your site.
  • Response Type
    Specifies whether the response is global or local, as follows:
    1. Global
      -- The response is valid for all functions in the application. Global responses can be deselected from the list of valid responses for a specific function.
    2. Local
      (default) -- The response is valid only for those functions with which it is explicitly associated on the Function Definition screen.
    A response is specified as global (that is, valid for all functions in the application) or local (that is, valid only if explicitly associated with a function). For each response defined, the combination of response name, associated control key, and function initiated must be unique within the application.
  • Response Execution
    Specifies whether the invoked function is immediately executable or deferred. The following considerations apply:
    • In online applications, the default for all functions except the HELP, SIGNON, SIGNOFF, FORWARD, and BACKWARD system functions is deferred.
    • In the batch environment, the default for all functions is immediately executable.
    Defaults can be overridden by entering the appropriate number in the data field immediately following the
    Response execution
    prompt.
  • Assigned Key
    Specifies an online control key or a batch control event that selects the response at runtime.
    The following considerations apply:
    • Valid
      online
      assigned key specifications are ENTER, CLEAR, PA1 through PA3, PF1 through PF24, FWD, BWD, and HDR. LPEN can be specified as a control key if the use of light pens is supported by the installation. The following considerations apply:
      • CLEAR, PA1, PA2,
        and
        PA3
        do not transmit data.
      • The
        FWD, BWD,
        and
        HDR
        control keys are associated with pageable maps.
      • FWD
        and
        BWD
        are synonymous with the keyboard control keys defined for paging forward and backward respectively. If FWD or BWD is specified and the keys defined for paging forward and backward are changed, the response definition does not have to be updated or the application recompiled.
        HDR
        is not associated with any keyboard control key. Conditions encountered during a map paging session cause the response associated with this control key value to be selected.
    • Valid
      batch
      control events are EOF and IOERR. The following considerations apply:
      • EOF
        indicates that the most recent input-file read operation resulted in an end-of-file condition.
      • IOERR
        indicates that the most recent input file read operation resulted in a physical input-error condition. In CA ADS Batch, an output error causes the runtime system to terminate the application.
  • Control Command
    Specifies the CA ADS control command used to pass processing control to the function associated with the response, as follows:
    1. Transfer
      (default) -- Control is passed by means of a TRANSFER command.
    2. Invoke
      -- Control is passed by means of an INVOKE command.
    3. Link
      -- Control is passed by means of a LINK command.
    4. Return
      -- Control is passed by means of a RETURN command.
    5. Return Continue
      -- Control is passed by means of a RETURN command to the premap process.
    6. Return Clear
      -- Control is passed by means of a RETURN command and buffers are initialized.
    7. Return Continue Clear
      -- Control is passed by means of a RETURN command to the premap process and buffers are initialized.
    In process code for dialogs associated with functions, the only control command needed is EXECUTE NEXT FUNCTION. When a valid response is made, EXECUTE NEXT FUNCTION causes the runtime system to execute the control command associated with the response. The control commands perform the same record buffer and currency maintenance as they do when they are coded in processes.