Display Types of the Variable Database Zoom Screen

Table 83 shows the predefined display types that are available for the Variable Database Zoom screen:

Table 83 Display Types of the Variable Database Zoom Screen

Changing Display Types

While in the Variable Database Zoom screen, the display type can be changed using the DISPLAY command. The format of the command is

DISPLAY x

In this command, x is the identifying letter for the desired type.

DISPLAY can be abbreviated to DI.

Note: For a list of display types, enter DISPLAY ? to show the Display Options window. To select a display type in the window, type S (Select) in the Option field next to the ID. To exit the window without selecting a display type, press PF03/PF15 (END).

Example

DI B

displays the Blank Line display type

The Default display of the Variable Database Zoom screen includes the first 64 characters of the value of each variable in the selected database row.

Zoom Screen Option

The following option is available in the Variable Database Zoom screen:

A (Additional Information) – Display a second line for the selected variable. The second line contains the remainder (up to 76 characters) of the value of the selected variable.

To exit the Variable Database Zoom screen without implementing any changes, type CAN (cancel) in the COMMAND line and press Enter.

To enable changes to a variable database loaded in memory to be immediately accessible by Control-O rules, the modified database must be reloaded by use of the following operator command:

F CONTROLO,LOADGLOBAL=dbname

Note: Variables in a variable database can also be updated or modified using DO SET statements in Control-O rules, or through SETOGLB statements in a KSL or KOA script. For more information, see DO SET: Automated Console Action Parameter. For more information on KSL and KOA, refer to the KeyStroke Language User Guide.

Use the following operator command to save changes made to a variable database in memory:

F CONTROLO,WRITEGLOBAL=dbname

WARNING: Updating the IOAVAR physical database using screen IV in MODE ADMIN is hazardous in a live system!

The following discussion concentrates on the IOAVAR database which is used by Control-M, but similar problems might occur with Control-O only pools.

Updating the IOAVAR physical database using screen IV in MODE ADMIN in a live system can lead to

• variables getting lost
• blank variable names

The following scenario can lead to variables getting lost.

The IOAVAR database can be changed in the following ways:

• By Control-M SET operations (SET VAR in the Job Scheduling Definition, %%SET in the JCL) that change the live database in memory.

  These changes are saved in the physical database when the WRITEGLOBAL=IOAVAR command is automatically issued.

  Only a WRITEGLOBAL saves these changes to the database.

• By manually changing the physical database via screen IV in MODE ADMIN.

  These manual changes are brought to the live database in memory by a LOADGLOBAL command.

  A LOADGLOBAL=IOAVAR is performed automatically when Control-O/CMEM starts.

  A LOADGLOBAL=IOAVAR can be issued manually when changes that are made to the physical database must be brought into the live database in memory while the system is active.

  A LOADGLOBAL=IOAVAR replaces the entire existing copy of the database in memory.

It is hazardous to update the IOAVAR physical database using screen IV in MODE ADMIN in a live system and issue a LOADGLOBAL because in a live system an IOAVAR variable might be updated at any time and if the LOADGLOBAL is issued just before the WRITEGLOBAL is issued, it will cause recent changes that have not yet been saved with the WRITEGLOBAL to be wiped out.

The following scenario can lead to blank variable names:

When a variable is deleted from the database via IV screen in MODE ADMIN in a live system, and until a LOADGLOBAL=IOAVAR is issued, the variable remains in memory. If the deleted variable is added or updated by Control-M before the LOADGLOBAL=IOAVAR is issued, the variable will still be found in memory, and only the VALUE of the variable will be updated. The WRITEGLOBAL=IOAVAR writes only the value of changed or updated variables to the database (even if the value has not actually changed).

The end result will be that the physical database will include only the VALUE of the IOAVAR variable which has been deleted and updated but without its VARNAME which has been deleted. When viewed in IV screen in MODE ADMIN, blanks will appear in the VARNAME field.