Online Help Messages

CA SymDump for CICS Online Messages › Online Help Messages

Online Help Messages

You can view the following messages in the CA SymDump for CICS online Help facility.

CASD3469

API FAILURE OCCURRED DURING CAPTURE

Reason:

During dump capture, program IN25STRU attempted to gather information for the abending task, but failed.

Action:

Verify that the security definitions for the abending task allow CA InterTest for CICS to perform the CICS inquiry commands necessary to complete dump capture. Carefully review the security violation logs and correct the problem. If necessary, contact your systems programmer.

CASD3470

CAPTURE FAILURE DUE TO NOTAUTH CONDITION

Reason:

During dump capture, program IN25STRU attempted to gather information for the abending task, but failed due to a NOTAUTH condition.

Action:

Verify that the security definitions for the abending task allow CA SymDump to perform the CICS inquiry commands necessary to complete dump capture. Carefully review the security violation logs and correct the problem. If necessary, contact your systems programmer.

CASD6048

SYMDUMP is suppressing the CICS dump

Reason:

Since CA SymDump for CICS has captured the dump, it is suppressing the CICS transaction dump.

Action:

None.

CASD6049

SYMDUMP R.0000 COLD ASM MM/DD/YYYY HH.MM

Reason:

This is an informational message always displayed when CA SymDump for CICS is started, showing the release of the product, and the assembly date and time for IN25COLD, the primary dump capture module.

Action:

None.

CASD6050

CICS WILL CAPTURE THIS DUMP

Reason:

Due to the options set in the CA SymDump for CICS PROTDMP file, CA SymDump for CICS is not suppressing the CICS dump. CICS will capture the dump as it would have normally.

Action:

None.

CASD6069

SYMDUMP INTERCEPT OF DUMP REQUEST FOR TRANSACTION NNNN: ABEND(NNNN),
TASK(XXXXX), TERMINAL ID(XXXX)

Reason:

Informational message denoting that CA SymDump for CICS has intercepted a transaction dump, with the attributes shown.

Action:

None.

CASD6070

SYMDUMP ANCHOR GETMAIN FAILURE ENCOUNTERED

Reason:

A catastrophic internal system failure has occurred.

Action:

Contact CA SymDump for CICS technical support.

CASD6071

A SYSTEM OR STORAGE DUMP HAS BEEN REQUESTED BY TRANSACTION NNNN DUMP CODE IS XXXXXXXX

Reason:

Informational message indicating that CA SymDump for CICS has intercepted a System or Storage dump with the code shown.

Action:

None.

CASD6072

SYMDUMP WILL NOT CAPTURE THIS DUMP

Reason:

Informational message indicating that CA SymDump for CICS will not capture the intercepted dump. There are other messages indicating why this action has been taken.

Action:

None.

CASD6073

SYMDUMP HAS CAPTURED THIS DUMP

Reason:

Informational message indicating that CA SymDump for CICS will capture the intercepted dump.

Action:

None.

CASD6074

SYMDUMP EXCLUSION SPECIFIED FOR THIS ABEND

Reason:

Informational message indicating that CA SymDump for CICS will not capture the intercepted dump, due to exclusion specified in the PROTDMP file. This is controlled through the CA SymDump for CICS Configuration screen (SYMI).

Action:

None.

CASD6077

SYMDUMP LSTACK GETMAIN FAILURE ENCOUNTERED

Reason:

A catastrophic internal system failure has occurred.

Action:

Contact CA SymDump for CICS technical support.

CASD6078

SYMDUMP TRACE GETMAIN FAILURE ENCOUNTERED

Reason:

A catastrophic internal system failure has occurred.

Action:

Contact CA SymDump for CICS technical support.

CASD6079

SYMDUMP STACK GETMAIN FAILURE ENCOUNTERED

Reason:

A catastrophic internal system failure has occurred.

Action:

Contact CA SymDump for CICS technical support.

CASD6080

DUPLICATE DUMP SUPPRESSION IN EFFECT

Reason:

Informational message indicating that duplicate dump suppression is active, and that the dump is being suppressed for that reason.

Action:

None.

CASD6081

STIMERM FAILURE, CANNOT CAPTURE DUMP

Reason:

A catastrophic internal system failure has occurred.

Action:

Contact CA SymDump for CICS technical support.

CASD6082

PROTDMP index exceeded, probable application program loop. Dump not captured.

Reason:

The number of index entries on the PROTDMP file has been exceeded. This is most likely due to a loop in the application program. CA SymDump for CICS was unable to capture the dump.

Action:

Correct the application program loop.

CASD6083

SYMDUMP subtask has exceeded cputime limit: possible loop at offset +00000.

Reason:

The CPU timer has been exceeded. Either this is a very large dump and it is truly taking this long for CA SymDump for CICS to capture it, or the subtask is looping.

Action:

Contact your systems programmer to determine if the subtask is looping or if the CPU timer needs to be increased.

CASD6084

SYMDUMP subtask has abended at offset +00000.

Reason:

During the dump capture process, the SymDump capture has abended at the given offset. CA SymDump has recovered from this abend but did not capture the dump. CA SymDump for CICS must take a normal transaction dump for the original application abend in this case.

Action:

For assistance, contact CA technical support.

CASD6085

SYMDUMP DOES NOT SUPPORT "C" LANGUAGE CAPTURE.

Reason:

CA SymDump for CICS does not support capture or redisplay of transaction dumps for C language programs.

Action:

CA SymDump for CICS will not suppress the CICS transaction dump for a C program dump request. Format and review the CICS transaction dump to determine its cause.

CASD6086

Dump is abbreviated.

Reason:

CA SymDump for CICS was unable to capture a complete dump of the abending/ dumping task for one of the following reasons:

CA SymDump for CICS is improperly installed
DFHPEP did not execute at termination of the abending task
The task abended recursively
The task is not eligible for a complete dump capture. This occurs for the following abend codes: ACRI, AELA, AELB, AEMP, AETA, AEXY, AEXZ, AFCY, AICH, AISX, AISX, AJCE, AJCG, AKC3, AMSC, APTA, ASCP, ASPA, ASP5, ATCH, ATCI, ATC7, ATCV, ATD3, ATMA, ATND, ATNI, ATPE, ATRA, AXF0, AXF4, AXSC, AZCN, AZIB, AZID, AZIE, AZI6, AZI7, AZI9, AZR3, AZVA, AZCT
The abend was produced by the CSNE transaction.

Action:

The dump is intact and can be viewed using CA SymDump for CICS. It should be sufficient to resolve most abends. However, if the message occurs for all captured dumps, contact your systems programmer to ensure that DFHPEP has been modified to link to IN25PEP, as described in the installation materials. If DFHPEP is set up correctly, refer to the CICS Recovery and Restart Guide for reasons why DFHPEP may not execute. If the message was generated for one of the last three reasons, no action is necessary.

