CA Datacom/DB Return Codes › Explanation of Code Descriptions

Explanation of Code Descriptions

In the tables that list internal return codes, columns M and B indicate whether the error automatically generated a Master List dump (M) and a Master List dump with buffers (B). The specified dump was generated if the column contains a Y (YES) or if the column contains an N (NO) it is not generated. M-B combinations can be N-N, Y-Y, or Y-N but never N-Y. Be aware that the values for M and B listed in the tables are the default values and can be overridden if running the MUF. A few of the return codes indicate S-N, which means a special minimal (short) master List dump and no buffers. This minimal option saves time for the few codes that have small dump needs.

Note: This option is only available as a default and you cannot set it. However, you can override the option with either a Y (YES) setting or an N (NO) setting.

A return code of blanks indicates successful processing of the command. A non-blank return code indicates an error.

Many non-blank CA Datacom/DB return codes create a Master List SNAP dump, which contains the CA Datacom/DB task areas that are associated with the failing request. If you use the MUF start option (recommended as a best practice) of SYSOUT. For example, SYSOUT 0,1M,1M,1M,1M,1M The Master List snaps displays in the PXXML DD statement. If you do not have the SYSOUT option, the snap is written to the PXX. To obtain the PXX output, execute the REPORT AREA=PXX function of DBUTLTY according to directions supplied in the CA Datacom/DB DBUTLTY Reference Guide. A few return codes have a default of a Master List dump with buffers. If one of these errors occur, or another return code that you have overridden the option to set a ‘B’ buffer dump, then MUF handles this most efficiently by requesting a System dump (IPCS) of z/OS. Because buffer dumps are very large with the use of 64-bit memory for both the index and data areas, this System dump is faster in the creation.

Note: For more information on return codes, see the CA Datacom/DB Programming Guide.

The following chart maps to each application-sensitive return code those CA Datacom/DB commands most likely to generate that return code.

Note: When you contact CA Support and depending on the CA Datacom/DB return code that you received, certain output, reports, or dumps are required to diagnose the problem. The entries in the following topics indicate, by return code, the documentation that you need to have available before calling CA Support. For information about contacting CA Support, see the Troubleshooting topic that is located on the Version 15.0 bookshelf.