DFHTRxxxx messages

DFHTR0001
applid An abend (code abcode) has occurred at offset X'offset' in module modname.
Explanation:

An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in CICS code.

Alternatively, unexpected data has been input, or storage has been overwritten.

The code abcode is a 3-digit hexadecimal MVS code (if applicable), followed by a 4-digit alphanumeric CICS code. The MVS code is a system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The CICS code is an abend code or a number referring to a CICS message (for example, AKEA is a CICS abend code; 1310 refers to message DFHTS1310).

System action:

An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

If CICS is still running, it is necessary to decide whether to terminate CICS.

Look up the MVS code, if there is one, in the relevant MVS codes manual which is detailed in the book list in the front of this manual.

Next, look up the CICS alphanumeric code in this manual. This tells you, for example, whether the error was a program check, an abend, or a runaway, and may give you some guidance concerning user response.

If module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.

If you cannot run without the full use of module modname you should bring CICS down in a controlled shutdown.

You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHTRSR, DFHTRPT, DFHTRDM , DFHTRFT

XMEOUT Parameters: applid, abcode,X'offset', modname

DFHTR0002
applid A severe error (code X'code') has occurred in module modname.
Explanation:

An error has been detected in module modname. The code X'code' is the exception trace point id which uniquely identifies what the error is and where the error was detected. For further information about CICS exception trace entries, refer to the CICS Problem Determination Guide.

System action:

An exception entry (code X'code') is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

There may be an error in CICS code. The severity of its impact depends on the importance of the function being executed at the time of the error.

CICS may not have been terminated.

If the message occurs once and module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.

If the message recurs or if you cannot run without the full use of module modname you should bring CICS down in a controlled shutdown.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHTRSR

XMEOUT Parameters: applid, X'code',modname

DFHTR0004
applid A possible loop has been detected at offset X'offset' in module modname.
Explanation:

A CICS function is taking more time to process than CICS expects. A possible loop has been detected in module modname at offset X'offset'. This is the offset of the instruction which was executing at the time the error was detected.

System action:

An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

If CICS has not been terminated, it is necessary to decide whether the problem is serious enough to bring CICS down.

Since some CICS functions can use a lot of processor time, this message may have been caused by a long-running function. So there may not be an error here. Usually, CICS purges a CICS function which exceeds the runaway task time interval which you have specified in the SIT (this is the ICVR which is measured in milliseconds). This means that module modname is terminated and CICS continues.

But if you have declared ICVR=0 in the SIT and you consider that module modname has gone into a loop, you have to terminate CICS in order to terminate the runaway function.

If CICS has terminated module modname and you consider that it was not a runaway, you should increase the ICVR time interval in the SIT. You have to bring CICS down at a suitable time to do this permanently. But you can change the ICVR time interval temporarily online, using the CEMT transaction.

If raising the ICVR time does not solve the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHTRSR, DFHTRPT, DFHTRDM, DFHTRFT

XMEOUT Parameters: applid, X'offset', modname

DFHTR0101
STORAGE FOR INTERNAL TRACE TABLE NOT AVAILABLE -TRACE INOPERATIVE.
Explanation:

During CICS initialization, there was insufficient storage for even the minimum allowable internal trace table size (16KB).

System action:

CICS terminates with a system dump.

User response:

The failure to get even 16KB from MVS at this early stage of initialization almost certainly means that other areas of CICS and other system functions will not be able to acquire the storage they require to operate, so the system is unlikely to initialize completely. A possible solution is to increase the value for the REGION keyword on the EXEC statement for the CICS job.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRDM

DFHTR0102
REQUESTED TRACE TABLE SIZE NOT AVAILABLE.
Explanation:

CICS issues a variable-type GETMAIN to MVS for the internal trace table storage. This message indicates that the upper limit specified (on the TRTABSZ keyword) was not available, but that at least the lower limit of 16K was obtained.

Message DFHTR0103 which follows this message gives the actual size acquired.

System action:

CICS continues with an internal trace table of the size given by message DFHTR0103.

User response:

There are three possible courses of action:

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRDM

DFHTR0103
TRACE TABLE SIZE IS nnK.
Explanation:

The internal trace table acquired during CICS initialization has a table size nnKB.

This is either the same as that specified on the TRTABSZ keyword of the SIT or message DFHTR0101 or DFHTR0102 has preceded this on the console.

System action:

CICS continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRDM

DFHTR0104
applid No buffer storage available for auxiliary trace data set. Auxiliary trace is inoperative.
Explanation:

An attempt to start auxiliary trace failed because there was insufficient storage available from MVS for the 4KB output buffer.

System action:

A CICS system dump with dump code TR0104 is taken. CICS then continues with auxiliary trace inactive.

User response:

Determine why so little MVS storage is available and retry if possible.

Destination:

Console

Modules:

DFHTRDM

XMEOUT Parameter: applid

DFHTR0105
AUXILIARY TRACE DATA SET dataset COULD NOT BE OPENED - AUXILIARY TRACE INOPERATIVE.
Explanation:

An attempt to start auxiliary trace or to switch auxiliary trace extents has failed because the request to BSAM to open data set dataset failed.

System action:

There are two cases:

User response:

Check that the DD statement for data set dataset is present.

If it is, format the system dump and examine the TR domain information. The DCB for the auxiliary trace data set should be present. Use this to determine the reason for the open failure.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRSR, DFHTRSU

DFHTR0106
applid DFHTRAO could not be loaded. Auxiliary trace is inoperative.
Explanation:

An attempt to start auxiliary trace failed because the CICS module, DFHTRAO, which is used to write to the auxiliary trace data set, could not be loaded.

System action:

The loader domain (LD) will have issued messages and dumps as necessary. CICS continues with auxiliary trace inactive.

User response:

Refer to the associated loader domain messages for further information and guidance.

Destination:

Console

Modules:

DFHTRSR

XMEOUT Parameter: applid

DFHTR0107
ABEND X'abcode' ON AUXILIARY TRACE DATA SET dataset - AUXILIARY TRACE STOPPED.
Explanation:

The DCB abend exit for named auxiliary trace data set dataset was driven after a request to BSAM.

The 3-digit abend code is indicated as X'abcode'

System action:

CICS continues with auxiliary trace inactive.

User response:

Refer to the OS/390 MVS System Codes manual for an explanation of the abend code, X'abcode'.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRAO

DFHTR0108
I/O ERROR ON AUXILIARY TRACE DATA SET dataset - AUXILIARY TRACE STOPPED.
Explanation:

The SYNAD exit for the auxiliary trace data set dataset was driven after a request to BSAM.

System action:

CICS will continue with auxiliary trace inactive.

User response:

Use this message and any BSAM messages to determine the source of the error.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRAO

DFHTR0109
AUXILIARY TRACE DATA SET dataset FULL -AUXILIARY TRACE HAS BEEN STOPPED.
Explanation:

The auxiliary trace data set dataset is full. Auxiliary trace has been stopped because autoswitch is not active.

System action:

CICS continues with auxiliary trace inactive.

User response:

The auxiliary trace data set dataset can now be processed by the print routine DFHTU640.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRSU

DFHTR0110
AUXILIARY TRACE DATA SET dataset1 FULL - SWITCHING TO dataset2.
Explanation:

The auxiliary trace data set dataset1 is full. Auxiliary trace is continuing on data set dataset2 because autoswitching was requested.

System action:

CICS continues with auxiliary trace active on the data set dataset2.

User response:

Process the full data set if required.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRSU

DFHTR0111
applid Unable to acquire storage for GTF buffer - GTF trace inoperative.
Explanation:

An attempt to start CICS tracing to the MVS Generalized Trace Facility (GTF) failed because there was insufficient storage available from MVS for the 256-byte buffer required.

This message can be issued by DFHTRDM during CICS initialization if GTFTR=ON is specified on the SIT or start-up overrides, or by DFHTRSU if the request to start GTF was made after CICS was up and running.

System action:

CICS continues with GTF tracing inactive.

User response:

The failure to acquire even 256 bytes of storage indicates that the CICS region is probably in a stall condition. This can only be relieved by removing some of the users of MVS storage or by restarting CICS, possibly with a larger region size.