CASD6101

ERROR IN DISPLAYING SYMDUMP

Reason:

The program has encountered an unusual condition and terminated processing.

Action:

Check the installation. Contact CA technical support.

CASD6102

SYMDUMP FILE IS NOT OPEN

Reason:

The CA SymDump for CICS file could not be accessed.

Action:

Use the CEMT command to check the status of the file and to determine why the file was closed.

CASD6103

INSUFFICIENT STORAGE TO DISPLAY SYMDUMP

Reason:

There is not enough free DSA storage in CICS to process a CA SymDump for CICS display request.

Action:

Check why CICS is short on storage and reenter the transaction.

CASD6104

I/O ERROR ON SYMDUMP FILE

Reason:

An error occurred during a read or write to the CA SymDump for CICS file.

Action:

Check the CICS log for any VSAM messages relating to the file.

CASD6105

A PROGRAM WAS NOT DEFINED OR WAS DISABLED

Reason:

One of the CA SymDump for CICS programs could not be located.

Action:

Check the installation instructions to determine all the PPT entries that must be defined in CICS.

CASD6106

A TWA WAS NOT DEFINED FOR THIS TASK

Reason:

The transaction invoking this display requires a TWA size to be defined.

Action:

Check the installation instructions to determine the correct TWA size for this task.

CASD6108

PROTDMP INDEX MISSING OR DAMAGED

Reason:

The dump of a program on the CA SymDump for CICS file is not valid.

Action:

Determine whether the problem occurs with other dumps as well. Contact CA technical support.

CASD6109

TCA NOT FOUND IN CAPTURED DUMP

Reason:

CA SymDump for CICS was unable to capture a complete transaction dump. A possible cause is storage corruption. The breakpoint display may not show the actual point of abend, but areas captured by CA SymDump for CICS will be available for your review.

Action:

Determine whether the problem occurs with other dumps as well. Contact CA technical support.

CASD6110

CURRENT PPT NOT FOUND IN DUMP

Reason:

Action:

Determine whether the problem occurs with other dumps as well. Contact CA technical support.

CASD6111

CURRENT PROGRAM NOT FOUND IN DUMP

Reason:

Action:

Determine whether the problem occurs with other dumps as well. Contact CA technical support.

CASD6112

PL/I STORAGE NOT FOUND IN DUMP

Reason:

Action:

Determine whether the problem occurs with other dumps as well. Contact CA technical support.

CASD6113

COBOL STORAGE NOT FOUND IN DUMP

Reason:

Action:

Determine whether the problem occurs with other dumps as well. Contact CA technical support.

CASD6114

CSA NOT FOUND IN CAPTURED DUMP

Reason:

Action:

Determine whether the problem occurs with other dumps as well. Contact CA technical support.

CASD6115

EIUS NOT FOUND IN CAPTURED DUMP

Reason:

Action:

Determine whether the problem occurs with other dumps as well. Contact CA technical support.

CASD6116

RSA NOT FOUND IN CAPTURED DUMP

Reason:

Action:

Determine whether the problem occurs with other dumps as well. Contact CA technical support.

CASD6117

TGT NOT FOUND IN CAPTURED DUMP

Reason:

Action:

Determine whether the problem occurs with other dumps as well. Contact CA technical support.

CASD6118

BACKTRACE TABLE NOT FOUND IN CAPTURED DUMP

Reason:

Action:

Determine whether the problem occurs with other dumps as well. Contact CA technical support.

CASD6119

AIBX not found in captured dump

Reason:

The AIBX was not available when the dump was captured, and therefore not available to be viewed.

Action:

Some dump display selections are unavailable for viewing.

CASD6122

Unable to resolve backtrace

Reason:

The backtrace is not available because the CICS Internal Trace did not have sufficient information to build the backtrace table.

Action:

No action required.

CASD6123

EIS not found in captured dump

Reason:

The EIS was not available when the dump was captured, so therefore not available to be viewed.

Action:

No action required.

CASD6124

Unable to resolve abending address

Reason:

CA SymDump for CICS was unable to determine the address where the program abended.

Action:

No action required.

CASD6125

Region is short‑on‑storage

Reason:

CICS is short on storage. The dump capture will be incomplete because CA SymDump for CICS is curtailing activity to help CICS recover from system stress.

Action:

Discuss the problem with your systems programmer. Determine the cause of the system stress and rectify it.

CASD6126

Captured dump is incomplete, cannot be displayed.

Reason:

This message indicates that CA SymDump for CICS failed during the dump capture process, and that the dump is incomplete and cannot be viewed. The user should contact systems programming to review the CICS message log for error messages indicating the cause of the failure, so that they may collect this and any related documentation (including SVC dumps that may have been produced) to report and forward the information to CA Level 1 technical support for problem resolution.

Action:

None.

CASD6127

Corrupt pointers found, dump may be incomplete.

Reason:

This message indicates that during the capture process, CA SymDump for CICS was unable to follow a storage or control block chain that normally would be found intact. CA SymDump for CICS proceeds to capture as much of the dump as possible and the user is able to use all the basic functions of CA SymDump for CICS to debug the abending task. There could be areas and functions normally available that are not available to the user in the dump. The problem is probably related to the task abend, and does not indicate a problem with CA SymDump for CICS.

Action:

Contact your Systems programmer to collect documentation, and determine the cause of the broken chain.

CASD6128

Dump is incomplete, task may have been purged.

Reason:

This message indicates that this task was purged from CICS, and because of this abnormal method of termination areas normally found during dump capture could not be located for capture. Because of this, CA SymDump for CICS tries to capture as much of the dump as possible, but the dump may be incomplete, or may not be available to the user for diagnostic purposes. This does not indicate a problem with CA SymDump for CICS.

Action:

Contact your Systems programmer to collect documentation, and determine the reason for the task purge.

CASD6129

SymDump shutdown is in progress

Reason:

CA SymDump for CICS is being shut down. No further dump captures can be performed.

Action:

None.

CASD6176

INTERTEST HELP FILE IS UNDEFINED, CLOSED OR DISABLED

Reason:

Information explaining the cause of your dump is stored on the HELP file, which cannot be accessed.

Action:

Define the HELP file correctly, and ensure that it is open and enabled.

CASD6177

INSUFFICIENT STORAGE TO PROVIDE REQUEST ‑ TRY LATER

Reason:

An internal storage request could not be honored by CICS.

Action:

For CICS 3.1 and above, check that the minimum EDSA specifications have been made according to instructions in the Installation Guide for CA SymDump for CICS. For all CICS release, review your system for excessive virtual and real storage utilization.

CASD6178

ERROR IN PROGRAM PROCESSING ‑ SEE DUMP

Reason:

A serious problem or abend occurred in your task.

Action:

Contact CA technical support for help in analyzing the dump.

