Using CA Datacom/DB Utility (DBUTLTY) › Simplify Considerations › Functions Needing the CXX

Functions Needing the CXX

With the Simplify feature, normal DBUTLTY functions can access and update control data and user data using MUF. This ensures MUF has control while providing current and updated information.

This section reviews the DBUTLTY functions that need the CXX and in releases prior to Version 14.0 caused the CXX to be opened for update in the DBUTLTY address space. With the Simplify feature, these functions have been changed to use the MUF for all CXX access and update while providing another level of control that benefits the functions.

Updates include the following:

• The CXX DD statement required by these functions can be removed. If CXX update access is no longer needed, you can remove that right from security. This action makes the CXX much safer by having fewer people with the ability to accidentally overlay or change it.

  Note: The CXX DD statement is dynamically allocated if the MUF is down and a function is running that requires MUF to be down or if you have directed that the DBUTLTY is to execute with MUF down.

• A related change that affects all the functions is the Run Unit. Without Simplify, a DBUTLTY function connected to the MUF obtains a Run Unit from the MUF. If that DBUTLTY opens the CXX locally, it also obtains a Run Unit locally. With Simplify, the MUF Run Unit is shared locally and both have a single number.
• All editing of CXX information allowing the function to continue occurs in the MUF address space. All setting of CXX information such as loading, unloading, loaded, and so forth, occurs in the MUF address space.
• All CXX information used is current.

Following are the function changes:

BACKUP

• AREA=CXX gets all information from the MUF. Before processing each database for information, an internal COMM STATS is done to synchronize the current MUF information.
• AREA=a (user data area) communicates with MUF to ensure it is appropriate to execute the function. It is protected by MUF to guarantee no conflict of the BACKUP requirements. When MULTUSE=YES is specified, where allowed, running with Simplify mode works the same as without. For all other cases, Simplify works differently as described following.

  With SEQ=PHYSICAL,UPDATE=NO:

  • Allows execution with the area being open for read or update by other users and produces a hot backup.
  • Causes MUF to push current pipeline buffers from MUF memory to DASD where this backup gets its data.

  With SEQ=NATIVE or SEQ=PHYSICAL,UPDATE=YES:

  • Ensures no other users of the database exist and once started, allows no other users of the database.
  • Attempts to close the database.
  • Native obtains a share ENQ on the index areas. Both native and physical obtain a share ENQ on the data areas. To allow a MUF failure and restart to know about the execution of the DBUTLTY function, the DBUTLTY obtains a share ENQ on CADTCM02 and DBUTLTY/cxxname/dbid. This includes all forms of BACKUP and EXTRACT except SEQ=PHYSICAL,UPDATE=NO. If MUF restarts, it uses an ENQ with TEST to see if the DBUTLTY function is still executing. If not, the status is removed. If yes, the base is set to be in open with backup in process running. The function communicates with MUF briefly during its startup processing and then executes within the DBUTLTY address space to read and write all the appropriate rows and then communicate with MUF briefly to note completion.

    When a large number of rows need processing, the time the DBUTLTY is not talking to MUF can be lengthy. After the row processing and before the close processing, the DBUTLTY has special code to verify it is in synchronization with the MUF and if not, drives a resynchronization process. If there is a MUF outage during the time of row processing and the MUF reenabled prior to the close time, the DBUTLTY automatically disconnects from the failed MUF and reconnects to the current MUF. If the MUF is not currently enabled, the DBUTLTY function honors a DBSIDPR setting of DELAY68 (or a DBUTLTY override with SET OPTION1=DELAY68=n) to wait for the enable a set maximum number of minutes.

    Note: This synchronization process occurs once and only at the point between row processing completes and close processing starts.

CXXMAINT

The CONVERT1214, CONVERT1412, OPTION=ALTER,and OPTION2=MATCHSID, functions cannot run with MUF enabled. The other functions expect to run with the MUF enabled where it is used.

EXTBKUP

Does not use the CXX or MUF.

EXTEND

AREA=IXX

• Ensures that the database is not open for any other purpose and once started, blocks other opens.
• Obtains exclusive ENQ of index areas.
• Obtains an exclusive ENQ on CADTCM02 and DBUTLTY/cxxname/dbid.
• Communicates with MUF briefly during its startup processing, executes within the DBUTLTY address space to format new tracks and then communicates with MUF briefly to note completion.

  If a large number of tracks need processing, the time the DBUTLTY is not talking to MUF can be lengthy. After the track processing and before the close processing, the DBUTLTY has special code to verify it is in synchronization with the MUF and if not, drives a resynchronization process. If there is a MUF outage during the time of track processing and the MUF reenabled prior to the close time, the DBUTLTY automatically disconnects from the failed MUF and reconnects to the current MUF. If the MUF is not currently enabled, the DBUTLTY function honors a DBSIDPR setting of DELAY68 or a DBUTLTY override with SET OPTION1=DELAY68=n to wait for the enable a set maximum number of minutes.

  Note: This synchronization process occurs once and only at the point between track processing completes and close processing starts.