Destination:

Console

Modules:

DFHTRDM, DFHTRSU

XMEOUT Parameter: applid

DFHTR0112
applid Bad data passed for tracing to module modname.
Explanation:

Some data passed to the trace (TR) domain for addition to the internal trace table, auxiliary trace data set or GTF trace caused a program check when an attempt was made to access it.

This could either be as a result of a request made by CICS system code or a request made by a user program through the API or XPI.

If transaction isolation is active, this message can be issued if a transaction passes another transaction’s storage to CICS. A program check occurs when CICS attempts to trace this storage because the storage is fetch protected.

System action:

A system dump with dump code TR0112 is taken.

If the message was issued by DFHTRPT the dump contains an exception trace entry (point ID TR0102) that includes the erroneous parameter list passed to DFHTRPT.

If the message was issued by DFHTRFT the dump contains an exception trace entry (point ID TR0402) that includes the erroneous parameter list passed to DFHTRFT.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Examine the interpreted exception trace entry to determine the domain that issued the call and the ID of the entry. Then look at the specified addresses and lengths in the datan fields to see if they contain reasonable values. The fault is in the module that set up these fields for the trace call.

If transaction isolation is active, examine the calling domain’s parameter list, data2, for storage that belongs to another transaction. Correct the offending application program. It should not be passing another transaction’s storage. Alternatively, alter the definition of the application so that it can validly access another transaction’s storage. See the CICS Resource Definition Guide for more information on how to alter the definition.

Destination:

Console

Modules:

DFHTRPT, DFHTRFT

XMEOUT Parameters: applid, modname

DFHTR0113
applid Auxiliary trace is being started on data set dataset.
Explanation:

A request to start auxiliary trace has been successfully processed. The trace records are being written to data set dataset.

System action:

CICS continues with auxiliary trace active.

User response:

None.

Destination:

Console

Modules:

DFHTRSR

XMEOUT Parameters: applid, dataset

DFHTR0114
AN ABEND HAS OCCURRED DURING INITIALIZATION OF TRACE IN MODULE modname.
Explanation:

Module modname’s recovery routine received control during pre-initialization of the trace (TR) domain. This indicates that a program check has occurred in module modname.

There are three possible causes of this condition.

  1. The module has been overwritten in main storage.
  2. The module is at an incompatible level with the rest of the CICS modules.
  3. There is an error in the module.
System action:

A system dump with dump code KERNDUMP is taken.

User response:

Inform the system programmer.

There may be an error in CICS code. The severity of its impact will depend on the importance of the function being executed at the time of the error.

CICS may not have been terminated.

If the message occurs once and module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.

If the message recurs or if you cannot run without the full use of module modname you should bring CICS down in a controlled shutdown.

Use the dump to determine the cause of the condition.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRDM , DFHTRSR

DFHTR0115
AN ABEND HAS OCCURRED IN THE AUXILIARY TRACE MODULE DFHTRAO.
Explanation:

Module DFHTRAO’s recovery routine has received control.

This indicates a program check or MVS abend has occurred in DFHTRAO.

There are three possible causes of this condition:

System action:

A system dump with dump code KERNDUMP is taken.

User response:

There may be an error in CICS code. The severity of its impact depends on the importance of the function being executed at the time of the error.

CICS may not have been terminated.

If the message occurs once and module DFHTRAO is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.

If the message recurs or if you cannot run without the full use of module DFHTRAO, you should bring CICS down in a controlled shutdown.

Use the dump to determine the cause of the condition.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRAO

DFHTR0116
AN ABEND HAS OCCURRED IN THE TRACE SUBROUTINES MODULE DFHTRSU.
Explanation:

The recovery routine belonging to the trace domain module DFHTRSU has received control.

This indicates a program check or MVS abend has occurred in that module.

There are three possible causes of this condition:

System action:

A system dump with dump code KERNDUMP is taken.

User response:

There may be an error in CICS code. The severity of its impact depends on the importance of the function being executed at the time of the error.

CICS may not have been terminated.