CASD6179

FUNCTION NOT SUPPORTED

Reason:

An unsupported option number was entered on a menu.

Action:

Specify only valid option numbers that appear on the menu.

CASD6180

I/O ERROR ON INTERTEST HELP FILE

Reason:

A request for HELP file information resulted in and I/O error.

Action:

Ask your technical staff to check the usability of the disk and file.

CASD6181

PROGRAM: (*) HAS NOT BEEN DEFINED OR IS DISABLED

Reason:

A request to access CA SymDump for CICS program was not honored.

Action:

Check that the CA SymDump for CICS installation was completed and that no programs are disabled.

CASD6182

ABEND/DUMP CODE IS NOT ON INTERTEST HELP FILE

Reason:

Because the abend/dump code is not found in the HELP file, CA SymDump for CICS cannot analyze the reason for the abend.

Action:

To take advantage of the HELP facility, allow abends and dumps to use CICS default codes.

CASD6183

FORMATTING OF TRACE TABLE HAS FAILED ‑ REQUEST ABORTED

Reason:

Formatting of the trace table for display failed.

Action:

Submit this request later. If it fails again, contact CA technical support with the associated dumps.

CASD6184

A TRACE TABLE WAS NOT FOUND IN THIS DUMP

Reason:

Storage for the task that abended was probably corrupted. The formatted trace table cannot be displayed for this dump.

Action:

None.

CASD6185

NO SYMBOLIC DATA FOUND FOR THE ABENDING PROGRAM

Reason:

The source listing for the program that caused the abend cannot be displayed.

Action:

Recompile the abending program with the post‑processor and repeat the request.

CASD6186

REQUESTED AREA COULD NOT BE FOUND IN DUMP

Reason:

Storage for the task that abended was probably corrupted. This area of the task cannot be viewed.

Action:

None.

CASD6187

DUMP DATA COULD NOT BE RESOLVED FOR SYMBOLIC DISPLAY

Reason:

Either a work area could not be built because of storage constraints or the data areas in the dump were overlaid in such a way that CA SymDump for CICS could not resolve the symbolic information.

Action:

Use the TCA, TCTTE, EIB, trace table and other system areas to resolve the problem. The formatted versions of many of these areas can be displayed.

CASD6188

SYMBOLIC DATA MAY NOT BE COMPLETE

Reason:

The transaction that abended had an invalid storage chain. Therefore, some symbolic data may be missing.

Action:

Try to follow the storage chains to determine where the task was destroyed.

CASD6189

OPTION IS ONLY VALID FOR COBOL PROGRAMS

Reason:

This option is only valid for COBOL programs.

Action:

Select a valid option.

CASD6226

INSUFFICIENT STORAGE TO PROVIDE REQUEST ‑ TRY LATER

Reason:

An internal storage request could not be honored by CICS.

Action:

For CICS 3.1 and above, check that the minimum EDSA specifications have been made according to instructions in the Installation Guide for CA SymDump for CICS. For all CICS releases, review your system for excessive virtual and real storage utilization.

CASD6227

ERROR IN PROGRAM PROCESSING ‑ SEE DUMP

Reason:

A serious problem or abend occurred in your task.

Action:

Contact CA technical support for help in analyzing the dump.

CASD6228

PROGRAM: (*) HAS NOT BEEN DEFINED OR IS DISABLED

Reason:

A request to access CA SymDump for CICS program was not honored.

Action:

Check that the CA SymDump for CICS installation was completed and that no programs are disabled.

CASD6229

BOTTOM OF DATA

Reason:

The end of the data is displayed.

Action:

To see additional data, scroll up.

CASD6230

TOP OF DATA

Reason:

The top of the data is displayed.

Action:

To see additional data, scroll down.

CASD6231

INVALID COMMAND

Reason:

The command is not listed in the menu, or is contradicted by the PK key that was pressed.

Action:

Specify the correct command.

CASD6232

SCROLL LIMIT REACHED

Reason:

The maximum scroll limit has been reached.

Action:

Reduce the scroll amount, or scroll in the other direction.

CASD6233

NO TRACE ENTRIES WERE CAPTURED

Reason:

The trace cannot be displayed, because no entries were captured.

Action:

Determine if the problem occurs with other dumps as well. Contact CA technical support.

CASD6234

CURRENT FILTER MASK ENTRIES LISTED ABOVE

Reason:

Informational.

Action:

None.

CASD6235

(*) NOT FOUND, BOTTOM OF DATA REACHED

Reason:

The FIND command failed.

Action:

PF12 retrieves the command. Correct the entry and try again.

CASD6236

(*) NOT FOUND, TOP OF DATA REACHED

Reason:

The FIND command failed.

Action:

PF120 retrieves the command. Correct the entry and try again.

CASD6237

MASK ERROR, PLEASE RESPECIFY

Reason:

There was a mask format error.

Action:

Review the mask entries and correct the error.

CASD6238

GETMAINS WITHOUT FREEMAINS ARE HIGHLIGHTED

Reason:

The HOGM command has successfully located GETMAINs without freemains and has highlighted them.

Action:

Use the FIND HILITE command to locate the highlighted entries, or scroll to visually scan for them.

CASD6239

ALL GETMAINS HAVE MATCHING FREEMAINS

Reason:

The HOGM command did not find any unmatched getmains and freemains.

Action:

Review the filter selection mask to ensure that you have included all of the entries that you wanted to be checked.

CASD6241

PLACE STRING IN QUOTES OR REMOVE LEADING SPACES

Reason:

The FIND command could not be processed.

Action:

Correct the command and try again.

CASD6242

HIGHLIGHTING OF TRACE RECORDS HAS NOT BEEN PERFORMED

Reason:

A FIND HILITE command was issued, but there are not highlighted entries at this time.

Action:

Issue the HOGM command, and try again.

CASD6243

NO GETMAINS WERE FOUND, HIGHLIGHTING WAS NOT PERFORMED

Reason:

A HOGM command was issued, but there were no getmains in the trace entries.

Action:

Ensure that your filter mask is correct.

CASD6244

PLEASE ENTER A FIND ON THE COMMAND LINE

Reason:

PF5 Repeat FIND was entered, but there is no FIND command to repeat.

Action:

Specify a FIND command.

CASD6245

ROWS ARE LOGICAL "AND"S

Reason:

Each row is logically anded and used as a filter selection criteria.

Action:

None.

CASD6246

ROWS ARE LOGICAL "AND"S, COLUMNS ARE LOGICAL "OR"S

Reason:

Each row is logically anded, and the columns are logically ored.

Action:

None.

CASD6247

(*) FOUND IN ENTRY (*)

Reason:

The FIND command located the specified string in the specified entry.

Action:

None.

CASD6250

SYMDUMP/CICS COULD NOT LOCATE THE TRACE FORMAT REGION

