Version 14.0 › CA Datacom Tools Products › New Features and Enhancements › Automation of the Installation for the DB Subsystem › MUF Changes

MUF Changes

The following are changes that occur in MUF:

• The FORCE_SVC startup option is no longer needed. If specified, a message occurs indicating it is obsolete and ignored. Remove this option.
• The MUFMSG startup option defaults to YES,NO,YES and does not display the SVC number of 000. You can set it to YES in case there are message interception routines that skip over the message prefix based upon an expected size.
• The first MUF execution after an IPL installs the Version 14.0 Program Call PC routine DBPCCPR if it was not previously installed by CAIRIM or a previous Version 14.0 MUF.
• A new MUF startup option has been added, but only for testing or in the event of a serious memory overlay. X_FORCE_CAAT_REFRESH YES causes the MUF to abandon any previous Version 14.0 common memory and start fresh and instantly causes errors for existing Version 14.0 MUFs executing. The most likely symptom is RC 68, RC 86, or hung executing programs. If the common memory is overlaid and needs refreshing then other MUFs are not successfully running.

For more information, see the CA Datacom/DB Database and System Administration Guide.

Messages Added

• DB00205 - 1206 CACS CAAT ERROR NNN
• DB00205 - 1207 INSTALL SYSTEM ANCHOR FAILED
• DB00205 - 1208 DBSIDPR PC=INVALID
• DB00205 - 1209 UNABLE TO GET SYSTEM LINKAGE
• DB00205 - 1210 UNABLE TO CREATE DATA SPACE

Messages Changed

• DB00249I - message reflecting fields of the DBSIDPR being used, no longer prints the SUBID keyword and now prints the PC=value of either PROD or Test. For example:

  DB00249I - DBSIDPR 2010/09/14 10.19 SVC=000 TOGROUP=DBDVM0 CCISYS= PC=PROD

  Note: User programs use the same PC as the MUF selected.

• DB00201 - removed the SVC=nn

Messages Removed

• Existing DB00205 message number 1113
• DB00219I - MVS ECSA REQUIREMENT -9999,999 K

For more information, see the CA Datacom/DB Message Reference Guide.