Skip to Content
Information
Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

MXDPA

Codes

Description

MXDPA0000I  DBPA Transaction processing has begun.

Explanation: Written to console log to denote that the DBPA Transaction Processing has begun.

System Action: None.

User Response: None.

Module: DBUGDBPA

MXDPA0001I  DBPA Transaction processing has ended.

Explanation: Written to console log to denote that the DBPA Transaction Processing has ended.

System Action: None.

User Response: None.

Module: DBUGDBPA

MXDPA0002E DBPA Transactions bypassed. Cannot load DBUGGBL.

Explanation: Written to console log to denote that the DBPA Transaction Processing cannot continue, as program DBUGGBL (the Global Table) could not be loaded.

System Action: No Code Debug CICS DBPA Transaction Processing will take place.

User Response: See to the output from the IVP (Installation Verification Program) to determine the reason.

Module: DBUGDBPA

MXDPA0013E DBPA Transactions bypassed. Wrong release of DBUGGBL.

Explanation: Written to console log to denote that the DBPA Transaction Processing cannot continue, as the wrong release of program DBUGGBL (the Global Table) was detected.

System Action: No Code Debug CICS DBPA Transaction Processing will take place.

User Response: See to the output from the IVP (Installation Verification Program) to determine the reason.

Module: DBUGDBPA

MXDPA0015EDBPA Transactions bypassed. Code Debug for CICS is not active.

System Action: This message is written to the console and the printed report.

User Response: Code Debug CICS must be active in order for DBPA Transaction Processing to take place.

Module: DBUGDBPA

MXDPA0017E DBPA Processing terminated. More than 1 abend detected.

Explanation: More than 1 abend was detected during processing.

System Action: DBPA Transaction Processing terminated.

User Response: Contact Code Debug CICS BMC Support.

Module: DBUGDBPA

MXDPA0018I Refer to the console log and printed report for additional messages.

Explanation: The XDBP transaction was run at a terminal. When processing is complete, this message is displayed at the terminal.

System Action: None.

User Response: Check the console log for possible errors. See to the printed report for DBPA transaction errors.

Module: DBUGDBPA

MXDPA0019E ON and OFF are invalid.

Explanation: Transaction images DBPA ON and DBPA OFF are not allowed as DBPA transactions when using the new input method.

System Action: Invalid input is ignored and processing continues.

User Response: Remove any DBPA ON or DBPA OFF transaction images from your input data set.

Module: DBUGDBPA

MXDPA0020E No DBPA Parameter Overrides found in CMSC PARMLIB.

Explanation: During the validation process of BMC PARMLIB XDDB prefixed members, no parameter overrides were found in the CMSC PARMLIB.

System Action: None.

User Response: If no overrides are required, no response is necessary. If overrides are required, verify that Code Debug CICS is correctly configured within the BMC AMI Common Mainframe Services Controller (CMSC). See the Code Debug CICS Installation and Configuration Guide for more information. Also,see to the Code Debug CICS System Facilities and Code Coverage Test Parameters report produced during Code Debug CICS initialization DBPA parameter processing. This report will list the XDDB prefixed members that are processed, the contents of those members, and the resulting values of the DBPA and Code Coverage Test Parameters being used.

Module: DBUGDBPA


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI DevX Code Debug for CICS 17.02