Reason:

To format the CICS trace entries, CA SymDump for CICS must locate the Trace Formatting Region within your existing CCI NETWORK. In this case, this region could not be found. Either the region has not been started, or the IN25OPTS TRCFFMID is incorrect.

Action:

Contact your Systems Programmer for resolution.

CASD6251

CCI INIT FAILURE ‑ SEE DUMP

Reason:

While trying to format your CICS trace entries, CA SymDump for CICS needed to perform an initialization call to CCI SERVICES within your CCI NETWORK. This call failed. A dump has been produced, and there may also be diagnostic messages produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION SYSPRINT file.

Action:

Contact your Systems Programmer with this information.

CASD6252

IN25OPTS MISSING OR INCORRECT

Reason:

CA SymDump for CICS was unable to locate a proper IN25OPTS module. Processing cannot continue.

Action:

Contact your Systems Programmer. Determine why the IN25OPTS module cannot be located and resolve the issue.

CASD6253

CCI CONVERSE FAILURE ‑ SEE DUMP

Reason:

While formatting your CICS trace entries CA SymDump for CICS uses CCI SERVICES to enable communication between CICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI call has failed. A dump has been taken and there will be diagnostic messages produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION SYSPRINT file.

Action:

Record this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CASD6254

SUBTASK SEND FAILURE ‑ SEE DUMP

Reason:

Action:

Record this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CASD6255

INSUFFICIENT STORAGE TRY AGAIN LATER

Reason:

During Trace Formatting, a CICS getmain request failed due to insufficient storage. You are advised to try the request again to see if the storage has become available.

Action:

Try request again. If the problem persists, contact your Systems Programmer to review the virtual storage limits specified for your CICS region, and increase these as needed.

CASD6256

IN25BTRC FORMAT CONVERSE TIMEOUT, TRY AGAIN LATER

Reason:

While formatting your CICS trace entries CA SymDump for CICS uses CCI SERVICES to enable communication between CICS and the TRACE FORMAT REGION within your CCI NETWORK. To ensure that finite resources are not wasted when the terminal is unattended, or during a system slowdown, a timeout limit is specified in the IN25OPTS for your CICS region. In this case the timeout limit has been exceeded.

Action:

This may occur normally due to system loads. If the problem persists, contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation. Review the IN25OPTS parameter TRCFTOUT for controlling the timeout duration.

CASD6257

TRACE TIMEOUT, ALL FILTERS AND OVERRIDES HAVE BEEN RESET

Reason:

Action:

This may occur normally due to system loads, or the operator has not solicited any terminal output for longer than the timeout limit specified in IN25OPTS. If the problem is persistent, contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation. Review the IN25OPTS parameter TRCFTOUT for controlling the timeout duration.

CASD6258

(*) hilited in (*) entries

Reason:

This is a purely informational message in response to a HILITE or 'H' command having been entered on the command line. All occurrences of a specified string have been located, and the entries are highlighted.

Action:

None.

CASD6259

IN25BTRC CCI CONVERSE ‑ (*)

Reason:

While formatting your CICS trace entries CA SymDump for CICS uses CCI SERVICES to enable communication between CICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI call has failed. A dump may have been taken and diagnostic messages are produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION SYSPRINT file.

Action:

Record this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CASD6260

IN25DTRC CCI CONVERSE ‑ (*)

Reason:

While formatting your CICS trace entries CA SymDump for CICS uses CCI SERVICES to enable communication between CICS and the TRACE FORMAT REGION within your CCI NETWORK. A CCI call has failed. A dump may have been taken and diagnostic messages are produced to the CICS MSGUSR queue and/or the TRACE FORMAT REGION SYSPRINT file.

Action:

Record this message number, and the time/date of the occurrence. Contact your systems programmer for resolution. They may need to contact CA technical support with the appropriate documentation.

CASD6261

MAXIMUM THREADS REACHED FOR TRACE FORMAT, TRY AGAIN LATER

Reason:

While formatting your CICS trace entries CA SymDump for CICS uses CCI SERVICES to enable communication between CICS and the TRACE FORMAT REGION within your CCI NETWORK. Trace formatting also requires a considerable amount of virtual storage. To ensure that resource limits are not exceeded, a thread limit is specified in the IN25OPTS for your CICS region. In this case the thread limit has been exceeded, and you are advised to wait until a thread becomes available.

Action:

This may occur normally due to system loads. If the problem persists, Contact your Systems Programmer for resolution, by reviewing and possibly increasing the IN25OPTS TRCFTHRD value specified.

CASD6262

INSUFFICIENT STORAGE FOR TRACE FORMAT, TRY AGAIN LATER

Reason:

Formatting your CICS trace entries requires a considerable amount of virtual storage. To ensure that resource limits are not exceeded, a maximum total storage limit is specified in the IN25OPTS table used by the TRACE FORMAT REGION. In this case, this maximum total storage limit for all concurrent threads has been exceeded.

Action:

This may occur normally due to system loads. If the problem persists, Contact your Systems Programmer for resolution, by reviewing and possibly increasing the IN25OPTS TRCFMEGM value specified.

CASD6263

TRACE SIZE BEYOND OPTS LIMIT, CONTACT SYSTEMS PROGRAMMER.

Reason:

Formatting your CICS trace entries requires a considerable amount of virtual storage. To ensure that resource limits are not exceeded, a maximum thread storage limit is specified in the IN25OPTS table used by the TRACE FORMAT REGION. In this case, this maximum thread storage limit has been exceeded by the selected trace.

Action:

Contact your Systems Programmer for resolution, by reviewing and possibly increasing the IN25OPTS TRCFMEGT value specified.

CASD6264

TRACE TIMEOUT, OVERRIDES ARE RESET, FILTERS ARE RETAINED.

Reason:

Action:

CASD6275

TWA SIZE IS SMALLER THAN REQUIRED AMOUNT

Reason:

The TWA size for transaction SYMD is incorrect.

Action:

See the Installation Guide for the minimum length requirement and correct the TWA size entry.

CASD6276

ONLY 'S', 'D', 'H' AND 'R' ARE VALID SELECT LETTERS

Reason:

You did not specify a valid letter.

Action:

Correct the selection.

CASD6277

INSUFFICIENT STORAGE TO PROVIDE REQUEST ‑ TRY LATER

Reason:

There isn't enough storage in the CICS region to process this request.

Action:

Contact your systems programmer. If the problem cannot be resolved, contact CA technical support.

CASD6278

ERROR IN PROGRAM PROCESSING ‑ SEE DUMP

Reason:

The program has encountered an unusual condition and terminated processing.

Action:

Print the dump, and contact CA technical support.

CASD6279

SYMDUMP DUMP DISPLAY FACILITY HAS ENDED

Reason:

Program termination was requested by the user with PF4.