If the message occurs once and module DFHTRSU is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.

If the message recurs or if you cannot run without the full use of module DFHTRSU, bring CICS down in a controlled shutdown.

Use the dump to determine the cause of the condition.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRSU

DFHTR0117
applid Auxiliary trace on data set dataset has been stopped.
Explanation:

An operator or application program request, to stop CICS tracing to the auxiliary trace data set dataset, has been successfully processed.

System action:

CICS continues with auxiliary trace inactive.

User response:

The auxiliary trace data set dataset can now be processed by the print routine DFHTU640.

Destination:

Console

Modules:

DFHTRSR

XMEOUT Parameters: applid, dataset

DFHTR0118
applid Auxiliary trace is being switched from dataset1 to dataset2.
Explanation:

An operator or application program request to switch extents on the auxiliary trace data set while auxiliary trace is active is being processed.

System action:

CICS stops tracing on the first named data set dataset1, and resumes tracing on the second named data set dataset2.

User response:

The first named auxiliary trace data set dataset1 can now be processed by the print routine DFHTU640.

Destination:

Console

Modules:

DFHTRSR

XMEOUT Parameters: applid, dataset1, dataset2

DFHTR1000
applid CICS abend requested by global trap exit DFHTRAP in module modname.
Explanation:

The field engineering global trap exit program (DFHTRAP) requested termination of CICS.

System action:

CICS disables the trap exit so that it will not be reentered, and terminates CICS.

User response:

Determine why DFHTRAP has requested system termination and act accordingly. You should use the global trap exit only in consultation with an IBM support representative.

Destination:

Console

Modules:

DFHTRPT, DFHTRFT

XMEOUT Parameters: applid, modname

DFHTR1001
applid Program check occurred within global trap exit - DFHTRAP now marked unusable by module modname.
Explanation:

After making a trace entry, the CICS trace domain (TR) called the field engineering global trap exit program (DFHTRAP). A program check occurred during execution of DFHTRAP.

System action:

CICS marks the currently active version of DFHTRAP unusable, and will ignore it on future calls to TR domain. CICS then takes a dump with system dump code TR1001, and continues execution.

User response:

Use the dump to find the cause of the program check. To replace the currently active but unusable DFHTRAP by a new version in the CICS program library, issue the following commands in the sequence shown:

You should use the global trap exit only in consultation with an IBM support representative.

Destination:

Console

Modules:

DFHTRPT, DFHTRFT

XMEOUT Parameters: applid, modname

DFHTR1002
applid Program DFHTRAP is not available - global trap not activated
Explanation:

CICS could not activate the field engineering global trap exit program, DFHTRAP, during processing of the TRAP=ON SIT keyword or override in CICS initialization. This is almost certainly because DFHTRAP is not present in the program library.

System action:

CICS takes a system dump with dump code TR1002 and continues with the global trap not activated.

User response:

Ensure that DFHTRAP is defined to RDO and made available in the program library.

You should use the global trap exit only in consultation with an IBM support representative.

Destination:

Console

Modules:

DFHTRDM

XMEOUT Parameter: applid

DFHTR1003
applid CICS system dump requested by global trap exit DFHTRAP in module modname.
Explanation:

The user-coded global trap exit program (DFHTRAP) has requested a system dump in its return action settings.

System action:

CICS takes a system dump with dump code TR1003 and continues with the global trap still active.

User response:

Analyze the requested dump.

You should use the global trap exit only in consultation with an IBM support representative.

Destination:

Console

Modules:

DFHTRPT, DFHTRFT

XMEOUT Parameters: applid, modname

DFHTR2000
INCOMPLETE ENTRY IGNORED.
Explanation:

CICS trace entries longer than 256 bytes have to be split into multiple Generalized Trace Facility (GTF) entries because of GTF’s length restriction. The CICS entry becomes a header entry followed by one or more continuation entries. This message in the GTF printout indicates that a CICS entry on GTF longer than 256 bytes has not been printed because a new header entry from the same MVS TCB was encountered before all of the continuation entries from a previous split entry were received.

System action:

The incomplete entry is ignored.

User response:

