Application Parameter Manager › Establish the Parameter Database and Interface › Ways to Implement

Ways to Implement

You can implement the Application Parameter Manager by choosing one of the following methods:

• Enter the name of the data set that holds parameter data as the value of the specific global variable you have created for this purpose.

  Use OPSVIEW option 4.8 to establish such a global variable if none exists. The format for this variable is GLOBAL8.ASOZ9_APPLDSNS.

  A sample of the OPSVIEW option 4.8 panel, shown here, indicates how you might set this variable:

  AOF CTRL - Display Global Variables -------- S034 --------  ROW 1 TO 2 OF 2
  COMMAND ===>                                               SCROLL ===> PAGE
          Line Commands: S Show Subnodes  M Modify     X Hex Browse  B Browse 
                         D Remove Node    P Drop Node  O Delete One
    System ===> *        Wait ===>
    Global Prefix: GLOBAL8 
    Subnode Name   Nodes Subnode Value
    ASOZ9_APPLDSNS     0 !SMITH.O.CNTL
    Z9_ARCHIVE         6 NO VALUE ASSIGNED AT THIS LEVEL
    **END**
  

  In this example !SMITH.O.CNTL is the data set that contains members that contain parameter data. Another example could be !SYS1.OPS.CNTL. These data sets, as global variable values for the Application Parameter Manager, always begin with the ! (exclamation mark) character.

  If you use this option, you do not need to edit programs.

• Customize the REXX program of the Application Parameter Manager, ASOPRMIN, located in SYS1.OPS.REXX on the CA OPS/MVS distribution media. ASOPRMIN contains these specifications:
  • The LOCAPPL DD data set allocations, allocated to the CA OPS/MVS address space. This DD, a standard z/OS partitioned data set, contains parameter values specific to the current CA OPS/MVS system. Data in the LOCAPPL partitioned data set is not shared across systems.
  • The GBLAPPL DD data set allocations, also allocated to the CA OPS/MVS address space. Also a z/OS partitioned data set, GBLAPPL, contains parameter values that CA OPS/MVS systems share. Data sets in the GBLAPPL DD allocation share parameter data through standard shared DASD, and the GBLAPPL allocations of multiple systems specify the same physical data set.
  • The GLOBAL PREFIX or GPFX. This is used as the high-level qualifier of global variables. Because individual sites can customize which variable prefixes designate global variables and which designate local variables, you need to consider what prefix to use. The default prefix for global variables is the four #AP_ characters. If you cannot use this default prefix for creating global variables because it has already been assigned, then use an unassigned prefix as the default.

  By using both the LOCAPPL and GBLAPPL ddnames, you reduce the amount of parameter administration. Many parameters have the same value in all CA OPS/MVS systems, while other parameters require different values for each system. You can specify parameters common to all CA OPS/MVS systems once in GBLAPPL.