Action:

To display dumps again, reenter the transaction.

CASD6280

TOP OF DATA

Reason:

You have used PF7 to scroll to the beginning of the dump list. The first item on the list is the most recent dump.

Action:

Use PF8 to scroll forward, if desired.

CASD6281

BOTTOM OF DATA

Reason:

You have used PF8 to scroll to the bottom of the dump list.

Action:

Scroll backward using PF7, if desired.

CASD6282

I/O ERROR IN FILE PROCESSING

Reason:

An error has occurred during a READ or WRITE to the CA SymDump for CICS file.

Action:

Check the CICS log for any VSAM messages relating to the file.

CASD6283

FILE IS NOT OPEN

Reason:

The CA SymDump for CICS file could not be accessed.

Action:

Use the CEMT command to check the status of the file and to determine why the file was closed.

CASD6284

REMOTE FILE CANNOT BE ACCESSED

Reason:

A READ or WRITE command issued to a remote file failed to complete successfully.

Action:

Check the file definition and the CICS connection to the remote system.

CASD6285

FILE IS NOT DEFINED

Reason:

The CA SymDump for CICS file could not be accessed because it was not defined in CICS.

Action:

Check the FCT definition for the file in CICS and reenter the transaction.

CASD6286

PRESS ENTER TO CONFIRM DELETE

Reason:

D was entered next to a dump, requesting that the entry be deleted.

Action:

Press Enter to delete the dump from the file. Any other entry cancels the delete request.

CASD6287

INVALID DATE SUPPLIED

Reason:

The date specified in the selection criteria was not in the form mmddyy, or the month, day and year that you specified was not valid.

Action:

Specify a valid day, month and year.

CASD6288

INVALID TIME SUPPLIED

Reason:

The time specified in the selection criteria was not in the form hh or the hour was not within the range of 0 to 24.

Action:

Specify a valid hour parameter.

CASD6289

INVALID DUMP FILE NAME SUPPLIED

Reason:

The file name specified may not defined in the FCT, or the SYMDWILD= option is specified in IN25OPTS and your wildcard specification is invalid.

Action:

Define the file in the FCT, and review your SYMDWILD= value. Reenter the transaction criteria specification.

CASD6290

NO FILE ENTRIES MATCH THE SEARCH CRITERIA

Reason:

No dump entries were found on the CA SymDump for CICS file that corresponded to the criteria specified.

Action:

Check the criteria and alter the specifications, if desired, or use PF4 to exit.

CASD6292

DUMP NO LONGER EXISTS

Reason:

The dump requested has been deleted either by an explicit delete request or by CA SymDump for CICS (if the dump was not being HELD).

Action:

None.

CASD6293

OVERFLOW IN FREESPAN AREA OF SYMDUMP FILE

Reason:

Too many freespace fragments on a CA SymDump for CICS file caused an overflow of the freespan list.

Action:

Delete any unnecessary dumps.

CASD6294

PROGRAM IN25COLD NOT FOUND

Reason:

The IN25COLD program was not found in the PPT or could not be loaded.

Action:

If CA SymDump for CICS is being used in this CICS system for analysis only, no action is required. If CA SymDump for CICS is also going to be used to capture dumps in this system, you must determine why the program cannot be found or loaded.

CASD6295

SYMDUMP FILE IS FULL

Reason:

There is not enough free space on the CA SymDump for CICS file for more dumps.

Action:

Delete unnecessary dumps.

CASD6296

SYMDUMP FILE IS WRONG FORMAT

Reason:

The PROTDMP file was not properly initialized and cannot be used. CICS 3.1 and above users of CA SymDump for CICS cannot use the same PROTDMP file as CICS 2.1 and below users.

Action:

Initialize PROTDMP correctly.

CASD6297

Try function later, Dump in progress

Reason:

The PROTDMP file is busy capturing a dump and cannot process your request right now.

Action:

Try the request again later.

CASD6298

I/O error on CA SymDump file ‑ notify systems programmer

Reason:

There was an I/O error on the CA SymDump for CICS file.

Action:

Notify your systems programmer.

CASD6299

Abend in DSP0, vsam acb open ‑ notify systems programmer

Reason:

There was an abend in IN25DSP0.

Action:

Notify your systems programmer.

CASD6300

Dump is already held

Reason:

An attempt was made to HOLD a dump that had previously been marked HOLD.

Action:

No action required.

CASD6301

Dump is already released

Reason:

An attempt was made to release a dump that had been previously released.

Action:

No action required.

CASD6301

SORT command syntax is invalid

Reason:

The SORT command was specified incorrectly. Valid syntax for the SORT command is:

SORT {DUMPFILE|TRAN|PROGRAM|OFFSET|ABEND|CREATED} {A|D}

The second parameter signifies which column to SORT by and the third parameter signifies whether to SORT in ascending or descending order. If you do not specify a third parameter, the default is ascending.

If you specify the SORT command without parameters, the default SORT sequence is used, which is descending date‑time within Dump File Id.

Action:

Correct the command and retry.

CASD6375

CICS INTERNAL TRACE HAS BEEN CAPTURED BY SYMDUMP

Reason:

The SYMT transaction has successfully captured the CICS internal trace.

Action:

None.

CASD6376

PROGRAM (*) WAS NOT FOUND

Reason:

One of the CA SymDump for CICS programs could not be located.

Action:

Check the installation instructions to determine all the PPT entries that must be defined in CICS.

CASD6377

SYMDUMP NOT STARTED, TRACE CAPTURE NOT PERFORMED

Reason:

CA SymDump for CICS must be started before you can issue the SYMT transaction.

Action:

Start CA SymDump for CICS, and reenter the SYMT transaction.

CASD6378

SYMDUMP UNABLE TO CAPTURE TRACE, PROTDMP IS FULL

Reason:

The SYMT transaction could not capture the CICS internal trace because the PROTDUMP file is full.

Action:

Delete entries from the PROTDUMP file, or redefine it, then the SYMT transaction will work.

CASD6379

SYMDUMP UNABLE TO CAPTURE TRACE, INSUFFICIENT SPACE ON PROTDMP

Reason:

The SYMT transaction could not capture the CICS internal trace because the PROTDUMP file is full.

Action:

Delete entries from the PROTDUMP file, or redefine it, then the SYMT transaction will work.

CASD6380

SYMDUMP UNABLE TO CAPTURE TRACE DUE TO GETMAIN FAILURE

Reason:

The SYMT transaction could not capture the CICS internal trace because a getmain request could not be satisfied.

Action:

Examine the CICS message log for other messages that explain the lack of storage. Examine the size of the CICS internal trace table and reduce the size prior to re‑executing the trace capture.

CASD6509

ABENDED TASK (*) STORAGE (*)

Reason:

