Modifying Action Diagrams › Understanding Contexts › Device Contexts › CTL

CTL

The Subfile Control (CTL) context contains the fields that are in the subfile control record of the device functions that have a subfile panel display such as Display File or Edit Transaction.

The fields available in the CTL context depend on the function type, the access path used by the function, and whether you have specified restrictor parameters for the function. The *CMD key shipped field and any parameters specified as mapped or restrictor parameters are present on the CTL context.

If the function is attached to a SPN access path, the CTL context contains all of the fields from the header format on the access path.

If the access path is a RTV or a RSQ and the function is:

• Display type (Display File or Select Record), all of the fields on the access path are available in the CTL context unless any of those fields have been dropped from the panel subfile control format. The key fields can be used as positioner parameters, the non-key fields can be used as selectors.
• Edit type (Edit File), all of the key fields on the access path are available in the CTL context unless any of those fields have been dropped from the panel subfile control format. These fields can be used as positioner parameters. For key fields, which are restrictor parameters for the function, any associated virtual fields are also present on the CTL context.

If you defined any key fields as restrictor parameters, any virtual fields are also available in the CTL context.

The CTL context is available in the action diagrams of all functions that have a subfile panel display:

• Display File (DSPFIL)
• Display Transaction (DSPTRN)
• Edit File (EDTFIL)
• Edit Transactions (EDTTRN)
• Select Record (SELRCD)

The CA 2E shipped field *CMD key provides the means of specifying that a specific piece of logic is to be executed whenever the user presses a particular function key. The *CMD key is a status (STS) field and already has defined conditions for many possible function or control key combinations.

For more information on a list of the default function keys, see this module, in the chapter, "Modifying Device Designs."

Consider the following example of the use of the *CMD key.

To specify the use of a function key to call another program, you should insert the relevant processing at the appropriate point in the action diagram, for example:

  > USER: Process command keys
  .--

  :  .-CASE                                    <<<
  :  |-CTL. *CMD key is CF06                   <<<
  :  | Print detailed report                   <<<
  :  ‘-ENDCASE

  ‘--

Consider the following example of the indirect use of a *CMD key.

If you want to be able to remap the function keys of your application to another standard, you should use LST conditions in place of direct function key conditions. For example, you could:

1. Define a LST condition called Display Print.
2. Condition your action diagram using this condition.

   Assign a function key such as F6 to the Display Print condition.

  > USER: Process command keys
  .--

  :  .-CASE                                    <<<
  :  |-CTL. *CMD key is Display print          <<<
  :  | Print detailed report                   <<<
  :  ‘-ENDCASE

  ‘--