CA IDMS Reference 19.0

PDF
English

General Options Screen Page two

The second page of the General Options screen is used to specify runtime security restrictions for a CA ADS application.
idmscu
The second page of the General Options screen is used to specify runtime security restrictions for a CA ADS application.
How to Access
The application developer accesses this screen from the first General Options screen in one of two ways:
  • Pressing [PF8]
  • Entering a
    2
     in the
    Page
     field and pressing [Enter]
Security Classes
This screen allows the application developer to specify a DC/UCF security class for the current application. Application security class is no longer used by the CA ADS runtime system and is not used by CA IDMS internal security. It is provided for downward compatibility with applications compiled under previous releases of DC/UCF and for installations that use privately designed security systems that rely on the application security class being stored in the ADSO-APPLICATION-GLOBAL-RECORD during runtime.
Security classes assigned to responses are checked by CA IDMS central security if security has been enabled.
Signon Functions
The second page of the General Options screen also allows the application developer to specify a signon function to be executed before any other application function. A signon function, if specified, is the first function initiated by the runtime system. If signon is required, the application cannot be executed until an acceptable signon is entered. If signon is optional, the application can be executed whether or not a signon is entered.
Security for Runtime Menus
The application developer can also specify whether runtime menus are to be security tailored. Only those responses for which the user has execution authority are displayed on security-tailored menus.
The second page of the ADSA General Options screen itself can be the object of user security restrictions imposed by the security administrator, through restricting execution authority for program ADAPGOP2. Only application developers having execution authority for ADAPGOP2 would have access to the second page of the General Options screen.
Note:
 For more information about CA IDMS central security, see the
CA IDMS Security Administrating section
.
Sample Screen
 

                              General Options                Page 2  of 2

 Application name:  TESTAPPL   Version:    1

    Security class. . . . . . .   42

    Menus are . . . . . . . . .  1   1. Not used   2. Security tailored
                                     3. Untailored

    Signon is . . . . . . . . .  1   1. Not used   2. Optional

    Signon function is. . . . .

 Enter  F1=Help  F3=Exit  F4=Prev  F5=Next  F7=Bkwd
Field Descriptions
  • Application Name
    Specifies the name of the current application, as specified on the Main Menu screen. This field is protected.
  • Security Class
    Applicable to online applications only, specifies the DC/UCF security class, in the range 1 to 256, assigned to the application.
    File specification allows compatibility with Release 14.0 for applications compiled under previous releases of CA IDMS and maintains the functionality of installation-designed security systems that rely on application security classes being stored in the ADSO-APPLICATION-GLOBAL-RECORD during runtime.
  • Menus Are
    Specifies whether runtime menus are security tailored. The application developer can select one of the following specifications by entering the appropriate number in the data field following this specification. The options are:
    1. Not used
       -- specifies that the application does not use menus.
    2. Security tailored
       -- specifies that only those responses that the user has authority to execute are displayed on the runtime menus.
    3. Untailored
       -- (default) specifies that all responses defined as valid for application functions are displayed on menus, regardless whether the user has the authority to execute them.
    The CA ADS runtime system tests to determine whether the user has authority to execute each menu response if menus are security tailored. Only those responses for which the user has execution authority are then displayed on the menus. If the user attempts to execute a response for which execution authority is not granted, the current function screen is redisplayed with the following message:
    
UNACCEPTABLE RESPONSE. PLEASE TRY AGAIN
  • Signon Is
    Specifies whether a signon function is executed for the application. The application developer can select a signon specification by entering the applicable number in the field following this specification. A signon function can be specified as follows:
    1. Not used
       -- (default) specifies that no signon function is executed for the application.
    2. Optional
       -- specifies that a signon function will be executed only when the user is not signed on to DC/UCF. When the user is already signed on to DC/UCF, the task top function is executed instead of the signon function (if it is a different function). Also, the user is not required to sign on to the application to execute unsecured functions.
    3. Required
       -- specifies that the application signon function is always executed regardless of whether the user has signed on to DC/UCF, and regardless of which function is the task top function. The user can only execute other functions after successfully signing on to the application.
  • Signon Function Is
    Specifies the name of a signon menu function to be defined by using the
    Function Definition (Menu)
     screen. If
    Signon
     is specified as
    Optional
     or
    Required
    , a signon function must be supplied. If
    Signon
     is specified as
    Not used
    , a signon function name cannot be specified.
    To identify system functions, enter the system function name. System functions are reserved and cannot be edited.
    ADSA warns the application developer if a function type code (1, 2 or 3), a program name, or a dialog name are reserved for a system function.