This message identifies which storage area captured by CA SymDump for CICS is currently being displayed using the CORE facility. A list of CA SymDump for CICS tags and their related storage block areas are listed in the CA SymDump for CICS User Guide.

Action:

None.

CASD6510

INVALID ADDRESS, NOT CAPTURED BY SYMDUMP

Reason:

Storage at the requested address was not captured by CA SymDump for CICS at the point of abend, and is not available for a CORE display.

Action:

Review the request. Refer to the CA SymDump for CICS User Guide for a list of storage areas that CA SymDump for CICS captures. Modify the request appropriately.

CASD6511

SSCR DATA STREAM INCOMPLETE, CAPTURED DATA DISPLAYED

Reason:

The SSCR data stream was incomplete, but as much data as was captured has been displayed.

Action:

None.

CASD6512

SSCR DATA HAS EXTENDED ATTRIBUTES (NOT SUPPORTED ON THIS TERMINAL)

Reason:

This terminal does not support the extended attributes needed to display the screen.

Action:

Retry this request from a terminal that supports extended attributes.

CASD6550

SQLCODE ‑NNN OCCURRED DURING DUMP CAPTURE

Reason:

This error occurs during the CA SymDump for CICS transaction dump capture process. The query issued to obtain the Last SQL Statement failed due to reasons explained by the SQLCODE information in the message. CA SymDump for CICS was unable to obtain the Last SQL Statement issued by the application.

Action:

See the SQLCODE in the DB2 Messages and Codes manual for a detailed explanation of why the failure occurred. Correct the problem so that this does not occur in the future.

CASD6551

CA SYMDUMP/CICS HAS PRODUCED AN EXT2 TRANSACTION DUMP FOR THE FOLLOWING REASON

Reason:

This error occurs during the CA SymDump for CICS transaction dump capture process. For some reason the secondary phase of the transaction dump capture where the LASTSQL information would be written to the PROTDMP file was not completed. An EXT2 transaction dump was produced to aid in diagnosis. Error message CASD6552 contains additional information.

Action:

Review message code CASD6552, which accompanies CASD6551. Contact CA technical support for additional help if the problem cannot be resolved with the information provided in the message text.

CASD6552

TASK NNNNN XXXXXX

Reason:

Action:

Review message code CASD6552, which accompanies CASD6551. Contact CA technical support for additional help if the problem cannot be resolved with the information provided in the message text.

CASD6607

INSUFFICIENT STORAGE TO PROVIDE REQUEST ‑ TRY LATER

Reason:

An internal storage request could not be honored by CICS.

Action:

For CICS 3.1 and above, check that the minimum EDSA specifications have been made according to instructions in the Installation Guide. For all CICS releases, review your system for excessive virtual and real storage utilization.

CASD6608

ERROR IN PROGRAM PROCESSING ‑ SEE DUMP

Reason:

The transaction that abended had an invalid storage chain. Therefore, some symbolic data may be missing.

Action:

Try to follow the storage chains to determine where the task was destroyed.

CASD6609

PROGRAM: (*) HAS NOT BEEN DEFINED OR IS DISABLED

Reason:

A request to access CA SymDump for CICS program was not honored.

Action:

Ask your technical staff to check the usability of the disk and file.

CASD6801

ERROR IN INITIATING SYMDUMP

Reason:

The program has encountered an unusual condition and terminated processing.

Action:

Check the product's installation. Contact CA technical support.

CASD6802

PROGRAM (*) WAS NOT FOUND

Reason:

The specified program was not found in the PPT.

Action:

Check the installation procedure and correct any errors.

CASD6803

NO VALID REQUEST WAS FOUND

Reason:

The CA SymDump for CICS initialization program did not receive a valid start request.

Action:

Check the Installation Guide for the necessary PCT definitions.

CASD6804

SYMDUMP HAS INITIALIZED SUCCESSFULLY

Reason:

A start request has been issued using the CA SymDump for CICS primary menu (option 2) and the function has completed successfully.

Action:

Dumps will now be written to the CA SymDump for CICS file.

CASD6805

REQUEST REJECTED DUE TO INSUFFICIENT VIRTUAL STORAGE ‑ TRY LATER

Reason:

There isn't enough free DSA storage in CICS to fill a storage request.

Action:

Check why CICS is short on storage and reenter the transaction.

CASD6806

"END" REQUEST REJECTED. ERROR CODE: (*)

Reason:

A VSAM error was encountered during processing of an END request. CA SymDump for CICS was not terminated.

Action:

Check the VSAM manual for an explanation of the error code.

CASD6807

START REQUEST FAILED

Reason:

CA SymDump for CICS could not be started because of a VSAM error encountered during OPEN processing.

Action:

Use the CEMT command to determine the status of the file.

CASD6808

START REQUEST REJECTED. ERROR CODE: (*)

Reason:

CA SymDump for CICS could not be started because of a VSAM error encountered during OPEN processing.

Action:

Check the VSAM manual for an explanation of the error code.

CASD6809

START REQUEST PROCESSED. WARNING CODE: (*)

Reason:

The CA SymDump for CICS file was opened successfully, but VSAM has issued a warning during OPEN processing.

Action:

Check the VSAM manual for an explanation of the error code.

CASD6810

SYMDUMP HAS BEEN INITIALIZED BUT PARAMETERS HAVE NOT BEEN LOADED

Reason:

CA SymDump for CICS initialization has completed successfully, but no valid initialization parameters were found on the CA SymDump for CICS file.

Action:

Default parameters will be used during processing.

CASD6811

SYMDUMP HAS ENDED

Reason:

An end request has been issued from the CA SymDump for CICS primary menu (option 3) and CA SymDump for CICS has been terminated.

Action:

Dumps will now be written to the CICS dump file.

CASD6812

PROGRAM IN25COLD IS THE WRONG RELEASE

Reason:

The release of program IN25COLD does not match the release of the IN25INST program.

Action:

Perform the following steps:

Run the transaction VRPT and use option 4 to check for any other programs that may be the wrong release.
Check that all CA SymDump for CICS programs are coming from the same library.
Recheck the outputs produced during installation.

CASD6813

A CA LMP RIMSTAT ERROR HAS BEEN DETECTED

Reason:

LMP check failed for CA SymDump for CICS.

Action:

Contact CA technical support.

CASD6814

SYMDUMP WAS ALREADY STARTED

Reason:

CA SymDump for CICS has already been started.

Action:

None.

CASD6815

SYMDUMP WAS ALREADY TERMINATED

Reason:

CA SymDump for CICS has already been terminated.

Action:

None.

CASD6816

SYMDUMP FILE IS WRONG FORMAT

Reason:

The PROTDMP file was not properly initialized and cannot be used. CICS 3.1 and above users of CA SymDump for CICS cannot use the same PROTDMP file as CICS 2.1 and below users.

Action:

Initialize PROTDMP correctly.

