Global Members

Global members reside in global libraries. A different global library is used for each computer (SMF ID) on which Control‑O operates. The global library name is composed of

• the prefix defined for Control-O operations files in the OLPREFO Control‑O target library parameter
• the global identifier .GLB
• the string "CPU" followed by the SMF ID of the specified computer

CTO.Vxxx.GLB.CPUSYSA

$GLOBAL is usually the default global member. This member contains Control‑O AutoEdit variables that are not assigned to specific global members, yet must be available globally. The member format is identical to the format of a Control‑M AutoEdit variable member. Therefore, Control‑O global members can be referenced by Control‑M jobs using MEMSYM and LIBSYM parameters.

Note: In contrast, global variables created and accessed using the IOA Variable Database facility cannot be accessed by Control‑M jobs using MEMSYM and LIBSYM parameters. For Control‑M to access these variables, you must explicitly state its path name and variable name in job definition statements such as SET VAR and DO SET. For more information, see IOA Administration.

Updates or additions to global variables (by rules or KOA scripts) are kept in memory by Control‑O and are available to all other rules. While Control‑O is active, global variables can be reloaded from, or written back to, the PDS (partitioned dataset) global library, in total or by member name, using operator commands LOADGLOBAL and WRITEGLOBAL. When Control‑O is stopped, the global variables are written back to their respective partitioned datasets.