This situation can arise in one of two ways:

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHTRPRG

DFHTR2001
INSUFFICIENT STORAGE FOR RECONSTRUCTION BUFFER.
Explanation:

A CICS entry longer than 256 bytes has been split into a header record and one or more continuation records on the generalized trace facility (GTF). It cannot be formatted because MVS could not allocate sufficient working storage for a buffer to allow reconstruction of the segmented entry.

System action:

The entry is printed in hexadecimal and the print job continues.

User response:

Rerun the GTF print job with a larger region size.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHTRPRG

DFHTR2002
INVALID ENTRY PASSED FOR FORMATTING.
Explanation:

A GTF entry with the CICS format identifier (X'EF') has been passed to the CICS GTF print routine but the data it contains is not part of a valid CICS trace entry.

System action:

The invalid entry is printed in hexadecimal and the print job continues.

User response:

Examine the entry for clues to its origin.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHTRPRG

DFHTR2003
UNEXPECTED CONTINUATION ENTRY ENCOUNTERED.
Explanation:

CICS trace entries longer than 256 bytes have to be split into multiple GTF entries because of GTF’s length restriction. The CICS entry becomes a header entry followed by one or more continuation entries. This message in the GTF printout indicates that a GTF entry has been passed to the CICS GTF print routine that is not the start of a CICS segmented entry and the entry type is not one for which a continuation is currently expected.

System action:

The invalid entry is printed in hexadecimal and the print job continues.

User response:

This situation could arise if the header record for a segmented entry is overwritten because of GTF’s normal cyclic re-use of space in its data set. In this case the invalid entries would be very close to the start of the printout.

If this is not so, examine the entry for clues to its origin.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHTRPRG

DFHTR2004
THE MAXIMUM NUMBER OF BUFFERS (nn) HAVE BEEN ALLOCATED. NONE ARE FREE FOR REUSE.
Explanation:

A CICS trace entry longer than 256 bytes has been split into a header record and one or more continuation records on the generalized trace facility (GTF). However, it cannot be formatted because the maximum number of buffers allowed for reconstruction of segmented entries for a specific type has been reached. This maximum is currently set to nn. The number of buffers for a specific type relates directly to the number of regions or systems writing trace entries to the GTF trace data set. During writing, the segmented entries for some of the different regions or systems could become interleaved in the data set. To ensure that the entries are formatted completely and correctly, it is necessary to have a buffer available for each region or system whose trace entries have become interleaved in this way. For further information on trace types and segmented entries see the section on trace formatting in the CICS Diagnosis Reference.

System action:

The entry is printed in hexadecimal and the print job continues.

User response:

None, but if the situation occurs regularly, contact your IBM Support Center to discuss whether the maximum value set is too low.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHTRPRG

DFHTR2005
THE LOAD FAILED FOR LOAD MODULE modname. PLACE MODULE IN THE LINK LIST AND TRY AGAIN.
Explanation:

The generalized trace facility (GTF) trace formatter tried to load the correct release of trace formatter for the trace entry being processed.

System action:

The job continues printing trace entries in hexadecimal only.

User response:

Place the named trace formatter load module into the link list and rerun the job. If the named trace formatter is not available, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHTRPRG

DFHTR2006
UNKNOWN ENTRY PASSED FOR FORMATTING.
Explanation:

An unknown CICS GTF trace entry has been passed to the CICS GTF print routine. The probable reason for this is that the CICS GTF formatting routine being used is from a previous CICS release and therefore does not recognize entries from the current release.

System action:

The unknown entry is printed in hexadecimal and the print job continues.

User response:

Examine the entry for clues to its origin. Ensure you are running GTF formatting routine DFHTGxxx where xxx is the current CICS release level.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHTRPRG

DFHTR3001
ERROR IN OPENING DFHAXPRT FILE.
Explanation:

The auxiliary trace print program DFHTU640 could not open the data set defined to receive the print output.

System action:

The print job terminates with a return code of 8.

User response:

Ensure that the DD statement for DFHAXPRT is present and correct in the DFHTU640 job.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRPRA

