TOM Registry

The Total Object Manager (TOM) Registry is a z/OS data space that is backed by a VSAM Linear Data Set (VLDS) and managed by Runtime Component Services (RTCS). When you access the Registry, TOM makes requests to the RTCS to obtain or update Registry information. In a multi-TOM TOMPLEX, where multiple TOM PASs running on different systems within a sysplex share the same Registry, the Registry owner is one TOM, which services remote requests from other TOM PASs via XCF.

Related topic

Using-Total-Object-Manager

The Registry is defined by using the REGISTRY_DSN= parameter in the MAMPLXxx BBPARM parmlib data set member. This member should be shared by all TOM PASs that will share the Registry.

The TOM Registry stores definitions, which are required by TOM to manage your environment. These definitions include systems where a TOM PAS runs, objects, sets, object statuses, and calendars.

TOM stores definition items in a Definition Base:

  • Objects, sets and object statuses are stored in an object Definition Base.
  • Calendar definitions are stored in a calendar Definition Base.

When the Registry is first allocated and the TOM PAS is initialized, TOM creates two Definition Bases in the Registry: an object Definition Base named DEFAULT, which contains no definitions, and a calendar Definition Base named DEFAULTCAL, which contains a set of default calendar definitions. You can define additional object and calendar Definition Bases as needed.

This section contains the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*