CASD6817

User is not authorized to issue request

Reason:

This user is not authorized to do this request.

Action:

Obtain proper authority and then re‑issue the request.

CASD6818

Global exit program IN25STRU is not enabled

Reason:

Program IN25STRU is required for proper dump capture, but is currently not available.

Action:

Notify your systems programmer.

CASD6951

INVALID INPUT DATA FOUND

Reason:

The data entered where the cursor is positioned is not valid.

Action:

Specify valid data in the field.

CASD6952

INSUFFICIENT STORAGE TO PROVIDE REQUEST ‑ TRY LATER

Reason:

There isn't enough free DSA storage in CICS to fill a storage request.

Action:

Determine why CICS is short on storage and reenter the transaction.

CASD6953

RROR IN PROGRAM PROCESSING ‑ SEE DUMP

Reason:

The program has encountered an unusual condition and terminated processing.

Action:

Print the dump and contact CA technical support.

CASD6954

SYMDUMP INITIALIZATION PROCESSING HAS ENDED

Reason:

The user requested program termination with PF4.

Action:

To redisplay the initialization menu, reenter the transaction.

CASD6955

OPTION IS NOT AVAILABLE

Reason:

The transaction through which this option is invoked is not defined in CICS.

Action:

Define the appropriate transactions in CICS as specified in the Installation Guide.

CASD6956

PARAMETERS HAVE BEEN UPDATED BY ANOTHER TASK ‑ ENTER AGAIN

Reason:

While the current parameters were displayed, another task has updated the parameters. The new parameters are now displayed.

Action:

Specify the changes again, and ensure that another user is not currently updating the parameters. Enter option 1 again to update the file.

CASD6957

SYMDUMP PARAMETERS HAVE BEEN UPDATED

Reason:

Update of CA SymDump for CICS parameters (option 1) was requested and processing has successfully completed.

Action:

None.

CASD6958

INVALID OPTION ‑ ENTER 1, 2, OR 3

Reason:

The command specified on the command line was not valid.

Action:

Specify a valid option or END.

CASD6959

PROGRAM IN25COLD NOT FOUND

Reason:

The IN25COLD program was not active in the PPT or could not be loaded.

Action:

Check all installation steps, correct any errors, and resubmit the job. Dumps will not be captured until this error is corrected.

CASD6960

SYMDUMP IS ACTIVE

Reason:

CA SymDump for CICS is active.

Action:

None.

CASD6961

SYMDUMP IS NOT ACTIVE

Reason:

CA SymDump for CICS is not active.

Action:

None.

CASD6962

SYMDUMP IS ACTIVE; SYMDUMP FILE IS FULL

Reason:

CA SymDump for CICS is active. However, there is not enough free space on the CA SymDump for CICS file for more dumps.

Action:

Delete any unnecessary dumps or release dumps currently being held.

CASD6963

SYMDUMP IS NOT ACTIVE; SYMDUMP FILE IS FULL

Reason:

CA SymDump for CICS is not active. However, there is not enough free space on the CA SymDump for CICS file for more dumps.

Action:

Delete any unnecessary dumps or release dumps currently being held.

CASD6964

I/O ERROR IN DUMP FILE PROCESSING

Reason:

The CA SymDump for CICS file specified could not be opened.

Action:

Check the installation procedures.

CASD6965

(*) FILE IS NOT OPEN

Reason:

The CA SymDump for CICS file specified could not be opened.

Action:

Check the installation procedures.

CASD6966

REMOTE DUMP FILE CANNOT BE ACCESSED

Reason:

The CA SymDump for CICS file specified could not be opened.

Action:

Check the installation procedures.

CASD6967

(*) FILE IS NOT DEFINED

Reason:

The FCT entry for the specified CA SymDump for CICS file could not be found.

Action:

Check the installation procedures.

CASD6968

(*) FILE IS NOT INITIALIZED, OR IS DAMAGED

Reason:

CA SymDump for CICS could not read the first record on the CA SymDump for CICS dump file.

Action:

Check the installation procedures.

CASD6969

Press ENTER to confirm parameter update request; PF3 to cancel

Reason:

This is a confirmation warning.

Action:

If you are sure you want to update the configuration parameters, press enter; otherwise press PF3 to cancel.

CASD6970

I/O error on CA SymDump file ‑ notify systems programmer

Reason:

There was an I/O error on the CA SymDump for CICS file.

Action:

Notify your systems programmer.

CASD6971

Try function later, Dump in progress

Reason:

The PROTDMP file is busy capturing a dump and cannot process your request right now.

Action:

Try the request again later.

CASD6972

Abend in DSP0, vsam acb open ‑ notify system programmer

Reason:

There was an abend in IN25DSP0.

Action:

Notify your systems programmer.

CASD7007

INSUFFICIENT STORAGE TO PROVIDE REQUEST ‑ TRY LATER

Reason:

An internal storage request could not be honored by CICS.

Action:

For CICS 3.1 and above, check the minimum EDSA specifications have been made according to instructions in the Installation Guide. For all CICS releases, review your system for excessive virtual and real storage utilization.

CASD7008

ERROR IN PROGRAM PROCESSING ‑ SEE DUMP

Reason:

A serious problem or abend occurred in your task.

Action:

Contact CA technical support.

CASD7011

PROGRAM: (*) HAS NOT BEEN DEFINED OR IS DISABLED

Reason:

The dump of a program on the CA SymDump for CICS file is not valid.

Action:

Determine whether the problem occurs with other dumps as well. Contact CA technical support.

CASD7207

INSUFFICIENT STORAGE TO PROVIDE REQUEST ‑ TRY LATER

Reason:

An internal storage request could not be honored by CICS.

Action:

For CICS 3.1 and above, check the minimum EDSA specifications have been made according to instructions in the Installation Guide. For all CICS releases, review your system for excessive virtual and real storage utilization.

CASD7208

ERROR IN PROGRAM PROCESSING ‑ SEE DUMP

Reason:

A serious problem or abend occurred in your task.

Action:

Contact CA technical support.

CASD7211

PROGRAM: (*) HAS NOT BEEN DEFINED OR IS DISABLED

Reason:

A request to access CA SymDump for CICS program was not honored.

Action:

Ensure that CA SymDump for CICS installation was completed and that no programs are disabled.

CASD7301

INSUFFICIENT STORAGE TO VERIFY FILE ‑ TRY LATER

Reason:

There is not enough storage at this time.

Action:

Try later when more storage is available.

CASD7302

ERROR IN PROGRAM PROCESSING ‑ SEE DUMP

Reason:

An abend occurred.

Action:

Analyzed the dump.

CASD7303

I/O ERROR ON DUMPFILE

Reason:

The dump file definitions did not allow reading, browsing or updating of the file.

Action:

Fix the file definitions, and try again.

CASD7304