DFHTR3002
ERROR IN OPENING DFHAUXT FILE.
Explanation:

The auxiliary trace print program DFHTU640 could not open the auxiliary trace data set to be processed.

System action:

The print job terminates with a return code of 8.

User response:

Ensure that the DD statement for DFHAUXT is present and correct in the DFHTU640 job.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRPRA

DFHTR3003
ERROR IN OPENING DFHAXPRM FILE.
Explanation:

The auxiliary trace print program DFHTU640 could not open the parameter input data set DFHAXPRM.

System action:

The print job terminates with a return code of 8.

User response:

Ensure that the DD statement for DFHAXPRM is present and correct in the DFHTU640 job, or specify your input parameters on the PARM keyword of the EXEC statement.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHTRPRA

DFHTR3010
ERROR IN TRACE DATA - ENTRIES MAY HAVE BEEN LOST.
Explanation:

The trace block being formatted contains invalid length and/or pointer fields. This can happen if the trace table is accidentally overwritten.

System action:

The trace formatting code scans the block to try and find valid entries. Any that are found are printed. The rest of the data is ignored.

User response:

Try and determine what caused the overwriting of the internal trace table.

The trace entries immediately before and after this message in the print out should be viewed with suspicion. They may contain incorrect data, or there may be one or more entries missing altogether at this point.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHTRFPB

DFHTR4001
Pos position, Blank record.
Explanation:

The trace selection parameters for either the auxiliary trace print program DFHTU640, the system dump print program DFHPD640, or the GTF trace print program DFHTR640 are not correctly specified. There were no valid selective trace print parameters found.

System action:

The print job terminates with a return code of 8.

User response:

Ensure that the DD statement for DFHAXPRM is present and correct in the print job, or specify your input parameters on the PARM keyword of the EXEC statement. A blank line has been found as input on a job control statement. Specify at least one valid selection parameter on this job control statement and rerun the print job. Please refer to the CICS Operations and Utilities Guide for a list of valid trace print selection parameters.

Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHTRFPPEnd of change

DFHTR4002
Pos position, Invalid keyword.
Explanation:

The trace selection parameters for either the auxiliary trace print program DFHTU640, the system dump print program DFHPD640, or the GTF trace print program DFHTR640 are not correctly specified. The keyword found in position of the control statement is not a valid trace selection parameter or has been specified incorrectly.

System action:

The print job terminates with a return code of 8.

User response:

Specify a valid selective trace print parameter and rerun the job. Please refer to the CICS Operations and Utilities Guide for a list of valid trace print selection parameters.

Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHTRFPPEnd of change

DFHTR4003
Pos position, Unexpected end of data.
Explanation:

The trace selection parameters for either the auxiliary trace print program DFHTU640, the system dump print program DFHPD640, or the GTF trace print program DFHTR640 are not correctly specified. An unexpected end of data has been encountered.

System action:

The print job terminates with a return code of 8.

User response:

Ensure that the DD statement for DFHAXPRM is present and correct in the print job, or specify your input parameters on the PARM keyword of the EXEC statement. Specify the trace selection parameters correctly. Please refer to the CICS Operations and Utilities Guide for further information on how to do this.

Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHTRFPPEnd of change

DFHTR4004
Pos position, Missing parenthesis.
Explanation:

The trace selection parameters for either the auxiliary trace print program DFHTU640, the system dump print program DFHPD640, or the GTF trace print program DFHTR640 are not correctly specified. Keywords have been specified which need matching parentheses and one of these is missing.

System action:

The print job terminates with a return code of 8.

User response:

To specify more than one entry for a selection, you must put the list of entries in parentheses. For example, to select tranids ABRQ, AORD, and MYTR, specify TRANID=(ABRQ,AORD,MYTR). Ensure you have specified matching pairs of parentheses as required.

Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHTRFPPEnd of change

DFHTR4005
Pos position, Null data.
Explanation:

The trace selection parameters for either the auxiliary trace print program DFHTU640, the system dump print program DFHPD640, or the GTF trace print program DFHTR640 are not correctly specified. Null data has been found at position in the trace selection parameter statement.

System action:

