Performance Considerations › System Generation Parameters

System Generation Parameters

The CA ADS system is generated by submitting ADSO, PROGRAM, and TASK statements to the DC/UCF system generation compiler. Optionally, the KEYS statement is used to define site-specific control key functions. These statements are used as follows:

• The ADSO statement includes parameters that define the CA ADS runtime environment, as follows:
  • The task code (ADS) that initiates the CA ADS runtime system
  • The mainline dialog that can begin executing immediately
  • The maximum number of dialog levels that can be established by each application
  • The disposition of record buffers during a pseudo-converse (that is, whether they can be written to the scratch area of the data dictionary)
  • The size of the primary and secondary record buffers
  • The AUTOSTATUS facility that handles errors generated by database, logical record, or queue and scratch record processing
  • The Status Definition Record that associates status codes returned by database, logical record, and queue and scratch record access with condition names
  • The treatment of numeric values placed into alphanumeric fields by arithmetic and assignment commands
  • The display of the Dialog Abort Information screen when the runtime system detects an abend condition in an executing dialog
  • Whether dialog statistics will be collected
  • How CA ADS is to perform a mapout when a dialog's map is already displayed as a result of a previous mapout in a pageable map
  • Whether record buffer blocks are to be compressed across a pseudo-converse when they are retained in the storage pool
  • How the amount of storage to be allocated for record buffer blocks is to be determined
• The PROGRAM statement defines the following CA ADS components as DC/UCF programs:
  • The ADSORUN1, ADSORUN2, and ADSOMAIN runtime system programs
  • The system maps (the menu map, runtime message map, and maps for each of the application and dialog compiler screens)
  • The application and dialog compiler programs (ADSA and ADSC)
  • CA ADS dialogs (an optional parameter if null Program Definition Elements (PDEs) are defined in the SYSTEM statement)
• The TASK statement defines the following task codes:
  • ADS and ADS2 to initiate the runtime system
  • ADSA to initiate the application compiler
  • ADSC to initiate the dialog compiler
  • ADSR to initiate the runtime system when returning from a linked user program

For detailed syntax and examples of the sysgen statements, refer to the CA IDMS System Generation Guide.

The following discussion highlights selected aspects of system generation that have particular import when considering system performance in a CA ADS environment. These features are as follows:

• Allocating primary and secondary storage pools
• Relocating resources
• Specifying the number of online tasks and external request units

Each of these considerations is discussed separately below.