LOST RECORD SPAN RECLAIMED TO FREESPANS OF SYMDUMP FILE

Reason:

CA SymDump for CICS has internally freed space in the file. This may have occurred because the index section of the file was about to overflow.

Action:

None. If this happens too often, contact CA technical support.

CASD7305

BAD FREE SPAN REMOVED FROM LIST OF SYMDUMP FILE

Reason:

CA SymDump for CICS has internally freed space in the file. This may have occurred because the index section of the file was about to overflow.

Action:

None. If this happens too often, contact CA technical support.

CASD7306

RECORDS HAVE BEEN FOUND TO BELONG TO TWO OR MORE SYMDUMPS

Reason:

Records belong to multiple CA SymDump for CICS data sets, which is a problem that should not occur.

Action:

Print the first five records in the file, and contact CA technical support.

CASD7308

SYMDUMP FILE NOT REPAIRED ‑ VERIFICATION TO BE RETRIED

Reason:

During verification, a new dump was written to the file. The verification must be repeated.

Action:

None.

CASD7309

SYMDUMP FILE COULD NOT BE REPAIRED ‑ VERIFICATION ABORTED

Reason:

During verification, a new dump was written to the file. This has happened twice. The verification must be tried later when the system is less active.

Action:

None.

CASD7400

IN25EXIT does not have required global work area.

Reason:

During dump capture, program IN25STRU failed due to a catastrophic internal failure.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7401

SymDump cannot process this abend.

Reason:

During dump capture, program IN25STRU failed due to a catastrophic internal failure.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7402

GETMAIN failure in IN25EXIT for thread ECB.

Reason:

During dump capture, program IN25STRU failed due to a catastrophic internal failure.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7403

IN25EXIT failure on MVS_WAIT (exception).

Reason:

During dump capture, program IN25STRU failed due to a catastrophic internal failure.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7404

IN25EXIT failure on MVS_WAIT (invalid).

Reason:

During dump capture, program IN25STRU failed due to a catastrophic internal failure.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7405

IN25EXIT failure on MVS_WAIT (kernerror).

Reason:

During dump capture, program IN25STRU failed due to a catastrophic internal failure.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7406

IN25EXIT failure on MVS_WAIT (purged).

Reason:

During dump capture, program IN25STRU failed due to a catastrophic internal failure. This may be due to the operator purging tasks that were in the process of dump capture.

Action:

Save all output, including the complete JESLOG and any dumps produced. Review the CICS log for signs of system stress. If you cannot determine the cause of the task purges, contact CA technical support.

CASD7407

IN25EXIT failure on MVS_WAIT (disaster).

Reason:

During dump capture, program IN25STRU failed due to a catastrophic internal failure.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7409

Terminal receive failure in IN25STRU

Reason:

During dump capture, program IN25STRU attempted to capture the current contents of the 3270 screen, but failed.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7410

API failure IN25STRU

Reason:

During dump capture, program IN25STRU attempted to gather information for the abending task, but failed.

Action:

Verify that the security definitions for the abending task allow CA SymDump for CICS to perform the CICS inquiry commands necessary to complete dump capture. Carefully review the security violation logs, and correct the problem. If necessary, contact your systems programmer.

CASD7411

Dump capture will be incomplete.

Reason:

During dump capture, CA SymDump for CICS was unable to capture a complete dump. Other messages may indicate the reason for the problem.

Action:

Review the dump, as it may still be useful. If it is unusable and you cannot determine the cause of the failure, contact CA technical support.

CASD7412

A system or storage dump has been requested by transaction nnnn dump code is xxxxxxxx (task xxx).

Reason:

CA SymDump for CICS has intercepted a system dump request, but does not capture system dumps. This is an informational message, which is displayed if messages to the console are enabled through SYMI.

Action:

None.

CASD7413

SymDump will not capture this dump.

Reason:

Check for other messages which indicate why the dump was not captured. This is an informational message, which is displayed if messages to the console are enabled through SYMI.

Action:

None.

CASD7414

SymDump is suppressing the CICS dump.

Reason:

The configuration options 'Suppress AP0001 dumps' and/or 'Suppress transaction dumps' have been set to 'Y' through SYMI. This is an informational message, which is displayed if messages to the console are enabled through SYMI.

Action:

None.

CASD7415

CICS will capture this dump.

Reason:

Check for other messages which indicate why the dump was not captured. This is an informational message, which is displayed if messages to the console are enabled through SYMI.

Action:

None.

CASD7417

STIMERM failure, cannot capture dump.

Reason:

During dump capture, CA SymDump for CICS encountered a catastrophic internal failure.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7418

Recursive XDUREQ entry, cannot capture dump.

Reason:

During dump capture, CA SymDump for CICS encountered a catastrophic internal failure.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7419

SymDump intercept of dump request for transaction nnnn: abend(nnnn), task(xxxxx)

Reason:

This is an informational message, which is displayed if messages to the console are enabled through SYMI.

Action:

None.

CASD7420

Task missing IN25STRU work area

Reason:

If CA SymDump for CICS tries to capture an abend for a task that started before CA SymDump for CICS started, a CA SymDump for CICS work area that must be attached to the task can be missing. In this case, CA SymDump for CICS cannot capture the dump and it terminates. The problem can also occur when CA Top Secret has put a terminal into LOCK MODE and the task is abended.

Action:

None. The dump in question cannot be captured by CA SymDump for CICS.

CASD7500

Dump capture has terminated abnormally

Reason:

This message appears with one or more other messages. It indicates there is a problem with CA SymDump for CICS dump capture.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7501

Please contact CA SymDump technical support.

Reason:

This message appears with one or more other messages.

Action:

Contact your systems programmer (who should then contact Technical support).

CASD7502

IN25STRU failure, GLWA not available.

Reason:

During dump capture, program IN25STRU failed due to a catastrophic internal failure.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7503

IN25STRU is requesting a dump (SDUMP)

Reason:

CA SymDump for CICS program IN25STRU has detected a problem and has requested an SDUMP of the region.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7504

IN25STRU recovery routine has no SDWA

Reason:

During dump capture, program IN25STRU failed due to a catastrophic internal failure.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7505

IN25STRU GETMAIN failure unable to take dump

Reason:

During dump capture, program IN25STRU failed due to a catastrophic internal failure.

Action:

Save all output, including the complete JESLOG and any dumps produced, and contact CA technical support.

CASD7506

TRANSACTION XXXX (TASK NNNNN) IS NOT RESPONSIVE,
DUMP CAPTURE WILL BE ABBREVIATED

Reason:

During dump capture, CA InterTest for CICS has put the task into a wait state for more than one minute. CA SymDump for CICS is capturing an abbreviated dump for this task, and will continue to process other dumps.

Action:

Determine the cause of the task going into a wait state, and resolve the problem so that future dumps can be captured completely.