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

DB01413I

DEBUG a b c

Reason:

The following variables are replaced:

• a is replaced by OCS or OC3, the two subtasks that are involved in data set processing such as:
  • allocation of a DD statement
  • un-allocation of the statement
• b is replaced by a number that is the relative number of the subtask that issues the message. For example, 1 for the first OCS or first OC3.
• c is replaced by ALLOC, UNALLOC, EDIT_X or EDIT_Y
  • ALLOC is used during allocation
  • UNALLOC is used during un-allocation
  • EDIT_X is used during internal processing case 1
  • EDIT_Y is used during internal processing case 2
• d is replaced by the DDNAME of the data set that is being processed. For example, IXX1234 or PAY001.

An undocumented DIAGOPTION requested the message to note the dynamic allocation or unallocation of a DD statement. CA uses it for testing and it should not be needed at your site. If it is necessary to support a problem, the specific option is provided by CA Support.

Action:

If CA Support activates this message to debug a problem, they will provide the needed action. The message is informational.

DB01414E

ERROR HANDLING DBSIDPR DEBUG_TRACE x y z

Reason:

The DBSIDPR Macro option DEBUG_TRACE was activated as directed by CA Support to address a trace. However, the information that is provided cannot be used successfully to allocate the needed dataset.

• x is replaced by the DDNAME to use
• y is the data set name
• z is additional information for CA Support to analyze

Action:

None. This message is for information only.

DB01415E

DSN WRONG, DBSIDPR FORCE_DSN_CHAR ddname FOUND dsn

Reason:

The DBSYSID Macro option FORCE_DSN_CHAR provides a character string that is required to be in every system and database Data Set Name. It is not in the name of the data set being opened. In the message, the area being opened replaces the ddname, such as CXX or IXX001, The data set name that MVS provides replaces the dsn. The edit can be valuable in protecting that production and test environments do not get connected to each other’s data sets.

Action:

If the data set is wrong for this environment, correct as appropriate to only open correct datasets in this environment. In some cases, it might be necessary to rename a dataset to requirements. Also see message DB01416 as it always follows DB01415.

DB01416E

DSN WRONG, DBSIDPR FORCE_DSN_CHAR ddname REQUIRED x

Reason:

The DBSYSID Macro option FORCE_DSN_CHAR provides a character string that is required to be in every system and database Data Set Name. It is not in the name of the data set being opened. In the message, the area being opened replaces the ddname, such as CXX or IXX001, The required character string replaces the x.

Action:

See the action for message DB01415.