The following are changes to the DBUTLTY functions:
The ACCESS function has a new keyword IGN68= which makes it possible to ignore return code 68. IGN68= makes it easier to set up and run JCL incorporating a stack of DBUTLTY functions without requiring that the MUF be enabled. For example, IGN68= would be useful if you wanted to load a database, perhaps to allow restart to properly occur, without first enabling the MUF.
The BACKUP AREA=CXX function has a new optional keyword DBID= which identifies the database to be backed up. If not specified, the function backs up the entire CXX as would have occurred in the previous release. With DBID= specified, the only output is the designated database. Only one DBID can be specified and only once, that is, you cannot specify a range of databases.
The COMM function has a new keyword IGN68= which makes it possible to ignore return code 68. IGN68= makes it easier to set up and run JCL incorporating a stack of DBUTLTY functions without requiring that the MUF be enabled. For example, IGN68= would be useful if you wanted to load a database, perhaps to allow restart to properly occur, without first enabling the MUF.
COMM OPTION=CANCEL has been removed.
The COMM STATS function flushes the pipeline for the database as part of pushing the STATS to the CXX, index, and data sets.
COMM STATUS has had changes to the COMM STATUS report.
The ALTER DBCS option of the DBUTLTY function CXXMAINT allows you to specify what kind of double-byte character set (DBCS) support you would like for your Directory (CXX). Information on how to use this option has been updated to indicate that, if using SQL, the MUF must be restarted after running this command.
The CXXMAINT OPTION=ALTER function uses the OPTION2=keyword to activate other features:
By default, when you convert an r11 CXX to a version 12 CXX, use of Single User mode is blocked for user programs, even if secured Single User is allowed. If you want to run Single User, you can use a new keyword, OPTION2=, when executing CXXMAINT.
To remove support for Single User, OPTION2=N_SU can be specified. This new option is provided to the full CXX report and has been added to the DB00271I MUF startup message
Running in Single User mode instead of Multi-User mode has been supported, but long recommended against. The Single User environment allows no logging and therefore has no restart or recovery capability. In addition, running in Single User bypasses external security. With these things in mind, the only uses of Single User mode that CA Datacom needs to continue to support are the DBUTLTY functions that run Single User and the DBFLSUB feature that loads an area with user program input. These exceptions of DBUTLTY and DBFLSUB are not affected by the N_SU option.
If a Single User open that is allowed occurs, message DB00138I is issued, confirming that fact and documenting the Single User execution.
The EXTBKUP function has a new option FORMAT=. If you do not specify FORMAT=, or if you specify FORMAT=EXTRACT, output is one or more extracted files, as was previously the case. If you specify FORMAT=BACKUP, the output is a single file in backup format with all records compressed by any option to be expanded. When FORMAT=BACKUP, you are required to have a previous single FILEOUT function to define the single output file, and in that FILEOUT function the keyword TABLE= must be set to *** (three asterisks) to specify that all tables are to be written to the output file.
THE LOAD function option AREA=CXX using DBID= has been moved to MUF. This move prevents you from running it with the database open. It also ensures that MUF is always in control and has knowledge of all information in the CXX, a normal case being a single MUF or MUFplex to a CXX.
If a user has a LOAD or RETIX function coded in their JCL with SORT=0 specified or defaulted, that is, SORT= not specified at all, this information is added to the history report, and the first time in each MUF execution that an area is opened in a database that has the LOAD or RETIX function coded without the sort option, an informational message is generated. The message alerts you to the condition and can therefore help you know to add the sort option, and then see the results.
Following are two new features that are also blocked during LOAD or RETIX executions when the sort option is not being used:
The RECOVERY OPTION=FORWARD function has a new optional URINUM= keyword to speed support when MULTUSE=YES is not specified. The URINUM= keyword is used at the direction of Technical Support to gather documentation about the processing of a specific URI number.
The DBUTLTY Impact Report (TYPE=I,AREA=CXX) has been enhanced to provide information about cases in which the disposition of a table is INDEX NOT LOADED after a catalog. In those cases, further information is provided regarding key-level status. That is, whether each individual key in the table is LOADED or NOT LOADED.
There are changes associated with certain messages related to the AREA=PXX report, and there are also changes with regard to the DUMPS=FULL and DUMPS=REQUEST options.
The count of records in a table, as known to the CXX, can become wrong if the MUF is restarted after a MUF outage occurs. The DBUTLTY RETIX function, with the KEYNAME=*SETR option, lets you recount the records and set the new value in MUF.
If a user has a LOAD or RETIX function coded in their JCL with SORT=0 specified or defaulted, that is, SORT= not specified at all, this information is added to the history report, and the first time in each MUF execution that an area is opened in a database that has the LOAD or RETIX function coded without the sort option, an informational message is generated. The message alerts you to the condition and can therefore help you know to add the sort option, and then see the results.
Following are two new features that are also blocked during LOAD or RETIX executions when the sort option is not being used:
The RXX report command summary that prints the occurrences of some commands now specifies the following for the MOVER command:
Specified for MOVER log records that were done for a record moved in support of the UPDAT command for compressed tables.
Specified for MOVER log records that were done for a record moved in support of the DBUTLTY OLREORG function.
The SET function has the following enhancements
You have a DBMSTLST comprised of numbers relating to the index and data buffers. Those numbers are often very small. In many DBUTLTY functions, the index and data buffers are not used at all. In other functions, they are used very little. But they are used a great deal in a few functions.
Because the functions that would benefit from more index and data buffers are few but can be very long running, the DBUTLTY SET function OPTION1= keyword makes it easier for you to have a general Master List as in previous releases, but to also have the ability to increase the buffers for needed functions in databases with a large number of records. Consider the following, for example:
The override values must be set prior to the first DBUTLTY function that opens as Single User. The following are the Master List-related DBUTLTY SET function OPTION1= enhancements:
The SPILLOPT function for z/VSE has the new keyword DEVICE= that specifies the device type for the output file.
Note: For more information, see the CA Datacom/DB DBUTLTY Reference Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|