AREA=a (user data area)

With MULTUSE=YES works the same with Simplify as without Simplify. Without MULTUSE=YES:

• Ensures that the database is not open for any other purpose and once started, blocks other opens.
• Obtains exclusive ENQ of data areas.
• Obtains an exclusive ENQ on CADTCM02 and DBUTLTY/cxxname/dbid.
• Communicates with MUF briefly during its startup processing, executes within the DBUTLTY address space to format tracks and then communicates with MUF briefly to note completion.

  If a large number of tracks need processing, the time the DBUTLTY is not talking to MUF can be lengthy. After the track processing and before the close processing, the DBUTLTY has special code to verify it is in synchronization with the MUF and if not, drives a resynchronization process. If there is a MUF outage during the time of track processing and the MUF reenabled prior to the close time, the DBUTLTY automatically disconnects from the failed MUF and reconnects to the current MUF. If the MUF is not currently enabled, the DBUTLTY function honors a DBSIDPR setting of DELAY68 or a DBUTLTY override with SET OPTION1=DELAY68=n to wait for the enable a set maximum number of minutes.

  Note: This synchronization process occurs once and only at the point between track processing completes and close processing starts.

EXTRACT

Same as BACKUP for data area.

INIT

AREA=IXX

• Ensures that the database is not open for any other purpose and once started, blocks other opens.
• Obtains exclusive ENQ of index areas.
• Sets the CXX database as in INIT INDEX.
• Obtains an exclusive ENQ on CADTCM02 and DBUTLTY/cxxname/dbid/IXX/COMMON.
• Communicates with MUF briefly during its startup processing, executes within the DBUTLTY address space to format tracks and then communicates with MUF briefly to note completion.

  If a large number of tracks need processing, the time the DBUTLTY is not talking to MUF can be lengthy. After the track processing and before the close processing, the DBUTLTY has special code to verify it is in synchronization with the MUF and if not, drives a resynchronization process. If there is a MUF outage during the time of track processing and the MUF reenabled prior to the close time, the DBUTLTY automatically disconnects from the failed MUF and reconnects to the current MUF. If the MUF is not currently enabled, the DBUTLTY function honors a DBSIDPR setting of DELAY68 or a DBUTLTY override with SET OPTION1=DELAY68=n to wait for the enable a set maximum number of minutes.

  Note: This synchronization process occurs once and only at the point between track processing completes and close processing starts.

AREA=a (user data area)

With MULTUSE=YES, works the same with Simplify as without Simplify. Without MULTUSE=YES:

• Ensures that the database is not open for any other purpose and once started, blocks other opens.
• Obtains exclusive ENQ of data areas.
• Obtains an exclusive ENQ on CADTCM02 and DBUTLTY/cxxname/dbid.
• Communicates with MUF briefly during its startup processing, executes within the DBUTLTY address space to format some tracks and then communicates with MUF briefly to note completion.

  It is unlikely that an INIT of a data area will execute long because it does not format all tracks but just some at the start of the extent. The following LOAD will format the rest. After the track processing and before the close processing, the DBUTLTY has special code to verify it is in synchronization with the MUF and if not, drives a resynchronization process. If there is a MUF outage during the time of track processing and the MUF reenabled prior to the close time, the DBUTLTY automatically disconnects from the failed MUF and reconnects to the current MUF. If the MUF is not currently enabled, the DBUTLTY function honors a DBSIDPR setting of DELAY68 or a DBUTLTY override with SET OPTION1=DELAY68=n to wait for the enable a set maximum number of minutes.

  Note: This synchronization process occurs once and only at the point between track processing completes and close processing starts.

LOAD

With MULTUSE=YES, works the same with Simplify as without Simplify. Without MULTUSE=YES:

