Previous Topic: MUF_ML_DUMPS_PXX (MFE)Next Topic: MUF_OPTIONS (MFO)


MUF_OPEN_BASES (MFB)

This table provides information about open databases. One row exists for every open User Requirements Table, both external to the MUF and internal to the MUF. It is designed primarily for CA Datacom STAR sites to provide information about what bases are open by what jobs and at what distributed nodes. Also, this table provides what jobs locally have a database open. This can be valuable to CA Datacom STAR and non-CA Datacom STAR sites.

Column Name

SQL Data Type

Nullable

Description

DBID

 

SMALLINT

No

The database ID for this row. For a CA Datacom STAR environment, this is the data base ID as it is known by the reporting MUF.

JOB_NAME

 

CHAR(8)

No

Job name of a job that has at least one URT open against a table in this database.

JOB_NODE

 

CHAR(8)

No

Contains blanks in a non-CA Datacom STAR MUF. In a CA Datacom STAR MUF, this field contains the CA Datacom STAR node name from the MUF that the application is connected to.

MUF_NAME

 

CHAR(8)

No

Name of the MUF specified in the MUF Multi-User startup option or the name of the MUF job name.

PARTITION

 

CHAR(1)

No

Indicates whether this base is part of a CA Datacom STAR partitioned database. This flag is set to Y only if the DBID is the object of a $PARTITIONED relationship in CA Datacom Datadictionary therefore, this flag reflects a partitioned child.

REMOTE

 

CHAR(1)

No

Indicates whether the database ID represents a database which resides at a remote MUF using CA Datacom STAR. STAR_BASE must be Y for this flag to be Y.

REMOTE_DBID

 

SMALLINT

Yes

Contains null when the REMOTE field contains N. Otherwise, it contains the database ID as it is known at the MUF where the database resides. Thus, this database ID may match or differ from the DBID field.

REMOTE_NODE

 

CHAR(8)

Yes

Contains null in a non-CA Datacom STAR environment. Also contains null if this database is local or if REMOTE is N. For a remote database, contains the node name of the MUF at the remote site.

REPLICA

 

CHAR(1)

No

Specifies whether this base is part of a CA Datacom STAR replicated database. This flag is set to Y only if the DBID is the object of a $REPLICATED relationship in CA Datacom Datadictionary. If the DBID is a child of a partitioned base, then the PARTITION flag is also set to Y.

RUN_UNIT

 

INTEGER

No

Contains the run-unit number for this job. The run unit number could be zero for an opening job, but a job may be assigned the run unit number of zero. For a job running at another MUF, the run unit number is the number assigned the job at the remote location. The run unit number matches the reported run unit number in messages that range from 0 through 99,999.

STAR_BASE

 

CHAR(1)

No

Indicates whether this database exists to support CA Datacom STAR services.

N

Indicates a normal local database with an index and data areas.

Y

Indicates this database exists only for CA Datacom STAR usage. With a Y, the BAS definition in CA Datacom Datadictionary has either a $RESIDES relationship to a remote MUF or a $PARTITIONED or $REPLICATED relationship to a child base.

URT_DBID

 

SMALLINT

No

Contains a database ID as it exists in the application programs User Requirements Table (URT). For local databases and non-CA Datacom STAR environments, the URT_DBID matches the DBID. If the JOB_NODE reflects a remote MUF, the URT_DBID is the database ID as it is known at the remote MUF node. If the DBID is a partitioned or replicated database, then this database ID may reflect the root base.

URT_NUMBER

 

SMALLINT

No

Contains the external User Requirements Table Number for the User Requirements Table with this database open. Each URT open by a job has a unique number ranging from -32768 through 32767 except that zero is now displayed as 10000. The specific number has no importance and may appear random.