Updating Contents of a Database in Memory

To implement changes to a variable database that has already been loaded into memory, so that the changes are immediately accessible by Control‑M jobs and other INCONTROL products:

1. Reload the modified database using one of the following operator commands:
   • If Control‑O is not installed, use

     F CTMCMEM,LOADGLOBAL[=dbname]

   • If Control‑O is installed, use

     F CONTROLO,LOADGLOBAL[=dbname]

     where dbname is the name of the database.

   Variables in a variable database can also be updated or modified through DO SET statements in Control‑M jobs, or through SETOGLB statements in a KSL/KOA script. For more information, see the DO SET parameter in the job production parameters chapter of the Control‑M for z/OS User Guide.

2. Use one of the following operator commands to save changes made to the database in memory:
   • If Control‑O is not installed, use

     F CTMCMEM,WRITEGLOBAL[=dbname]

   • If Control‑O is installed, use

     F CONTROLO,WRITEGLOBAL[=dbname]

     where dbname is the name of the database.

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.