• Ensures that the database is not open for any other purpose and once started blocks other opens.
• Gets an exclusive ENQ of each index area and data area.
• Gets an exclusive ENQ on CADTCM02 and DBUTLTY/cxxname/dbid.
• Communicates with MUF briefly during its startup processing and then will execute within the DBUTLTY address space to read and write all the appropriate rows and then communicate with MUF briefly to note completion.

  When a large number of rows need processing, the time the DBUTLTY is not talking to MUF can be lengthy. After the row processing and before the close processing, the DBUTLTY has special code to verify it is in synchronization with the MUF and if not, drives a resynchronization process. If there is a MUF outage during the time of row processing and the MUF reenabled prior to the close time, the DBUTLTY automatically disconnects from the failed MUF and reconnects to the current MUF. If the MUF is not currently enabled, the DBUTLTY function honors a DBSIDPR setting of DELAY68 (or a DBUTLTY override with SET OPTION1=DELAY68=n) to wait for the enable a set maximum number of minutes.

  Note: This synchronization process occurs once and only at the point between row processing completes and close processing starts.

RECOVERY forward

With MULTUSE=YES works the same with Simplify as without Simplify. Without MULTUSE=YES:

• Ensures that the database is not open for any other purpose and once started, blocks other opens.
• Obtains an exclusive ENQ of each index area and data area.
• Obtains an exclusive ENQ on CADTCM02 and DBUTLTY/cxxname/dbid.
• Communicates with MUF briefly during its startup processing, executes within the DBUTLTY address space to read and write all the appropriate rows and then communicates with MUF briefly to note completion.

  When a large number of rows need processing, the time the DBUTLTY is not talking to MUF can be lengthy. After the row processing and before the close processing, the DBUTLTY has special code to verify it is in synchronization with the MUF and if not, drives a resynchronization process. If there is a MUF outage during the time of row processing and the MUF reenabled prior to the close time, the DBUTLTY automatically disconnects from the failed MUF and reconnects to the current MUF. If the MUF is not currently enabled, the DBUTLTY function honors a DBSIDPR setting of DELAY68 (or a DBUTLTY override with SET OPTION1=DELAY68=n) to wait for the enable a set maximum number of minutes.

  Note: This synchronization process occurs once and only at the point between row processing completes and close processing starts.

REORG load portion

With MULTUSE=YES works the same with Simplify as without Simplify. Without MULTUSE=YES:

• Ensures that the database is not open for any other purpose and once started, blocks other opens.
• Obtains an exclusive ENQ of each index area and data area.
• Obtains an exclusive ENQ on CADTCM02 and DBUTLTY/cxxname/dbid.
• Communicates with MUF briefly during its startup processing, executes within the DBUTLTY address space to read and write all the appropriate rows and then communicates with MUF briefly to note completion.

  When a large number of rows need processing, the time the DBUTLTY is not talking to MUF can be lengthy. After the row processing and before the close processing, the DBUTLTY has special code to verify it is in synchronization with the MUF and if not, drives a resynchronization process. If there is a MUF outage during the time of row processing and the MUF reenabled prior to the close time, the DBUTLTY automatically disconnects from the failed MUF and reconnects to the current MUF. If the MUF is not currently enabled, the DBUTLTY function honors a DBSIDPR setting of DELAY68 (or a DBUTLTY override with SET OPTION1=DELAY68=n) to wait for the enable a set maximum number of minutes.

  Note: This synchronization process occurs once and only at the point between row processing completes and close processing starts.

REPORT

• AREA=CXX obtains all information printed from the MUF. Before processing each database for information, an internal COMM STATS is done to synchronize the current MUF information.
• AREA=LXX obtains all information printed from the MUF. Does not open the LXX locally.

RESET

Not allowed either LXX or CXX

RETIX

With MULTUSE=YES works the same with Simplify as without Simplify.

Without MULTUSE=YES, it ensures that the database is not open for any other purpose and once started, blocks other opens.

• Obtains an exclusive ENQ of each index area and data area.
• Obtains an exclusive ENQ on CADTCM02 and DBUTLTY/cxxname/dbid.
• Communicates with MUF briefly during its startup processing, executes within the DBUTLTY address space to read and write all the appropriate rows and then communicates with MUF briefly to note completion.

  When a large number of rows need processing, the time the DBUTLTY is not talking to MUF can be lengthy. After the row processing and before the close processing, the DBUTLTY has special code to verify it is in synchronization with the MUF and if not, drives a resynchronization process. If there is a MUF outage during the time of row processing and the MUF reenabled prior to the close time, the DBUTLTY automatically disconnects from the failed MUF and reconnects to the current MUF. If the MUF is not currently enabled, the DBUTLTY function honors a DBSIDPR setting of DELAY68 (or a DBUTLTY override with SET OPTION1=DELAY68=n) to wait for the enable a set maximum number of minutes.

  Note: This synchronization process occurs once and only at the point between row processing completes and close processing starts.