DFHME0126    applid Error in SYMREC invocation. Return code in R15 = X'mmmm', Reason code in R0 = X'nnnn'.

Explanation

While handling an error, CICS tried to write a symptom record to SYS1.LOGREC.

However, a further problem was detected while attempting to invoke the SYMREC service.

Return code X'mmmm' in register 15 and reason code X'nnnn' in register 0 indicate the reason for the error. This may be one of the following.

  • CICS has been prevented from writing the symptom record to SYS1.LOGREC by the ASREXIT MVS installation exit. In this case a system dump is not produced.

  • There is an error in the SYMRBLD macro. (This is the macro CICS uses to build its symptom records.)

  • CICS has supplied invalid data to be added to the symptom record.

  • There is an error in the SYMREC service. Examples of possible problems include a storage error, or insufficient space in the LOGREC buffer.

  • The SYMREC service is currently inoperative.

System action

Processing continues and a system dump may be produced.

An exception trace entry (pointid=X'0806') is made in the trace table which contains the symptom record which CICS attempted to write.

User response

Determine whether the error was caused by a problem in the format of the symptom record produced by CICS, or by a problem in the SYMREC service.

The meanings of the return and reason codes, together with additional information about the SYMREC service can be found in the z/OS MVS Programming: Assembler Services Reference ABE-HSP manual.

Return codes 0010 or 0014 indicate a problem in the SYMREC service which must be reported to the MVS System Administrator.

A return code of 000C and a reason code of 0F1C indicates that the ASREXIT installation exit has prevented CICS from writing the symptom record. This could be caused by an installation error. Report the problem to your MVS system administrator.

Any other return code indicates that the symptom record is invalid to the SYMREC service.

The impact of this error need not be severe, if for example, the problem occurs only as an isolated incident or on the production of a particular message. In these cases, this message can be ignored.

However, if the problem is persistent, you will need further assistance from IBM. See IBM problem support for guidance on how to proceed.

Module

DFHMEWS

Destination

Console



DFHME0126.html | Timestamp icon Last updated: Sunday, 4 June 2017