The print job terminates with a return code of 8.

User response:

Ensure you put valid data in the trace selection parameters. Please refer to the CICS Operations and Utilities Guide for guidance on valid trace print selection parameters.

Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHTRFPPEnd of change

DFHTR4007
Pos position, Invalid separator.
Explanation:

The trace selection parameters for either the auxiliary trace print program DFHTU640, the system dump print program DFHPD640, or the GTF trace print program DFHTR640 are not correctly specified. An invalid separator has been found at position.

System action:

The print job terminates with a return code of 8.

User response:

You must use commas to separate keywords and entries in a list.

Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHTRFPPEnd of change

DFHTR4008
Pos position, Parameter length invalid.
Explanation:

The trace selection parameters for either the auxiliary trace print program DFHTU640, the system dump print program DFHPD640, or the GTF trace print program DFHTR640 are not correctly specified. A trace selection parameter has been specified with an incorrect length.

System action:

The print job terminates with a return code of 8.

User response:

Ensure that the length of the specified trace selection parameter is correct.

Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHTRFPPEnd of change

DFHTR4009
Pos position, Parameter value invalid.
Explanation:

The trace selection parameters for either the auxiliary trace print program DFHTU640, the system dump print program DFHPD640, or the GTF trace print program DFHTR640 are not correctly specified. A trace selection parameter has been specified with an invalid value at position position.

System action:

The print job terminates with a return code of 8.

User response:

Correct the incorrect parameter value. Refer to the CICS Operations and Utilities Guide for guidance on valid trace print selection parameters.

Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHTRFPPEnd of change

DFHTR4010
Pos position, Parameter range invalid.
Explanation:

The trace selection parameters for either the auxiliary trace print program DFHTU640, the system dump print program DFHPD640, or the GTF trace print program DFHTR640 are not correctly specified. A value has been specified at position which is outside the valid range for this parameter.

System action:

The print job terminates with a return code of 8.

User response:

Ensure that the value specified is in the correct range for this selection parameter. Refer to the CICS Operations and Utilities Guide for guidance on valid trace print selection parameters.

Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHTRFPPEnd of change

DFHTR4011
Pos position, Invalid page size range.
Explanation:

The trace selection parameters for either the auxiliary trace print program DFHTU640, the system dump print program DFHPD640, or the GTF trace print program DFHTR640 are not correctly specified. The value specified at position for the PAGESIZE=(value) in the range 20 through 9999 lines per page.

System action:

The print job terminates with a return code of 8.

User response:

Specify a value for PAGESIZE=(value) in the range 20 through 9999 lines per page.

Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHTRFPPEnd of change

DFHTR4012
Pos position, Invalid combination of FULL, ABBREV and SHORT trace.
Explanation:

The trace selection parameters for either the auxiliary trace print program DFHTU640, the system dump print program DFHPD640, or the GTF trace print program DFHTR640 are not correctly specified. Two or more of the selection parameters ABBREV, SHORT, or FULL have been specified together. These parameters are mutually exclusive.

System action:

The print job terminates with a return code of 8.

User response:

Specify either ABBREV or SHORT or FULL and rerun the print job.

Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHTRFPPEnd of change

Start of changeDFHTR5001End of change
Start of changeTHE LOAD FOR A FEATURE PROGRAM HAS FAILED.End of change
Start of change
Explanation:

The load for a feature formatting program has failed. This can happen if the program text is not included in one of the named datasets for the job.

End of change
Start of change
System action:

The trace formatting continues without feature tracing.

End of change
Start of change
User response:

Try and determine what caused the load error.

Note:
This message cannot be changed with the message editing utility.
End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHTRFFEEnd of change

Start of changeDFHTR5002End of change
Start of changeFEATURE FORMATTING PROGRAM HAS FAILED.End of change
Start of change
Explanation:

A feature formatting program has failed.

End of change
Start of change
System action:

The trace formatting continues without feature tracing.

End of change
Start of change
User response:

Refer to the documentation provided with your feature.

Note:
This message cannot be changed with the message editing utility.
End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHTRFFEEnd of change

[[ Contents Previous Page | Next Page Index ]]