Processing, DBUTLTY and SQL Messages › CA Datacom/DB Processing Messages (DB0xxxxc) › DB00137E

DB00137E

INVALID RELEASE DBSYSID MODULE - x

Reason:

This message occurs if the module loaded as DBSIDPR or equivalent is not compiled using a supported release of the DBSYSID Macro. The variable x is the name of the module loaded.

Note: For DBUTLTY, a DBSIDPR equivalent is named using the function SET OPTION1=SIDNAME=x where x is a module name. For users of the Multiple MUF Interface MMI, a DBSIDPR equivalent is the value specified for the SIDNAME= keyword in the DBURSTR Macro generating the User Requirements Table URT.

If this message occurs during the enable of a MUF, then the DBSIDPR module is not the result of assembling the DBSYSID Macro at the same version as the MUF.

If this message occurs during the execution of DBUTLTY, then the DBSIDPR module or equivalent is not the result of assembling the DBSYSID Macro at the same version as the DBUTLTY.

If this message occurs during the OPEN command to the CA Datacom interface (not DBUTLTY), then the module loaded is not the result of assembling the DBSYSID Macro at a supported version for the interface. For this case, the DBSYSID Macro must be assembled using one of the following methods:

• Use the same release as the interface release. This method is the normal case. With this method, the interface provides full support of the DBSYSID Macro options.
• Use the prior release to the interface release. This method is a special case to make upgrades a little easier. With this method, the interface provides full support of the DBSYSID Macro options.
• Use any prior release to the interface release back to r11. This method is a special case to allow CA Sysview to communicate to all MUFs on a System. With this method, the interface provides only the local support of the DBSYSID Macro options required by CA Sysview.

Action:

This message is an error and no execution is allowed. Provide a module that meets the required version compatibility as explained.