DFHFCxxxx messages

Note:
In cases where standard message inserts such as opid or termid are undefined or cannot be determined, the inserts are replaced by dashes.
DFHFC0001
applid An abend (code aaa/bbbb) 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,

The code aaa/bbbb is a three digit hexadecimal MVS code (if applicable), followed by a four 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:

Notify the system programmer. 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.

Then look up the CICS alphanumeric code. This tells you, for example, whether the error was a program check, an abend, or a runaway, and may give you some further guidance.

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:

DFHFCAT, DFHFCCA, DFHFCDN, DFHFCDTS, DFHFCDTX, DFHFCES, DFHFCFL, DFHFCFR, DFHFCFS, DFHFCIR, DFHFCLF, DFHFCLJ, DFHFCMT, DFHFCQI, DFHFCQR, DFHFCQS, DFHFCQU, DFHFCRC, DFHFCRL, DFHFCRO, DFHFCRP, DFHFCRR, DFHFCRS, DFHFCRV, DFHFCSD, DFHFCST, DFHFCVR, DFHFCVS

XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname

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

An error has been detected in module modname. The code code is the exception trace point ID which uniquely identifies what the error is and where the error was detected.

To discover the cause of the problem, examine the exception trace entry and immediately preceding entries. For further information about CICS exception trace entries, see the CICS Problem Determination Guide.

System action:

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

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

User response:

Inform the system programmer. This indicates a possible 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:

DFHFCAT, DFHFCCA, DFHFCDN, DFHFCDTS, DFHFCDTX, DFHEIFC, DFHFCES, DFHFCFL, DFHFCFR, DFHFCFS, DFHFCIR, DFHFCLF, DFHFCLJ, DFHFCMT, DFHFCOR, DFHFCQI, DFHFCQR, DFHFCQS, DFHFCQU, DFHFCRC, DFHFCRD, DFHFCRL, DFHFCRO, DFHFCRP, DFHFCRR, DFHFCRS, DFHFCSD, DFHFCST, DFHFCVR, DFHFCVS

XMEOUT Parameters: applid, X'code',modname

DFHFC0003
applid Insufficient storage (code X'code') in module modname.
Explanation:

A CICS GETMAIN was issued by module modname, but there was insufficient storage available to satisfy the request.

The code X'code' is the exception trace point ID which uniquely identifies the place where the error was detected.

System action:

An exception entry is made in the trace table (code code in the message). 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:

Inform the system programmer. If CICS has been terminated by another module, look out for the relevant termination messages (from the domain manager, for example), and look up the user response for these messages.

If CICS is still running, the problem may be a temporary one which rights itself if more storage becomes available. If you can manage without module modname, you may decide to continue 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 all CICS modules, you should bring CICS down in a controlled shutdown.

Try increasing the size limits of the DSAs or EDSAs. See the CICS System Definition Guide or the CICS Performance Guide for further information on CICS storage.

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameters: applid, X'code',modname

DFHFC0004
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:

Notify the system programmer. 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 CPU 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 as a system initialization parameter 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, 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 require further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCAT, DFHFCDN, DFHFCDTS, DFHFCDTX, DFHFCFR, DFHFCFS, DFHFCMT, DFHFCRL, DFHFCRP, DFHFCSD, DFHFCST, DFHFCVR, DFHFCVS

XMEOUT Parameters: applid, X'offset', modname

DFHFC0005
applid A hardware error has occurred (module modname, code X'code'). The Time-of-Day clock is invalid.
Explanation:

A hardware error has occurred during the running of module modname. The MVS store clock facility is the timing mechanism for the operating system.

The code code is the exception trace point ID which uniquely identifies the place where the error was detected.

System action:

An exception entry (code code in the message) 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 to this effect is issued.

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

User response:

Notify the system programmer. This is in all probability a hardware error and you should in the first instance investigate the MVS store clock and find out whether it is working properly. If this is the cause, you should take the appropriate action to have it repaired or replaced.

In the unlikely event that this is not a hardware problem, you will require further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

XMEOUT Parameters: applid, modname,X'code'

DFHFC0100I
applid File Control initialization has started.
Explanation:

This is an informational message indicating the start of file control initialization.

System action:

Initialization continues.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameter: applid

DFHFC0101I
applid File Control initialization has ended.
Explanation:

File control initialization has completed successfully.

System action:

Initialization continues.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHFCRP.

XMEOUT Parameter: applid

DFHFC0102
applid File Control initialization has failed.
Explanation:

File control has failed to initialize correctly.

System action:

Message DFHSI1521 is usually issued and initialization is terminated.

If the failure occurred at a critical stage during file control initialization, CICS initialization is terminated immediately with a dump, and message DFHSI1521 is not issued.

User response:

The error can be identified by a trace entry, and possibly by a prior message. You should then take action that is appropriate to the error.

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameter: applid

DFHFC0103
applid Required module modname could not be loaded.
Explanation:

Module modname is required by file control. It could not be loaded because it is missing from the DFHRPL library list.

System action:

The system terminates with a system dump and code FC0103.

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

User response:

Ensure that module modname is in the DFHRPL library list.

If this is not the cause of the problem you will require further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCIN1, DFHFCRP, DFHFCFS

XMEOUT Parameters: applid, modname

DFHFC0104
applid Unexpected catalog error.
Explanation:

File control issued a request to the catalog (CC) domain which failed. This is probably caused by an I/O error on the catalog.

System action:

A system dump is produced with code FC0104.

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

User response:

Determine the cause of the error from the messages issued from the catalog domain.

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameter: applid

DFHFC0106
applid Insufficient storage to satisfy GETMAIN request in module modname.
Explanation:

The storage (SM) domain has insufficient space to satisfy a GETMAIN request made during CICS initialization.

System action:

A system dump is produced.

User response:

None.

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameters: applid, modname

DFHFC0107D
applid Unable to load File Control table DFHFCTxx. Enter either an alternative suffix, or 'YES', or 'NO'.
Explanation:

The file control table, DFHFCTxx could not be found in the DFHRPL library list during a cold or initial start of CICS.

System action:

File control initialization waits for a reply to this message.

User response:

Reply as follows:

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameters: applid, xx

DFHFC0108
applid Invalid reply to message DFHFC0107D. A 1 or 2 character suffix, or YES or NO is required
Explanation:

The reply to message DFHFC0107 was invalid. The reply may have been too long or may have contained invalid characters.

System action:

Message DFHFC0107 is reissued and initialization waits for a reply.

User response:

Reply to message DFHFC0107.

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameter: applid

DFHFC0110
applid Error, a xxxx version of DFHFCTxx has been loaded.
Explanation:

DFHFCRP loaded DFHFCTxx that was assembled for CICS release xxxx. It is not valid to run CICS with an FCT assembled against a previous release.

System action:

File control initialization, and hence CICS, is terminated.

User response:

Reassemble DFHFCTxx for the CICS release being used. Cold start CICS.

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameters: applid, xxxx,DFHFCTxx

DFHFC0111
applid Error, CICS is attempting to initialize with release xxxx of DFP.
Explanation:

DFHFCRP detected that CICS was being initialized with data facility product (DFP) level xxxx. CICS does not support this level of DFP.

System action:

File control initialization, and hence CICS, is terminated.

User response:

Install a level of DFP supported by this release of CICS.

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameters: applid, xxxx

DFHFC0112
applid Install of remote FCT entry filename failed. SYSID sysid, specified in the entry, is the local SYSID.
Explanation:

DFHFCRP attempted to install file filename from the assembled FCT. The install failed because the file was defined as TYPE=REMOTE but the SYSIDNT specified, sysid, was the system identifier of this local system.

System action:

File filename is not installed and file control initialization continues.

User response:

Examine the entry for filename in the FCT and either make the entry a local entry (TYPE=FILE) or correct the SYSIDNT specified.

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameters: applid, filename, sysid

DFHFC0116
applid The load of callable service IGWARLS has failed with return code X'eeee'.
Explanation:

Callable service IGWARLS is required by file control for processing files which have update SERVREQs and are using the VSAM catalog as a repository for data set recovery attributes. The load of IGWARLS requested by file control initialization has failed. This is a serious problem because CICS is using a level of VSAM that supports use of the VSAM catalog for specifying data set recovery attributes.

System action:

CICS initialization fails.

User response:

IGWARLS is supplied on SYS1.CSSLIB. Ensure that SYS1.CSSLIB is in the concatenation for the MVS linklist or LPA. If the failure persists, this is likely to be an internal CICS error. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameters: applid, X'eeee'

DFHFC0118
applid System initialization parameter requesting RLS support has been ignored because the level of VSAM does not support RLS.
Explanation:

RLS=YES has been specified on CICS startup but the level of VSAM does not support RLS access.

System action:

CICS initialization continues without RLS support.

User response:

If you intend to use RLS access ensure that the level of VSAM is DFSMS 1.3 or later.

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameter: applid

DFHFC0150
date time applid termid tranid An attempt to release locks for unit of work X'uowid' failed. VSAM return code X'rrrr' reason code X'cccc'.
Explanation:

Unit of work uowid for tranid tranid has attempted to release its RLS locks. The release locks request made to VSAM has failed because VSAM detected an error.

The IDALKREL response is rrrr and the reason code is cccc.

termid identifies the terminal running this transaction.

System action:

CICS continues with the completion of the unit of work.

The unit of work is shunted. The shunt reason indicates that a further release locks attempt is required.

Some records may remain locked until a successful lock release command can be processed by VSAM.

If the failure is caused by the SMSVSAM server being unavailable, CICS automatically retries the completion of the UOW when the server becomes available.

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

User response:

Use the VSAM codes to determine the cause of the problem. The most likely cause of this failure is that the SMSVSAM server failed at the time of the error. For the meaning of the VSAM codes, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

When the condition that caused the lock release to fail has been resolved, you may need to retry the unit of work using

CEMT SET DSNAME RETRY

or

EXEC CICS SET DSNAME(dsname) ACTION(RETRY)

.

If you cannot resolve the problem or the problem recurs, there may be a more severe error. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCCA

XMEOUT Parameters: date, time,applid, termid, tranid, X'uowid', X'rrrr', X'cccc'

DFHFC0151
date time applid termid tranid An attempt to retain locks for unit of work X'uowid' failed. VSAM return code X'rrrr' reason code X'cccc'.
Explanation:

Unit of work uowid for transaction tranid has gone indoubt because it has lost contact with its coordinating system. Consequently CICS has attempted to convert all RLS locks owned by this unit of work into retained locks. This attempt has failed because VSAM has detected an error.

The IDARETLK macro response is rrrr and the reason code is cccc.

termid identifies the terminal running this transaction.

System action:

CICS continues shunting this unit of work. It is possible that some locks may remain as active locks (which cause other transactions to wait until their timeout value is reached) rather than as retained locks (which cause other transactions to encounter LOCKED responses.)

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

User response:

Use the VSAM codes to determine the cause of the problem. For the meaning of the VSAM codes, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets. The most likely reason for the failure to convert locks into retained locks is that the SMSVSAM server was not available. Other VSAM codes may indicate a more severe error.

Normally no other action should be necessary. When contact is reestablished, the coordinating system instructs this system to commit or backout. At the end of commit or backout, all retained and active locks are released.

A problem that you may encounter is that some locks may have been left as active locks. This may cause slow response (and eventual failures) from transactions that wait for these locks and have to wait for their full timeout interval.

In this case, you can use the CEMT SET UOW command to force the unit of work to commit or backout, or to make a decision to commit or backout according to the ACTION attribute in the transaction definition. Alternatively, you can use the CEMT SET DSNAME command which will force all in-doubt units of work which had updated the specified data set. However, you should not normally use these commands because they can cause this CICS to become out of step with its coordinating system with consequent loss of data integrity.

If you cannot resolve the problem or the problem recurs, there may be a more severe error. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCCA

XMEOUT Parameters: date, time,applid, termid, tranid, X'uowid', X'rrrr', X'cccc'

DFHFC0152
date time applid termid tranid An attempt to retain locks for data set within unit of work X'uowid' failed. VSAM return code X'rrrr' reason code X'cccc'.
Explanation:

Unit of work uowid for transaction tranid has failed backout for one of its data sets. CICS has attempted to convert all the RLS locks owned by this unit of work that are associated with the failing data set into retained locks. This attempt has failed because VSAM has detected an error.

The IDARETLK response is rrrr and the reason code is cccc.

termid identifies the terminal running this transaction.

This message is followed by message DFHFC0312 which identifies the failing data set.

System action:

CICS continues shunting this unit of work. Some locks may remain as active locks (which cause other transactions to wait until their timeout value is reached) rather than as retained locks (which cause other transactions to encounter LOCKED responses).

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

User response:

Use the VSAM codes to determine the cause of the problem. For the meaning of the VSAM codes, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

The most likely reason for the failure to convert locks into retained locks is that the SMSVSAM server was not available. It is also possible to get a failure because the specified logical unit of work ID does not exist for the subsystem (that is, the unit of work does not hold any locks) during lost locks recovery, or after a CICS restart which specified OFFSITE=YES as a system initialization override. If you are performing RLS lost locks recovery, message DFHFC0555 will have been issued when lost locks recovery started; if you are performing RLS offsite recovery, message DFHFC0574 will have been issued during file control initialization. Other VSAM codes may indicate a more severe error.

Normally no other action is necessary. When the condition that caused the backout failure has been resolved, the backout of this unit of work is retried. If the attempt to retry the backout succeeds, all locks are released.

Message DFHFC4701 specifies the cause of the backout failure. The most common cause of backout failures is a hardware problem causing I/O errors. In this case the data set needs to be restored and forward recovered. If CICSVR (or a functionally equivalent product) is used to perform forward recovery, and the data set was being accessed in RLS mode, units of work that have failed backout for this data set are retried automatically. If the data set was quiesced, you need to unquiesce it to allow the backout to succeed. When the data set is unquiesced, CICS automatically retries the backout.

Backouts may also be retried using

CEMT SET DSNAME RETRY

or

EXEC CICS SET DSNAME(dsname) ACTION(RETRY)

.

The only problem that you may encounter is that some locks may have been left as active locks. This can cause a slow response (and eventual failures) from transactions that wait for these locks and have to wait for their full timeout interval.

In this case, consider releasing all locks held against this data set using the CEMT SET DSNAME RESETLOCKS command. This command should only be considered in extreme cases because it discards both the retained locks held by this CICS system against the named data set and all associated log records. The consequence is that the corresponding backout operations are never performed and data integrity is lost.

If you cannot resolve the problem or the problem recurs, there may be a more severe error. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCCA

XMEOUT Parameters: date, time,applid, termid, tranid, X'uowid', X'rrrr', X'cccc'

DFHFC0153
applid The previous instance of the SMSVSAM server has failed. File control RLS access is being closed down.
Explanation:

The SMSVSAM server is the separate VSAM address space that handles all VSAM requests made in RLS mode. The instance of this address space which CICS has been using has terminated, and CICS has just detected the failure. CICS must close down all accesses from file control to this instance of the SMSVSAM server in order to be able to register with the next server instance when the server restarts.

If message DFHFC0568 is issued before DFHFC0153, CICS did not detect the failure until the server restarted and notified CICS that a new instance was available. If message DFHFC0568 is not issued before DFHFC0153, CICS detected the failure when it tried to access the failed instance of the server.

System action:

CICS disables all further RLS accesses, closes all files which were open in RLS mode, and attempts to unregister the RLS control ACB.

Transactions that attempt to access files previously opened in RLS mode abend. The abend code depends upon what the transaction was doing at the time of the failure.

User response:

The SMSVSAM server address space should normally restart itself. If it does not, restart the SMSVSAM server address space manually. If the SMSVSAM server address space fails to restart, there may be a more severe error. In this case, you need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCCA

XMEOUT Parameter: applid

Start of changeDFHFC0156End of change
Start of changeapplid A failure to reset the PERMITNONRLSUPDATE state has occurred. Vsam return code X'rrrr' reason code X'cccc'.End of change
Start of change
Explanation:

CICS has completed processing after a PERMITNONRLSUPDATE batch override response was returned by VSAM when CICS issued an RLS open. The call to VSAM from CICS to reset the state so that it is no longer in batch override status has failed.

The VSAM response is rrrr and the VSAM reason is cccc.

This message is followed by message DFHFC0312 which identifies the failing data set.

End of change
Start of change
System action:

CICS takes a system dump.

End of change
Start of change
User response:

To resolve the problem, keep the dump and contact your IBM Support Center.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCCAEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changerrrr',End of changeStart of changeX'End of changeStart of changeccccEnd of changeStart of change'End of change

DFHFC0157
applid tranid termid userid An I/O error has occurred on base data set dsname accessed via file filename component code X'code'.
Explanation:

An I/O error has been reported by VSAM after a request to update VSAM file filename.

The name of the base data set associated with the file is dsname although the error may have been encountered elsewhere. This is indicated by the value of the component code X'code'. Its possible values and the corresponding error locations are as follows.

System action:

The application request which encountered the error receives an ‘IOERR’ response.

CICS also issues message DFHFC0158 to display the VSAM diagnostic information for this error.

User response:

Follow standard procedure for I/O errors. No special additional action is required to respond to this particular message although the data set name and component code may help in identifying the problem.

Destination:

Console

Modules:

DFHFCRS

XMEOUT Parameters: applid, tranid,termid, userid, dsname, filename, X'code'

DFHFC0158
applid vsam-error-data
Explanation:

This message displays additional VSAM diagnostic information that is available following I/O errors and cache failures. The message is provided for information only.

The format of the data contained in message DFHFC0158 is described in OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets. in the section describing the physical error message format. This is a common data format used by other IBM products following I/O errors.

This message is issued after messages DFHFC0157, DFHFC0162 and DFHFC0163 and provides additional information to go with those messages.

System action:

Processing continues.

User response:

See the description of the associated preceding message (DFHFC0157, DFHFC0162 or DFHFC0163.)

Destination:

Console

Modules:

DFHFCRS, DFHFCVS

XMEOUT Parameters: applid, vsam-error-data

DFHFC0159
applid A request issued to cold start the RLS subsystem has failed. VSAM return code X'rrrr' reason code X'cccc'.
Explanation:

A cold or initial start of CICS has been requested. CICS has made a call to the RLS component of VSAM which requested RLS to cold start its status with respect to this CICS. This request has failed because VSAM RLS detected an error while performing cold start processing.

System action:

CICS continues to initialize. However, the restart of the RLS component of file control has failed and all RLS eligible files are unusable.

No dump is taken with this message. However, file control restart may subsequently produce message DFHFC0001 and take a dump if the error is of a type which should not occur during normal running.

User response:

If the VSAM return code indicates that the SMSVSAM server has failed, restart the SMSVSAM server (if it has not already automatically restarted). You also need to restart CICS because CICS has been warm started with respect to RLS when the server returns.

If the SMSVSAM server has not failed, this is probably an error in CICS or VSAM. You should keep the dump associated with message DFHFC0001. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCCA

XMEOUT Parameters: applid, X'rrrr',X'cccc'

DFHFC0160
applid An attempt to notify VSAM that CICS has completed lost locks processing for a data set has failed. VSAM return code X'rrrr' reason code X'cccc'.
Explanation:

Following a failure of the VSAM lock structure, VSAM has marked a data set as being in lost locks state with regard to this CICS. CICS has performed all recovery actions necessary to resolve its locks against this data set and has attempted to inform VSAM that it has completed its recovery. This attempt has failed.

The VSAM response is rrrr and the VSAM reason is cccc.

This message is followed by message DFHFC0312 which identifies the failing data set.

System action:

If the VSAM return code does not indicate that the SMSVSAM server has failed, CICS takes a system dump.

User response:

The most likely cause of this failure is that the SMSVSAM server failed at the time that CICS issued the request.

If the problem was caused by the SMSVSAM server having failed at the time that the request was issued, restart the SMSVSAM server (if it has not already automatically restarted). Otherwise, you can make CICS retry the attempt to notify VSAM of the completion of lost locks processing either by restarting CICS or by restarting the SMSVSAM server.

It is possible that your installation may have performed some action, such as deleting the data set, which would cause VSAM not to recognize the data set and therefore return an error. If this is the case for the data set named in message DFHFC0312, you need take no further action.

If the VSAM return and reason codes suggest an internal CICS or VSAM error, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCCA

XMEOUT Parameters: applid, X'rrrr',X'cccc'

DFHFC0161
applid Inquire recovery has failed. VSAM return code X'rrrr' reason code X'cccc'.
Explanation:

During restart CICS has issued an inquire recovery request to VSAM. This request has failed because VSAM has detected an error.

System action:

CICS restart continues. All RLS files are unusable.

If the VSAM return code does not indicate that the SMSVSAM server has failed, CICS later issues message DFHFC0001 which has an associated system dump.

User response:

The most likely cause of this failure is that the SMSVSAM server failed at the time that CICS issued the request. In that case you should restart the SMSVSAM server, if it has not already automatically restarted. There is no need to restart CICS.

If the VSAM return and reason codes indicate an internal CICS or VSAM error, keep the dump from message DFHFC0001. You will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCCA

XMEOUT Parameters: applid, X'rrrr',X'cccc'

DFHFC0162
applid A VSAM data cache has failed.
Explanation:

A data cache structure being used by VSAM RLS has failed.

System action:

The application request which encountered the error receives an ‘IOERR’ response.

CICS also issues message DFHFC0158 to display the VSAM diagnostic information for this error. The name of the failing cache can be derived from the information displayed in the following DFHFC0158 message.

While the data cache remains unusable, all data sets bound to this cache are also unusable. Any attempt to read from or write to such a data set cause an IOERR response.

CICS issues messages DFHFC0162 and DFHFC0158 the first time that an I/O request fails because of a cache failure. To prevent flooding the console with messages, CICS does not display these messages again until it is notified that a cache has been recovered. If several caches fail, DFHFC0162 and DFHFC0158 are only displayed for the first cache to fail. However, VSAM issues messages for all failed caches.

User response:

Allocate a new data cache and bring it on line to VSAM.

CICS is notified as soon as the new cache is available and is able to take appropriate recovery action.

Destination:

Console

Modules:

DFHFCRS

XMEOUT Parameter: applid

DFHFC0163
applid Connectivity to a VSAM RLS data cache has been lost.
Explanation:

Connectivity has been lost to a data cache that is being used by VSAM RLS.

System action:

The application request which encountered the error receives an ‘IOERR’ response.

CICS also displays message DFHFC0158 to display the VSAM diagnostic information for this error. The name of the failing cache can be derived from the information displayed in the following DFHFC0158 message.

While the data cache remains unusable, all data sets bound to this cache are also unusable. Any attempt to read from or write to such a data set receives an ‘IOERR’ response.

CICS issues messages DFHFC0163 and DFHFC0158 the first time that an I/O request fails because contact has been lost between the processor running this MVS image and the coupling facility that holds the data cache. To prevent flooding the console with messages, CICS does not display these messages again until it is notified that a cache has been recovered. If contact with several caches is lost, messages DFHFC0163 and DFHFC0158 are only displayed for the first cache to fail. However, VSAM issues messages for all caches for which contact has been lost.

User response:

Reestablish contact between the processor running CICS and the coupling facility that contains the cache.

CICS is notified as soon as contact has been reestablished and is able to take appropriate recovery action.

Destination:

Console

Modules:

DFHFCRS

XMEOUT Parameter: applid

DFHFC0164
date time applid tranid trannum termid userid. A request has timed out waiting for an RLS lock. There are nn transactions or Transactional VSAM units of recovery holding this lock.
Explanation:

This message and the following DFHFC0165 or DFHFC0175 messages are issued to assist in problem determination when transactions abend with the AFCV abend code, or when application programs receive the RECORDBUSY condition.

An attempt made by transaction tranid with task number trannum to update a file which is open in VSAM RLS mode has failed because the request timed out waiting to obtain a lock on a record.

VSAM RLS has detected that a request has waited for a lock for more than the timeout interval. However, RLS was unable to detect any deadlock. Possibly there is a deadlock between VSAM RLS requests and requests to another resource manager such as DB2 or DBCTL.

When the timeout occurred there were nn other transactions or Transactional VSAM units of recovery holding the required lock.

System action:

If the application request which encountered the error specified NOSUSPEND, it receives the RECORDBUSY condition and continues. If the request did not specify NOSUSPEND, it receives an AFCV abend.

CICS displays message DFHFC0164 to identify the failing transaction and the number of owners of the lock. CICS also issues message DFHFC0165 or DFHFC0175 once for each lock owner. CICS issues message DFHFC0168 instead of DFHFC0165 or DFHFC0175 in the unlikely event that VSAM RLS is unable to identify the lock owner.

User response:

The following DFHFC0165 or DFHFC0175 messages identify the transactions that are holding the required lock and the CICS systems that they are running in or the unit of recovery holding the required lock and the Transactional VSAM instance this is running in, respectively. Examine these transactions or units of recovery to see why they are not releasing VSAM RLS locks. For example:

Destination:

CSFL

Modules:

DFHFCRS

XMEOUT Parameters: date, time,applid, tranid, trannum, termid, userid, nn

DFHFC0165
date time applid tranid trannum termid userid. Transaction transid (tasknum) unit of work X'uowid' running in job jobname with applid applid2 in MVS mvsid holds {add to end lock | internal lock | exclusive lock on key | shared lock on key }X'keyid' in data set dsname causing {true | false} contention.
Explanation:

This message and the preceding message DFHFC0164 or DFHFC0174 are issued to assist in problem determination when transactions abend with the AFCV or AFCW abend codes, or when applications receive the RECORDBUSY condition.

Normally this message appears after VSAM returns a timeout response to CICS. However, it may also appear after VSAM returns a deadlock response to CICS when that deadlock arises as a result of a failure to promote a lock. When this message is associated with a timeout response from VSAM, it is preceded by message DFHFC0164. When this message is associated with a deadlock response from VSAM it is associated with message DFHFC0174.

There is one occurrence of message DFHFC0165 for each transaction currently owning the required lock.

The name of the transaction that has failed is tranid and it has task number trannum.

The message inserts that identify the owner of the lock which caused this transaction to time out are as follows:

The message identifies whether the lock is held as an exclusive lock or a shared lock:

A lock causes true contention if the request was for a lock against the locked key. A lock causes false contention if the request was for a lock against a different key but the lock requests clashed because of the RLS key hashing algorithm which is used when the key length exceeds 16 characters.

System action:

This message is preceded by DFHFC0164 or DFHFC0174. See the description of DFHFC0164 or DFHFC0174 for a description of the system action associated with this message.

User response:

This message is preceded by DFHFC0164 or DFHFC0174. See the description of DFHFC0164 or DFHFC0174 for a description of the user actions associated with this message.

Destination:

CSFL

Modules:

DFHFCRS

XMEOUT Parameters: date, time,applid, tranid, trannum, termid, userid, transid, tasknum,X'uowid', jobname, applid2, mvsid, {1=add to end lock , 2=internal lock , 3=exclusive lock on key , 4=shared lock on key }, X'keyid', dsname,{1=true, 2=false}

DFHFC0166
date time applid tranid termid userid. VSAM RLS has detected a deadlock. There are nn transactions or Transactional VSAM units of recovery in the deadlock chain.
Explanation:

This message and the following DFHFC0167 or DFHFC0177 messages are issued to assist in problem determination when transactions abend with AFCW abend codes.

An attempt made by transaction tranid to update a file which is open in VSAM RLS mode has failed because VSAM RLS detected that this request would have caused a deadlock with other transactions.

At the time that the timeout occurred there were nn other transactions or Transactional VSAM units of recovery in the chain which caused deadlock.

System action:

The application request which encountered the error receives an AFCW abend.

CICS issues message DFHFC0166 to identify the failing transaction and the number of transactions or units of recovery in the deadlock chain.

CICS also issues message DFHFC0167 or DFHFC0177 once for each transaction or unit of recovery involved in the deadlock chain. DFHFC0167 and DFHFC0177 identify the resource that the transaction or unit of recovery is holding and the resource that the transaction is waiting for.

User response:

Examine the transactions or units of recovery in the deadlock chain to determine why deadlock arose. If necessary, correct the programming logic to avoid deadlock-creating situations.

For guidance on writing programs that avoid deadlock problems, see the CICS Application Programming Guide.

Destination:

CSFL

Modules:

DFHFCRS

XMEOUT Parameters: date, time,applid, tranid, termid, userid, nn

DFHFC0167
date time applid tranid termid userid. Transaction transid(tasknum) with unit of work id X'uowid' running in jobname/applid2 in MVS mvsid holds {add to end lock | internal lock | exclusive lock on key | shared lock on key }X'key1' on data set dsname1 and is waiting for {add to end lock |internal lock | exclusive lock on key |shared lock on key }X'key2' on data set dsname2.
Explanation:

This message and the preceding DFHFC0166 message are issued to assist in problem determination when transactions abend with AFCW abend codes.

The preceding message DFHFC0166 reports that a deadlock has been detected and includes how many transactions exist in the deadlock chain.

Message DFHFC0167 is issued once for each transaction in the deadlock chain and includes the resource that transaction holds and which resource it is waiting for.

The message inserts are as follows:

The message identifies whether the lock is held as an exclusive lock or a shared lock and whether the transaction is attempting to acquire an exclusive or shared lock.

System action:

The application request which encountered the error receives an AFCW abend.

User response:

See the description of message DFHFC0166.

Destination:

CSFL

Modules:

DFHFCRS

XMEOUT Parameters: date, time,applid, tranid, termid, userid, transid(tasknum), X'uowid', jobname/applid2, mvsid, {1=add to end lock , 2=internal lock , 3=exclusive lock on key , 4=shared lock on key },X'key1', dsname1, {1=add to end lock , 2=internal lock , 3=exclusive lock on key , 4=shared lock on key },X'key2', dsname2

DFHFC0168
date time applid tranid trannum termid userid.{ An exclusive | A shared} lock on key X'keyid' in data set dsname is causing {true | false} contention but the owner of this lock is unknown.
Explanation:

This message and the preceding DFHFC0164 message are issued to assist in problem determination when transactions abend with AFCV abend codes.

Message DFHFC0168 is issued whenever VSAM RLS is unable to determine the owner of a lock. This is an abnormal condition. It may indicate that a processor in the sysplex is stopped.

dsname is the name of the data set against which the lock is held. keyid identifies the key which is locked. As it is not always possible to display keys in character form, the key is displayed in hexadecimal notation.

The message identifies whether the lock is held as an exclusive lock or a shared lock.

A lock causes true contention if the request was for a lock against the locked key. A lock causes false contention if the request was for a lock against a different key but the lock requests clashed as a result of hashing algorithms used in creating RLS keys.

System action:

Processing continues.

User response:

None. The message is issued to assist in problem determination.

Destination:

CSFL

Modules:

DFHFCRS

XMEOUT Parameters: date, time,applid, tranid, trannum, termid, userid, {1= An exclusive,2= A shared}, X'keyid', dsname, {1=true, 2=false}

DFHFC0169
date time applid termid userid. Transaction tranid with transaction number trannum encountered an RLS retained lock held on data set dsname by unit of work X'uowid' within CICS with applid applid2.
Explanation:

An attempt was made to update a record which is currently held locked by a retained RLS lock.

Message inserts are as follows:

This message is issued to aid in problem diagnosis. It identifies the owner of the lock that is causing a request to fail with a ‘LOCKED’ response.

System action:

The application request which encountered the error receives a ‘LOCKED’ response.

User response:

If repeated LOCKED responses are causing a problem, note the name of the CICS system and the identifier of the unit of work and attempt to find why this unit of work is holding a retained lock. There are three reasons why a unit of work can hold a retained lock.

  1. The unit of work was running in a CICS system that has failed. If this CICS system is restarted, the lock is normally released.
  2. The unit of work has gone indoubt. Indoubt failures occur as a result of a failure in communication between two CICS systems, neither of which need be the CICS system that is encountering the ‘LOCKED’ response.

    From a terminal connected to the CICS system with applid applid2, issue the command

    CEMT I UOW(uowid)

    or

    CEMT I UOWDSNFAIL

    to identify the applid of the CICS system that is coordinating the distributed unit of work. Then attempt to reestablish contact between the coordinating CICS and the system that owns the lock.

  3. The unit of work has failed backout. From a terminal connected to the CICS system with applid applid2, issue the command
    CEMT INQUIRE
    UOWDSNFAIL DATASET(dsname)
    to determine the reason why unit of work uowid failed backout while processing data set dsname. There are several reasons why a unit of work can fail backout, each identified by a different reason code from CEMT INQUIRE UOWDSNFAIL. See the CICS Problem Determination Guide for guidance on how to resolve each of these types of backout failure.
Destination:

CSFL

Modules:

DFHFCRS

XMEOUT Parameters: date, time,applid, termid, userid, tranid, trannum, dsname, X'uowid',applid2

DFHFC0170
applid An attempt to release locks which are held by RLS but unknown to CICS has failed.
Explanation:

An attempt was made to release locks which are held on behalf of this CICS system by the VSAM RLS lock manager, but about which CICS has no knowledge. Such locks are known as "orphan" locks. The attempt to release the locks failed, either because the VSAM RLS server is not available or because there were no locks to release.

System action:

CICS continues. The locks are automatically released after the VSAM RLS server becomes available again.

The presence of these "orphan" locks could prevent the running of non-RLS applications against the data sets which hold such locks. "Orphan" locks can also cause LOCKED responses to be returned to applications running on CICS systems which have access to an available VSAM RLS server and try to update the locked records, or try to read the records with one of the read integrity options.

Since CICS has no knowledge of "orphan" locks, it is not possible to get information about them using CICS API commands.

User response:

If the failure is due to the server not being available, wait for the VSAM RLS server to restart. If it does not restart automatically, determine the reason and attempt to start it manually.

If the failure is due to there being no locks to release, this could either be a result of some user action resulting in locks being deleted such as deleting the data set, or it could indicate a severe VSAM error. If user action is not responsible, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCRR

XMEOUT Parameter: applid

DFHFC0171
applid Lost locks recovery might be delayed by inflight transactions.
Explanation:

A coupling facility (CF) lock structure failure has occurred, and SMSVSAM has been unable to rebuild the lock structure dynamically. This has resulted in the loss of VSAM RLS locks. SMSVSAM has notified CICS of this event so that CICS can perform lost locks recovery processing. In the course of this processing, CICS has attempted to purge inflight transactions that hold one or more of the lost locks in order to expedite recovery from the lost locks condition. However, it has not been possible to purge all of the transactions.

RLS lost locks recovery cannot complete until all UOWs that have updated data sets in RLS mode are completed. It is unlikely that an inflight transaction can complete normally in a lost locks situation because it will abend at the next attempt to access RLS. CICS attempts to purge inflight transactions because allowing them to run to completion (when they will probably abend anyway) could take a long time. This is particularly the case for conversational transactions.

System action:

CICS continues.

If the failure to purge a transaction is due to a severe error, message DFHFC0002 is issued and a dump is taken.

User response:

It may not be necessary to take any action because the purging of transactions is only a precautionary measure.

This message indicates that there are inflight UOWs that have not yet completed only when there are data sets that return a LOSTLOCKS value of RECOVERLOCKS after you have resolved any failed units of work that had updated the data sets. (See the EXEC CICS INQUIRE DSNAME(...) command for information about the LOSTLOCKS parameter.)

If it is possible to identify the transactions in question, either ensure that they run to normal completion, or attempt to force purge them using the CEMT master terminal command. However, as this should be a rare situation, consider performing an immediate shutdown of CICS followed by an emergency restart as an alternative solution. This causes all inflight transactions to be backed out.

Destination:

Console

Modules:

DFHFCRR

XMEOUT Parameter: applid

DFHFC0172
applid File control is unable to return to processing on the QR TCB because a change mode request has failed. CICS will t erminate.
Explanation:

Normally most CICS functions are run on a TCB called the QR TCB. Exceptionally, file control issues OPEN and CLOSE requests on a TCB called the FO TCB. File control may also process VSAM read and write requests on a TCB called the CO TCB if SUBTSKS=1 has been specified in the SIT.

After completing its work on the RO or CO TCB, file control must return to processing on the QR TCB. In order to return to the QR TCB, file control has issued a CHANGE_MODE call to the CICS dispatcher. This request has failed.

System action:

This is a severe error. CICS is unable to continue processing because it must be running on the QR TCB in order to do so. CICS is terminated with a dump.

The dispatcher domain has put out messages to describe the failure in the CHANGE_MODE request.

User response:

See the messages issued by the dispatcher domain for further guidance.

Destination:

Console

Modules:

DFHFCRO, DFHFCCA, DFFCRV, DFHFCFS

XMEOUT Parameter: applid

DFHFC0173
date time applid VSAM has issued a {deadlock | timeout | locked} response but cannot supply problem determination data.
Explanation:

After certain failures, VSAM normally provides problem determination information which CICS uses to issue diagnostic messages and create exception trace entries.

However, although VSAM set a return code indicating that a failure occurred, it is unable to provide any problem determination information.

The failure detected by VSAM RLS is one of the following:

System action:

CICS continues processing the error in the normal way but cannot issue any of the normal problem determination messages or create the usual exception trace entries.

CICS does not take a dump. However, you can request a dump via the dump table in the usual way.

User response:

This indicates an error in VSAM RLS. You may wish to take a dump of the SMSVSAM server. See the appropriate DFSMS/MVS manual for further guidance.

Destination:

CSFL

Modules:

DFHFCRS

XMEOUT Parameters: date, time,applid, {1=deadlock, 2=timeout, 3=locked}

DFHFC0174
date time applid tranid trannum termid userid A deadlock has occurred as a result of a lock promote failure. There are nnn transactions or Transactional VSAM units of recovery holding this lock.
Explanation:

This message and the following DFHFC0165 or DFHFC0175 messages are issued to assist in problem determination when transactions abend with the AFCW abend code or receive RECORDBUSY response as NOSUSPEND was specified.

An attempt made by transaction tranid with transaction number trannum to update a file which is open in VSAM RLS mode has failed because VSAM has detected a deadlock while attempting to promote a shared lock to become an exclusive lock.

VSAM RLS returns problem determination information to CICS to assist with debugging the deadlock. However, this type of deadlock looks to VSAM like a timeout and thus the information returned to CICS looks like the information returned after a timeout. Hence this message is followed by one or more DFHFC0165 or DFHFC0175 messages instead of the DFHFC0167 messages which follow other types of deadlocks.

When the deadlock occurred there were nnn other transactions or Transactional VSAM units of recovery holding the required lock.

System action:

The transaction receives an AFCW abend or RECORDBUSY response.

CICS displays message DFHFC0174 to identify the failing transaction and the number of owners of the lock. CICS also issues message DFHFC0165 or DFHFC0175 once for each lock owner. CICS issues message DFHFC0168 instead of DFHFC0165 or DFHFC0175 in the unlikely event that VSAM RLS is unable to identify the lock owner.

User response:

The following DFHFC0165 or DFHFC0175 messages identify the transactions that are holding the required lock and the CICS systems that they are running in, or the units of recovery which are holding the locks and the Transactional VSAM instances they are running in, respectively. Examine these transactions or units of recovery to determine why they are not releasing VSAM RLS locks. Examine other RLS resources they acquire to determine whether this could cause a deadlock with the failing transaction.

Destination:

CSFL

Modules:

DFHFCRS

XMEOUT Parameters: date, time,applid, tranid, trannum, termid, userid, nnn

DFHFC0175
date time applid tranid trannum termid userid. Transactional VSAM unit of recovery X'urid' running in job jobname on Transactional VSAM instance TVSInstance in MVS mvsid holds {add to end lock | internal lock | exclusive lock on key | shared lock on key }X'keyid' in data set dsname causing {true | false} contention.
Explanation:

This message and the preceding message DFHFC0164 or DFHFC0174 are issued to assist in problem determination when transactions abend with the AFCV or AFCW abend codes, or when applications receive the RECORDBUSY condition.

Normally this message appears after VSAM returns a timeout response to CICS. However, it may also appear after VSAM returns a deadlock response to CICS when that deadlock arises as a result of a failure to promote a lock. When this message is associated with a timeout response from VSAM, it is preceded by message DFHFC0164. When this message is associated with a deadlock response from VSAM it is associated with message DFHFC0174.

There is one occurrence of message DFHFC0175 for each unit of recovery currently owning the required lock.

The name of the transaction that has failed is tranid and it has task number trannum.

The message inserts that identify the owner of the lock which caused this transaction to time out are as follows:

The message identifies whether the lock is held as an exclusive lock or a shared lock:

A lock causes true contention if the request was for a lock against the locked key. A lock causes false contention if the request was for a lock against a different key but the lock requests clashed because of the RLS key hashing algorithm which is used when the key length exceeds 16 characters.

System action:

This message is preceded by DFHFC0164 or DFHFC0174. See the description of DFHFC0164 or DFHFC0174 for a description of the system action associated with this message.

User response:

This message is preceded by DFHFC0164 or DFHFC0174. See the description of DFHFC0164 or DFHFC0174 for a description of the user actions associated with this message.

Destination:

CSFL

Modules:

DFHFCRS

XMEOUT Parameters: date, time,applid, tranid, trannum, termid, userid, X'urid', jobname,TVSInstance, mvsid, {1=add to end lock , 2=internal lock , 3=exclusive lock on key , 4=shared lock on key },X'keyid', dsname, {1=true,2=false}

DFHFC0177
date time applid tranid termid userid. Transactional VSAM unit of recovery id X'urid' running in jobname/TVSInstance in MVS mvsid holds {add to end lock | internal lock | exclusive lock on key | shared lock on key }X'key1' on data set dsname1 and is waiting for {add to end lock |internal lock | exclusive lock on key |shared lock on key }X'key2' on data set dsname2.
Explanation:

This message and the preceding DFHFC0166 message are issued to assist in problem determination when transactions abend with AFCW abend codes.

The preceding message DFHFC0166 reports that a deadlock has been detected and includes how many units of recovery exist in the deadlock chain.

Message DFHFC0177 is issued once for each unit of recovery in the deadlock chain and includes the resource that unit of recovery holds and which resource it is waiting for.

The message inserts are as follows:

The message identifies whether the lock is held as an exclusive lock or a shared lock and whether the unit of recovery is attempting to acquire an exclusive or shared lock.

System action:

The application request which encountered the error receives an AFCW abend.

User response:

See the description of message DFHFC0166.

Destination:

CSFL

Modules:

DFHFCRS

XMEOUT Parameters: date, time,applid, tranid, termid, userid, X'urid', jobname/TVSInstance, mvsid, {1=add to end lock , 2=internal lock , 3=exclusive lock on key , 4=shared lock on key }, X'key1', dsname1,{1=add to end lock , 2=internal lock ,3=exclusive lock on key , 4=shared lock on key }, X'key2', dsname2

DFHFC0179
date time applid termid userid. Transaction tranid with transaction number trannum encountered an RLS retained lock held on data set dsname by unit of recovery X'urid' within Transactional VSAM instance TVSInstance.
Explanation:

An attempt was made to update a record which is currently held locked by a retained RLS lock.

Message inserts are as follows:

This message is issued to aid in problem diagnosis. It identifies the owner of the lock that is causing a request to fail with a ‘LOCKED’ response.

System action:

The application request which encountered the error receives a ‘LOCKED’ response.

User response:

If repeated LOCKED responses are causing a problem, note the name of the Transactional VSAM instance and the identifier of the unit of recovery and attempt to find out why the unit of recovery is holding a retained lock. The Transactional VSAM unit of recovery may have failed or suffered backout failure. If the Transactional VSAM application has failed the lock will normally be released if the application is rerun. If the Transactional VSAM application has suffered backout failure you will need to use Transactional VSAM procedures to perform backout failure retry in order to release the lock.

Destination:

CSFL

Modules:

DFHFCRS

XMEOUT Parameters: date, time,applid, termid, userid, tranid, trannum, dsname, X'urid',TVSInstance

DFHFC0200
date time applid {RLS | Non-RLS} file filename has been allocated to data set dataset. Module module.
Explanation:

This message provides a record of the dynamic allocation of the file filename to the data set dataset.

System action:

Processing continues.

User response:

None.

Destination:

CSFL

Modules:

DFHFCN, DFHFCRO

XMEOUT Parameters: date, time,applid, {1=RLS, 2=Non-RLS}, filename, dataset, module

DFHFC0201
date time applid {RLS | Non-RLS} file filename has been deallocated. Module module.
Explanation:

This message provides a record of the dynamic deallocation of the file filename.

System action:

Processing continues.

User response:

None.

Destination:

CSFL

Modules:

DFHFCN, DFHFCRO

XMEOUT Parameters: date, time,applid, {1=RLS, 2=Non-RLS}, filename, module

DFHFC0202
date time applid terminal userid tranid FCT entry for filename has been added.
Explanation:

This message provides the system with a record of the dynamic addition of FCT entry, filename.

System action:

Processing continues.

User response:

None.

Destination:

CSFL

Modules:

DFHFCMT.

XMEOUT Parameters: date, time,applid, terminal, userid, tranid, filename

DFHFC0203
date time applid terminal userid tranid FCT entry for filename has been deleted.
Explanation:

This message provides a record of the dynamic deletion of FCT entry filename.

This occurs when a file, which already exists in the system, is being installed using RDO. It should be followed by message DFHFC0202 indicating that the new file definition has been added.

System action:

Processing continues.

User response:

None.

Destination:

CSFL

Modules:

DFHFCMT.

XMEOUT Parameters: date, time,applid, terminal, userid, tranid, filename

DFHFC0204
date time applid terminal userid tranid FCT entry for filename has been updated.
Explanation:

This message provides a record of updates to an FCT entry other than OPEN, CLOSE, ENABLE and DISABLE.

An FCT entry is updated by an EXEC CICS SET FILE command or by a CEMT SET FILE command.

System action:

Processing continues.

User response:

None.

Destination:

CSFL

Modules:

DFHFCMT.

XMEOUT Parameters: date, time,applid, terminal, userid, tranid, filename

DFHFC0205
date time applid terminal userid tranid SHRCTL block for LSR pool lsrpool has been updated.
Explanation:

This message provides a record of the updates to a SHRCTL block.

A SHRCTL block exists for VSAM LSR pools 1-8 and is updated by an RDO install of an LSRPOOL object.

System action:

Processing continues.

User response:

None.

Destination:

CSFL

Modules:

DFHFCRL.

XMEOUT Parameters: date, time,applid, terminal, userid, tranid, lsrpool

DFHFC0206
date time applid terminal userid tranid AFCT entry for filename has been added.
Explanation:

This message provides the system with a record of the dynamic addition of a remote file filename.

System action:

Processing continues.

User response:

None.

Destination:

CSFL

Modules:

DFHAFMT.

XMEOUT Parameters: date, time,applid, terminal, userid, tranid, filename

DFHFC0207
date time applid terminal userid tranid AFCT entry for filename has been deleted.
Explanation:

This message provides a record of the dynamic deletion of a remote file filename.

This occurs when a remote file, which already exists in the system, is being deleted using RDO.

System action:

Processing continues.

User response:

None.

Destination:

CSFL

Modules:

DFHAFMT.

XMEOUT Parameters: date, time,applid, terminal, userid, tranid, filename

Start of changeDFHFC0208IEnd of change
Start of changeapplid LSR pool n is being built dynamically by CICS because all of the necessary parameters have not been supplied. Either there is no LSRPOOL definition or it is incomplete. The following are not defined: 'CISIZE''STRINGS''MAXKEYLENGTH'. A delay is possible.End of change
Start of change
Explanation:

If one or more of the parameters, CI size, strings and maxkeylength are not defined for a LSR pool, either because there is no LSRPOOL definition or it is incomplete, then CICS will calculate the size by using information from the VSAM Catalog for data sets allocated to this LSR pool.

End of change
Start of change
System action:

CICS will issue SHOWCATS to obtain the information necessary to calculate the LSR pool size. If any data sets have been migrated the SHOWCAT could take longer than expected.

End of change
Start of change
User response:

If there are severe delays due to SHOWCAT processing, you will have to wait for migrated data sets to be recalled, and for the calculation of the LSR pool size to complete. If you wish to avoid similar problems in the future, consider defining the LSR pool explicitly. The missing parameters are contained in this message.

Normally, you will not experience delays, in which case no user action is required.

You can suppress this message with the system initialization parameter, MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCLEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changen,End of changeStart of change'CISIZE', End of changeStart of change'STRINGS', End of changeStart of change'MAXKEYLENGTH'End of change

DFHFC0300
applid (tranid termid) purge deferred due to incomplete I/O operation on VSAM file 'filename'.
Explanation:

An attempt has been made to purge a transaction using FORCE. Transaction tranid is currently waiting for completion of an I/O operation on the VSAM file filename. termid identifies the terminal running this transaction. The data set name appears in message DFHFC0305 which follows this message.

System action:

The transaction waits until the I/O operation is completed before the purge is allowed to take effect. This is done to avoid a risk to data integrity. After the I/O completes the transaction is terminated with transaction abend code AFCY.

User response:

If the transaction does not terminate within a few seconds, it may be that the I/O wait is genuine (for example, another CEC has reserved the DASD volume). If this is the case, wait until the I/O situation is relieved before trying again.

Alternatively, there may be a system problem that warrants terminating CICS and using emergency restart to guarantee data integrity. If this is the case, terminate CICS and perform an emergency restart.

Destination:

Console

Modules:

DFHFCVR

XMEOUT Parameters: applid, tranid,termid, filename

DFHFC0301
applid (tranid termid) purge deferred due to incomplete I/O operation on BDAM file 'filename'.
Explanation:

An attempt has been made to purge a transaction using FORCE. Transaction tranid is currently waiting for completion of an I/O operation on the BDAM file filename. termid identifies the terminal running this transaction. The data set name appears in message DFHFC0305 which follows this message.

System action:

The transaction waits until the I/O operation is completed before the purge is allowed to take effect. This is done to avoid a risk to data integrity. After the I/O operation is completed, the transaction is terminated with transaction abend code AFCY.

User response:

If the transaction does not terminate within a few seconds, the I/O wait might be genuine (for example, another CEC has reserved the DASD volume). If this is the case, wait until the I/O situation is relieved before trying again.

Alternatively, there may be a system problem that warrants terminating CICS and using emergency restart to guarantee data integrity If this is the case, terminate CICS and perform an emergency restart.

Destination:

Console

Modules:

DFHFCBD

XMEOUT Parameters: applid, tranid,termid, filename

DFHFC0302
applid (tranid termid) CICS terminating. Failure while waiting for I/O operation on VSAM file 'filename'.
Explanation:

A DISASTER type error occurred when the transaction tranid was waiting for the completion of an I/O operation on the VSAM file whose file name and data set name appear in message DFHFC0305 which follows this message. termid identifies the terminal running this transaction.

System action:

CICS is terminated with a system dump (dump code FC0302).

User response:

This problem was caused by an earlier error. Look for earlier messages and return codes (for example, from the dispatcher domain) and associated trace entries and dumps.

If the problem cannot be traced to an application error, you will require further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCVR

XMEOUT Parameters: applid, tranid,termid, filename

DFHFC0303
applid (tranid termid) CICS terminating. Failure while waiting for I/O operation on BDAM file 'filename'.
Explanation:

A DISASTER type error occurred when transaction tranid was waiting for the completion of an I/O operation on BDAM file filename.

termid identifies the terminal running this transaction.

System action:

CICS is terminated with a system dump (dump code FC0303).

User response:

This problem was caused by an earlier error. Look for earlier messages and return codes (for example, from the dispatcher domain) and associated trace entries and dumps.

If the problem cannot be traced to an application error, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCBD

XMEOUT Parameters: applid, tranid,termid, filename

DFHFC0304
applid Dump taken in module_name due to a file control OPEN/CLOSE error.
Explanation:

This message is issued after DFHFCFS has made an OPEN or CLOSE request which has completed with an error. The specific error is identified by another message. In most cases the other message appears before this message, but if the error occurs during the building of a shared resources pool, the other message appears after this message.

The failure is identified as one of the following:

System action:

A trace entry is made and a dump is taken with dumpcode FC0304.

User response:

Locate the fault by examining the trace entry and the dump.

Destination:

Console

Modules:

DFHFCL, DFHFCM, DFHFCN

XMEOUT Parameters: applid, module_name

DFHFC0305
applid Message msgno file 'filename' dsname 'dataset'.
Explanation:

This message follows message DFHFC0300, DFHFC0302, DFHFC0307, DFHFC0308 or DFHFC0309. It identifies the VSAM data set name referred to in those messages.

If this message follows DFHFC0300 or DFHFC0302, it is issued from DFHFCVR.

If this message follows DFHFC0308 or DFHFC0309, it is issued from DFHFCRV.

If this message follows DFHFC0307, it is issued from DFHFCVS.

System action:

Processing continues in the way specified in the preceding message from the list above, whichever is applicable.

User response:

Find the earlier message to which this information refers and follow the user response for that message.

Destination:

Console

Modules:

DFHFCVR, DFHFCVS, DFHFCRV

XMEOUT Parameters: applid, msgno,filename, dataset

DFHFC0307
applid I/O error on file 'filename', component code X'code'. File is temporarily disabled.
Explanation:

An I/O error was reported by VSAM after a request to update VSAM file filename.

The file has been specified with LSR so VSAM has not released the buffers it assigned to process the request. Therefore, CICS must take special action to release them.

The name of the data set associated with the file is in message DFHFC0305 which follows, although the error may have been encountered elsewhere. This is indicated by the value of the component code X'code'. Its possible values and the corresponding error locations are as follows.

System action:

Activity against the file is stopped, and the file is closed and then reopened in order to release the VSAM output buffers. Until the close has completed successfully, the file appears ‘UNENABLED’ to new would-be users and they receive a ‘NOTOPEN’ response to requests to use the file. The application request which encountered the error receives an ‘IOERR’ response.

User response:

The installation should follow its standard procedure for I/O errors. No special additional action is required to respond to this particular message although the data set name and component code may help in identifying the problem.

Destination:

Console

Modules:

DFHFCVS

XMEOUT Parameters: applid, filename, X'code'

DFHFC0308
applid tranid termid Purge deferred due to incomplete I/O operation on VSAM RLS file filename
Explanation:

An attempt has been made to purge a transaction using FORCE. Transaction tranid is currently waiting for completion of an I/O operation on the VSAM RLS file filename. termid identifies the terminal running this transaction. The data set name is included in message DFHFC0305 which follows this message.

System action:

The transaction waits until the I/O operation is completed before the purge is allowed to take effect. This is done to avoid a risk to data integrity. After the I/O operation is completed, the transaction is terminated with transaction abend code AFCY.

User response:

If the transaction does not terminate within a few seconds, the I/O wait might be genuine (for example, another CEC has reserved the DASD volume). If this is the case, wait until the I/O situation is relieved before trying again.

Alternatively, there may be a system problem that warrants terminating CICS and using emergency restart to guarantee data integrity. If this is the case, terminate CICS and perform an emergency restart.

Destination:

Console

Modules:

DFHFCRV

XMEOUT Parameters: applid, tranid,termid, filename

DFHFC0309
applid tranid termid Failure while waiting for I/O operation on VSAM RLS file filename
Explanation:

A DISASTER type error occurred when the transaction tranid was waiting for the completion of an I/O operation on the VSAM RLS file filename

System action:

CICS returns to VSAM who completes the wait for the I/O operation on CICS behalf. Since VSAM rather than CICS completes the wait for I/O to complete, there may be a significant degradation in CICS performance until the operation completes.

User response:

This problem was caused by an earlier error. Look for earlier messages and return codes (for example, from the dispatcher domain) and associated trace entries and dumps.

If the problem cannot be traced to an application error, you will require further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCRV

XMEOUT Parameters: applid, tranid,termid, filename

DFHFC0310
applid tranid termid Purge deferred due to incomplete I/O operation on the RLS control ACB.
Explanation:

An attempt has been made to purge a transaction using FORCE. Transaction tranid is currently waiting for completion of an I/O operation on the VSAM RLS control ACB.

termid identifies the terminal running this transaction.

System action:

The transaction waits until the I/O operation is completed before the purge is allowed to take effect. This is done to avoid a risk to data integrity. After the I/O operation is completed, the transaction is terminated with transaction abend code AFCY.

User response:

If the transaction does not terminate within a few seconds, the VSAM wait might be genuine (for example, certain requests may take a fairly long time to complete). If this is the case, wait until the VSAM request has completed before trying again.

Alternatively, there may be a system problem that warrants terminating CICS and using emergency restart to guarantee data integrity. If this is the case, terminate CICS and perform an emergency restart.

Destination:

Console

Modules:

DFHFCCA

XMEOUT Parameters: applid, tranid,termid

DFHFC0311
applid tranid termid Failure waiting for I/O operation on the RLS control ACB.
Explanation:

A DISASTER type error occurred when the transaction tranid was waiting for the completion of an I/O operation on the VSAM RLS control ACB.

System action:

CICS returns to VSAM and VSAM completes the wait for the I/O operation on CICS behalf. Since VSAM rather than CICS completes the wait for I/O to complete, there may be a significant degradation in CICS performance until the operation completes.

User response:

This problem was caused by an earlier error. Look for earlier messages and return codes (for example, from the dispatcher domain) and associated trace entries and dumps.

If the problem cannot be traced to an application error, you will require further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCCA

XMEOUT Parameters: applid, tranid,termid

DFHFC0312
applid Message msgno data set dsname
Explanation:

This message follows message DFHFC0152 or DFHFC0160. It identifies the VSAM data set name referred to in those messages.

System action:

Processing continues as specified in either DFHFC0152, or DFHFC0160.

User response:

Find the earlier message to which this information refers and follow the user response for that message.

Destination:

Console

Modules:

DFHFCCA

XMEOUT Parameters: applid, msgno,dsname

Start of changeDFHFC0313IEnd of change
Start of changeapplid VSAM has returned an error with an RPL feedback - return code : X'rc' component code : X'cc' error code : X'ec' for file : filename and dsname : dataset The data set may be out of synch with its Alternate Indices.End of change
Start of change
Explanation:

VSAM has returned an error for VSAM file filename.

An ILLOGIC response is returned to the application.

This is indicated by the value of the component code X'cc'. Its possible values and the corresponding error locations are as follows:

End of change
Start of change
System action:

An ILLOGIC response is returned to the application.

End of change
Start of change
User response:

You may need to delete, redefine and re-build your alternate indices based on this file.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCVSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changerc',End of changeStart of changeX'End of changeStart of changecc', End of changeStart of changeX'End of changeStart of changeec', End of changeStart of changefilename, End of changeStart of changedatasetEnd of change

Start of changeDFHFC0314IEnd of change
Start of changeapplid VSAM has insufficient LSR buffers to fully backout the failed request.End of change
Start of change
Explanation:

VSAM has returned an error for VSAM file mentioned in DFHFC0313 and an error code of X'98'.

An ILLOGIC response is returned to the application.

The error code indicates that VSAM has insufficient LSR buffers to backout the failed request fully.

End of change
Start of change
System action:

An ILLOGIC response is returned to the application.

End of change
Start of change
User response:

Increase the allocation of LSR buffers. You may also need to delete, redefine and re-build your alternate indices based on this file.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCVSEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

DFHFC0400
applid This CICS system is not authorized to provide shared access to data tables - reason code X'code'.
Explanation:

CICS is about to open a data table but has been unable to make provision for sharing the table with other CICS systems because a security check for update access to the resource name DFHAPPL.applid has failed. The value of the reason code, X'code', provides further information on the reason for the failure of the security check. It has the format X'ffrraaaa' where ff identifies the authorization check which failed, rr gives the register 15 return code from SAF, and aaaa is the SAFPRRET value.

The values of X'ff' are

X'01'
Access was refused by an AUTH security check.
X'02'
Access was refused by a FASTAUTH security check.
System action:

CICS continues normally but no other CICS systems are able to share any data tables it creates until authority is granted and a table is subsequently opened.

User response:

Ensure that CICS has the necessary authorization to provide shared access to data tables. Refer to the description of either the AUTH or FASTAUTH macro in the RACF documentation for explanations of the values that were reported in the reason code, X'code', and to determine the changes to the security definitions or setup that are required to allow the CICS system to act as a shared data table server (assuming that this is desired).

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, X'code'

DFHFC0401
applid This CICS system is now authorized to provide shared access to data tables.
Explanation:

CICS is about to open a data table. On a previous occasion message DFHFC0400 was issued because authorization checks failed preventing this CICS system from making provision for sharing its data tables with any other CICS system. The check has been retried successfully.

System action:

CICS continues normally. Subject to specific authorization checks, other CICS systems are now able to share this system's data tables.

User response:

None.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameter: applid

DFHFC0402
applid CICS cannot provide shared access to data tables because CICS is not defined as an MVS subsystem.
Explanation:

CICS is about to open a data table but has been unable to make provision for sharing the table with other CICS systems because CICS has not been defined as an MVS subsystem.

System action:

CICS continues normally but no other CICS systems are able to share any data tables it creates.

User response:

CICS must be defined as an MVS subsystem in order to permit the sharing of data tables between CICS systems.

See the CICS Shared Data Tables Guide for more guidance.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameter: applid

DFHFC0403
applid CICS cannot provide shared access to remote data tables because CICS is not defined as an MVS subsystem.
Explanation:

CICS is about to access a remote file resource. However, shared data tables cannot be used to access any remote tables because CICS has not been defined as an MVS subsystem.

If this message is issued on a CICS system at release 3.2.1, it means that the shared data tables module DFHDTINS is installed in the LPA or in the load library used by this CICS system, and has therefore been loaded by mistake.

System action:

CICS continues normally and function ships this and subsequent remote file requests.

User response:

CICS must be defined as an MVS subsystem in order to permit the sharing of data tables between CICS systems.

If the message was issued by a CICS/ESA 3.2.1 system, check where the DFHDTINS module is located. If DFHDTINS is in the load library specified by this CICS, it should be removed: shared data tables support cannot be installed on a CICS system at a lower level than 3.3. If it is in the link pack area (LPA) of this MVS system, it should be removed: the DFHDTINS module should not be placed in the LPA of an MVS system which contains any CICS regions at release 3.2.1 which might want to use data tables, unless a PTF has been applied to the CICS 3.2.1 regions.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameter: applid

DFHFC0405
applid This CICS system cannot provide shared access to data tables because an earlier job step has used MVS cross-memory services.
Explanation:

CICS is prevented from using shared data tables because of the use of MVS cross-memory services by an earlier job step. CICS has attempted to create an entry table during LOGON as a shared data table server, but this has resulted in an MVS 052 ABEND because a prior jobstep owned space-switching entry tables. (MVS does not allow subsequent job steps to establish a cross-memory environment.)

System action:

CICS continues normally but other CICS systems are unable to gain shared access to any data tables that this CICS system creates.

User response:

In order to use the shared access to data tables feature, review the sequence of job steps in the job which includes this CICS system.

See the CICS Shared Data Tables Guide and also the explanation of system abend code 052, reason code 0314 in MVS System Codes for more guidance.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameter: applid

DFHFC0406
applid This CICS system is not authorized for shared access to any data tables owned by the CICS system with applid applid2 - reason code X'code'.
Explanation:

A file request for a remote file resource is about to be passed to a CICS system with the specified applid. The remote system has registered as a shared data table server, but this system cannot access any of its tables because a security check for read access to the resource name DFHAPPL.applid2 has failed, where applid2 is the applid of the data table owning CICS system. The value of the reason code, X'code', provides further information on the reason for the failure of the bind security check. It has the format X'ffrraaaa' where ff identifies the authorization check which failed, rr gives the register 15 return code from SAF, and aaaa is the SAFPRRET value.

The values of X'ff' are

X'01'
Access was refused by an AUTH security check.
X'02'
Access was refused by a FASTAUTH security check.
User response:

If it was intended that this CICS system should be able to access data tables owned by the system applid2, refer to the description of either the AUTH or FASTAUTH macro in the RACF documentation for explanations of the values that were reported in the reason code, X'code', and to determine what changes to the security definitions or setup are required.

System action:

CICS continues normally and function ships this and subsequent requests directed to the specified remote system until authority is granted. Access is retried after about 10 minutes.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, applid2,X'code'

DFHFC0407
applid This CICS system is now authorized for shared access to data tables owned by the CICS system with applid applid2.
Explanation:

The security check which failed earlier and was reported in message DFHFC0406, has now succeeded. This system can now attempt to access shared data tables owned by the CICS system with applid applid2.

System action:

CICS continues normally. Subject to specific resource authorization checks, shared data tables owned by the remote CICS system can now be accessed by this system.

User response:

None.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, applid2

DFHFC0408
applid This CICS system is not authorized for shared access to remote file filename - reason code X'code'.
Explanation:

A file request to the specified remote file resource has just been processed. The file owning region contains shared data tables. An attempt was made to connect to any data table associated with the file but the connecting region failed the security check for shared access to the file resource. However, function shipped access was not similarly prevented.

This message can be issued whether or not the remote file has an associated data table. This is because it is not possible to determine whether a table exists until cross-memory linkage has been established to the file owning region, and this is only done after a connection attempt has passed all security checks. Once cross-memory linkage has been set up, any further connection attempts can first check whether a table exists. The shared access security check is then only needed when a data table is known to be available.

The value of the reason code, X'code', provides further information on the reason for the failure of the file security check. It has the format X'ffrraaaa'; where ff identifies the userid that was refused access, rr gives the register 15 return code from SAF, and aaaa is the SAFPRRET value.

The values of X'ff' are

X'01'
The requesting system's own userid was refused read access to the remote file filename.
X'02'
The default userid of the CICS system which owns the remote file filename was used in the security check for read access to the file, and access was refused.
System action:

CICS continues normally and function ships this and subsequent requests directed to the specified remote file until authority to use shared access is granted. Access is retried after about 10 minutes.

User response:

Check whether shared access from this system to the specified file is intended. If it is, use the additional information provided in the reason code to determine what changes to the security definitions or set-up are required.

See the CICS Shared Data Tables Guide for an explanation of the rules determining which userid is used for a file security check.

Destination:

Console

Modules:

DFHEIFC

XMEOUT Parameters: applid, filename, X'code'

DFHFC0409
applid This CICS system is now authorized for shared access to remote file filename.
Explanation:

The security check which failed earlier, and was reported in message DFHFC0408, has now succeeded. This system can now use shared access to the specified table.

System action:

CICS continues normally.

User response:

None.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename

DFHFC0410
applid Data table cannot be opened. Data table initialization has failed for reason X'code'.
Explanation:

CICS is about to open a data table but has been unable to initialize shared data table services. The value of the reason code, X'code', provides further information about why CICS was unable to initialize shared data table services.

The format of the reason code is either: X'ffaaaaaa', in which ff is a value less than X'80' that identifies the type of failure, and aaaaaa is additional information provided for some of the failures, or when an abnormal termination (abend) has occurred, X'axxxrrrr' in which a is a value greater than or equal to X'8' that categorizes the type of abend, rrrr contains any register 15 abend reason code, and xxx contains the system or user completion code as three hexadecimal digits.

When X'code' < X'80000000', the values of X'ff' are:

X'01'
An unexpected failure occurred. This code is reported when the data tables SVC detects an unexpected error.
X'04'
An error was returned by the MVS RESMGR macro, called to establish an MVS resource manager for end-of-task processing. The first byte of the additional information, X'aa0000' contains the low order byte of the register 15 return code from the MVS RESMGR macro.
X'06'
An error was returned by the CICS SVC. The first byte of the additional information, X'aa0000' is the register 15 return code from the attempt to call the CICS SVC.
X'08'
An error was returned by the MVS DSPSERV macro. The additional information in the reason code consists of 1 byte containing the register 15 return code followed by 2 bytes containing the middle bytes from the register 0 reason code returned by DSPSERV.
X'09'
An error was returned by the MVS ALESERV macro, called to create an access list entry either for the data space or for references to the primary address space. The additional information in the reason code consists of one byte containing the register 15 return code followed by two bytes containing the ALESERV function code (service type) and qualifier (options) which identify the failing request.
X'0E'
An attempt to serialize the use of shared data table services (thus ensuring that only one TCB per address space can use the services) has failed. The first byte of additional information contains the ENQ return code.

When X'code' >= X'80000000', the values of X'a' are formed from combinations of:

X'8'
An abend was detected.
X'4'
A user abend was detected, in which case xxx contains the hexadecimal equivalent of the user completion code (otherwise, xxx contains the hexadecimal system completion code).
X'2'
An abend was detected but could not be analyzed fully because no SDWA was available.
X'1'
An asynchronous abend was detected (otherwise, the abend was synchronous or could not be classified because there was no SDWA).
System action:

CICS continues normally. This message is followed either by message DFHFC0931 or by DFHFC0932. The following message indicates the action taken for the table involved. A system dump is taken for unexpected errors (X'ff' =X'01') and for abends (if dumps are requested for that abend code).

User response:

The response depends on the reason for the failure as indicated in the first byte of the reason code:

X'01'
Use the system dump to help you determine the cause of the problem.
X'04'
Refer to the documentation of the MVS RESMGR macro to interpret the low-order byte of the register 15 return code reported in the reason code.
X'06'
The most likely reason for a failure of the CICS SVC call is that the data tables SVC module DFHDTSVC could not be loaded, in which case the return code value is X'02'. If this is the case, check that the DFHDTSVC module is in the LPA or in an authorized library in the link list of the MVS system. If the module is in the correct location, investigate why it could not be loaded. There might be a hardware fault on the disk. Another less likely value for the return code is X'06', which implies that DFHDTSVC has been relink-edited and not marked reentrant.
X'08'
Refer to the documentation of the MVS DSPSERV macro to interpret the register 0 and register 15 return codes reported in the additional information part of the reason code.
X'09'
The function code (service type) and qualifier (options) reported in the reason code can be used to determine which ALESERV request was being attempted. Refer to the MVS ALESERV documentation and macro to interpret the function code, qualifier, and register 15 return code reported in the reason code.
X'0E'
This might indicate that the limit on the number of ENQs per address space has been reached, or that another TCB running in this CICS address space has already initialized as a requester of shared data table services.
>= X'80'
When the reason code indicates that an abend has been detected, use the additional information provided in the reason code to find out what the abend was, and refer to information on that abend code to determine the cause.
Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, X'code'

DFHFC0411
applid Data table cannot be opened. Data table initialization has failed owing to a storage failure - reason code X'code'.
Explanation:

CICS is about to open a data table but has been unable to initialize shared data table services because of a failure to obtain storage. The value of the reason code, X'code', provides further information about the type of storage which could not be obtained.

The format of the reason code is X'ttnnnnnn' in which tt identifies the type of storage and, for some of the codes, nnnnnn gives the hexadecimal size in bytes of the storage which could not be obtained. For fixed-length storage blocks, the reason code does not usually report the size.

The values of X'tt' are:

X'01'
Private storage from MVS subpool 230 (key 0) for a work area used by the data tables SVC
X'02'
Private storage from MVS subpool 0 for the local header block used by a shared data table server
X'03'
Private storage from MVS subpool 0 for a pool for data table blocks
X'04'
Private storage from MVS subpool 0 for a pool for file blocks
X'08'
MVS/ESA data space storage
X'09'
Private storage from MVS subpool 230 (key 0) for a region anchor
X'11'
Private storage from MVS subpool 0 for a dummy recovery block
X'12'
Storage from MVS subpool 252 required to load the DFHDTAM load module
X'13'
Private storage from MVS subpool 230 (CICS key) for a parameter list used by the data tables SVC
X'14'
Private storage from MVS subpool 230 (key 0) for a new ALET list section
System action:

CICS continues normally. This message is followed either by message DFHFC0931 or by DFHFC0932. The following message indicates the action taken for the table involved.

User response:

The response depends on the type of storage indicated by the reason code. If it indicates private storage, you should reconsider the various region size parameters which have been specified on the CICS job, or have been set as defaults for the system by IEALIMIT or the IEFUSI installation exit. It might be necessary to take an SDUMP of the CICS job and process it using the VERBEXIT VSMDATA in order to investigate the way in which MVS storage has been allocated to the various subpools.

If it indicates data space storage, check whether the size of data spaces in this MVS system has been limited by use of the IEFUSI installation exit.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, X'code'

DFHFC0412
applid Data table cannot be opened. Data table initialization has failed owing to a module loading failure - reason code X'code'.
Explanation:

CICS is about to open a data table but a module loading failure has prevented the initialization of shared data table services. The value of the reason code, X'code', provides further information about which module was being loaded, and what went wrong with the attempt to load it.

The format of the reason code is X'mfrraaaa' in which m identifies the module and f is a code for the type of failure. For some failures, rr contains the register 15 return code from the failing macro call, and aaaa might contain additional information.

The value of X'm' can be:

X'1'
DFHDTFOR
X'2'
DFHDTAM
X'6'
DFHMVRMS

The values of X'f' are:

X'1'
module not found by a LOAD, BLDL or CSVQUERY macro call.
X'2'
an error was returned by the MVS LOAD macro. The two bytes X'aaaa' of additional information in the reason code contain the completion code from the LOAD. X'rr' is the register 15 return code.
X'3'
an error was returned by the MVS CSVQUERY macro. X'rr' is the register 15 return code.
X'4'
an error was returned by the MVS BLDL macro. The two bytes X'aaaa' of additional information in the reason code contain the R0 reason code returned by BLDL.
X'5'
the module is not reentrant.
X'6'
the module had the wrong AMODE.
X'7'
the module had the wrong RMODE.
Note for CICS/ESA 3.2.1 users:
There is an additional code of X'08000000' which is only seen on a CICS/ESA 3.2.1 system that has DFHDTINS installed in the LPA or in its load library, and has mistakenly loaded this module.
System action:

CICS continues normally. This message is followed either by message DFHFC0931 or by DFHFC0932. The following message indicates the action taken for the table involved.

User response:

The response depends on the reason for the failure as indicated in the second hex digit of the reason code:

X'1'
Use the first hex digit to determine which module could not be found, and ensure that it is in the correct library.
X'2'
Refer to the documentation of the MVS LOAD macro to interpret the return and completion codes given in the reason code. There might also be a message from the MVS LOAD which explains the reason for the failure.
X'3'
Refer to the documentation of the MVS CSVQUERY macro to interpret the return code given in the second byte of X'code'.
X'4'
This indicates an I/O error or a storage allocation failure. Refer to the documentation of the MVS BLDL macro to interpret the values in the reason code X'code'.
X'5', X'6', X'7'
Use the first digit of the reason code to determine the name of the module, then check the status of that module. These errors imply that it is either not the module which was supplied with CICS or that it has become corrupted.
Note for CICS/ESA 3.2.1 users:
If the reason code was X'08000000', the shared data tables module DFHDTINS has been incorrectly installed in a library which is used by this CICS/ESA 3.2.1 system. If DFHDTINS is in the load library specified by this CICS, it should be removed: shared data tables support cannot be installed on a CICS system at a lower level than 3.3. If it is in the link pack area (LPA) of this MVS system, it should be removed: the DFHDTINS module should not be placed in the LPA of an MVS system which contains any CICS regions at release 3.2.1 which might want to use data tables, unless a PTF has been applied to the CICS 3.2.1 regions
Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, X'code'

DFHFC0415
applid Remote data tables cannot be accessed. Shared data table initialization has failed for reason X'code'.
Explanation:

CICS is about to access a remote file resource which may have an associated shared data table. However, shared data tables cannot be used to access any remote tables because CICS has been unable to initialize data table services. Start of changeNote that if CICS finds module DFHTDINS in the STEPLIB concatenation or in the LPA it will assume that shared data tables is required and will thus try to initialize it.End of change The value of the reason code, X'code', provides further information about why this CICS region was unable to perform the initialization required to act as a requester of shared data table services.

The format of the reason code is either: X'ffaaaaaa' in which ff is a value less than X'80' that identifies the type of failure, and aaaaaa is additional information provided for some of the failures; or, when an abnormal termination (ABEND) has occurred, X'axxxrrrr' in which a is a value greater than or equal to X'8' that categorizes the type of abend, rrrr contains any register 15 abend reason code, and xxx contains the system or user completion code as three hexadecimal digits.

When X'code' < X'80000000', the values of X'ff' are:

X'01'
An unexpected failure occurred. This code is reported when the data tables SVC detects an error which should never occur.
X'06'
An error was returned by the CICS SVC. The first byte of the additional information, aa0000, is the register 15 return code from the attempt to call the CICS SVC.
X'0E'
An attempt to serialize the use of shared data table services (thus ensuring that only one TCB per address space can use the services) has failed. The first byte of additional information contains the ENQ return code.

When X'code' >= X'80000000', the values of X'a' are formed from combinations of:

X'8'
An abend was detected.
X'4'
A user abend was detected, in which case xxx contains the hexadecimal equivalent of the user completion code (otherwise, xxx contains the hexadecimal system completion code).
X'2'
An abend was detected but could not be analyzed fully because no SDWA was available.
X'1'
An asynchronous abend was detected (otherwise, the abend was synchronous or could not be classified because there was no SDWA).
System action:

CICS continues normally and function ships this and subsequent remote file requests. Initialization is retried after about 10 minutes. A system dump is taken for unexpected errors (X'ff' =X'01') and for abends (if dumps are requested for that abend code).

User response:

The response depends on the reason for the failure as indicated in the first byte of the reason code:

X'01'
Use the system dump to help you determine the cause of the problem.
X'06'
The most likely reason for a failure of the CICS SVC call is that the data tables SVC module DFHDTSVC could not be loaded, in which case the return code value is X'02'. If this is the case, check that the DFHDTSVC module is in the LPA or in an authorized library in the link list of the MVS system. If the module is in the correct location, then investigate why it could not be loaded; possibly there might be a hardware fault on the disk. Another less likely value for the return code is X'06', which implies that DFHDTSVC has been relink-edited and not marked reentrant.
X'0E'
This might indicate that the limit on the number of ENQs per address space has been reached, or that another TCB running in this CICS address space has already initialized as a requester of shared data table services.
>= X'80'
When the reason code indicates that an abend has been detected, use the additional information provided in the reason code to find out what the abend was, and refer to information on that abend code to determine the cause.
Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, X'code'

DFHFC0416
applid Remote data tables cannot be accessed. Shared data table initialization has failed owing to a storage failure - reason code X'code'.
Explanation:

CICS is about to access a remote file resource. However, a failure to get storage has prevented CICS from initializing shared data table services. The value of the reason code, X'code', provides further information about the type of storage which could not be obtained:

The format of the reason code is X'ttnnnnnn' in which tt identifies the type of storage and, for some of the codes, nnnnnn gives the hexadecimal size in bytes of the storage which could not be obtained. For storage blocks whose length is fixed, the reason code does not usually report the size.

The values of X'tt' are:

X'01'
Private storage from MVS subpool 253 (below the 16MB line) for a work area required by module DFHQSSS
X'02'
Private storage from MVS subpool 0 for the shared data table header block required for this CICS to act as a data tables requester
X'09'
Private storage from MVS subpool 230 (key 0) for a region anchor
X'0A'
ECSA storage from subpool 241 (key 0) for a qualified subsystem block
X'0B'
ECSA storage from MVS subpool 241 (key 0) for a system anchor
X'0E'
Private storage from MVS subpool 230 (key 0) for a connect header block
System action:

CICS continues normally and function ships this and subsequent remote file requests. Initialization is retried after about 10 minutes.

User response:

The response depends on the type of storage indicated by the reason code.

If it indicates private storage, you should reconsider the various region size parameters which have been specified on the CICS job or have been set as defaults for the system by IEALIMIT or the IEFUSI installation exit. It might be necessary to take an SDUMP of the CICS job and process it using the VERBEXIT VSMDATA in order to investigate the way in which MVS storage has been allocated to the various subpools.

If it indicates ECSA (extended common service area) storage, you should review the CSA size specified in system parameter list IEASYSxx, or by use of the CSA override on initialization of the MVS system. You should also review the size of the ESQA, since the system might have started to use ECSA storage if the ESQA storage is depleted.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, X'code'

DFHFC0417
applid Remote data tables cannot be accessed. Shared data table initialization has failed owing to a module loading failure - reason code X'code'.
Explanation:

CICS is about to access a remote file resource. However, shared data tables cannot be used to access any remote tables because a module loading failure prevents CICS from initializing data table services.

The value of the reason code, X'code', provides further information about which module was being loaded, and what went wrong with the attempt to load it.

The format of the reason code is X'mfrraaaa' in which m identifies the module and f is a code for the type of failure. For some failures, rr contains the register 15 return code from the failing macro call, and aaaa might contain additional information.

The value of X'm' can be:

X'3'
DFHDTAOR
X'4'
DFHDTCV

The values of f are:

X'1'
module not found by LOAD
X'2'
an error was returned by the MVS LOAD macro. The two bytes X'aaaa' of additional information in the reason code contain the completion code from the LOAD. X'rr' contains the register 15 return code
X'5'
the module is not reentrant.
X'6'
the module had the wrong AMODE.
System action:

CICS continues normally and function ships this and subsequent remote file requests. Initialization is retried after about 10 minutes.

User response:

The response depends on the reason for the failure as indicated in the second hex digit of the reason code:

X'1'
Use the first hex digit to determine which module could not be found, and ensure that it is in the correct library.
X'2'
Refer to the documentation of the MVS LOAD macro to interpret the return and completion codes reported in the reason code. There might also be a message from the MVS LOAD which explains the reason for the failure.
X'5', X'6'
Use the first digit of the reason code to determine the name of the module, then check the status of that module. This error implies that it is either not the module which was supplied with CICS or that it has become corrupted.
Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, X'code'

DFHFC0420
applid Shared access to data tables cannot be provided by this CICS system because it has not been registered as a shared data table server - reason code X'code'.
Explanation:

CICS is about to open a data table but has been unable to do so because this CICS system has not been registered as a shared data table server. The value of the reason code, X'code', provides further information about why this CICS system was unable to register (LOGON) as a shared data table server.

The format of the reason code is either: X'ffaaaaaa' in which ff is a value less than X'80' that identifies the type of failure, and aaaaaa is additional information provided for some of the failures; or, when an abnormal termination (ABEND) has occurred, X'axxxrrrr' in which a is a value greater than or equal to X'8' that categorizes the type of ABEND, rrrr contains any register 15 ABEND reason code, and xxx contains the system or user completion code as three hexadecimal digits.

When X'code' < X'80000000', the values of X'ff' are:

X'01'
This code is reported when the data tables SVC detects an unexpected error.
X'02'
Another region within the MVS image with the same APPLID as this region is already registered (logged on) as a shared data tables server.
X'03'
DFHDTRM has supplied the data tables SVC with an invalid address for the PC vector, or the PC vector specifies an invalid number of entry table entries (ETEs). In the latter case, X'aaaaaa' contains the number of ETEs that were requested.
X'04'
A failure occurred when attempting to establish an MVS resource manager for end-of-memory processing. The first byte of the additional information, X'aa0000' contains the low order byte of the register 15 return code from the MVS RESMGR macro.
X'05'
A failure occurred when attempting to make the server address space permanently non-swappable. The additional information, X'aaaaaa', contains the low order 3 bytes of the code posted in an ECB that was specified when the SYSEVENT TRANSWAP macro was issued.
X'06'
An error was returned by the CICS SVC. The first byte of the additional information, X'aa0000' is the register 15 return code from the attempt to call the CICS SVC.
X'0D'
An error occurred when issuing an MVS ENQ to ensure that, at any given time, only one server per MVS system can be active for a given APPLID. The first byte of the additional information, X'aa0000' contains the return code from ENQ.
X'10'
An attempt to create the environment for shared data tables connect security checks has found that the security environment has already been set up.
X'11'
There is a disparity between the actual version of the CICS security block and the version which was used to assemble the shared data tables module DFHDTXS.

When X'code' >= X'80000000', the values of X'a' are formed from combinations of:

X'8'
An ABEND was detected.
X'4'
A user ABEND was detected, in which case xxx contains the hexadecimal equivalent of the user completion code (otherwise, xxx contains the hexadecimal system completion code).
X'2'
An ABEND was detected but could not be analyzed fully because no SDWA was available.
X'1'
An asynchronous ABEND was detected (otherwise, the abend was synchronous or could not be classified because there was no SDWA).
System action:

CICS continues normally and attempts to open the table for local use only. A system dump is taken for unexpected errors (X'ff' =X'01') and for ABENDs (if dumps are requested for that ABEND code).

User response:

The response depends on the reason for the failure as indicated in the first byte of the reason code:

X'01'
Use the system dump to help you determine the cause of the problem.
X'02'
There cannot be more than one region with a given APPLID acting as a shared data table server within the same MVS image.
X'03'
This error might indicate that some corruption of the system has occurred, or that there is an error in CICS code.
X'04'
Refer to the documentation of the MVS RESMGR macro to interpret the return code reported in the additional information part of the reason code.
X'05'
Refer to the documentation of the MVS SYSEVENT macro to interpret the ECB contents reported in the additional information part of the reason code.
X'06'
Server initialization should have been completed before LOGON is issued, so CICS SVC errors associated with the loading of the data tables SVC module DFHDTSVC should not be encountered. Therefore this error probably indicates a logic problem or corruption of your system.
X'0D'
Refer to the documentation of the MVS ENQ macro to interpret the return code reported in the additional information part of the reason code.
X'10'
This error might indicate that some corruption of the system has occurred, or that there is an error in CICS code.
X'11'
This error might indicate that service has been applied which requires PTFs to both base CICS and the shared data tables code, and only one has been correctly updated, or that some corruption of the system has occurred, or that there is an error in CICS.
>= X'80'
When the reason code indicates that an ABEND has been detected, use the additional information provided in the reason code to find out what the ABEND was, and refer to information on that ABEND code to determine the cause.
Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, X'code'

DFHFC0421
applid Shared access to data tables cannot be provided by this CICS system because a storage failure has prevented it from registering as a shared data table server - reason code X'code'.
Explanation:

CICS is about to open a data table but cannot do so because a failure to acquire storage has prevented the register of this CICS system as a shared data table server. The value of the reason code, X'code', provides further information about the type of storage which could not be obtained:

The format of the reason code is X'ttnnnnnn' in which tt identifies the type of storage and, for some of the codes, nnnnnn gives the hexadecimal size in bytes of the storage which could not be obtained. For storage blocks whose length is fixed, the reason code does not usually report the size.

The values of X'tt' are:

X'01'
private storage from MVS subpool 253 (below the 16MB line) for a work area for module DFHQSSS or from MVS subpool 230 (key 0) for a work area used by the data tables SVC LOGON processing
X'0A'
ECSA storage from MVS subpool 241 (key 0) for a qualified subsystem block
X'0B'
ECSA storage from MVS subpool 241 (key 0) for a system anchor
X'0C'
ECSA storage from MVS subpool 241 (key 0) for a server element
X'0D'
ECSA storage from MVS subpool 241 (key 0) for a security block
System action:

CICS continues normally and attempts to open the table for local use only.

User response:

The response depends on the type of storage indicated by the reason code.

If it indicates private storage then you should probably reconsider the various region size parameters which have been specified on the CICS job, or have been set as defaults for the system by IEALIMIT or the IEFUSI installation exit. It might be necessary to take an SDUMP of the CICS job and process it using the VERBEXIT VSMDATA in order to investigate the way in which MVS storage has been allocated to the various subpools.

If it indicates ECSA (extended common service area) storage, you should review the CSA size specified in system parameter list IEASYSxx, or by use of the CSA override on initialization of the MVS system. You should also review the size of the ESQA, since the system might have started to use ECSA storage if the ESQA storage is depleted.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, X'code'

DFHFC0422
applid Shared access to data tables cannot be provided by this CICS system because a module loading failure has prevented it from registering as a shared data table server - reason code X'code'.
Explanation:

CICS is about to open a data table but cannot do so because a module loading failure has prevented the register of this CICS system as a shared data table server.

The value of the reason code, X'code', provides further information about which module was being loaded, and what went wrong with the attempt to load it.

The format of the reason code is X'mfrraaaa' in which m identifies the module and f is a code for the type of failure. For some failures, rr contains the register 15 return code from the failing macro call, and aaaa might contain additional information.

The value of X'm' can be:

X'5'
DFHDTXS

The values of X'f' are:

X'1'
module not found by LOAD
X'2'
an error was returned by the MVS LOAD macro. The two bytes X'aaaa' of additional information in the reason code contain the completion code from the LOAD. X'rr' contains the register 15 return code.
X'5'
the module is not reentrant.
X'6'
the module had the wrong AMODE.
System action:

CICS continues normally and attempts to open the table for local use only.

User response:

The response depends on the reason for the failure as indicated in the second hex digit of the reason code:

X'1'
Use the first hex digit to determine which module could not be found, and ensure that it is in the correct library.
X'2'
Refer to the documentation of the MVS LOAD macro to interpret the return and completion codes given in the reason code. There might also be a message from the MVS LOAD which explains the reason for the failure.
X'5', X'6'
Use the first digit of the reason code to determine the name of the module, then check the status of that module. This error implies that it is either not the module which was supplied with CICS or that it has become corrupted in some way.
Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, X'code'

DFHFC0430
applid Data table open request for file filename has failed for reason X'code'.
Explanation:

CICS has attempted to create a data table for file resource filename but has been unable to do so.

System action:

CICS continues normally. This message is followed either by message DFHFC0931 or by DFHFC0932. The following message indicates the action taken for the specified table.

User response:

This indicates an internal error or a corruption of your system. You may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, X'code'

DFHFC0431
applid Data table open request for file filename has failed owing to a storage failure - reason code X'code'.
Explanation:

CICS has attempted to create a data table for file resource filename but has been unable to do so owing to a failure to get storage. There is insufficient storage above the 16MB line and the value of the reason code, X'code', provides further information about the type of storage which could not be obtained.

The format of the reason code is X'ttnnnnnn' in which tt identifies the type of storage and, for some of the codes, nnnnnn gives the hexadecimal size in bytes of the storage which could not be obtained. For storage blocks whose length is fixed, the reason code does not usually report the size.

The values of X'tt' are:

X'03'
private storage from MVS subpool 0 for a data table block
X'04'
private storage from MVS subpool 0 for a file block
X'05'
private storage from MVS subpool 0 for a pool of backout cells (the pool is created if the file being opened is the first recoverable user-maintained table to be opened in this CICS run)
X'06'
private storage from MVS subpool 0 for a pool of table entry descriptor blocks, or for a descriptor block to be used when loading the table
X'07'
private storage from MVS subpool 0 for data table index storage
X'08'
storage for a pool of data table records in the MVS/ESA data space
System action:

CICS continues normally. This message is followed either by message DFHFC0931 or by DFHFC0932. The following message indicates the action taken for the table involved.

User response:

The response depends on the type of storage indicated by the reason code.

If it indicates private storage then you should probably reconsider the various region size parameters which have been specified on the CICS job, or have been set as defaults for the system by IEALIMIT or the IEFUSI installation exit. It might be necessary to take an SDUMP of the CICS job and process it using the VERBEXIT VSMDATA in order to investigate the way in which MVS storage has been allocated to the various subpools.

If it indicates data space storage then check whether the size of data spaces in this MVS system has been limited by use of the IEFUSI installation exit.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, X'code'

DFHFC0435
applid Data table access request for remote file filename has failed for reason X'code'.
Explanation:

An error has occurred while the requesting region was attempting to establish a connection to the remote file filename owned by the serving region. The value of the reason code, X'code', provides further information about why CICS was unable to connect to the remote file.

The format of the reason code is either: X'ffaaaaaa' in which ff is a value less than X'80' that identifies the type of failure, and aaaaaa is additional information provided for some of the failures; or, when an abnormal termination (ABEND) has occurred, X'axxxrrrr' in which a is a value greater than or equal to X'8' that categorizes the type of ABEND, rrrr contains any register 15 ABEND reason code, and xxx contains the system or user completion code as three hexadecimal digits.

When X'code' < X'80000000', the values of X'ff' are:

X'01'
An unexpected failure occurred. This code is reported when the data tables SVC detects an error which should never occur.
X'06'
An error was returned by the CICS SVC. The first byte of the additional information, aa0000, is the register 15 return code from the attempt to call the CICS SVC.
X'07'
The connection index returned by the data tables SVC exceeds the maximum value supported by the calling module (220 - 1).
X'0A'
The scan of the chain of files owned by the serving region has failed because there is a permanently invalid entry on the chain which indicates that the chain has become damaged.
X'0B'
The number of connections by this requesting CICS region to the remote file is already at the allowed maximum (232 - 1).
X'0C'
The vector which records details of all connections to shared data tables by this requesting CICS region needs expanding, but this would cause it to equal or exceed a size of 16MB.
X'0F'
An attempt to serialize with termination of the server has failed because the number of ENQs has reached the address space limit. The first byte of the additional information, X'aa0000', contains the return code from the ENQ.

When X'code' >= X'80000000', the values of X'a' are formed from combinations of:

X'8'
An ABEND was detected.
X'4'
A user ABEND was detected, in which case xxx contains the hexadecimal equivalent of the user completion code (otherwise, xxx contains the hexadecimal system completion code).
X'2'
An ABEND was detected but could not be fully analyzed because no SDWA was available.
X'1'
An asynchronous ABEND was detected (otherwise, the abend was synchronous or could not be classified because there was no SDWA).
System action:

CICS continues normally and function ships this and subsequent remote file requests. Use of shared tables is retried after about 10 minutes. A system dump is taken for unexpected errors (X'ff' =X'01') and for ABENDs (if dumps are requested for that ABEND code).

User response:

The response depends on the reason for the failure as indicated in the first byte of the reason code:

X'01'
Use the system dump to help you determine the cause of the problem.
X'06'
Requester initialization should have been completed before CONNECT is issued, so CICS SVC errors associated with the loading of the data tables SVC module DFHDTSVC should not be encountered. Therefore this error probably indicates a logic problem or corruption of your system.
X'07'
Some changes to your system configuration should be made, as this requesting region is trying to access too many shared data tables owned by other regions. It is necessary either to reduce the number of remote files being used, or to split the requesting CICS region into a number of smaller regions.
X'0A'
This indicates corruption of subpool 0 storage in the server region.
X'0B'
This indicates that either the requesting region contains more than 232 - 1 remote file definitions, all of which refer to the same file in the server region, or that storage has been corrupted.
X'0C'
Same response as X'07'.
X'0F'
Refer to the documentation of the MVS ENQ macro to interpret the return code reported in the additional information part of the reason code.
>= X'80'
When the reason code indicates that an ABEND has been detected, use the additional information provided in the reason code to find out what the ABEND was, and refer to information on that ABEND code to determine the cause.
Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, X'code'

DFHFC0436
applid Data table access request for remote file filename has failed because of a storage failure - reason code X'code'.
Explanation:

CICS has attempted to access the remote file resource filename but cannot do so because of a failure to get storage.

The value of the reason code, X'code', provides further information about the type of storage which could not be obtained:

The format of the reason code is X'ttnnnnnn' in which tt identifies the type of storage and, for some of the codes, nnnnnn gives the hexadecimal size in bytes of the storage which could not be obtained. For storage blocks whose length is fixed, the reason code does not usually report the size.

The values of X'tt' are:

X'01'
Private storage from MVS subpool 230 (key 0) for a work area used by module DFHDTXS or for a work area used by data tables SVC CONNECT processing.
X'0F'
Private storage from MVS subpool 230 (key 0) for a connect vector
System action:

CICS continues normally and function ships this and subsequent remote file requests. Use of shared tables is retried after about 10 minutes.

User response:

The response depends on the type of storage indicated by the reason code.

As it indicates private storage, you should probably reconsider the various region size parameters which have been specified on the CICS job, or have been set as defaults for the system by IEALIMIT or the IEFUSI installation exit. It might be necessary to take an SDUMP of the CICS job and process it using the VERBEXIT VSMDATA in order to investigate the way in which MVS storage has been allocated to the various subpools.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, X'code'

DFHFC0440
applid Data table close request for file filename has failed for reason X'code'.
Explanation:

CICS has attempted to close a data table for file resource filename but has been unable to do so.

System action:

CICS continues normally. The table is treated as having been closed.

A system dump is taken for unexpected errors (X'ff' =X'01') and for abends (if dumps are requested for that abend code).

User response:

The response depends on the reason for the failure as indicated in the first byte of the reason code:

X'01'
Use the system dump to help you determine the cause of the problem.
X'06'
Server initialization should have been completed before LOGON is issued, so CICS SVC errors associated with the loading of the data tables SVC module DFHDTSVC should not be encountered. Therefore this error probably indicates a logic problem or corruption of your system.
X'09'
The function code (service type) and qualifier (options) reported in the reason code can be used to determine which ALESERV request was being attempted. Refer to the MVS ALESERV documentation and macro to interpret the function code, qualifier, and register 15 return code reported in the reason code.
>= X'80'
When the reason code indicates that an ABEND has been detected, use the additional information provided in the reason code to find out what the ABEND was, and refer to information on that abend code to determine the cause.
Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, X'code'

DFHFC0441
applid Data table close request for file filename has failed owing to a storage failure - reason code X'code'.
Explanation:

CICS has attempted to close a data table for file resource filename but has been unable to do so owing to a failure to release storage.

The format of the reason code is X'ttnnnnnn' in which tt identifies the type of storage and, for some of the codes, nnnnnn gives the hexadecimal size in bytes of the storage which could not be obtained. For storage blocks whose length is fixed, the reason code does not usually report the size.

The values of X'tt' are:

X'14'
private storage from MVS subpool 230 (key 0) for a new ALET list section
System action:

CICS continues normally. The table is treated as having been closed.

User response:

You should probably reconsider the various region size parameters which have been specified on the CICS job, or have been set as defaults for the system by IEALIMIT or the IEFUSI installation exit. It may be necessary to take an SDUMP of the CICS job and process it using the VERBEXIT VSMDATA in order to investigate the way in which MVS storage has been allocated to the various subpools.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, X'code'

DFHFC0445
applid Data table disconnect request for remote file filename has failed for reason code.
Explanation:

CICS has attempted to disconnect from the remote data table filename but has been unable to do so.

An error has occurred while the requesting region was attempting to break the connection to the remote file filename owned by the serving region. The value of the reason code, X'code', provides further information about why CICS was unable to disconnect from the remote file.

The format of the reason code is either: X'ffaaaaaa' in which ff is a value less than X'80' that identifies the type of failure, and aaaaaa is additional information provided for some of the failures; or, when an abnormal termination (ABEND) has occurred, X'axxxrrrr' in which a is a value greater than or equal to X'8' that categorizes the type of ABEND, rrrr contains any register 15 ABEND reason code, and xxx contains the system or user completion code as three hexadecimal digits.

When X'code' < X'80000000', the values of X'ff' are:

X'01'
An unexpected failure occurred. This code is reported when the data tables SVC detects an error which should never occur.
X'06'
An error was returned by the CICS SVC. The first byte of the additional information, aa0000, is the register 15 return code from the attempt to call the CICS SVC.

When X'code' >= X'80000000', the values of X'a' are formed from combinations of:

X'8'
An ABEND was detected.
X'4'
A user ABEND was detected, in which case xxx contains the hexadecimal equivalent of the user completion code (otherwise, xxx contains the hexadecimal system completion code).
X'2'
An ABEND was detected but could not be analyzed fully because no SDWA was available.
X'1'
An asynchronous ABEND was detected (otherwise, the abend was synchronous or could not be classified because there was no SDWA).
System action:

CICS continues normally. The table is treated as having been disconnected from the requesting CICS system. A system dump is taken for unexpected errors (X'ff' =X'01') and for ABENDs (if dumps are requested for that ABEND code).

User response:

The response depends on the reason for the failure as indicated in the first byte of the reason code:

X'01'
Use the system dump to help you determine the cause of the problem.
X'06'
Requester initialization should have been completed before DISCONNECT is issued, so CICS SVC errors associated with the loading of the data tables SVC module DFHDTSVC should not be encountered. Therefore this error probably indicates a logic problem or corruption of your system.
>= X'80'
When the reason code indicates that an ABEND has been detected, use the additional information provided in the reason code to find out what the ABEND was, and refer to information on that ABEND code to determine the cause.
Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, code

DFHFC0446
applid Data table disconnect request for remote file filename has failed because of a storage failure - reason code X'code'.
Explanation:

CICS has attempted to disconnect from the remote data table filename but has been unable to do so owing to a failure to release storage.

System action:

CICS continues normally. The table is treated as having been disconnected from the requesting CICS system.

User response:

This indicates an in internal error or a corruption of the system. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, X'code'

DFHFC0490
applid Unable to use data table for file filename.
Explanation:

The data set to which file filename relates has an associated data table but CICS is unable to make use of the table data owing to a lack of storage.

System action:

CICS continues normally. Performance of read-only accesses to the file is degraded because records cannot be retrieved from the table.

User response:

Ensure that there is sufficient storage in the CICS region outside the EDSA.

See the CICS Shared Data Tables Guide for further guidance.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename

DFHFC0500
applid RLS OPEN of file filename failed. VSAM has returned code X'eeee' in R15 and reason X'cccc'.
Explanation:

While CICS was opening file filename, the CICS file control RLS open/close routine received a nonzero return code from VSAM.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use RLS files is sent a NOTOPEN condition.

User response:

For the meaning of the VSAM return code, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename, X'eeee', X'cccc'

DFHFC0501
applid RLS OPEN of file filename failed. VSAM has returned code 16 in R15. RLS access has been disabled.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine received a return code of 16 in register 15. This means that the RLS VSAM server is currently unavailable so file control has disabled RLS access.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use RLS files is sent a NOTOPEN condition.

CICS file control reenables RLS access when the RLS VSAM server restarts.

User response:

None.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename

DFHFC0502
applid RLS OPEN of file filename failed. Access type switch to RLS attempted while other files open for the same data set have non-RLS access type.
Explanation:

While CICS was opening file filename, the CICS file control RLS open/close routine detected that the access type for the file has been changed to RLS but there are still other files open for the data set with non-RLS access type. The file cannot be opened until all the other files have closed.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use the file is sent a NOTOPEN condition.

User response:

Close all the other files or change access of this file back to non-RLS. Files for the same data set should have the same access type.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename

DFHFC0503
applid Non-RLS OPEN of file filename failed. Access type switch to non-RLS attempted while other files open for the same data set have RLS access type.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine detected that the access type for the file has been changed to non-RLS but there are still other files open for the data set with RLS access type. The file cannot be opened until all the other files have closed.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use the file is sent a NOTOPEN condition.

User response:

Close all the other files or change access of this file back to RLS. Files for the same data set should have the same access type.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename

DFHFC0504
applid RLS OPEN of file filename failed. The VSAM SHOWCB macro has detected a RLS VSAM server failure. RLS access has been disabled.
Explanation:

While CICS was opening file filename, the CICS file control RLS open/close routine received a return code of X'1A' in register 15. This means that the RLS VSAM server is not available so file control has disabled RLS access. The return code was returned by the SHOWCB macro when CICS was attempting to find the reason for the open failure that had just been detected.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use RLS files is sent a NOTOPEN condition. CICS reenables RLS access when the RLS VSAM server restarts.

User response:

None.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename

DFHFC0505
applid RLS CLOSE of file filename failed. The VSAM SHOWCB macro has detected a RLS VSAM server failure. RLS access has been disabled.
Explanation:

While CICS was closing file filename, the CICS file control RLS open/close routine received a return code which indicates that the RLS VSAM server is unavailable. Consequently file control has disabled and closed down RLS access. This does not affect the rest of the close processing. The return code is returned by the SHOWCB macro which is invoked during CICS close.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any subsequent close requests for other files which are issued while the server is unavailable also receive the error return code but do not issue this message. CICS reenables RLS access when the RLS VSAM server restarts.

User response:

None.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename

DFHFC0507
applid RLS OPEN of file filename failed. Callable service IGWARLS is not present.
Explanation:

Callable service IGWARLS is required by file control for processing files which have update SERVREQs and are using the VSAM catalog as a repository for data set recovery attributes. CICS expects to find IGWARLS in the LPA. IGWARLS resides in library SYS1.CSSLIB. If SYS1.CSSLIB is not in the LPA concatenation, RLS files with update SERVREQs cannot be opened.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use RLS files is sent a NOTOPEN condition.

User response:

If you intend to use RLS access for files with UPDATE SERVREQs, ensure that SYS1.CSSLIB is included in the LPA concatenation.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename

DFHFC0508
applid RLS OPEN of file filename failed. VSAM has returned code X'AA' in register 15. RLS access has been disabled.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine received a return code of X'AA' in register 15. This means that the RLS VSAM server is currently unavailable so file control has disabled RLS access.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use RLS files is sent a NOTOPEN condition.

CICS file control reenables RLS access when the RLS VSAM server restarts.

User response:

None.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename

DFHFC0509
applid RLS OPEN of file filename failed. This file is an extended entry-sequenced data set (ESDS). The extended file attribute is not supported in this release of CICS.
Explanation:

While CICS was opening file filename, CICS received a nonzero return code from VSAM while attempting to verify that relative byte address (RBA) access is allowed. This failure indicates that filename is an extended ESDS, which is not supported in this release of CICS.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction that attempts to use ESDS RLS file is sent a NOTOPEN condition.

User response:

Redefine filename as a standard ESDS.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename

DFHFC0510
applid {RLS | Non-RLS} OPEN of file filename failed because the data set is unavailable. Module module.
Explanation:

An attempt to open file filename failed because CICS has internally marked the data set as unavailable. This is the result of an earlier EXEC CICS SET DSNAME UNAVAILABLE command, or CEMT equivalent. This prevents the opening of new RLS and non-RLS files against the data set.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transactions attempting to use the data set from this CICS region are sent a NOTOPEN condition.

User response:

Ensure that an EXEC CICS SET DSNAME AVAILABLE command (or the CEMT equivalent) is issued before attempting to open the file.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, module

Start of changeDFHFC0511End of change
Start of changeapplid RLS OPEN of file filename failed. This CICS has other files open for the data set (or its associated base) with non-RLS access mode. The data set name is dsname.End of change
Start of change
Explanation:

While CICS was opening file filename, the CICS file control RLS open/close routine detected that this region has other files open for the data set dsname, or its associated base data set, in non-RLS access mode. The file cannot be opened in RLS access mode until all the other non-RLS mode files have closed, even if these files are accessing the data set in read-only mode. This constraint is to ensure a consistent view of this data set from within each CICS region.

End of change
Start of change
System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use the file is sent a NOTOPEN condition.

End of change
Start of change
User response:

Close all the other files or change access of this file to non-RLS mode. Files accessing the same base data set from within a given CICS region must all have the same access mode. This includes access via a path data set.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCROEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changefilename,End of change Start of changedsnameEnd of change

Start of changeDFHFC0512End of change
Start of changeapplid Non-RLS OPEN of file filename failed. This CICS has other files open for the data set (or its associated base) with RLS access mode. The data set name is dsname.End of change
Start of change
Explanation:

While CICS was opening file filename, the CICS file control non-RLS open/close routine detected that this region has other files open for the data set dsname, or its associated base data set, in RLS access mode. This file cannot be opened in non-RLS access mode until all the other RLS mode files have closed, even if this file is opening the data set in read-only mode. This constraint is to ensure a consistent view of this data set from within each CICS region.

End of change
Start of change
System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use the file is sent a NOTOPEN condition.

End of change
Start of change
User response:

Close all the other files or change access of this file to RLS mode. Files accessing the same base data set from within a given CICS region must all have the same access mode. This includes access via a path data set.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCFSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changefilename,End of change Start of changedsnameEnd of change

Start of changeDFHFC0513End of change
Start of changeapplid Non-RLS OPEN of file filename has failed. CICS has unresolved RLS recovery work for the data set (or its associated base). The data set name is dsname.End of change
Start of change
Explanation:

While CICS was opening file filename, the CICS file control non-RLS open/close routine detected that this region has unresolved recovery work for the data set dsname, or its associated base data set, which requires the base data set and any associated path data sets to be accessed in RLS mode. This file cannot be opened until all the RLS recovery work has been resolved. This constraint ensures that any automatic resolution of the recovery work is not impeded by non-RLS accesses to the data set.

End of change
Start of change
System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use the file is sent a NOTOPEN condition.

End of change
Start of change
User response:

Use the INQUIRE UOWDSNFAIL command to investigate the RLS recovery work, and take action to resolve it. This may involve retrying backout-failed units of work and resynchronising indoubt-failed units of work. See the CICS Recovery and Restart Guide for more information on unit of work failures and their resolution.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCFSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changefilename,End of change Start of changedsnameEnd of change

DFHFC0520
applid {RLS | Non-RLS} OPEN of file filename failed. IGWARLS call returned codes X'rrrr', X'cccc' and problem determination X'dddddddd' to module module.
Explanation:

While CICS was opening file filename and retrieving information from the VSAM catalog using callable service IGWARLS, the CICS file control open/close routine in module module detected an error. The return code and reason code from IGWARLS are respectively rrrr and cccc. dddddddd is any available problem determination information.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

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

User response:

Use the IGWARLS reason code to determine the cause of the problem. For the meaning of the IGWARLS reason code, see OS/390 V2R10.0 DFSMSdfp Advanced Services.

If you cannot resolve the problem or the problem recurs, there may be a more severe error. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, X'rrrr', X'cccc', X'dddddddd', module

DFHFC0521
applid RLS OPEN of file filename failed. Undefined LOG parameter is invalid for an RLS file with update type SERVREQs.
Explanation:

While CICS was opening file filename and retrieving information from the VSAM catalog using callable service IGWARLS, the CICS file control open/close routine detected that the LOG parameter for the sphere is undefined. LOG must be specified for a file that has RLS access type and update type servreqs.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

Use IDCAMS ALTER to set the LOG parameter for the sphere.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename

DFHFC0522
applid {RLS | Non-RLS} OPEN of file filename failed. IGWARLS call has returned that the LOG parameter is set to ALL but LOGSTREAMID has not been specified. Module module.
Explanation:

While CICS was opening file filename and retrieving information from the VSAM catalog using callable service IGWARLS, the CICS file control open/close routine in module module detected that the LOG(ALL) has been specified without LOGSTREAMID.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

If forward recovery is required, use IDCAMS ALTER to add a LOGSTREAMID for the sphere. Otherwise, remove the forward recovery setting.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, module

DFHFC0523
applid RLS OPEN of file filename failed. The LOGSTREAMID for forward recovery is the same as the system log. Module module.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine in module module detected that the LOGSTREAMID for forward recovery is the same as that for the system log. The forward recovery LOGSTREAMID must be different from the system log.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

Use IDCAMS ALTER to change the LOGSTREAMID for forward recovery for the sphere. Ensure that it is different from the system log.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename, module

DFHFC0524
applid An attempt to write a log record failed because the record length was greater than the maximum supported by that log. Module module.
Explanation:

An attempt to write a log record, as part of a file update operation, has failed because the length of the data in the record was greater than the maximum supported by the associated log stream.

System action:

A trace entry is made and a dump is taken with a dumpcode of FC0524.

User response:

Redefine the log stream using a structure which has a MAXBUFSIZE larger than that of the file update record size.

Destination:

Console

Modules:

DFHFCLJ

XMEOUT Parameters: applid, module

DFHFC0525
applid {RLS | Non-RLS} OPEN of file filename failed because the forward recovery log stream could not be opened. Module module
Explanation:

While CICS was opening file filename, the CICS file control open/close routine in module module detected that the forward recovery log stream for the sphere could not be opened. An internal call to the CICS logger has returned an error.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

Start of change
User response:

Check for an IXGxxxx message with the name of the logstream. Refer to the appropriate z/OS MVS System Messages manual and also the z/OS Programming: Assembler Services Reference IAR-XCT. If this does not help, you will need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Destination:

Console

Modules:

DFHFCFS,DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, module

DFHFC0526
applid An error occurred on the request to the CICS log manager to close the forward recovery log stream for file filename. Module module.
Explanation:

While CICS was processing file filename, the CICS file control open/close routine in module module detected that a request to close the forward recovery log stream for the associated sphere returned an error.

System action:

Processing continues.

User response:

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

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, filename, module

DFHFC0527
applid Recovery attributes for file filename have been overridden by new settings found on the catalog.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine detected that the recovery settings for the sphere have changed.

System action:

Processing continues. The new recovery settings are assumed for the sphere.

User response:

Ensure that the change is as required.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename

DFHFC0528
applid RLS OPEN of file filename failed. Recovery attributes on the catalog have changed while there are other files still open for the sphere.
Explanation:

While CICS was opening file filename and retrieving information from the VSAM catalog using callable service IGWARLS, the CICS file control open/close routine detected that the recovery attributes on the catalog have changed. There are currently other files open for the sphere which have assumed the previous recovery attributes. Further opens will fail until all files have closed or the recovery attributes are returned to their previous settings. Recovery attributes on the catalog should not be changed without first quiescing the associated sphere in all CICS systems that use it.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

Quiesce the sphere and start again with the new settings.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename

DFHFC0529
applid Recovery attributes for file filename have been reset as there has been a switch of access type. Module module.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine in module module detected that the access type had been changed from RLS to non-RLS VSAM or vice versa. This has the effect of clearing out existing recovery attributes and starting again.

System action:

Processing continues. The new recovery settings are assumed for the sphere.

User response:

None.

Destination:

Console

Modules:

DFHFCRO, DFHFCFS

XMEOUT Parameters: applid, filename, module

DFHFC0530
applid {RLS | Non-RLS} OPEN of file filename failed. The automatic journal is the same stream as the system log. Module module.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine in module module detected that the automatic journal for the file is the same stream as that for the system log. This is not allowed so an internal call to the CICS logger has returned an error.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

Ensure that the stream given in the FCTE for automatic journaling is different from the system log.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, module

DFHFC0531
date time applid Automatic journal journal journalname journalname, opened for file filename is not of type MVS. Module module.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine in module module detected that the stream specified for the automatic journal, journalname, was not of type MVS. For example, it might be a dummy log, or you might be journalling to an SMF data set. This message informs you of this in case the journal type is not what you intended. journal is the number specified for JOURNAL on the file definition.

System action:

CICS continues processing.

User response:

Ensure that the stream type for the automatic journal is correct.

Destination:

CSFL

Modules:

DFHFCN, DFHFCRO

XMEOUT Parameters: date, time,applid, journal, journalname,filename, module

DFHFC0532
applid {RLS | Non-RLS} OPEN of file filename failed because the automatic journal could not be opened. Module module.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine in module module detected that the automatic journal for the file could not be opened. An internal call to the CICS logger has returned an error.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

This is likely to be an internal CICS error. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, module

DFHFC0533
applid An error occurred on the request to the CICS log manager to close the automatic journal for file filename. Module module.
Explanation:

While CICS was processing file filename, the CICS file control open/close routine in module module detected that a request to close the automatic journal returned an error.

System action:

CICS continues processing.

User response:

This is likely to be an internal CICS error. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, filename, module

DFHFC0534
applid Recovery attributes for file filename previously taken from the VSAM catalog have been overridden by new settings from the FCTE. Module module.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine in module module detected that the recovery settings for the sphere have been changed to undefined. For a non-RLS VSAM file, recovery attributes from the FCTE now take effect.

System action:

Processing continues. The new recovery settings are assumed for the file.

User response:

Ensure that this change to the recovery attributes is correct.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, module

DFHFC0535
applid Recovery attributes for file filename previously taken from the VSAM catalog have been overridden by new settings from the VSAM catalog. Module module.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine in module module detected that the recovery settings for the sphere on the VSAM catalog have changed. The new recovery attributes now take effect because there are no other files open for the data set.

System action:

Processing continues. The new recovery settings are assumed for the file.

User response:

Ensure that this change to the recovery attributes is correct.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, module

DFHFC0536
applid Recovery attributes for file filename previously taken from the FCTE have been overridden by new settings from the VSAM catalog. Module module.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine in module module detected that the recovery settings for the sphere on the VSAM catalog are no longer undefined. The new recovery attributes now take effect because there are no other files open for the data set.

System action:

Processing continues. The new recovery settings are assumed for the file.

User response:

Ensure that this change to the recovery attributes is correct.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, module

DFHFC0537
applid OPEN of file filename failed. The request to write a tie up record for the OPEN failed.
Explanation:

While CICS was opening file filename, a request to write a tie up record for the OPEN failed. CICS has closed the file again and failed the OPEN request.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

This is likely to be an internal CICS error. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename

DFHFC0539
applid {RLS | Non-RLS} OPEN of file filename failed. IGWARLS call has returned that the LOG parameter is not set to ALL but the BWO setting has been defined as TYPECICS. Module module.
Explanation:

While CICS was opening file filename and retrieving information from the VSAM catalog using callable service IGWARLS, the CICS file control open/close routine in module module detected that BWO has been set to TYPECICS but LOG(ALL) has not been specified.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

If BWO(TYPECICS) is required, specify LOG(ALL). Alternatively, the setting BWO(NO) is recommended.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, module

DFHFC0540
applid The BWO setting for file filename has not been explicitly set to NO or TYPECICS and is assumed to be BWO(NO). Module module.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine in module module detected that the BWO setting for the sphere on the VSAM catalog had not been explicitly specified as either BWO(TYPECICS) or BWO(NO). The setting is assumed to be BWO(NO).

System action:

Processing continues. The BWO(NO) setting is assumed for the file.

User response:

If you require to use backup while open, use the ALTER function of access method services to set BWO(TYPECICS) for this data set. If you do not require to backup while open, you do not need to take any action, but you may wish to use the ALTER function of access method services to explicitly set BWO(NO).

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, module

DFHFC0541
applid RLS OPEN of file filename failed. RLS is not supported.
Explanation:

While CICS was opening file filename the CICS file control open/close routine in module module detected that RLS was not supported. Either this CICS system is running with system initialization parameter RLS=NO or the level of VSAM does not support RLS.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use RLS files is sent a NOTOPEN condition. Determine why RLS access is not supported.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename

DFHFC0542
date time applid Forward recovery log ID fwdrecovlog, journalname journalname opened for file filename is not of type MVS. Module module.
Explanation:

While CICS was opening file filename, the CICS file control open/close routine in module module detected that the forward recovery log, journalname, was not of type MVS. For example, it might be a dummy log, or you might be logging to an SMF data set. This message informs you of this in case the log type is not what you intended.

fwdrecovlog is the forward recovery log ID specified in the file definition. If the forward recovery log stream is specified in the VSAM catalog rather than in the file definition, it must be of type MVS, so this message can be issued only when the forward recovery log is specified in the file definition.

System action:

CICS continues processing.

User response:

Correct the definition of the forward recovery log if it was not what you had intended.

Destination:

CSFL

Modules:

DFHFCFS

XMEOUT Parameters: date, time,applid, fwdrecovlog, journalname,filename, module

DFHFC0555
applid One or more data sets are in lost locks status. CICS will perform lost locks recovery.
Explanation:

CICS had one or more data sets open in RLS access mode at the time of a failure of the coupling facility lock structure from which SMSVSAM was not able to recover transparently. As a result, the RLS locks held by CICS for those data sets have been lost.

SMSVSAM has informed CICS that one or more data sets are in a lost locks state with respect to this CICS. CICS must therefore perform lost locks recovery for those data sets.

This can occur on a CICS warm or emergency restart, and on a dynamic RLS restart. On a CICS cold or initial start, if there are any data sets with lost locks status, that status is cleared with respect to this CICS.

System action:

The data sets with lost locks status are marked as being unavailable for general use. Units of work that attempt to access such data sets abend with an AFCU abend code.

CICS performs lost locks recovery for the data sets. For each data set, lost locks recovery involves waiting until all units of work that had made uncommitted updates to the data set have completed. These units of work are allowed to access the data set, in order to perform their recovery. When CICS has completed lost locks recovery for a data set, it reports this fact to SMSVSAM. When all CICS regions that had been accessing the data set have completed their lost locks recovery, then the data set is made available for general use again. Note that a data set becomes available for general use as soon as its lost locks recovery has been completed; it does not have to wait for all data sets to be recovered.

CICS takes the following actions to expedite lost locks recovery:

User response:

Lost locks recovery normally completes automatically without requiring any action from the user. However, if there are shunted units of work which had updated a data set with lost locks status, these prevent lost locks recovery from completing until they are resolved. Use the INQUIRE UOWDSNFAIL command to investigate these shunted units of work. See the CICS Recovery and Restart Guide for guidance on resolving shunted units of work which hold RLS retained locks.

Destination:

Console

Modules:

DFHFCRR

XMEOUT Parameter: applid

DFHFC0556
applid Unexpected notification of completion of lost locks recovery for data set dsname.
Explanation:

CICS has received a notification from SMSVSAM that lost locks recovery has completed for data set dsname, but CICS still has outstanding lost locks recovery work for that data set. This notification has therefore been issued out of sequence.

System action:

CICS continues processing. The data set remains in a lost locks state, and CICS continues with its lost locks recovery. New file control requests against the data set will continue to be rejected with AFCU abends. When all CICS regions have completed their lost locks recovery for the data set, then a valid notification will be received and CICS will remove the data set from the lost locks state.

There will be an instance of this message on each CICS system for each data set when an unexpected notification is received.

User response:

Lost locks recovery processing should complete normally without any user intervention.

However, this message is an indication of a probable logic error in SMSVSAM, so you should take dumps of all the SMSVSAM servers and their associated data spaces in the sysplex. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCRR

XMEOUT Parameters: applid, dsname

DFHFC0560
applid The register of the RLS control ACB has failed because the SMSVSAM server is not available. VSAM macro IDAREGP return code X'rrrr', reason code X'cccc'.
Explanation:

While CICS was initializing file control, the call to VSAM to register the control ACB for RLS processing returned an error. The codes returned mean that the SMSVSAM server address space is not available.

System action:

CICS continues processing but all RLS access is disabled. Any transaction attempting to use RLS files is sent a NOTOPEN condition. CICS reenables RLS access when the SMSVSAM server restarts.

User response:

The SMSVSAM server address space should restart itself. If it does not, restart the SMSVSAM server address space manually. If the SMSVSAM server address space fails to restart, there may be a more severe error. In this case, you need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCCA

XMEOUT Parameters: applid, X'rrrr',X'cccc'

DFHFC0562
applid The RLS control ACB has been successfully registered by CICS.
Explanation:

This message provides a record of the register of the RLS control ACB by CICS.

System action:

CICS processing continues.

User response:

None.

Destination:

Console

Modules:

DFHFCCA.

XMEOUT Parameter: applid

DFHFC0563
applid The RLS control ACB has been successfully unregistered by CICS.
Explanation:

This message provides a record of the unregister of the RLS control ACB by CICS.

System action:

CICS processing continues.

User response:

None.

Destination:

Console

Modules:

DFHFCCA.

XMEOUT Parameter: applid

DFHFC0564
applid The register of the RLS control ACB has failed. VSAM macro IDAREGP return code X'rrrr', reason code X'cccc', error data X'dddd'.
Explanation:

While CICS was initializing access to VSAM RLS, the call to VSAM to register the RLS control ACB returned an error.

System action:

CICS continues processing but all RLS access is disabled. Any transaction attempting to use RLS files is sent a NOTOPEN condition.

User response:

Use the VSAM codes to determine the cause of the problem. For the meaning of the VSAM codes, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

If you cannot resolve the problem or the problem recurs, there may be a more severe error. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCCA

XMEOUT Parameters: applid, X'rrrr',X'cccc', X'dddd'

DFHFC0565
applid The unregister of the RLS control ACB has failed. VSAM macro IDAUNRP return code X'rrrr', reason code X'cccc', error data X'dddd'.
Explanation:

While CICS was quiescing RLS access the call to VSAM to unregister the RLS control ACB returned an error.

System action:

CICS continues processing and all RLS access is disabled. Any transaction attempting to use RLS files is sent a NOTOPEN condition.

User response:

Use the VSAM codes to determine the cause of the problem. For the meaning of the VSAM codes, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

If you cannot resolve the problem or the problem recurs, there may be a more severe error. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCCA

XMEOUT Parameters: applid, X'rrrr',X'cccc', X'dddd'

DFHFC0566
applid The register of the RLS control ACB has failed. VSAM macro IDAREGP return code X'rrrr', reason code X'cccc'.
Explanation:

While CICS was initializing access to VSAM RLS, the call to VSAM to register the RLS control ACB returned an error.

System action:

CICS continues processing but all RLS access is disabled. Any transaction attempting to use RLS files is sent a NOTOPEN condition.

User response:

Use the VSAM codes to determine the cause of the problem. For the meaning of the VSAM codes, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

If you cannot resolve the problem or the problem recurs, there may be a more severe error. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCCA

XMEOUT Parameters: applid, X'rrrr',X'cccc'

DFHFC0567
applid The unregister of the RLS control ACB has failed. VSAM macro IDAUNRP return code X'rrrr', reason code X'cccc'.
Explanation:

While CICS was quiescing RLS access, the call to VSAM to unregister the RLS control ACB returned an error.

System action:

CICS continues processing and all RLS access is disabled. Any transaction attempting to use RLS files is sent a NOTOPEN condition.

User response:

Use the VSAM codes to determine the cause of the problem. For the meaning of the VSAM codes, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

If you cannot resolve the problem or the problem recurs, there may be a more severe error. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCCA

XMEOUT Parameters: applid, X'rrrr',X'cccc'

DFHFC0568I
applid File control dynamic RLS restart has started.
Explanation:

File control dynamic RLS restart has started.

System action:

Processing continues.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHFCRR

XMEOUT Parameter: applid

DFHFC0569I
applid File control dynamic RLS restart has ended.
Explanation:

File control dynamic RLS restart has completed successfully.

System action:

Processing continues.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHFCRR.

XMEOUT Parameter: applid

DFHFC0570
applid File control RLS access has been enabled.
Explanation:

RLS access is now available.

System action:

Processing continues.

User response:

None.

Destination:

Console

Modules:

DFHFCRR.

XMEOUT Parameter: applid

DFHFC0571
applid RLS access cannot be restarted.
Explanation:

An error has occurred while attempting to restart CICS access to VSAM RLS, either at startup, or during a dynamic RLS restart which took place when the VSAM RLS server became available while CICS was running. Because of this error, it may not be possible to access VSAM RLS again during this CICS run.

Access is made available again only if the VSAM RLS server in this MVS system fails causing CICS to perform dynamic RLS restart processing when it restarts, or if you choose to deliberately recycle the RLS server to trigger a dynamic restart.

System action:

CICS continues, but with access to VSAM RLS disabled (unless an offsite restart is being performed). Other CICS functions, including access to non-RLS VSAM files, should continue.

At the time the error affecting RLS restart is detected, CICS issues one or more messages and takes a system dump.

This error might also affect other aspects of this CICS system, for example if it is due to the corruption of internal CICS control structures.

If an offsite restart is being performed; that is, if OFFSITE=YES was specified as a system initialization override, then CICS does not continue, but is terminated with a system dump. When RLS offsite recovery is required, then there is no value in continuing without RLS, because it will be needed in order for the offsite restart to be able to complete. Until all CICS systems complete their offsite recovery work, including this one, no other CICS system in the CICSplex will be allowed to perform new RLS work either.

User response:

If you do not need access to any VSAM RLS files from this CICS system, you can allow CICS to continue. For example, this CICS system might never open files in RLS access mode, or you might prefer to continue without RLS access in order to continue this CICS run.

If you do need to access VSAM RLS files from this CICS, consider shutting CICS down and restarting it, or recycling the VSAM RLS server. However, be aware that recycling the server causes all CICS systems in this MVS to go through dynamic RLS restart processing, which implicitly closes all files that were open in RLS access mode.

To determine the cause of the original error, examine the messages and the system dump that were issued when the error was detected.

If you are performing an offsite restart, then restart CICS with OFFSITE=YES still specified as a system initialization override.

Destination:

Console

Modules:

DFHFCRR.

XMEOUT Parameter: applid

DFHFC0574
applid RLS offsite recovery will be performed. Normal RLS access is not allowed.
Explanation:

OFFSITE=YES has been specified as a SIT override, and RLS is supported by this CICS (RLS=YES has been specified and the level of DFSMS/MVS supports RLS). This message is issued during file control initialization to indicate that RLS offsite recovery processing is to be carried out during this CICS run.

System action:

RLS access is not allowed until after this CICS has performed its RLS recovery work. Only tasks performing the recovery work are allowed RLS access. Message DFHFC0575 is issued when RLS recovery has been completed by this CICS. RLS access for normal work is not allowed until this CICS has issued message DFHFC0575 and received the reply GO. The description of message DFHFC0575 explains when it is safe to reply to the message.

User response:

Wait for message DFHFC0575 to be issued. If this does not happen shortly after CICS restart has completed, there are probably some backout failed or indoubt failed units of work which had updated RLS data sets, and which are now delaying the completion of RLS recovery. In this case you should use the INQUIRE UOWDSNFAIL command to determine the causes of such failures, and to resolve them.

If some of the failures cannot be resolved cleanly, you may decide to force indoubt units of work and to reset locks for backout failed units of work. See the CICS Recovery and Restart Guide for guidance on resolving RLS retained locks.

If CICS terminates for any reason before message DFHFC0575 is issued, specify OFFSITE=YES on the restart.

OFFSITE=YES must be specified on all restarts until the offsite recovery has completed and you have responded to message DFHFC0575.

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameter: applid

DFHFC0575D
applid Reply 'GO' only after all CICS regions have completed offsite recovery and issued this message.
Explanation:

This message is issued when a CICS system is participating in an offsite recovery of a CICSplex.

The message is issued when this CICS system has completed all of its RLS recovery work. CICS has backed out or committed all units of work which had made updates to data sets open in RLS mode, and which were either inflight or shunted at the time of the disaster at the primary site (or, more exactly, which were in that state at the common point in time to which the CICS system logs have been pruned).

System action:

CICS processing continues, but the system task which issued this message waits for your reply. RLS access is not allowed for user applications until the reply is received, after which CICS allows new RLS work to run. The User Response explains when it is safe for you to reply.

User response:

The message indicates that RLS recovery work has been completed by a particular CICS region. Replying to it indicates that all RLS recovery for the offsite CICSplex has been completed. Do not reply until all CICS regions in the CICSplex have issued this message. When this has happened, you should reply GO. When you next restart this CICS region after having replied GO, you should revert to the default value of NO for the system initialization parameter OFFSITE.

GO is the only reply allowed. If you supply any other response, the message is reissued with a new reply number.

If you suspect that there will be a problem getting some of the CICS regions in the CICSplex to complete their RLS recovery work, and would therefore prefer to shut this CICS down in the meantime, you can use the master terminal to do so. You must specify OFFSITE=YES when you restart the CICS region because offsite recovery for the CICSplex has not been completed. Remember that OFFSITE=YES must be specified on all restarts until the offsite recovery has completed and you have responded to message DFHFC0575.

Destination:

Console

Modules:

DFHFCOR

XMEOUT Parameter: applid

DFHFC0577
applid RLS offsite recovery is now complete. RLS access is allowed.
Explanation:

This message is issued when a CICS system is participating in an offsite recovery of a CICSplex.

The message is issued when the reply GO has been supplied to message DFHFC0575.

System action:

CICS allows user applications to access RLS because it is assumed that a reply of GO means that all CICS systems in the CICSplex have completed their RLS recovery work, and it is therefore safe to allow sharing of RLS data sets.

User response:

Once you have received this message, you can recode your SIT overrides so that OFFSITE=NO is specified when this CICS is next restarted.

Destination:

Console

Modules:

DFHFCOR

XMEOUT Parameter: applid

DFHFC0920
applid Open of empty file filename failed. VSAM codes - eeee,rrrr,cccc
Explanation:

CICS file control issued an OPEN command for VSAM file filename but the command failed with VSAM return code cccc. The CICS internal error code eeee has a value of 8509 and rrrr is the return code in register 15.

This failure is probably caused by the file not being loaded before use by CICS.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

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

VSAM issues a console error message.

User response:

Check whether the file has been loaded before being accessed by CICS. This condition is probably the result of a user error in passing an empty file to CICS.

For the meaning of the VSAM return code, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, eeee, rrrr, cccc

DFHFC0931
applid OPEN of data table name failed for reason n.
Explanation:

CICS was unable to OPEN the user-maintained data table name for reason n, where n may have one of the following values:

1
The data table support initialization module DFHDTINS could not be loaded.
2
Initialization of data table support has failed. This message is preceded by one of messages DFHFC0410, DFHFC0411 or DFHFC0412 which identifies the reason for the failure.
3
The source data set for the data table is not a KSDS base data set.
4
The data table OPEN module DFHDTST has reported an error. This message is preceded by one of messages DFHFC0430 or DFHFC0431 which identifies the error.
6
The file definition for the data table allows neither read nor browse access.
System action:

The data table remains closed and is DISABLED. CICS processing continues.

User response:

The appropriate user response depends on the reason code n as follows:

1
Check that module DFHDTINS is present in the library.
2
See the user action for the preceding message (which will be one of DFHFC0410, DFHFC0411 or DFHFC0412).
3
Check whether the data table has been associated with the intended source data set.
4
See the user action for the preceding message (which will be one of DFHFC0430 or DFHFC0431).
6
Change the SERVREQs in the file definition. There is no benefit in using data tables support for a file which cannot be read or browsed.
Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, name,n

DFHFC0932
applid OPEN of data table name was incomplete for reason n.
Explanation:

CICS was unable to treat name as a CICS-maintained data table for reason n.

System action:

The data table’s source data set is opened for access as a normal VSAM data set, and no main storage table is built. CICS processing continues.

User response:

The appropriate user response depends on the reason code n. Refer to message DFHFC0931 for a list of reason codes and their appropriate user responses.

Urgent action is probably not necessary when this message occurs, as no function has been lost. However, READ performance may be adversely affected.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, name,n

DFHFC0933
applid MVS FREEMAIN failure detected during CLOSE of data table name.
Explanation:

An MVS FREEMAIN, issued while CICS was attempting to release the storage associated with data table name, returned the error response R15=4. Some storage in the CICS address space has not been freed. The error is probably the result of some earlier overwriting of data table control areas.

System action:

CICS closes data table name. CICS processing continues.

User response:

This condition does not adversely affect the data tables function. However, if the problem recurs take a system dump (SDUMP) as soon as possible after the appearance of this message. For example, by means of a CEMT PERFORM SNAP command.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, name

DFHFC0935
applid SHAREOPTIONS of the source for data table name allow inconsistencies between table and source.
Explanation:

The cross region SHAREOPTION for the source data set associated with the data table name is 3 or 4, or the SHAREOPTION is 2 and the table is being opened only for read access. It is possible for another job in this MVS system to update the source without notifying CICS. The result of this is that the data table may no longer match the source data set.

System action:

Opening and loading of the data table continues normally. CICS processing continues.

User response:

Check that the SHAREOPTION is specified correctly and that the DISP parameter is correct.

Note that source data set changes are reflected in the data table only when the changes are made by the CICS system which owns the table.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, name

DFHFC0936
applid Initiation of loading of data table name has failed.
Explanation:

An attempt to initiate the table loading transaction for the data table name has failed.

System action:

CICS processing continues. The effect this has is that the table always appears to be in the process of being loaded and the load completion exit, XDTLC, is not invoked.

One consequence of this is that the table is effectively demand loaded. This means that an entry is only made in the table when a transaction refers to it explicitly. A further consequence is that, for user maintained tables, API requests (other than READ) always result in a LOADING condition.

User response:

Take remedial action after determining the cause of the failure from the trace of the OPEN request and from any related messages and dumps. It may be that the system action of leaving the table open, but not loaded, adversely affects your application. For example, if the application depends on being able to update a user maintained table as soon as loading is complete. If so, closing and reopening the data table may be successful as an immediate response, if the problem was simply a temporary lack of resources.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, name

DFHFC0937
applid OPEN of name1 as a data table was not possible. The file has been opened and will use data table name2 which has the same source.
Explanation:

File name1 could not be opened as a CICS-maintained data table (CMT) because another CMT name2 is already open for the source data set specified in the file definition of name1. However, name1 is still able to benefit from shared data tables support by accessing the already open CMT.

System action:

name1 is opened as a normal CICS file, and therefore automatically uses the existing data table name2 whenever possible.

User response:

This is not normally a problem, but you should ensure that the data table name2 has the required characteristics in terms of its maximum number of records and in the behavior of any data table user exits that refer to it.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, name1,name2

DFHFC0940 I
date time applid CICS data table load has started for data table name.
Explanation:

CICS file control has detected that an open request has been issued for data table name, and a task has been attached to load the data table.

System action:

CICS processing continues.

User response:

None.

Destination:

CSFL

Modules:

DFHDTLX

XMEOUT Parameters: date, time,applid, name

DFHFC0941 I
date time applid CICS data table load has completed successfully for data table name.
Explanation:

The task that was attached to load the data table name has successfully completed loading.

System action:

The user exit XDTLC is invoked, if enabled, with the parameter UEPDTORC set to indicate a successful load. CICS processing continues.

User response:

None.

Destination:

CSFL

Modules:

DFHDTLX

XMEOUT Parameters: date, time,applid, name

DFHFC0942 E
date time applid CICS data table load has terminated abnormally for data table name, reason code = X'xx'.
Explanation:

The CICS task that is loading data table name has received a reason code X'xx', where X'xx' has one of the following values:

X'FB'
CICS file control has requested that the data table load be abandoned. This may occur, for example, if a close request has been made against the data table
X'FD'
an attempt has been made to add more entries to the data table than the maximum specified in the table definition
X'FE'
a shortage of virtual storage has been reported by the add entry (from DASD) service, due to a failure to get storage for the record.
System action:

The user exit XDTLC is invoked, if enabled, unless file control has requested that the load be abandoned (reason code X'FB'). The value of the UEPDTORC parameter passed to the exit indicates that loading completed abnormally. No more records are loaded into the data table. The user exit may ask for the file to be closed.

If the table is CICS-maintained, provided that the user exit has NOT requested that the file be closed, those records which were not added are retrieved from the source data set to satisfy API requests.

If the table is user-maintained, requests to access any record which was not added results in a "not found" response code. If the table has been closed, then API requests result in an "unenabled" response code.

CICS processing continues.

User response:

The appropriate user response depends on the reason code. User responses are as follows:

X'FB'
no action necessary
X'FD'
increase the size specified for the data table, either using the SIZE parameter in the FCT entry or the MAXNUMRECS field in the CEDA definition
X'FE'
increase the available storage above the 16MB line.
Destination:

Console and Transient Data Queue CSFL

Modules:

DFHDTLX

XMEOUT Parameters: date, time,applid, name, X'xx'

DFHFC0943 E
date time applid CICS data table load has terminated abnormally for data table name, reason code = X'xx'.
Explanation:

The CICS task that is loading data table name has received an unexpected return code from CICS file control while browsing the source data set. The reason code X'xx' should be one of the following.

X'02'
ILLOGIC--A VSAM error which does not fall into one of the other categories.
X'0C'
NOTOPEN--The file is CLOSED and UNENABLED, or still open and in use, but a CLOSE request has been received.
X'0D'
DISABLED--The file is disabled.
X'80'
IOERR--I/O error.
System action:

The user exit XDTLC is invoked, if enabled, with the parameter UEPDTORC set to indicate that loading completed abnormally. No more records are loaded into the data table. The user exit may ask for the file to be closed.

If the table is CICS-maintained, provided that the user exit has NOT requested that the file be closed, those records which were not added are retrieved from the source data set to satisfy API requests.

If the table is user maintained, requests to access any record which was not added results in a "not found" response code. If the table has been closed, API requests result in an "unenabled" response code.

CICS processing continues.

User response:

Investigate the reason for the return code from CICS file control. For further information about the reason code, see the description of exception conditions for the STARTBR and READNEXT commands, in the CICS Application Programming Reference.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHDTLX

XMEOUT Parameters: date, time,applid, name, X'xx'

DFHFC0945 E
date time applid CICS data table load has terminated abnormally for data table name.
Explanation:

The special CICS transaction that was loading data table name has detected an abnormal termination.

System action:

Depending on the cause of this abnormal termination, CICS may produce either a system dump or a transaction dump.

The user exit XDTLC is invoked, if enabled, with the parameter UEPDTORC set to indicate that loading completed abnormally. CICS then terminates the loading transaction with abend code AFCM. No more records are loaded into the data table. The user exit may ask for the file to be closed.

If the table is CICS-maintained, provided that the user exit has NOT requested that the file be closed, those records which were not added, are retrieved from the source data set to satisfy API requests.

If the table is user-maintained, requests to access any record which was not added result in a "not found" response code. If the table has been closed, then API requests result in an "unenabled" response code.

CICS processing continues.

User response:

Look at the system log for related CICS messages to determine the original abend detected by the loading transaction. Refer to the description of abend code AFCM for further information about the cause of the original termination.

For more information on how to determine system problems, refer to the CICS Problem Determination Guide.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHDTLX

XMEOUT Parameters: date, time,applid, name

DFHFC0946 E
date time applid CICS data table load has terminated abnormally for data table name, a call to FCFR has failed for reason code = n.
Explanation:

The CICS task that is loading data table name has failed while calling file control to browse the source data set. The value of the reason code n indicates the type of failure as follows:

  1. Response from FCFR was INVALID.
  2. Response from FCFR was DISASTER.
  3. Response from FCFR was PURGED.
  4. FCFR failed for some unexpected reason.
System action:

The user exit XDTLC is invoked, if enabled, with parameter UEPDTORC set to indicate that loading has completed abnormally. CICS then terminates the loading transaction with abend code AFCM. No more records are loaded into the data table. The user exit may ask for the file to be closed.

If the table is CICS-maintained, provided that the user exit has NOT requested that the file be closed, records which were not added are retrieved from the source data set to satisfy API requests. If the table is user-maintained, requests to access any record which was not added result in a "not found" response code. If the table has been closed, API requests result in an "unenabled" response code.

CICS processing continues.

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

User response:

Determine the cause of the failure of the domain call using the diagnostic information provided by file control.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHDTLX

XMEOUT Parameters: date, time,applid, name, n

DFHFC0947 E
date time applid CICS data table load has failed to close data table name, a call to FCFS has failed for reason code = n.
Explanation:

The CICS task that is loading data table name has failed while trying to close the file at the request of an exit program invoked at exit point XDTLC. The value of reason code n indicates the type of failure as follows:

  1. Response from FCFS was INVALID.
  2. Response from FCFS was DISASTER.
  3. Response from FCFS was PURGED.
  4. FCFS failed for some unexpected reason.
System action:

CICS terminates the loading transaction with abend code AFCM.

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

User response:

It is unlikely that the user exit invoked at the XDTLC exit point would request that the file should be closed unless a previous problem had occurred with the load. Determine the cause of any such previous problem by checking for earlier messages which may have been issued referring to data table name. Diagnostic information provided by file control may be used to investigate the failure of the close file call.

CICS processing continues.

Report the details of the symptom string given in message DFHME0116.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHDTLX

XMEOUT Parameters: date, time,applid, name, n

Start of changeDFHFC0949End of change
Start of changedate time applid CICS shared data table table load has terminated abnormally. A call to DFHXMIQ to retrieve the parameters for the load transaction has failed with response code = n.End of change
Start of change
Explanation:

The CICS task to load a shared data table has failed while trying to inquire on the parameters passed to it during attach. The value of the reason code n indicates the type of failure as follows:

  1. Response from XMIQ was INVALID.
  2. Response from XMIQ was DISASTER.
  3. Response from XMIQ was PURGED.
  4. XMIQ failed for some unexpected reason.
End of change
Start of change
System action:

The user exit XDTLC is not invoked as failure to retrieve the attach parameters means the filename is not known. CICS terminates the loading transaction with abend code AFCL. No records are loaded into the data table.

Requests to access any record which was not added result in a "not found" response code.

CICS processing continues.

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

End of change
Start of change
User response:

Determine the cause of the failure of the domain call using the diagnostic information provided by the CIS Transaction Manager.

The file should be closed so that a load may be attempted again when it is next opened.

End of change
Start of change
Destination:

Console and Transient Data Queue CSFL

End of change
Modules:

Start of changeDFHDTLXEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changenEnd of change

DFHFC0950
applid Warning. File filename Opened with VSAM SHROPT 3 or 4. CICS cannot prevent concurrent updates
Explanation:

VSAM share options 3 and 4 permit updating of a data set from multiple regions. Under these circumstances, CICS cannot prevent concurrent updates.

The file is being opened for update against a data set defined with share options 3 or 4, and the file has been defined with the following auto-journaling options:

Either: JREQ=WU or WN if the file is defined using the FCT macro,

Or: JNLADD = BEFORE, AFTER, OR ALL if the file is defined using RDO.

System action:

The file is opened and a warning message is issued.

User response:

None.

Destination:

Console

Modules:

DFHFCN

XMEOUT Parameters: applid, filename

DFHFC0951
applid {RLS | Non-RLS} OPEN of file filename failed. DSNAME not available from JCL or FCT. Module module.
Explanation:

A CICS attempt to open file filename failed because neither the JCL nor the FCT specified the data set name.

CICS file control did not open file filename, because:

  1. At initialization time, the startup JCL did not include a DD statement, and
  2. No user-submitted routine allocated the file dynamically, and
  3. The FCT does not contain a DSNAME parameter to enable CICS to allocate the file dynamically.
System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

Before resubmitting the transaction, you must supply the data set name in the JCL or the FCT. You can set the name in the FCT while CICS is running by using the CEMT transaction or the EXEC CICS SET command or by using CEDA to correct and reinstall the FCT entry.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, module

DFHFC0952
applid Dynamic allocation of {RLS |Non-RLS} file filename failed. Return code X'rrrr',X'cccc' in module module.
Explanation:

While dynamically allocating file filename, CICS file control issued an MVS DYNALLOC macro. The DYNALLOC failed with return code cccc. rrrr is the additional return code in register 15.

System action:

CICS continues with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

for the meaning of the DYNALLOC return codes, see the OS/390 MVS Programming: Authorized Assembler Services Guide.

Destination:

Console

Modules:

DFHFCFS DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, X'rrrr', X'cccc', module

DFHFC0953
applid Non-RLS OPEN or CLOSE of file filename failed. CICS logic error eeee,cccc
Explanation:

While processing a request to open or close file filename, CICS detected an internal logic error in the file control services program. The value of eeee identifies the error as follows:

8105
The DFHFCFS set base dsname block failed. cccc is the return code from DFHFCFS.
8302
Request to DFHFCN for a pool that is not in the FCT.
8701
Request to DFHFCN is not OPEN or CLOSE.
8704
Request to DFHFCL is not BUILD or DELETE.
8705
Request to DFHFCL is for invalid pool number cccc.
8706
Request to DFHFCL is for pool number cccc that is not in the FCT.
8707
DFHFCL failed to build BLDVRP parameters. cccc is the pool number.
8798
Logic error at OPEN detected in DFHFCN at offset cccc.
System action:

CICS terminates the task abnormally, produces a dump and continues processing with the status of file filename unchanged.

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

User response:

This is probably a logic error in CICS. You should note, however, that terminating CICS with an immediate shutdown while opening or closing files may cause such logic errors to happen as a normal occurrence. This is because CICS terminated immediately without regard to running tasks.

It is also possible for this error to occur if CICS has to calculate parameters for the BLDVRP macro, (this happens if you do not supply an LSR pool definition either by CEDA DEFINE LSRPOOL or by DFHFCT TYPE=SHRCTL), and all attempts to access the VSAM catalog for files in this LSR pool fail. Other messages are issued for the individual catalog failures.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, eeee, cccc

DFHFC0954
applid {RLS | Non-RLS} OPEN of file filename failed. No disposition specified for dynamic allocation. Module module.
Explanation:

CICS file control cannot open file filename, because it is not allocated. It is not allocated because:

  1. At initialization time, the startup JCL did not include a DD statement, and
  2. The FCT does not contain a DISP parameter to enable CICS to allocate the file dynamically.
System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file are sent a NOTOPEN condition.

User response:

If you want to use file filename in this run, supply the DISP parameter with the CEMT transaction or with a user transaction using the EXEC CICS SET command. When you have done this, transactions are able to access the file successfully.

The change described above is only effective for the lifetime of the CICS system. A permanent disposition definition of a file can be made either through a JCL DD statement, through a DEFINE file command, or through the DISP=operand of a macro FCT definition.

Destination:

Console

Modules:

DFHFCFS DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, module

DFHFC0955
applid Associated data set is dataset. Module module.
Explanation:

This message follows DFHFC0952 or DFHFC0510. It identifies the VSAM data set referred to in that message.

System action:

Processing continues in the way specified in DFHFC0952 or DFHFC0510.

User response:

Follow the user response for DFHFC0952 or DFHFC0510 as appropriate.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, dataset,module

DFHFC0956
applid {RLS | Non-RLS} OPEN of file filename failed. VSAM catalog error. Return code - X'eeee',X'cccc' in module module.
Explanation:

While reading the VSAM catalog to open the VSAM data set filename, CICS file control received the return code cccc from a SHOWCAT macro. The value of eeee is an error code from DFHFCN as follows:

8112
SHOWCAT for the AIX of a path failed.
8113
SHOWCAT for the data component of a base failed.
8116
SHOWCAT for the base of a path failed.
8117
SHOWCAT for an upgrade member failed.
System action:

CICS writes a system dump, and continues processing, with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

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

User response:

For the meaning of the SHOWCAT return code, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, X'eeee', X'cccc', module

DFHFC0958
applid Non-RLS OPEN of file filename failed. VSAM resource usage conflict with open file.
Explanation:

CICS did not open file filename because it found that its access method control block (ACB) specified a different buffer/string resource (NSR or LSR pool) from that specified by another ACB that is already open for the same base cluster.

VSAM provides integrity for different ACBs open for the same base cluster only if they use the same buffer/string resource.

System action:

CICS writes a system dump and continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

Determine the correct buffer/string resource and change the FCT.

Alternatively, if you specify DSNSHR=UPDATE in the FCT and open the file for read only, CICS permits the use of different buffer/string resources because no integrity exposure exists.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename

DFHFC0960
applid Non-RLS OPEN of file filename failed. Unable to build its LSR pool n. Return code - cccc.
Explanation:

CICS has requested VSAM to build the local shared resource (LSR) pool specified in the FCT entry for file filename. However, VSAM was unable to complete the request. n is the pool number, and cccc is the VSAM BLDVRP return code.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

Note:
The first time this error occurs, CICS writes a system dump before continuing.

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

User response:

For the meaning of the BLDVRP return code, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, n, cccc

DFHFC0961
date time applid Calculation of LSR pool n parameters incomplete. Filename filename has no DSNAME.
Explanation:

While dynamically calculating the parameters for the local shared resource pool (LSR) n, CICS found an FCT entry for which no DSNAME exists (either the FCT entry has no DSNAME, or no DD statement exists).

System action:

CICS processing continues.

Without a DSNAME, CICS cannot use the VSAM catalog to determine the file attributes. Therefore, in the LSR calculation, CICS uses the number of strings specified in the STRNO parameter of the FCT entry but does not use the BUFFERS or KEYLEN information.

User response:

Ensure that each FCT entry has either a DSNAME, or a DD statement corresponding to its DATASET name.

Start of changeExceptionally, if you use CPSM, please note that this message is normal for file EYUDREPN in a CMAS. Do not attempt to allocate a DSNAME or a DD statement for EYUDREPN in the JCL for the CMAS.End of change

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHFCFS

XMEOUT Parameters: date, time,applid, n, filename

DFHFC0962
date time applid Calculation of LSR pool n parameters incomplete for file filename. VSAM catalog access error. Return code - cccc
Explanation:

While CICS was dynamically calculating the parameters for the local shared resource (LSR) pool n, a VSAM SHOWCAT or a VSAM LOCATE failed with return code cccc. Parameters for file filename are incomplete.

System action:

CICS retains the accumulated LSR parameters for file filename and continues processing. No further attempts at calculating LSR parameters for file filename are made.

An exception trace is taken which identifies the failing VSAM request and its return code.

User response:

For the meaning of the SHOWCAT return code, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets. For the meaning of the LOCATE return code, see OS/390 V2R10.0 DFSMSdfp Advanced Services. This error indicates a corrupted VSAM catalog. If you cannot restore the catalog, you will need further assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHFCL

XMEOUT Parameters: date, time,applid, n, filename, cccc

DFHFC0963
applid LSR pool n not deleted. Code - cccc
Explanation:

CICS requested VSAM to delete a local shared resource (LSR) pool n. During processing of the request, a VSAM DLVRP macro failed with return code cccc. (cccc is the VSAM DLVRP return code.)

System action:

CICS takes a system dump and continues processing with the pool still in existence.

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

User response:

For the meaning of the DLVRP return code, see the OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, n,cccc

DFHFC0964
applid Non-RLS OPEN of file filename failed. VSAM codes - eeee,rrrr,cccc.
Start of change
Explanation:

CICS file control issued an open for a VSAM file, filename. The open has failed with VSAM error code, cccc. eeee has a value of 8502 and represents the CICS internal error code and rrrr is the return code in register 15.

End of change
System action:

CICS continues processing, with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

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

Start of change
User response:

VSAM will have issued a console error message. Use the VSAM message and the VSAM error code in the CICS message to solve the problem.

For the meaning of the VSAM error code, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

End of change
Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, eeee, rrrr, cccc

DFHFC0965
applid Open of BDAM file filename failed.
Explanation:

CICS file control issued an open for a BDAM file, filename. The open failed.

System action:

CICS continues processing, with file filename closed and with its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

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

User response:

BDAM will have issued a console error message. Refer to the BDAM message for further guidance to solve the problem.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename

DFHFC0966
applid Non-RLS OPEN of file filename failed. Unable to position ESDS. Error codes: eeee,rrrr,cccc.
Explanation:

Before opening the VSAM ESDS file filename for output, CICS file control could not determine the end-of-data relative byte address (RBA) correctly. During the positioning process, CICS may perform any of the following steps, each of which can fail:

The value of eeee in the message indicates the error or the failing function as follows:

8503
Open base cluster. rrrr is the VSAM return code in register 15. cccc is the error field in the VSAM ACB.
8504
Read last control interval (CI). rrrr is the VSAM return code in register 15. cccc is the FDBK field in the VSAM RPL.
8505
Last CI middle of spanned record.
8506
Close base cluster. rrrr is the VSAM return code in register 15. cccc is the error field in the VSAM ACB.
8507
Insufficient storage to get CI
8508
Dynamic allocation of base. rrrr is the MVS return code in register 15. cccc is the MVS DYNALLOC return code.
System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

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

User response:

For the meaning of the VSAM return codes, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets. For the meaning of the DYNALLOC return codes, refer to the OS/390 MVS Programming: Authorized Assembler Services Guide. CICS file control uses control interval processing when opening a VSAM ESDS. Therefore, ensure that you have specified ACCESS(CONTROL) for the data set.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, eeee, rrrr, cccc

DFHFC0967
applid Error detected while closing {RLS | Non-RLS} file filename - VSAM codes X'rrrr',X'cccc' in module module.
Explanation:

CICS file control issued a close for VSAM file filename. The close failed with VSAM return code cccc. rrrr is the return code in register 15.

System action:

CICS processing continues. CICS marks file filename as closed because VSAM will have closed the access method control block (ACB).

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

User response:

Use the VSAM return code, cccc and the preceding VSAM console message to determine the cause of the problem.

For the meaning of the VSAM return code, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, X'rrrr', X'cccc', module

DFHFC0968
applid Close of BDAM file filename failed
Explanation:

CICS file control issued a close for a BDAM file, filename. The close failed.

System action:

CICS continues, with file filename still open.

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

User response:

BDAM will have issued a console error message. Use the BDAM message to solve the problem.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename

DFHFC0969
applid Non-RLS CLOSE of file filename failed. CICS logic error - 8799 rrrr,cccc.
Explanation:

While attempting to close file filename, CICS detected internal logic error 8799 in the file control services program. cccc is the offset in DFHFCN at which the error occurred.

System action:

CICS terminates the task abnormally, takes a system dump, and continues processing with the status of file filename unchanged.

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

User response:

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

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, rrrr, cccc

DFHFC0970
applid Recoverable non-RLS file filename opened with VSAM SHROPT 3 or 4. CICS cannot ensure integrity.
Explanation:

While opening the recoverable VSAM file filename for update, CICS detected that it was defined with SHAREOPTION 3 or 4, which allows updating from multiple regions. CICS issues this message to warn you that it cannot ensure data integrity.

System action:

CICS opens file filename and continues processing.

User response:

If this integrity exposure is acceptable, no further user action is required.

If this integrity exposure is unplanned and unacceptable, cancel CICS, redefine file filename with a different SHAREOPTION, and restart.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename

DFHFC0971
applid Non-RLS OPEN of file filename returned warning when positioning ESDS. Error codes: rrrr,cccc.
Explanation:

Before opening the VSAM ESDS file filename for output, CICS file control had to determine the end-of-data relative byte address (RBA). The positioning process involved the dynamic allocation and deallocation of the base cluster to DDname DFHESDS. The deallocation failed.

The MVS DYNALLOC return code is cccc. rrrr is the additional return code in register 15.

System action:

CICS opens the file filename and continues processing.

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

User response:

For the meaning of the DYNALLOC return codes, see the OS/390 MVS Programming: Authorized Assembler Services Guide.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, rrrr, cccc

DFHFC0972
applid {RLS | Non-RLS} OPEN of file filename failed. VSAM catalog entry not found, return code - 8111 X'cccc' in module module.
Explanation:

While opening a VSAM file filename, CICS file control attempted to retrieve information from the VSAM catalog using the file name given in the JCL or the FCT. This initial retrieval failed with VSAM return code cccc from the SHOWCAT macro. 8111 indicates where within CICS file control the error was detected.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

You have probably specified DSNAME incorrectly in the FCT. If DSNAME is correctly specified, see the explanation of the SHOWCAT return code in OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, X'cccc', module

DFHFC0973
applid Dynamic deallocation of {RLS |Non-RLS} file filename failed. Return code - X'rrrr',X'cccc' in module module.
Explanation:

While closing file filename, CICS file control issued the MVS macro, DYNALLOC, to dynamically deallocate the file. Deallocation failed with the MVS return code, cccc. rrrr is the return code in register 15.

System action:

CICS continues with the file closed, but still allocated.

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

User response:

If you change the DSNAME in the FCT, and then reopen the file in the same CICS run, CICS may open the original data set. For an explanation of the MVS return code, refer to the OS/390 MVS Programming: Authorized Assembler Services Guide.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, X'rrrr', X'cccc', module

DFHFC0974
date time applid Calculation of LSR pool n parameters incomplete for file filename. VSAM catalog inconsistency - oooo
Explanation:

While dynamically calculating local shared resource (LSR) parameters for file filename, CICS found that a VSAM SHOWCAT macro gave a normal return code, but the object retrieved was logically incorrect. n is the pool number, and oooo is the VSAM object type in error.

System action:

CICS retains the accumulated LSR parameters for file filename, and continues processing. No further attempts at calculating LSR parameters for file filename are made.

User response:

This error indicates a corrupted VSAM catalog. If you cannot restore the catalog, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHFCL

XMEOUT Parameters: date, time,applid, n, filename, oooo

DFHFC0975
applid LSR pool n already exists
Explanation:

CICS requested VSAM to build the local shared resource (LSR) pool n. However, this pool already exists.

System action:

CICS continues processing. If the existing pool is unsuitable, subsequent file OPENs may fail.

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

User response:

Examine the system console log and the LSR statistical data for pool creation and deletion times, and in the case of the log, for possible pool delete failures. (The simplest and most likely reason for this error is the failure of a previous attempt to delete pool n.)

Destination:

Console

Modules:

DFHFCL

XMEOUT Parameters: applid, n

DFHFC0976
applid {RLS | Non-RLS} file filename not opened. DSNAME = NULLFILE or DD DUMMY. Module module.
Explanation:

CICS could not open file filename, because the DSNAME was NULLFILE or the DD statement was DUMMY.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

None.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, module

DFHFC0977
applid {RLS | Non-RLS} OPEN of file filename failed. VSAM catalog error. Return code - X'eeee',X'cccc' in module module.
Explanation:

While CICS was opening file filename and retrieving information from the VSAM catalog, an SVC 26 (LOCATE macro) failed with return code cccc. eeee is the CICS internal return code, as follows:

8114
SVC 26 failed on index or data.
8115
SVC 26 failed on base cluster.
System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

For the meaning of the LOCATE return code, see OS/390 V2R10.0 DFSMSdfp Advanced Services.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, X'eeee', X'cccc', module

DFHFC0978
applid {RLS | Non-RLS} OPEN of file filename failed. VSAM catalog error. Return code - X'eeee' in module module.
Explanation:

While CICS was opening file filename and retrieving information from the VSAM catalog, CICS file control open/close detected a CICS logic error. eeee is as follows:

8118
A VSAM catalog entry for a path does not have a base cluster or an AIX as its first association.
8119
In a VSAM catalog entry for an AIX, either the data association or the base cluster association is missing.
811A
In a VSAM catalog entry for a base cluster, the data association or the index association is missing.
811C
The open was requested against the data association or the index association. The base cluster, AIX or path should be specified instead.
System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

Obtain a VSAM LISTCAT listing for file filename. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, X'eeee', module

DFHFC0979
date time applid LSR pool n parameters incomplete for file filename because the DSNAME specified in the file entry could not be found on the VSAM catalog. VSAM has returned code rrrr in R15.
Explanation:

While dynamically calculating VSAM local shared resource (LSR) parameters, CICS attempted to retrieve information from the VSAM catalog using the data set name in the FCT entry for file filename. The catalog access failed with the VSAM return code rrrr from the SHOWCAT macro.

System action:

CICS continues processing, but does not use any parameters for file filename in calculations for the LSR pool.

User response:

Ensure that you have correctly specified the JCL for the file, and that the catalog containing the file is included in the JCL. If these checks do not reveal the error, see the meaning of the SHOWCAT return code, rrrr, in OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets.

Destination:

CSMT

Modules:

DFHFCFS

XMEOUT Parameters: date, time,applid, n, filename, rrrr

DFHFC0980
applid Non-RLS OPEN of base for file filename failed. CICS logic error eeee,cccc.
Explanation:

While trying to open the VSAM ESDS base of a path through which a record insert has been requested for file filename, CICS has detected an internal logic error. eeee is as follows:

8E01
Request to DFHFCM is not OPEN or CLOSE.
8E99
Logic error during DFHFCM processing at offset cccc.
System action:

CICS takes a system dump and terminates the transaction abnormally.

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

User response:

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

Destination:

Console

Modules:

DFHFCM

XMEOUT Parameters: applid, filename, eeee, cccc

DFHFC0981
applid Dynamic allocation of base for non-RLS file filename failed. Return code rrrr,cccc.
Explanation:

While trying to open the VSAM KSDS base of a path through which a record insert has been requested for file filename, CICS file control issued an MVS DYNALLOC command which failed with the return code cccc. rrrr is the return code in register 15.

System action:

CICS takes a system dump and terminates the transaction abnormally.

User response:

For the meaning of the DYNALLOC return codes, refer to the MVS/ESA System Programming Reference: Application Development Guide.

Destination:

Console

Modules:

DFHFCM

XMEOUT Parameters: applid, filename, rrrr, cccc

DFHFC0982
applid Non-RLS OPEN of base for file filename failed. VSAM codes - rrrr,cccc.
Explanation:

While trying to open the VSAM KSDS base of a path through which a record insert has been requested for file filename, CICS file control issued an OPEN which failed with the VSAM error code cccc from the ACB. rrrr is the VSAM return code in register 15.

System action:

CICS takes a system dump and terminates the transaction abnormally.

User response:

VSAM issues a console error message. Use the VSAM message and the VSAM return code in the CICS message to solve the problem.

For the meaning of the VSAM return code, see the MVS/DFP Access Method Services for VSAM Catalogs.

Destination:

Console

Modules:

DFHFCM

XMEOUT Parameters: applid, filename, rrrr, cccc

DFHFC0983
applid Non-RLS CLOSE of base for file filename failed. CICS logic error eeee,cccc.
Explanation:

While trying to close the VSAM KSDS base of a path through which a record insert has been requested for file filename, CICS has detected an error. eeee is as follows:

8E05
Failure in DFHFCM to close VSAM base. cccc is the error code from the VSAM ACB.
8E07
SVC 99 dynamic deallocation in DFHFCM failed. cccc is the SVC 99 error return code.
System action:

CICS takes a system dump and continues processing, with base left open.

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

User response:

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

Destination:

Console

Modules:

DFHFCM

XMEOUT Parameters: applid, filename, eeee, cccc

DFHFC0987
applid {RLS | Non-RLS} OPEN of file filename failed: Not available for type of processing. VSAM codes - 0008, 00A8 in module module.
Explanation:

When CICS attempted to open the VSAM file filename, the OPEN failed with the VSAM return codes shown in the message text. The probable reason for the failure is that the data set is in use by another region or another ACB in the CICS region, and that the VSAM share options prohibit the level of sharing needed to permit the OPEN.

A data set may not be open in both RLS and non-RLS mode, via different files, at the same time, with one exception. It is possible for a data set to be open in non-RLS read-only mode from either another CICS region or from batch at the same time as the data set is open in RLS mode.

System action:

CICS continues processing, with the file left closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

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

User response:

If the data set is in use by another user, wait until it is free and then retry the OPEN.

If the problem recurs and you cannot resolve the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, module

DFHFC0988
applid Non-RLS OPEN of file filename failed. This data set type is not supported by CICS.
Explanation:

An attempt to open file filename has failed because the file referenced a data set of a type not supported by CICS.

CICS File Control supports opening VSAM KSDS, ESDS, RRDS and VRRDS data sets, paths over KSDS and ESDS data sets, and BDAM data sets. No other data set types are supported. For example, CICS does not support opening a VSAM linear data set.

System action:

CICS continues processing with filename closed and its state UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

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

User response:

You have probably specified DSNAME incorrectly in the file definition. Correct the file definition.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename

DFHFC0989I
applid Non-RLS OPEN of file filename will be delayed because the associated data set dataset is being recalled.
Explanation:

File filename is taking longer than expected to open because the associated data set has been migrated and has to be recalled before the file open processing can complete.

System action:

The open of file filename will be delayed until its associated data set has been recalled.

User response:

None.

Destination:

Console

Modules:

DFHFCN

XMEOUT Parameters: applid, filename, dataset

DFHFC0990
applid {RLS | Non-RLS} OPEN of file filename failed. Recovery specified, but the path is not in the upgrade set. Base data set dsname. Module module.
Explanation:

An attempt was made to open a recoverable file, associated with a VSAM path over an alternate index, for update processing (SERVREQ=ADD, DELETE or UPDATE set). However, the alternate index is not in the upgrade set of the base. CICS detects this condition and does not attempt to open the file.

If the alternate index is not in the upgrade set of the base, any updates made via the base are not reflected in the alternate index and so updates made via the path may compromise data integrity. Note the open of the path fails if RECOVERY=ALL or RECOVERY=BACKOUTONLY is specified on the path FCTE entry, or on the base data set.

The base takes the recovery attributes of the first file to open for update against it since a cold or initial start. Those attributes remain in force on the data set, and consistency checks are performed between the FCT entry and the data set at file open time.

System action:

CICS continues processing with file filename closed and not enabled.

User response:

Take the data set offline and redefine the alternate index with the UPGRADE option. Run a BLDINDEX job to bring the alternate index up to date with the base data set and then retry the open of the file.

Destination:

Console

Modules:

DFHFCFS, DFHFCRO

XMEOUT Parameters: applid, {1=RLS, 2=Non-RLS}, filename, dsname, module

DFHFC0991
applid Non-RLS OPEN of file filename failed. Recovery attributes conflict with those on the VSAM data set - cccc. Base data set dsname
Explanation:

An attempt was made to open a file filename for update processing. (SERVREQ=ADD, DELETE or UPDATE set), CICS detected that the recovery attributes on the file were inconsistent with those currently in force for the VSAM data set as recorded in the CICS data set name block. The file was not opened in order to maintain data integrity.

The data set takes the recovery attributes of the first file to open for update against it since a cold or initial start. Code cccc identifies the inconsistency found and takes the following values:

8514
Both the file and the data set have RECOVERY=ALL specified, but the forward recovery logs specified are different.
8515
The data set has RECOVERY=BACKOUTONLY or RECOVERY=NONE specified, and the file is trying to open with RECOVERY=ALL.
8516
The data set has RECOVERY=NONE specified. The file is attempting to open with RECOVERY=BACKOUTONLY.
851B
The file specified RECOVERY=NONE or BACKOUTONLY. The VSAM data set had RECOVERY=ALL specified.
851C
The file specified RECOVERY=NONE. The VSAM data set had BACKOUTONLY specified.
System action:

CICS continues processing with file filename closed and not enabled.

User response:

Ensure that files referencing the same VSAM data set have the same recovery attributes specified.

Alter the FCT entries using the CEDA ALTER FILE command and reinstall the group.

To nullify the recovery attribute set for the base data set, the user can issue a CEMT SET DSNAME REMOVE or EXEC CICS SET DSNAME REMOVE command. This deletes the base cluster block, and leaves CICS with no record of prior recovery settings for this VSAM data set. The first file to subsequently open against this data set causes a new base cluster block to be built. If the file is opened for update processing, the recovery attributes of this file are copied into the base cluster block.

If you want to have files referencing the same VSAM data set with different backout recovery attributes you should use Global User Exit XFCNREC.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, cccc, dsname

DFHFC0995
applid Hiperspace allocation for LSR pool n was incomplete or zero.
Explanation:

CICS requested VSAM to provide hiperspace buffers when building local shared resource (LSR) pool number n, but there was insufficient expanded storage available to satisfy the request completely.

System action:

CICS continues processing. VSAM uses the buffers it has been able to provide.

User response:

Review your installation’s use of expanded storage and use MVS facilities to adjust its allocation, or change your RDO LSRPOOL definition or DFHFCT TYPE=SHRCTL definition, to reduce the hiperspace buffer requirements for pool n.

Destination:

Console

Modules:

DFHFCL

XMEOUT Parameters: applid, n

DFHFC0996
date time applid {Open | Close | Enable | Disable | Cancel of close} of file filename suppressed due to intervention of User Exit.
Explanation:

An open, close, enable, disable or cancel close request has been issued against the specified file. An exit program enabled at the global user exit point XFCSREQ in CICS file control has directed CICS not to carry out the request.

System action:

If the request being issued is an enable, disable, close or cancel close request, the file state remains unchanged, that is, it remains in the same state as before the request was issued.

If the request is an open request, the state remains unchanged unless the file was in a closed, enabled state. In this state, the open request could be an implicit open request, (that is, the file is being opened as part of a file API request). If it is an implicit open request, the file state is changed to closed unenabled to ensure the file API request is halted, and a NOTOPEN condition is returned to the application.

User response:

Examine the reason for the command being suppressed. This is installation specific.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHFCFS

XMEOUT Parameters: date, time,applid, {1=Open, 2=Close,3=Enable, 4=Disable, 5=Cancel of close}, filename

DFHFC0997I
applid RLS OPEN of file filename is delayed because the associated data set dsname is being recalled.
Explanation:

RLS file filename is taking longer than expected to open because the associated data set has been migrated and has to be recalled before the file open processing can complete.

System action:

The open of file filename is delayed until its associated data set has been recalled.

User response:

None.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename, dsname

DFHFC0998
applid User exit XFCNREC is causing file filename to be opened even though a file recovery inconsistency of type X'code' exists. CICS cannot guarantee data integrity for base data set dsname
Explanation:

An attempt was made to open file filename for update processing, (SERVREQ=ADD, DELETE or UPDATE set), and CICS detected that the backout recovery attribute on the file was inconsistent with that on the VSAM base data set. Normally CICS would fail the open on detection of an inconsistency. However, a program running at user exit XFCNREC has indicated that the open should continue even though an inconsistency has been detected. CICS can no longer guarantee the integrity of the data on the associated data set. Code X'code' identifies the inconsistency and can take one of the following values:

X'8516'
The data set has RECOVERY=NONE specified. The file is attempting to open with RECOVERY=BACKOUTONLY.
X'851C'
The file specified RECOVERY=NONE. The VSAM data set had BACKOUTONLY specified.

An INQUIRE on the RECOVSTATUS for the data set from this point onwards returns a NOTRECOVABLE response. The data set is marked as not recoverable until the next CEMT SET DSNAME REMOVE, EXEC CICS SET DSNAME REMOVE command or cold or initial start.

System action:

CICS opens file filename and continues processing using the recovery setting from the file definition to determine whether backout logging should be performed.

User response:

Ensure that it is correct for the backout recovery attribute inconsistency to be ignored for this data set.

If the backout recovery attribute inconsistency should not have been ignored, ensure that files referencing the same VSAM data set have the same recovery attributes. If they do not, either alter the FCT entries using the CEDA ALTER FILE command and reinstall the group, or alter the FCT macro definition of the file. Note that this reassembled FCT only takes effect at the next CICS cold or initial start.

To nullify the recovery attribute set for the base data set, issue a CEMT SET DSNAME REMOVE or EXEC CICS SET DSNAME REMOVE command. This deletes the base cluster block and leaves CICS with no record of prior recovery settings for this VSAM data set. The first file to subsequently open against this data set causes a new base cluster block to be built. If the file is opened for update processing, the recovery attributes of this file are copied into the base cluster block.

Destination:

Console

Modules:

DFHFCN

XMEOUT Parameters: applid, filename, X'code', dsname

DFHFC0999
applid RLS OPEN of file filename failed. RLS access is disabled.
Explanation:

While CICS was opening file filename the CICS file control open/close routine detected that RLS access is disabled. A PREVIOUS open or record management request received a serious error from VSAM and disabled RLS access.

System action:

CICS continues processing with file filename closed and its state UNENABLED. Any transaction attempting to use RLS files is sent a NOTOPEN condition.

User response:

Determine why RLS access was disabled.

Destination:

Console

Modules:

DFHFCRO

XMEOUT Parameters: applid, filename

DFHFC2813
applid Program DFHRCEX cannot be found.
Explanation:

An attempt to link to program DFHRCEX during file control initialization has failed. This is a severe error.

System action:

CICS startup is abnormally terminated with a dump.

User response:

Find out why DFHRCEX could not be located.

Destination:

Console

Modules:

DFHFCRP

XMEOUT Parameter: applid

DFHFC3001
date time applid Record not backed out because it may have been overridden by a non-RLS batch job. Diagnostic information follows in message DFHFC3010. The record was updated by unit of work X'local-uowid' for file filename, base data set data-set-name
Explanation:

A log record was presented to file control for backing out, but although the updated record was protected by a VSAM RLS lock, a non-RLS batch job had elected to override the RLS locks held on this data set and therefore the condition of the record can no longer be guaranteed. The update had been made to the base data set data-set-name via the CICS file filename, under the unit of work identified by local_uowid.

System action:

The update is not backed out because the condition of the updated record cannot be guaranteed, The updated data is committed instead. Diagnostic information is provided by this message and the subsequent message DFHFC3010.

User response:

See the associated message DFHFC3010 for more information and guidance.

Destination:

CSFL

Modules:

DFHFCRC

XMEOUT Parameters: date, time,applid, X'local-uowid', filename,data-set-name

DFHFC3002
date time applid Record backed out at request of user exit although it may have been overridden by a non-RLS batch job. Diagnostic information follows in message DFHFC3010. The record was updated by unit of work X'local-uowid' for file filename, base data set data-set-name
Explanation:

A log record was presented to file control for backing out, but although the updated record was protected by a VSAM RLS lock, a non-RLS batch job had elected to override the RLS locks held on this data set. However, an exit program enabled at the XFCBOVER exit point decided that the non-RLS batch job would not have caused corruption of the record, and requested that the backout should go ahead. The update had been made to the base data set data-set-name via the CICS file filename, under the unit of work identified by local_uowid.

System action:

An attempt to backout the update is made because the user exit requested that backout should go ahead. Diagnostic information is provided by this message and the subsequent message DFHFC3010.

User response:

See the associated message DFHFC3010 for more information and guidance.

Destination:

CSFL

Modules:

DFHFCRC

XMEOUT Parameters: date, time,applid, X'local-uowid', filename,data-set-name

DFHFC3003
date time applid Record not backed out because locks for a backout-failed data set have been reset. Diagnostic information follows in message DFHFC3010. The record was updated by unit of work X'local-uowid' for file filename, base data set data-set-name
Explanation:

An update made by unit of work local-uowid to the base data set data set name via the CICS file filename was protected by a lock while awaiting successful backout, but a decision has been taken locally to reset the locks for this data set. The log record representing the update has therefore been presented to file control for the purpose of providing diagnostic information in this and the subsequent message DFHFC3010.

System action:

The update is not backed out and the lock is released. The implication of resetting the locks for a data set is that the backout has failed for some reason which cannot be easily corrected. Diagnostic information is provided by this message and the subsequent message DFHFC3010.

User response:

See the associated message DFHFC3010 for more information and guidance.

Destination:

CSFL

Modules:

DFHFCRC

XMEOUT Parameters: date, time,applid, X'local-uowid', filename,data-set-name

DFHFC3004
date time applid Record backed out because of the forced back out of an indoubt unit of work. Diagnostic information follows in message DFHFC3010. The record was updated by unit of work X'local-uowid' for file filename, base data set data-set-name
Explanation:

A log record has been presented to file control for backing out because the local unit of work local-uowid, which was part of a distributed unit of work, has gone in-doubt, and CICS has backed out the local unit of work. This decision to back out the record is the result of one of the following:

The update being backed out was made to the base data set data-set-name via the CICS file filename. This and the subsequent message provides diagnostic information which is of use in correcting the situation if the actual resolution of the distributed unit of work was to commit it rather than to back it out.

System action:

The update is backed out, and diagnostic information is provided by this message and the subsequent message DFHFC3010.

User response:

See the associated message DFHFC3010 for more information and guidance.

Destination:

CSFL

Modules:

DFHFCRC

XMEOUT Parameters: date, time,applid, X'local-uowid', filename,data-set-name

DFHFC3010
date time applid Diagnostic information for unit of work X'local-uowid' and file filename. Update was a {read-update | write-add} made by transaction tranid at terminal termid under task number tasknum. Key length key-length, data length data-length, base ESDS RBA X'base-RBA-or-zero', record key X'record-key'
Explanation:

This message follows each DFHFC3001, DFHFC3002, DFHFC3003, or DFHFC3004 message, and provides additional information to help diagnose and correct the situation reported in the preceding message.

For any given filename and unit of work CICS normally issues messages of only one type; for example, a series of DFHFC3001 messages each followed by DFHFC3010, or a series of DFHFC3003 messages each followed by DFHFC3010.

The exception to this is when an exit program enabled at the XFCBOVER global user exit point elects to backout some updates and not to backout others. In this situation CICS might issue a combination of DFHFC3001 and DFHFC3002 messages (each followed by DFHFC3010) for the same filename and unit of work.

This message includes the following information:

local-uowid
The local unit-of-work identifier for correlation with the preceding message.
filename
The file name for correlation with the preceding message.
read-update or write-add.
The type of before-image log record presented to file control. The type is read-update if the update made to the file was either: a READ UPDATE, READNEXT UPDATE or READPREV UPDATE request (which will normally have been followed by a REWRITE or DELETE request), or a DELETE request which specified a RIDFLD. The type is write-add if the update made to the file was a WRITE request.
tranid
The transaction under which the original update was made.
termid
The terminal from which the transaction which made the original update was run.
tasknum
The task number under which the transaction which made the original update was run
key-length
The length of the record key
data-length
The length of the data in the before-image.
base-RBA-or-zero
The base RBA if the update was made to an ESDS, or zero if not.
record-key
The value of the record key field, in hexadecimal.
System action:

None beyond the system action described under the preceding message.

User response:

Use the diagnostic information to determine any changes that need to be made to the data set to ensure that the contents are correct. Once you have identified the record which may not now contain the correct contents, and the transaction which originally updated it, a knowledge of your application programs should allow you to determine the necessary action.

Destination:

CSFL

Modules:

DFHFCRC

XMEOUT Parameters: date, time,applid, X'local-uowid', filename,{1=read-update, 2=write-add},tranid, termid, tasknum, key-length, data-length, X'base-RBA-or-zero', X'record-key'

DFHFC4700
applid {An unexpected | A VSAM | A length | A lock | A timeout | An unexpected delete} error has occurred during file backout. (Module DFHFCFR has returned reason code (X'xx'), access method code (X'cccccccc') and length error code (X'yy').)
Explanation:

File backout has called module DFHFCFR as part of its processing, and an error has been returned which should not be possible during backout. The message text includes the type of error that has occurred.

Additional diagnostic information is provided by: the reason code xx returned from DFHFCFR, the code cccccccc which was returned to DFHFCFR from the access method that it called, and the length error code yy.

The length error code is normally either X'00', indicating that length errors are not applicable to the type of request which was in error, or X'01', indicating that there was no length error. A value greater than X'01' occurs when the message text indicates that the type of error is a length error.

System action:

An exception trace point is written, and a system dump is taken.

The error is processed as a backout failure. Unless a user exit program enabled at the XFCBFAIL exit point bypasses backout failure processing, message DFHFC4701 or DFHFC4702 follows and gives details of the file and data set involved.

CICS continues.

User response:

Inform the system programmer. This indicates a possible error in CICS, VSAM or BDAM code. The severity of its impact depends on whether the backout can be successfully retried.

If the data set being backed out is a VSAM data set, you can retry the backout. Message DFHFC4701 names the data set, and the failed backout can be retried using SET DSNAME RETRY. If the problem is due to some transient condition which has since cleared, the backout will now succeed.

If the data set being backed out is a BDAM data set, the backout cannot be retried. The data is committed and the locks are released, unless an exit program enabled at the XFCBFAIL exit point terminates CICS, in which case data integrity can be preserved by performing an emergency restart.

If the backout cannot be successfully retried, then take action depending on the type of error indicated in the message text:

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

Destination:

Console

Modules:

DFHFCRC

XMEOUT Parameters: applid, {1=An unexpected, 2=A VSAM, 3=A length, 4=A lock, 5=A timeout, 6=An unexpected delete}, X'xx', X'cccccccc', X'yy'

DFHFC4701
date time applid Backout failed for transaction tranid, VSAM file filename, unit of work X'local_uowid', task task_number, base base_dsname, path path_dsname, failure code X'bfail_code'.
Explanation:

File backout has been unable to backout an uncommitted change made to a VSAM data set via file filename, that was made by the unit of work local_uowid.

The file is associated with the data set path_dsname. This is either a base cluster data set if the path_dsname and base_dsname given in the message are the same, or is a path data set whose base cluster is the base_dsname given in the message if the two names differ.

The change that is being backed out was originally made by task task_number servicing transaction code tranid, running under the unit of work local_uowid The current task number will differ from the original one that is given in the message if this backout is itself a retry of an earlier backout which also failed, or is a backout being carried out following resolution of an indoubt situation, and the current transaction code will differ from the original one if the transaction has been disabled.

The failure code X'bfail_code' indicates the reason for the failure.

System action:

The system continues normally.

Backing out of the unit of work continues, but no further attempts to backout updates made by this unit of work to the base_dsname named in the message are made.

When the unit of work has been backed out as far as is possible, those updates which could not be backed out are deferred (shunted) until the backout can be retried.

It is possible for other work to continue to access the base cluster data set, but the records in that data set that were changed by this unit of work are locked by retained locks. This ensures that any attempt to access these records results in a LOCKED response being returned to the application. The records must remain locked until the backout has been successfully retried in order to preserve data integrity.

If, when the backout is retried, it fails again for either the same or another reason, this message is issued again, with the failure code indicating the reason for the failure on this occasion.

User response:

You may decide to leave the data set online for any of the errors indicated by X'bfail_code', especially if you believe that the backout failure may have been due to some transient situation, and that the backout may succeed if retried. You can manually drive retry of the backout using the SET DSNAME RETRY command, or alternatively wait until some event triggers retries of the shunted backouts in the system.

As a last resort, and at the cost of losing data integrity, you could bypass the deferred backout of uncommitted changes to this data set using the SET DSNAME RESETLOCKS command.

The user response depends on the value of the failure code X'bfail_code'.

10
The backout attempted to add a duplicate key value to a unique alternate index. The backout can never be carried out unless you can delete the existing record with this alternate key value, then retry the backout using SET DSNAME RETRY. This failure can only occur for a file being accessed in non-RLS mode.
20
The data set ran out of storage while the request was being processed. You should reallocate the data set with more space, then retry the backout using SET DSNAME RETRY. Do not forward recover the data set. If you accessed the file in RLS mode, there are extra steps required to ensure that the retained locks remain associated with the data set. These are explained in the CICS Recovery and Restart Guide.
24
An I/O error has occurred on the data set. You should consider the possibility that the data set needs restoring, especially if there have been a large number of these messages referring to the same base cluster data set, or if there have also been I/O errors issued during request processing for that data set.

If you do decide to restore the data set, you should take the following steps:

  1. Prevent access to the data set
  2. Restore a backup copy and forward recover the data set (for example, using CICSVR)
  3. Reallow access to the data set
  4. Retry deferred backouts.

For an RLS mode data set, prevent access by issuing a SET DSNAME QUIESCED command which closes all open files throughout the sysplex and prevents further RLS opens. Reallow access by issuing a SET DSNAME UNQUIESCED command, which also retries deferred backouts automatically.

For a non-RLS mode data set, prevent access by issuing a SET DSNAME UNAVAILABLE command to prevent further non-RLS opens and issue SET FILE CLOSED commands for all open files. Reallow access by issuing a SET DSNAME AVAILABLE command, and retry deferred backouts using SET DSNAME RETRY.

40
Logical delete for an ESDS data set was not performed because the XFCLDEL exit either chose not to carry out the logical delete, or was not enabled.
41
A DFSMSdss non-BWO backup is in progress for the data set. The backout will be automatically retried when the backup completes.
B0
A deadlock was detected. This can only happen for files opened in non-RLS mode. Since this is a transient condition, you should just retry the backout using SET DSNAME RETRY.
C0
A failure of the VSAM RLS server was detected by this request. The backout is automatically retried when the server becomes available again.
C1
VSAM RLS access is disabled because the server is unavailable. The backout is automatically retried when the server becomes available again.
C2
The VSAM RLS server has recycled (failed and restarted) whilst a record was being backed out. This is a very rare occurrence since the failure and restart must have taken place after the record to be backed out was read for update, and before it was rewritten or deleted. A retry of the backout should be successful, but because the server has already become available, backout will not be automatically retried. You should use SET DSNAME RETRY to drive backout retry.
C3
The VSAM RLS cache structure to which the data set was bound has either failed or has lost connectivity, and VSAM has been unable either to rebuild the failed cache structure, or to bind the data set to an alternative cache structure in the cache set. The backout is automatically retried when the cache structure becomes available again.
C4
VSAM has returned a response indicating that the RLS lock structure in the coupling facility is full. Allocate a larger lock structure, rebuild into it and retry the backout using set dsname retry. See OS/390 MVS Setting up a Sysplex, (GC28-1779) and DFSMS/MVS DFSMSdfp Storage Administration Reference, (SC26-4920) for further information on how to allocate, and build into, larger lock structures.
F0
There was no space to add another alternate key value to a non-unique alternate index. You should rebuild the data set with a larger alternate index data CI size (unless you are already at the maximum), and then retry the backout using SET DSNAME RETRY. If you accessed the file in RLS mode, there are extra steps required to ensure that the retained locks remain associated with the data set. These are explained in the CICS Recovery and Restart Guide. Do not forward recover the data set.
FB
An error occurred when opening the file for backout. Determine why the file would not open, and if it is possible to correct it, do so and then issue SET DSNAME RETRY to retry the backout. If the error occurred because the data set was quiesced, the backout is automatically retried when the data set is unquiesced. If the error occurred because the VSAM RLS server was not available, the backout is automatically retried when it becomes available again.
FE
An error occurred which is not expected to be possible during backout. An exception trace point is written, message DFHFC4700 is issued and a system dump is taken. Use these to determine the cause of the error. It might be worth retrying the backout, using SET DSNAME RETRY, since the problem could have been some transient condition which has since cleared.
Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCRC

XMEOUT Parameters: date, time,applid, tranid, filename, X'local_uowid', task_number, base_dsname,path_dsname, X'bfail_code'

DFHFC4702
date time applid Backout failed for transaction tranid, BDAM file filename, unit of work X'local_uowid', task task_number.
Explanation:

File backout has been unable to backout an uncommitted change made to a BDAM data set via file filename, that was made by the unit of work local_uowid.

The change that is being backed out was originally made by task task_number servicing transaction code tranid, running under the unit of work local_uowid. However, if this backout is being attempted after waiting for an indoubt situation to be resolved, the current task number will be different from the original one given in the message, and transaction code will be different from the original one if the transaction has been disabled.

System action:

The system continues normally.

Backing out of the unit of work continues, and any further failures to backout changes made to this BDAM data set result in the message being reissued.

Unless a program invoked at the backout failure exit point, XFCBFAIL, took some action to prevent it, it is possible for other work to continue to access the BDAM data set, but data integrity is compromised because the changes have not been backed out.

User response:

Unless you are prepared to continue using the data set in spite of the loss of data integrity, you should take some action to correct matters, such as closing all files that are using the data set and backing out the uncommitted changes offline.

One possible cause of a BDAM backout failure is that a logical delete could not be performed because the XFCLDEL exit either chose not to carry out the logical delete or was not enabled. If this is the case then you may want to ensure that a suitable exit program is enabled at the XFCLDEL exit point, so that any future attempts at backing out writes made to BDAM data sets will succeed.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCRC

XMEOUT Parameters: date, time,applid, tranid, filename, X'local_uowid', task_number

DFHFC4800
date time applid A failure has been detected on forward recovery log stream log_stream. The associated RLS data set has been quiesced. Data set dsname
Explanation:

The logger domain has detected an error on the forward recovery log stream log_stream. As a result, the associated RLS data set dsname cannot safely continue to be used.

System action:

Processing continues. The RLS data set dsname has been quiesced.

User response:

First, take a backup of the data set to establish a new forward recovery point. You can then correct the problem causing the log stream failure, delete and redefine the failed MVS log stream, and unquiesce the data set to reallow RLS access.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCLF

XMEOUT Parameters: date, time,applid, log_stream, dsname

DFHFC4801
date time applid A failure has been detected on forward recovery log stream log_stream. The associated non-RLS data set has been set unavailable and its files closed. Data set dsname
Explanation:

The logger domain has detected an error on the forward recovery log stream log_stream. As a result, the associated non-RLS data set dsname cannot safely continue to be used.

System action:

Processing continues. The data set dsname has been set unavailable and all files associated with it have been closed.

User response:

First, take a backup of the data set to establish a new forward recovery point. Then, having corrected the problem which caused the log stream failure, you can delete and redefine the failed MVS log stream. If the name of the forward recovery log stream for the data set is held in the VSAM catalog, you can now make the data set available again, using SET DSNAME AVAILABLE. If the name of the forward recovery log stream for the data set is held in the file definition, you must issue SET JOURNALNAME RESET for the forward recovery log before making the data set available again using SET DSNAME AVAILABLE.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCLF

XMEOUT Parameters: date, time,applid, log_stream, dsname

DFHFC4802
date time applid A failure has been detected on auto journal journal_name. The associated file file_name has been closed.
Explanation:

The logger domain has detected an error on the automatic journal journal_name. As a result, the automatic journal is no longer reliable.

System action:

The associated file filename has been set closed.

User response:

The appropriate action depends on how you use the automatic journal, and on whether you can tolerate missing information.

If you require a complete automatic journal with no missing information, you need to take some action to establish a new start point for the automatic journal. You can then correct the error causing the log stream failure, delete and redefine the log stream, issue SET JOURNALNAME RESET, and reopen the file.

If you do not require a complete automatic journal, if the log stream is still writeable, you can issue SET JOURNALNAME RESET, open the file, and continue autojournalling to the same journal. A message preceding this one reports details of the log stream failure.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCLF

XMEOUT Parameters: date, time,applid, journal_name, file_name

DFHFC5801A
applid File OPEN has failed for VSAM data set. The BWO values in the ICF catalog indicate that data set needs to be restored and forward recovered. Data set 'dsname'.
Explanation:

CICS has rejected a file open for the VSAM base data set dsname. This base data set could not be opened because the integrated catalog facility (ICF) catalog backup while open (BWO) flags indicated a corrupted data set.

This message is accompanied by message DFHFC5806 which includes the name of the file involved in the OPEN failure.

System action:

The file open for data set dsname fails. CICS continues processing but the file is closed and its state is set to UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

Carry out the following procedure:

  1. If a BWO copy of this VSAM data set is available:
    1. Restore the BWO copy of this data set via DFHSM and/or DFDSS.
    2. Apply the CICS forward recovery logs via a log-apply utility, such as CICS VSAM Recovery (CICSVR), to bring the data set to a point of consistency.
  2. If no BWO copy of this base data set exists but a normal quiesced copy does, apply the forward recovery logs to the data set in the normal way to bring the data set to a point of consistency.
  3. Set the ICF catalog BWO flags to indicate that the data set has been recovered to the point of failure. This can be done by issuing a CEMT SET DSNAME RECOVERED or EXEC CICS SET DSNAME RECOVERED command.
  4. Rename the data set to that of the original data set prior to the failure.
  5. Make the data set available.
Note:
Some log-apply utilities, such as CICS VSAM Recovery MVS/ESA (CICSVR MVS/ESA) Version 2, set the ICF catalog BWO flags to a RECOVERED state after the CICS forward recovery logs have been applied.
Destination:

Console

Modules:

DFHFCAT

XMEOUT Parameters: applid, dsname

DFHFC5802A
applid File OPEN has failed for VSAM data set. The BWO values in the ICF catalog indicate that data set needs to be forward recovered. Data set 'dsname'.
Explanation:

CICS has rejected a file open for the VSAM base data set dsname. This base data set could not be opened because the ICF catalog backup while open (BWO) flags indicated that the data set was back-level and needed to be forward recovered. This failure occurs if a BWO of a VSAM base data set is restored but not forward recovered. This message is accompanied by DFHFC5806 which includes the name of the file involved in the OPEN failure.

System action:

The file open for data set dsname fails. CICS continues processing but the file is closed and its state set to UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

Carry out the following procedure:

  1. Apply the CICS forward recovery logs via a log-apply utility, such as CICS VSAM Recovery (CICSVR), to bring the data set to a point of consistency.
  2. Set the ICF catalog BWO flags to indicate that the data set has been recovered to the point of failure. This can be done by issuing a CEMT SET DSNAME RECOVERED or EXEC CICS SET DSNAME RECOVERED command.
Note:
Some log-apply utilities, such as CICS VSAM Recovery (CICSVR), set the ICF catalog BWO flags to a RECOVERED state after the CICS forward recovery logs have been applied.
Destination:

Console

Modules:

DFHFCAT

XMEOUT Parameters: applid, dsname

DFHFC5803
applid A severe error (code X'code') has occurred while inquiring/setting VSAM data set BWO attributes. Data set 'dsname' Return Code X'xxxxxxxx' Reason Code X'yyyyyyyy' Prob Det X'zzzzzzzzzzzzzzzz'.
Explanation:

A severe error has been detected in DFHFCAT while inquiring or setting ICF catalog backup while open (BWO) attributes of base data set dsname. The error code is the exception trace point ID which uniquely identifies the call which has failed. The code X'code' can take the following values:

Value
Meaning
X'0B57'
A call to MVS/DFP Callable Services to inquire if a data set is known to a SMS sub-system has failed
X'0B59'
A call to MVS/DFP Callable Services to update the BWO flags to a forward recovered state for a data set has failed
X'0B5A'
A call to MVS/DFP Callable Services to update the recovery point for a data set has failed
X'0B5B'
A call to MVS/DFP Callable Services to update the BWO flags to a BWO disabled state for a data set has failed
X'0B5C'
A call to MVS/DFP Callable Services to inquire if the BWO flags for a data set were in a BWO enabled state has failed
X'0B5D'
A call to MVS/DFP Callable Services to update the BWO flags to a BWO enabled state for a data set has failed.

For further information about CICS exception trace entries, see the CICS Problem Determination Guide.

The values xxxxxxxx, yyyyyyyy and zzzzzzzzzzzzzzzz are the BWO return code, reason code and problem determination code from the MVS/DFP Callable Services Interface call to update/inquire the ICF catalog BWO attributes.

This message is accompanied by message DFHFC5806 when a file open failure occurs or by message DFHFC5810 when a file close failure occurs.

System action:

CICS makes an exception trace point entry and issues this message. No system dump is taken. The actions taken depend on the operation in progress at the time of the error.

If the error occurs while opening a file, the open request fails, the file is closed, and its state is set to UNENABLED.

If the error occurs while closing a file, the status of the file is unchanged.

If the error occurs during activity keypoint when updating the recovery point, CICS tries to update the recovery point on the next activity keypoint that creates a keypoint directory element (KPDE).

If the error occurs while setting the data set RECOVERED via CEMT or EXEC CICS commands, a non-OK response is returned.

User response:

Use the return code, reason code and problem determination code to determine why the call to MVS/DFP Callable Services has failed. For further information see MVS/DFP Callable Services in the MVS/DFP V3.2 System Programming Reference.

Ensure that the appropriate level of MVS/DFP is installed on the processor where CICS is running. Also ensure that the data set is SMS managed and known to the SMS subsystem.

Destination:

Console

Modules:

DFHFCAT

XMEOUT Parameters: applid, X'code',dsname, X'xxxxxxxx', X'yyyyyyyy',X'zzzzzzzzzzzzzzzz'

DFHFC5804
applid File CLOSE failed during CICS termination. File ' filename'.
Explanation:

An attempt to close file filename during orderly CICS termination has failed. This message is produced only as a warning that this file could not be closed. Data integrity has been maintained.

System action:

CICS termination continues.

If this file was open against a base data set open for update with BACKUPTYPE=DYNAMIC specified, one of the following messages is issued on the first open for update for this base data set in the next CICS run:

User response:

In order to avoid repetition of this failure, try to determine why the file was not closed from any other DFHFCxxxx messages produced during termination.

Destination:

Console

Modules:

DFHFCSD

XMEOUT Parameters: applid, filename

DFHFC5805
applid File OPEN failed. RECOVERY attributes of VSAM data set are not valid. File 'filename' data set 'dsname'.
Explanation:

The file filename is defined as eligible for backup while open for update (BACKUPTYPE=DYNAMIC). An attempt to open this file for update processing (SERVREQ=ADD, DELETE or UPDATE set), has failed because CICS has detected that the RECOVERY attributes have not been validated for the VSAM base data set dsname. A data set cannot be defined with BACKUPTYPE=DYNAMIC without RECOVERY=ALL specified.

System action:

The file open for data set dsname fails. Processing continues but the file is closed and its state set to UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

This is probably caused by a logic error in CICS. You should, however, check if there are any other DFHFCxxxx messages that indicate the cause of the error.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, dsname

DFHFC5806
applid File OPEN failed. DFHFCAT returned an error response from a BWO action on a VSAM data set. File 'filename' data set 'dsname'.
Explanation:

An attempt to open file filename has failed due to the failure of a call to MVS/DFP Callable Services or due to an invalid state returned from a call to MVS/DFP Callable Services for the VSAM base data set dsname. This message is accompanied by one of the following messages depending on the type of error being reported:

System action:

CICS fails the file open request for data set dsname. Processing continues but the file is closed and its state set to UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

See the accompanying message for the appropriate action to take in resolving this error.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, dsname

DFHFC5807
applid File OPEN failed. BACKUPTYPE attributes conflict with those currently defined for the VSAM data set. File 'filename' data set 'dsname'.
Explanation:

An attempt to open file filename for update processing, (SERVREQ=ADD, DELETE or UPDATE set), against the VSAM base data set dsname has failed. This is because CICS has detected an attribute conflict between the opening CICS FCT entry and the base data set’s DSNB which was already opened for update. An FCT entry with a BACKUPTYPE=STATIC cannot be opened against a DSNB which already has or had an FCT entry opened against it with BACKUPTYPE=DYNAMIC. Similarly, an FCT entry with a BACKUPTYPE=DYNAMIC cannot be opened against a DSNB which already has or had an FCT entry opened against it with BACKUPTYPE=STATIC.

Note:
A CICS base data set’s DSNB cannot change BACKUPTYPE midway through a CICS run. In order to do this, you must destroy the DSNB and create a new one. There are three ways of doing this:
  • CEMT SET DSNAME REMOVE
  • EXEC CICS SET DSNAME REMOVE
  • Terminate CICS and restart with a cold start.
If you respecify a DSNB with BACKUPTYPE=DYNAMIC, where previously it was specified with RECOVERY=NONE or BACKOUTONLY and BACKUPTYPE=STATIC, no forward recovery logging exists for the time that the DSNB had RECOVERY=NONE or BACKOUTONLY specified. Therefore you should take a backup copy of the data set before the change. This ensures that the data set can be recovered to a consistent point should a failure occur.
System action:

The file open for data set dsname fails. CICS continues processing but the file is closed and its state set to UNENABLED. Any transaction attempting to use this file is sent a NOTOPEN condition.

User response:

Determine the correct values for the BACKUPTYPE and RECOVERY attributes, and if necessary, redefine them for the FCT entry via CEDA.

Alternatively, remove the old DSNB as already described and reattempt the open.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, dsname

DFHFC5808
applid File OPEN warning. VSAM data set already set eligible for BWO on first open for update. File 'filename' data set 'dsname'.
Explanation:

The file filename is defined as eligible for backup while open for update (BACKUPTYPE=DYNAMIC). While opening this file for update processing, (SERVREQ=ADD, DELETE or UPDATE set), against the VSAM base data set dsname, CICS detected that the ICF catalog has already defined this base data set as eligible for BWO.

If a batch job has updated this data set in a prior batch window and a DFHSM backup was scheduled for the same time, you should discard the backup produced in the batch window as it is not possible to forward recover it to a consistent point should a failure occur. This is because updates made to the data set in the batch window are not reflected in the CICS forward recovery logs. This situation is likely to arise if CICS fails to close a file defined with BACKUPTYPE=DYNAMIC during CICS termination.

System action:

CICS updates the ICF catalog recovery point and open processing continues.

User response:

To ensure complete data integrity, quiesce all files opened against this base data set and take a backup copy. This can now be forward recovered at a later date and reflects updates made to this data set during a prior batch window.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, dsname

DFHFC5809
applid File OPEN warning. BACKUPTYPE attributes conflict with BWO values defined in ICF catalog. BWO values have been updated. File 'filename' data set 'dsname'.
Explanation:

The file filename is defined as not eligible for backup while open for update (BACKUPTYPE=STATIC). While opening this file for update processing (SERVREQ=ADD, DELETE or UPDATE set), against the VSAM base data set dsname, CICS detected that the BWO flags in the ICF catalog already defined this base data set as eligible for BWO. However, the CICS FCT entry and the DSNB define the base data set as not eligible for BWO.

If a batch job has updated this data set in a prior batch window and a DFHSM backup was scheduled for the same time, you should discard the backup produced in the batch window as it is not possible to forward recover it to a consistent point should a failure occur. This is because updates made to the data set in the batch window are not reflected in the CICS forward recovery logs.

This situation is likely to arise if CICS fails to close a file that is defined with BACKUPTYPE=DYNAMIC, during CICS termination and the file is redefined with BACKUPTYPE=STATIC on a subsequent CICS run.

System action:

CICS updates the ICF catalog to indicate that the data set is no longer eligible for BWO. File open processing continues.

User response:

Determine the correct value for the BACKUPTYPE attribute, and if necessary, redefine it via CEDA.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, dsname

DFHFC5810
applid File CLOSE failed. DFHFCAT returned an error response from a BWO action on a VSAM data set. File 'filename' data set 'dsname'.
Explanation:

An attempt to close file filename has failed because of the failure of a call to MVS/DFP Callable Services for the VSAM base data set dsname. This file is defined as eligible for backup while open for update (BACKUPTYPE=DYNAMIC), and is open for update processing, (SERVREQ=ADD, DELETE or UPDATE set). This message is accompanied by message DFHFC5803 or DFHFC0002, depending on the type of error reported.

System action:

The file close request for data set dsname fails. Processing continues and the file remains open.

User response:

See the accompanying message for the appropriate action to take in resolving this error.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, dsname

DFHFC5811
applid File OPEN warning. BACKUPTYPE=DYNAMIC attribute has been ignored. File 'filename' data set 'dsname'.
Explanation:

The file filename is defined as eligible for backup while open for update (BACKUPTYPE=DYNAMIC). During an attempt to open this file for update processing, (SERVREQ=ADD, DELETE or UPDATE set), against the VSAM base data set dsname, either:

System action:

CICS ignores the BACKUPTYPE=DYNAMIC parameter and continues as if STATIC were specified. File open processing continues.

User response:

If BWO support is required, ensure that the appropriate level of MVS/DFP Callable Services is installed.

If BWO support is not required, ensure that the file is defined with the BACKUPTYPE=STATIC attribute.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, dsname

DFHFC5812
applid File OPEN warning. BACKUPTYPE=DYNAMIC has been ignored for VSAM AIX data set. STATIC has been defaulted. File filename data set dsname.
Explanation:

The file filename is defined as eligible for backup while open for update (BACKUPTYPE=DYNAMIC). This file is opening against the data set dsname which is a VSAM AIX. BACKUPTYPE=DYNAMIC is not a valid option for a VSAM AIX. BACKUPTYPE=STATIC has been defaulted.

System action:

File open processing continues.

User response:

Redefine this file via CEDA, specifying BACKUPTYPE=STATIC.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, dsname

DFHFC5813
applid File OPEN warning. Level of {DFHSM | DFDSS | DFHSM and DFDSS} does not support BWO.
Explanation:

You have opened a VSAM file for update and requested backup while open (BWO) support by specifying BACKUPTYPE=DYNAMIC in the FCT. However, CICS has detected that the software release level of DFHSM and/or DFDSS required for BWO support has not been installed on the processor on which CICS is running.

This message is issued once for the first file to open for update and be defined as eligible for BWO after a cold or initial start.

System action:

CICS file open processing continues. If the file open completes without error, the file is defined as eligible for BWO. However, no BWO backup facilities are available using DFHSM and/or DFDSS on the processor on which CICS is running.

User response:

Ensure that DFHSM and/or DFDSS, both of version 2.5.0 or later, are installed on the processor on which the BWO backup is to be made.

Note:
DFSMS/MVS 1.1 (DFSMShsm and DFSMSdss) supersedes DFHSM 2.5 and DFDSS 2.5.
Destination:

Console

Modules:

DFHFCAT

XMEOUT Parameters: applid, {1=DFHSM, 2=DFDSS, 3=DFHSM and DFDSS}

DFHFC5814
applid An error (code X'code') has occurred while inquiring on VSAM data set attributes in the ICF catalog. {SHOWCAT | LOCATE} return code X'rrrr'. Data set dsname.
Explanation:

While reading the ICF catalog to obtain attributes of data set dsname, CICS received return code rrrr from a VSAM SHOWCAT or LOCATE macro or detected an associated error. The error code code is the exception trace which uniquely identifies the error. It can take the following values:

Value
Meaning
X'237A'
SHOWCAT for the data set failed with return code rrrr.
X'237B'
In the VSAM catalog entry for an AIX, either the data association or the base cluster association is missing.
X'237C'
SHOWCAT for the AIX of a path failed with return code rrrr.
X'237D'
The VSAM catalog entry for a path does not have a base cluster or an AIX as its first association.
X'237E'
LOCATE for the data set failed with return code rrrr.

For further information about CICS exception trace entries, see the CICS Diagnosis Reference.

System action:

CICS processing continues after making an exception trace entry and taking a system dump with dumpcode FC5814.

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

User response:

Use the SHOWCAT or LOCATE return code if present to determine the cause of the problem. For the meaning of the SHOWCAT return code, see OS/390 V2R10.0 DFSMS Macro Instructions for Data Sets. For the meaning of the LOCATE return code, see OS/390 V2R10.0 DFSMSdfp Advanced Services. A VSAM LISTCAT listing for the data set may also be useful.

If you cannot resolve the problem or the problem recurs, there may be a more severe error. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCAT

XMEOUT Parameters: applid, X'code',{1=SHOWCAT, 2=LOCATE}, X'rrrr', dsname

DFHFC5815
applid An error has occurred while inquiring on VSAM data set attributes in the ICF catalog. VSAM RLS codes X'rrrr', X'cccc'. Problem determination: X'dddddddd'. Data set dsname.
Explanation:

While reading the ICF catalog to obtain RLS attributes of data set dsname, CICS received reason code cccc from a VSAM IGWARLS macro. rrrr is the return code in register 15. ddddddd is any available VSAM problem determination information.

System action:

CICS processing continues after making an exception trace entry and taking a system dump with dumpcode FC5815.

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

User response:

Use the IGWARLS reason code and problem determination information to determine the cause of the problem. For the meaning of the IGWARLS reason code, see OS/390 V2R10.0 DFSMSdfp Advanced Services.

If you cannot resolve the problem or the problem recurs, there may be a more severe error. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHFCAT

XMEOUT Parameters: applid, X'rrrr',X'cccc', X'dddddddd', dsname

DFHFC5820
applid Any files that are still open against the base data set may need to be closed. File filename, data set dsname.
Explanation:

File filename was the first file to open a dynamically allocated data set dsname. This file is being closed leaving one or more files still open against the same base data set. However, if one of these files requires secondary extents, the request will fail with a CICS ILLOGIC error (EIBRCODE X'08BA0000').

System action:

Close processing completes normally.

User response:

To avoid this potential problem, you are advised to close and reopen the files that remain open against the base data set. If you are unsure of the data set associations, run a LISTCAT against the above base dataset to produce a list of all associated data sets. Use CEMT INQ FILE(*) to identify which files are affected. All of these should be closed and reopened, for example, using the CEMT SET FILE(file name) CLOSE and CEMT SET FILE(file name) OPEN.

Destination:

Console

Modules:

DFHFCFS

XMEOUT Parameters: applid, filename, dsname

DFHFC6000
date time applid About to {quiesce |unquiesce} data set dsname
Explanation:

This message is issued just before a request is made to VSAM RLS to quiesce or unquiesce base data set dsname throughout the sysplex. The quiesce or unquiesce is initiated either by an end user issuing EXEC CICS SET DSNAME QUIESCESTATE or the CEMT equivalent, or internally by CICS.

System action:

The data set is quiesced or unquiesced, as indicated in the message.

User response:

None.

Destination:

CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=quiesce, 2=unquiesce}, dsname

DFHFC6001
date time applid Data set successfully {quiesced | unquiesced} by {CICS |user}. Data set dsname
Explanation:

A request to VSAM RLS to quiesce or unquiesce base data set dsname throughout the sysplex has been successfully completed.

System action:

CICS processing continues. The quiesce state of the data set in the ICF catalog is set to quiesced or unquiesced, as indicated in the message.

User response:

None.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=quiesced, 2=unquiesced}, {1=CICS, 2=user}, dsname

DFHFC6003
date time applid Attempt by {CICS |user} to {quiesce | unquiesce} a data set has been rejected because {quiesce | unquiesce | non-BWO backup |BWO backup | unknown event} is in progress. Data set dsname
Explanation:

This message is issued after a request to VSAM RLS to quiesce or unquiesce base data set dsname throughout the sysplex was rejected because a conflicting data set operation is in progress for that data set. The conflicting operation is specified in the message.

System action:

CICS processing continues. The quiesce state of the data set in the ICF catalog remains unchanged.

User response:

Wait for the conflicting data set operation to complete then retry the quiesce or unquiesce using EXEC CICS SET DSNAME or the CEMT equivalent.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=CICS, 2=user},{1=quiesce, 2=unquiesce}, {1=quiesce, 2=unquiesce, 3=non-BWO backup, 4=BWO backup, 5=unknown event}, dsname

DFHFC6005
date time applid Attempt by {CICS |user} to quiesce a data set has failed. Quiesce was cancelled. Data set dsname
Explanation:

A request to VSAM RLS to quiesce base data set dsname throughout the sysplex has been cancelled by a participating CICS region. The CICS region could be any CICS in the sysplex. The quiesce was cancelled for one of the following reasons.

A preceding console message in the sysplex indicates the reason. For XFCVSDS the message is DFHFC6023. For XFCSREQ the message is DFHFC6024. For timeout the message is DFHFC6020. If there is no preceding message, EXEC CICS SET DSNAME UNQUIESCED has been used.

System action:

CICS processing continues. The quiesce state of the data set in the ICF catalog is set to unquiesced as a result of the cancel.

User response:

The response depends on the reason for the cancellation. If a preceding message was issued, refer to the explanation for that message for background information.

If EXEC CICS SET DSNAME UNQUIESCED was the reason, determine what the desired quiesce state should really be. If it should be quiesced, issue an EXEC CICS SET DSNAME QUIESCED command or the CEMT equivalent.

If an exit suppressed the quiesce, the user code at XFCVSDS or XFCSREQ must be disabled on all CICS regions in the sysplex before the data set can be quiesced.

If the quiesce timed out, retry the quiesce using EXEC CICS SET DSNAME QUIESCED or the CEMT equivalent. If the timeout occurs again, consider using EXEC CICS SET DSNAME IMMQUIESCED or the CEMT equivalent. This force-purges transactions accessing the data set, thereby speeding up the closing of files. Alternatively, attempt to identify any long-running transactions that are using the data set, and terminate them.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=CICS, 2=user},dsname

DFHFC6007
date time applid Attempt by {CICS |user} to {quiesce | unquiesce} a data set failed because the SMSVSAM server is not available. Data set dsname
Explanation:

A request to VSAM RLS to quiesce or unquiesce base data set dsname throughout the sysplex has failed because the SMSVSAM server address space is not available.

System action:

CICS processing continues. The SMSVSAM server address space should attempt to restart automatically.

The quiesce state of the data set in the ICF catalog is unpredictable.

User response:

The SMSVSAM server address space should normally restart itself. If it does not, restart the SMSVSAM server address space manually. Then issue an EXEC CICS SET DSNAME command or the CEMT equivalent to set the quiesce state in the ICF catalog to quiesced or unquiesced as desired.

If the SMSVSAM server address space fails to restart, there may be a more severe error. In this case, you need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=CICS, 2=user},{1=quiesce, 2=unquiesce}, dsname

DFHFC6008
date time applid Attempt by {CICS |user} to {quiesce | unquiesce} a data set has failed. VSAM RLS codes X'rrrr', X'cccc'. Data set dsname
Explanation:

This message is issued after a request to VSAM RLS to quiesce or unquiesce base data set dsname throughout the sysplex failed with an unexpected error. The VSAM IDAQUIES macro failed with reason code cccc. rrrr is the return code in register 15.

System action:

CICS processing continues after taking a system dump with dumpcode FC6008. The quiesce state of the data set in the ICF catalog is unpredictable.

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

User response:

Use the IDAQUIES reason code to determine the cause of the problem. For the meaning of the IDAQUIES reason code, see the OS/390 V2R10.0 DFSMSdfp Diagnosis Reference.

When the problem has been resolved, issue an EXEC CICS SET DSNAME command or CEMT equivalent to set the quiesce state in the ICF catalog to quiesced or unquiesced as desired.

If you cannot resolve the problem or the problem recurs, there may be a more severe error. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=CICS, 2=user},{1=quiesce, 2=unquiesce}, X'rrrr', X'cccc', dsname

DFHFC6009
date time applid Attempt by {CICS |user} to {quiesce | unquiesce} a data set has failed because a VSAM data set could not be located dsname
Explanation:

A request to VSAM RLS to quiesce or unquiesce base data set dsname throughout the sysplex failed because dsname could not be located.

System action:

CICS processing continues.

User response:

Investigate associated error messages to find the cause of the problem, then retry quiesce or unquiesce.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=CICS, 2=user},{1=quiesce, 2=unquiesce}, dsname

DFHFC6010
date time applid Attempt by {CICS |user} to {quiesce | unquiesce} a data set has failed because it has been migrated. Data set dsname
Explanation:

A request to VSAM RLS to quiesce or unquiesce base data set dsname throughout the sysplex failed because dsname has been migrated. The data set must be recalled before the quiesce or unquiesce can take place.

System action:

CICS processing continues.

User response:

Recall the data set and retry the quiesce or unquiesce.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=CICS, 2=user},{1=quiesce, 2=unquiesce}, dsname

DFHFC6015
date time applid About to cancel {non-BWO | BWO} backup of data set dsname
Explanation:

A request is about to be made to VSAM RLS to cancel a DFSMSdss-initiated backup for base data set dsname. This is performed in response to user code at global exit XFCVSDS suppressing the backup.

The message indicates whether the backup is BWO or non-BWO.

System action:

The backup is cancelled throughout the sysplex.

User response:

None.

Destination:

CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=non-BWO, 2=BWO}, dsname

DFHFC6016
date time applid {Non-BWO | BWO} backup of a data set cancelled by CICS. Data set dsname
Explanation:

A request to VSAM RLS to cancel a DFSMSdss-initiated backup for base data set dsname has been successful.

System action:

CICS continues processing. The BWO or non-BWO backup is cancelled throughout the sysplex.

User response:

None.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=Non-BWO, 2=BWO}, dsname

DFHFC6017
date time applid Attempt by CICS to cancel a {non-BWO | BWO} backup of a data set has been rejected because a cancel is already underway. Data set dsname
Explanation:

A request to VSAM RLS to cancel a DFSMSdss-initiated backup for base data set dsname has been rejected because another cancel is already underway.

System action:

CICS processing continues. The BWO or non-BWO backup is cancelled throughout the sysplex by the other cancel request.

User response:

None.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=non-BWO, 2=BWO}, dsname

DFHFC6018
date time applid Attempt by CICS to cancel a {non-BWO | BWO} backup of a data set failed because the SMSVSAM server is not available. Data set dsname
Explanation:

A request to VSAM RLS to cancel a DFSMSdss-initiated backup for base data set dsname failed because the SMSVSAM server address space was not available.

System action:

CICS processing continues. The SMSVSAM server address space should attempt to restart automatically.

The BWO or non-BWO backup request is not canceled. The backup may fail or succeed depending on whether the SMSVSAM server concerned is coordinating the backup or not.

User response:

The SMSVSAM server address space should normally restart itself. If it does not, restart the SMSVSAM server address space manually. Then use DFSMSdss to retry the backup if it failed.

If the SMSVSAM server address space fails to restart, a more severe error is indicated. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=non-BWO, 2=BWO}, dsname

DFHFC6019
date time applid Attempt by CICS to cancel a {non-BWO | BWO} backup of a data set has failed. VSAM RLS codes X'rrrr', X'cccc'. Data set dsname
Explanation:

A request to VSAM RLS to cancel a DFSMSdss-initiated backup for base data set dsname has failed with an unexpected error. The VSAM IDAQUIES macro failed with reason code cccc. rrrr is the return code in register 15.

System action:

CICS processing continues after taking a system dump with dumpcode FC6019. The BWO or non-BWO backup is not cancelled.

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

User response:

Use the IDAQUIES reason code to determine the cause of the problem. For the meaning of the IDAQUIES reason code, see the OS/390 V2R10.0 DFSMSdfp Diagnosis Reference.

If you cannot resolve the problem, or the problem recurs, a more severe error is indicated. In this case, you will assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=non-BWO, 2=BWO}, X'rrrr', X'cccc', dsname

DFHFC6020
date time applid Timeout has occurred while quiescing a data set. Quiesce will be cancelled. Data set dsname
Explanation:

The request made to VSAM RLS to quiesce base data set dsname throughout the sysplex has timed out. The timeout limit is given by the system initialization parameter QUIESTIM.

This is probably due to the presence of long-running transactions on a participating CICS region failing to reach syncpoint, and therefore preventing the close of files open against the data set.

System action:

CICS cancels the quiesce throughout the sysplex by issuing an unquiesce for the data set. Depending upon the timing of the unquiesce request, one of two situations can result:

  1. Normally the unquiesce is processed immediately and the quiesce request is canceled by VSAM. In this case, message DFHFC6020 is followed by messages DFHFC6000 and DFHFC6001 for the unquiesce completing.
  2. Occasionally, depending on the timing of the unquiesce, the original quiesce request completes before the unquiesce request has been processed. Because the unquiesce cannot be canceled, it completes thereby canceling the original quiesce. In this case, message DFHFC6020 is followed by messages DFHFC6000, DFHFC6027, a DFHFC6001 for the quiesce completing, and another DFHFC6001 for the unquiesce completing.
User response:

If timeouts occur regularly, the following action can be taken to resolve the problem

The SET DSNAME IMMQUIESCED command can be used to force purge any transaction and quiesce the data set. This should not be used regularly because force purges can occasionally abend CICS. The messages issued as part of the force purge enable the system programmer to identify the long-running transaction if no other method is available.

See also the Explanation of message DFHFC6005 for guidance.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, dsname

DFHFC6021
date time applid An error has occurred while notifying VSAM RLS of the completion of CICS processing for a data set quiesce or backup. VSAM RLS codes X'rrrr', X'cccc'. Data set dsname
Explanation:

An unexpected error occurred when CICS notified VSAM RLS that it had completed its processing for a data set quiesce, or for a BWO or non-BWO backup. The VSAM IDAQUIES macro failed with reason code cccc. rrrr is the return code in register 15.

System action:

CICS processing continues after taking a system dump is taken with dumpcode FC6021. The failure of the IDAQUIES macro may cause the data set operation to timeout or fail.

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

User response:

Use the IDAQUIES reason code to determine the cause of the problem. For the meaning of the IDAQUIES reason code, see the OS/390 V2R10.0 DFSMSdfp Diagnosis Reference.

If the data set operation has failed, retry the data set operation once the problem has been resolved,

If you cannot resolve the problem, or the problem reoccurs, a more severe error is indicated. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQI

XMEOUT Parameters: date, time,applid, X'rrrr', X'cccc', dsname

DFHFC6022
STORAGE OBTAIN macro failure in CICS RLS quiesce exit. MVS code X'rrrr'
Explanation:

The CICS RLS quiesce exit was driven by VSAM RLS to process a data set operation request. An attempt was made to get storage for the request but the STORAGE OBTAIN macro failed. rrrr is the return code in register 15.

System action:

The CICS RLS quiesce exit writes a GTF trace entry. The request is not processed by CICS. The data set operation continues throughout the sysplex.

User response:

Use the return code to determine the cause of the problem, then refer to the Explanation of message DFHFC6030 for guidance. For the meaning of the return code, refer to the OS/390 MVS System Codes manual.

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

Console

Modules:

DFHFCQX

DFHFC6023
date time applid The quiesce of a data set has been suppressed by user exit XFCVSDS. Quiesce will be cancelled. Data set dsname
Explanation:

User code at global exit XFCVSDS has suppressed a quiesce for base data set dsname.

System action:

CICS cancels the quiesce throughout the sysplex by issuing an unquiesce for the data set.

User response:

See the Explanation of message DFHFC6005 for guidance.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQU

XMEOUT Parameters: date, time,applid, dsname

DFHFC6024
date time applid The quiesce of a data set has been suppressed by user exit XFCSREQ. Quiesce will be cancelled. Data set dsname
Explanation:

User code at global exit XFCSREQ has suppressed the close of a file open against base data set dsname. The file was being closed because the data set was being quiesced.

System action:

CICS cancels the quiesce throughout the sysplex by issuing an unquiesce for the data set.

User response:

See the Explanation of message DFHFC6005 for guidance.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCFS

XMEOUT Parameters: date, time,applid, dsname

DFHFC6025
date time applid {Non-BWO | BWO} backup of a data set has been suppressed by user exit XFCVSDS. Backup will be cancelled. Data set dsname
Explanation:

User code at global exit XFCVSDS has suppressed a DFSMSdss-initiated backup for base data set dsname.

System action:

CICS cancels the backup throughout the sysplex.

User response:

If the backup must take place, before it can succeed the user code at XFCVSDS must be disabled on all CICS regions in the sysplex.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQU

XMEOUT Parameters: date, time,applid, {1=Non-BWO, 2=BWO}, dsname

DFHFC6026
date time applid An error has occurred while notifying VSAM RLS of the completion of CICS processing for a data set quiesce or backup. The SMSVSAM server is not available. Data set dsname
Explanation:

CICS has notified VSAM RLS that it has completed its processing for a data set quiesce, or a BWO or non-BWO backup, but the SMSVSAM server address space is not available.

System action:

CICS processing continues. The SMSVSAM server address space should attempt to restart automatically.

The data set operation may fail or succeed, depending on whether the SMSVSAM server concerned was coordinating the operation or not.

User response:

The SMSVSAM server address space should normally restart itself. If it does not, restart the SMSVSAM server address space manually. Retry the data set operation if it has failed.

If the SMSVSAM server address space fails to restart, a more severe error is indicated. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQI

XMEOUT Parameters: date, time,applid, dsname

DFHFC6027
date time applid VSAM RLS has been notified of the completion of CICS processing for a quiesce or backup of data set dsname
Explanation:

CICS has successfully notified VSAM RLS that it has completed its processing for a data set quiesce, or a BWO or non-BWO backup.

System action:

CICS processing continues. The data set operation continues throughout the sysplex, until all CICS systems involved have successfully notified VSAM RLS of the completion of their processing.

User response:

None.

Destination:

CSFL

Modules:

DFHFCQI

XMEOUT Parameters: date, time,applid, dsname

DFHFC6028
date time applid File Control RLS quiesce system transaction transid has started.
Explanation:

CICS system transaction CFQS or CFQR has started successfully.

CFQS and CFQR provide support for VSAM RLS data set quiesce and unquiesce operations, DFSMSdss-initiated BWO and non-BWO backups, and certain other data set related operations.

System action:

CICS processing continues.

User response:

None.

Destination:

CSFL

Modules:

DFHFCQT

XMEOUT Parameters: date, time,applid, transid

DFHFC6029
date time applid File Control RLS quiesce system transaction transid has failed. Reattach will be attempted.
Explanation:

CICS system transaction CFQS or CFQR has failed due to a serious error. An attempt will be made to reattach the transaction transid.

A preceding message should indicate the cause of the error.

CFQS and CFQR provide support for VSAM RLS data set quiesce and unquiesce operations, DFSMSdss-initiated BWO and non-BWO backups, and certain other data set related operations.

System action:

The transaction is reattached and CICS processing continues.

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

User response:

Check Transient Data Queue CSFL for message DFHFC6028, indicating that the reattach of the transaction was successful. If the reattach fails, VSAM RLS data set quiesce support is lost. If this happens, CICS must be restarted.

If it is not possible to restore VSAM RLS quiesce support, a more severe error is indicated. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQT

XMEOUT Parameters: date, time,applid, transid

DFHFC6030
date time applid The CICS RLS quiesce exit was unable to process data set operation request X'type' for {data set | cache} name
Explanation:

The CICS RLS quiesce exit was driven by VSAM RLS to process data set operation request type for data set or cache name, but encountered a severe error and was unable to process the request. The error is normally caused by a STORAGE OBTAIN macro failure

A preceding console message (normally DFHFC6022) gives more information about the error.

This message is issued by DFHFCQR on behalf of the CICS RLS quiesce exit DFHFCQX.

Note:
The CICS RLS quiesce exit is used by VSAM RLS to notify CICS that processing is required for the following data set related operations. The number corresponds to type in the message.
01
The quiesce of a data set
02
The unquiesce of a data set
03
The start of a DFSMSdss non-BWO backup
04
The end of a DFSMSdss non-BWO backup
05
The start of a DFSMSdss BWO backup
06
The end of a DFSMSdss BWO backup
07
The recovery of lost locks for a data set
08
The completion of forward recovery for a data set
09
The recovery of a coupling facility cache structure.
System action:

CICS continues after taking a system dump with dumpcode FC6030. The data set operation request is not processed by CICS.

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

User response:

Referring to the preceding console message, attempt to determine the cause of the problem.

Because CICS could not process the request, this might invalidate later processing. For example, if the request was for the quiesce of a data set, open files against the data set must be closed manually, or the quiesce retried using EXEC CICS SET DSNAME QUIESCED or the CEMT equivalent. If the request was in connection with a BWO or non-BWO backup, the backup may be invalid and should be discarded.

If you cannot resolve the problem, or the problem recurs, a more severe error is indicated. In this case, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQR

XMEOUT Parameters: date, time,applid, X'type', {1=data set,2=cache}, name

DFHFC6031
date time applid Attempt by {CICS |user} to process data set operation request {quiesce | unquiesce} failed because the SMSVSAM server detected an internal error. Data set dsname
Explanation:

An attempt by a user to issue a quiesce function for the base data set dsname failed because the SMSVSAM server detected an internal error.

System action:

CICS continues processing. The request is canceled throughout the sysplex.

User response:

None.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=CICS, 2=user},{1=quiesce, 2=unquiesce}, dsname

DFHFC6032
date time applid Attempt by CICS to cancel {non-BWO | BWO} backup request failed because the SMSVSAM server detected an internal error. Data set dsname
Explanation:

An attempt by CICS to cancel a backup request for the base data set dsname failed because the SMSVSAM server detected an internal error.

System action:

CICS continues processing. See the message from DFSMSdss and the SMSVSAM server to identify the state of the backup request.

User response:

None.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=non-BWO, 2=BWO}, dsname

DFHFC6033
date time applid Attempt by CICS to notify VSAM RLS of the completion of CICS processing for a data set quiesce or backup of a data set failed because the SMSVSAM server detected an internal error. Data set dsname
Explanation:

An attempt by CICS to notify VSAM RLS of the completion of CICS processing for a data set quiesce or backup for the base data set dsname failed because the SMSVSAM server detected an internal error.

System action:

CICS continues processing. See the message from DFSMSdss and the SMSVSAM server to identify the state of the backup request.

User response:

None.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQI

XMEOUT Parameters: date, time,applid, dsname

DFHFC6034
date time applid Attempt by {CICS |user} to process data set operation request {quiesce | unquiesce} failed because the user is not authorized to access the sphere. Data set dsname
Explanation:

An attempt by a user to issue a quiesce function for the base data set dsname failed because the user is not authorized to access the sphere.

System action:

CICS continues processing. The request is canceled throughout the sysplex.

User response:

None.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=CICS, 2=user},{1=quiesce, 2=unquiesce}, dsname

DFHFC6035
date time applid Attempt by CICS to cancel {non-BWO | BWO} backup request failed because the user is not authorized to access the sphere. Data set dsname
Explanation:

Attempt by CICS to cancel a backup request for the base data set dsname failed because the user is not authorized to access the sphere.

System action:

CICS continues processing. See the message from DFSMSdss and the SMSVSAM server to identify the state of the backup request.

User response:

None.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQS

XMEOUT Parameters: date, time,applid, {1=non-BWO, 2=BWO}, dsname

DFHFC6036
date time applid Attempt by CICS to notify VSAM RLS of the completion of CICS processing for a data set quiesce or backup of a data set failed because the user is not authorized to access the sphere. Data set dsname
Explanation:

An attempt by CICS to notify VSAM RLS of the completion of CICS processing for a data set quiesce or backup for the base data set dsname failed because the user is not authorized to access the sphere.

System action:

CICS continues processing. See the message from DFSMSdss and the SMSVSAM server to identify the state of the backup request.

User response:

None.

Destination:

Console and Transient Data Queue CSFL

Modules:

DFHFCQI

XMEOUT Parameters: date, time,applid, dsname

Start of changeDFHFC7000End of change
Start of changeapplid The maximum records parameter(rrrr) specified on OPEN of coupling facility data table dddd, poolname pppp, for file filename, differs from the current maximum records parameter(ssss) for the table.End of change
Start of change
Explanation:

During OPEN of coupling facility data table dddd for file filename it has been found that the maximum records parameter rrrr specified in the file definition is different from that already specified for the table on a previous OPEN or server SET command.

End of change
Start of change
System action:

The open continues. This is a warning message. The maximum records parameter ssss already set is the one that applies. The different maximum records parameter is ignored.

End of change
Start of change
User response:

Ensure that the maximum records parameter that is in use is as expected. If not, delete the table and reopen it after correcting the maximum records parameter in the file definition. Alternatively, reopen the table via another file definition that already has the correct maximum records parameter or use the coupling facility data table server SET command to change the maximum records parameter for the table.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changerrrr,End of changeStart of changedddd, End of changeStart of changepppp, End of changeStart of changefilename, End of changeStart of changessssEnd of change

Start of changeDFHFC7002End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because access is not allowed.End of change
Start of change
Explanation:

The OPEN of coupling facility data table dddd for file filename, pool poolname has failed because access is not allowed. The security check for the table has failed.

A RACF message containing a return code indicating the reason for failure will have been issued prior to this message.

End of change
Start of change
System action:

The table cannot be opened.

End of change
Start of change
User response:

Set the correct table access using RACF.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7003End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because the table is not currently available for access.End of change
Start of change
Explanation:

The OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because the table is currently not available for access. The table has been set unavailable by an earlier server command. This prevents the opening of new files against this table.

End of change
Start of change
System action:

The table cannot be opened. CICS continues processing with the table closed and its state unenabled. Any transactions attempting to use the table will get a NOTOPEN condition.

End of change
Start of change
User response:

Ensure that the server command to set the table available is issued before attempting to open the file. The format of this command is MODIFY server-name,SET TABLE=name,AVAILABLE=YES|NO

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7004End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because the table is not yet loaded.End of change
Start of change
Explanation:

The OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because the table requires loading and is not already being loaded. The user has tried to open it for shared access. A shared access open will only succeed if the table is already being loaded or has completed loading.

End of change
Start of change
System action:

The table cannot be opened.

End of change
Start of change
User response:

Investigate why the table has not already been loaded or started loading. Change the file definition to make this OPEN do the load if that is appropriate.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7005End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because of a shared access conflict.End of change
Start of change
Explanation:

The OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because of a shared access conflict. CICS either requests an EXCLUSIVE open (for the purposes of loading) or a SHARED open (for all other cases).

For a shared open request, this error means that the open mode which CICS has specified for this data table conflicts with the shared access mode which has been specified by an existing exclusive open for the data table. For an exclusive open request, this means that the shared access mode which CICS has specified on the open conflicts with one or more existing shared opens for the data table. CICS should not normally specify conflicting open or shared access modes.

End of change
Start of change
System action:

The file cannot be opened.

End of change
Start of change
User response:

Investigate the access modes of other opens against the data table dddd in pool poolname, using a server query, to determine whether there is an error.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7006End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because of an exclusive access conflict.End of change
Start of change
Explanation:

The OPEN of coupling facility data table dddd for file filename, pool poolname has failed because of an exclusive access conflict. Exclusive access to the data table is not available. This error can occur when CICS has requested an exclusive open in order to load the data table from a source data set, if another open already has exclusive access. The error can also occur on a request to delete a data table if there are any opens against the data table. CICS should not normally specify access modes which could result in an exclusive access conflict.

End of change
Start of change
System action:

The table cannot be opened.

End of change
Start of change
User response:

Investigate any other opens against the data table dddd in pool poolname, for example using a server query, to determine whether it is expected that access is denied.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7007End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because one or more attributes on the file definition are incompatible with those that were set for the table when it was created.End of change
Start of change
Explanation:

An OPEN request naming an existing table specifies one or more attributes for the table which are not compatible with those for the existing table. The coupling facility data table server has rejected the open.

The attributes that may be incorrect are:

This can also occur if the coupling facility data table server that is attempting to open the table is at a lower release level than the server which created the table, as the newer server may have set internal attributes when it created the table which are not supported by the older server.

End of change
Start of change
System action:

CICS fails the open.

End of change
Start of change
User response:

Use the coupling facility data table server DISPLAY command to view the attributes for the table and then determine whether :

Note that this problem could occur if there has been unintentional use of the same table name in different file definitions.

When the problem has been corrected, retry the open.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7010End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because recovery is not enabled.End of change
Start of change
Explanation:

An attempt was made to open a recoverable table dddd for read/write access, but the client region has not yet issued a restart request to enable recovery support for this pool connection.

End of change
Start of change
System action:

The open fails.

End of change
Start of change
User response:

Investigate why there has been no restart request by checking for CICS error messages.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7012End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because there is no space in the pool.End of change
Start of change
Explanation:

The coupling facility list structure for the table pool has no more space available.

End of change
Start of change
System action:

The open fails.

End of change
Start of change
User response:

Investigate whether space can be freed in the coupling facility list structure by deleting tables, or records in tables, that are no longer required.

Alternatively, use the DISPLAY POOLSTATS command to find if the structure is currently at its maximum size; and if not, increase the size using the SETXCF ALTER command.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7013End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because the maximum number of tables has been reached.End of change
Start of change
Explanation:

A new table cannot be created because the maximum number of tables specified when the first server was started for the structure has been reached.

End of change
Start of change
System action:

The open fails.

End of change
Start of change
User response:

Investigate whether the number can be increased or whether there are any tables no longer required that could be deleted.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7014End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because there are too many users.End of change
Start of change
Explanation:

The number of concurrent opens for table dddd has reached the maximum supported limit which is currently 1024. This means that there are already 1024 files open which all reference the same coupling facility data table in the same coupling facility data table pool.

End of change
Start of change
System action:

The open fails.

End of change
Start of change
User response:

Investigate reducing the number of concurrent users; that is, the number of files open against this coupling facility data table.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7015End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because the table has been destroyed.End of change
Start of change
Explanation:

Table dddd in pool poolname is no longer valid. The most likely cause is that a delete request overlapped with the current request.

End of change
Start of change
System action:

The open fails.

End of change
Start of change
User response:

Investigate whether the table was deleted. This is not an error if the table is no longer required. If the table is still required, it should be recreated by opening it again.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7018End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because the table requires loading.End of change
Start of change
Explanation:

The OPEN of file filename has failed because it requires the associated coupling facility data table dddd, which resides in coupling facility data table pool poolname, to have been pre-loaded, but the table has not yet been loaded. Automatic loading of the data table could not be initiated because there is no source data set specified for this file, either in the file definition or in the CICS startup JCL.

End of change
Start of change
System action:

The file cannot be opened.

End of change
Start of change
User response:

There are a number of possible operational errors which might have resulted in this failure:

  1. The application does not require the coupling facility data table dddd to be pre-loaded. The 'load required' parameter should be removed from the file definition for file filename.
  2. The application does require the coupling facility data table dddd to be pre-loaded, but it should already have been loaded before file filename was opened.

    If this is the case, then there should be at least one file definition within the sysplex that names data table dddd in pool poolname and which specifies a source data set, or for which the source data set is supplied in the CICS startup JCL. You should issue an open for one of the files which specifies the source data set, after which an open of this file should succeed.

    You may also want to put operational procedures in place which will ensure that in future this file is only opened after the data table has been loaded. Use of the data tables load complete global user exit point, XDTLC, might be one way of achieving this.

  3. The application does require the coupling facility data table dddd to be pre-loaded, and it is intended that the load should be automatically initiated by opening file filename (unless the table has already been loaded).

    A source data set name should have been specified, either in the file definition for file filename or in the CICS startup JCL as a DD card for file filename, depending on whether dynamic allocation or preallocation is required respectively.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7019End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because the table requires loading but the supplied data set is not KSDS.End of change
Start of change
Explanation:

The OPEN of file filename has failed because it requires the associated coupling facility data table dddd, which resides in coupling facility data table pool poolname, to have been pre-loaded, but the table has not yet been loaded. Automatic loading of the data table could not be initiated because the source data set specified for this file, either in the file definition or in the CICS startup JCL, is not a KSDS. Coupling facility data tables can only be loaded from VSAM KSDS data sets.

End of change
Start of change
System action:

The file cannot be opened.

End of change
Start of change
User response:

Investigate whether the reason for this error is that the file should not have been defined as requiring loading, or that the data set name specified is incorrect, or that no data set name should have been specified (because the data table should be pre-loaded via some other file definition before this file is opened). Correct the file definition, re-install and retry the open.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7032End of change
Start of changeapplid CLOSE of coupling facility data table dddd for file filename, pool poolname, has failed because the table has been destroyed.End of change
Start of change
Explanation:

The table is no longer valid in the pool. The most likely reason is that a delete request overlapped with the current request.

End of change
Start of change
System action:

The close fails.

End of change
Start of change
User response:

Investigate whether the table was deleted. This is not an error if the table is no longer required. If the table is still required, it should be recreated by opening it again.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7051End of change
Start of changeapplid A request to inquire on which attributes of coupling facility data table dddd, file filename, pool poolname, are incompatible has failed because the table could not be found.End of change
Start of change
Explanation:

Inquire for coupling facility data table dddd has failed because during the request it was found that the table could not be found. CICS File Control issued the inquire as the result of an open failure due to incompatible table attributes. The inquire was intended to provide which attributes were in error so that they could be given as part of the open failure diagnostics.

End of change
Start of change
System action:

The table open has failed due to incompatible attributes and the processing to provide more information on which attributes are incorrect has detected that the table can now not be found.

End of change
Start of change
User response:

Investigate why the table cannot be found.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

DFHFC7071
applid The request to set shared access for coupling facility data table dddd, file filename, pool poolname, at the end of a successful table load, has failed because access is not allowed.
Explanation:

At the end of a coupling facility data table load, the source data set is closed and CICS File Control requests the server to change the table access from the exclusive access that was required for loading, to a shared access. The server has indicated that the table is not available for access. The security check for the table has failed.

Start of changeA RACF message containing a return code indicating the reason for failure will have been issued prior to this message.End of change

System action:

Although the table successfully opened and loaded, the load is not considered complete because the request to the server to set the access to 'shared' has not occurred. The table is closed again ready for the next open attempt which will reattempt the load. The close will still get the security error, but the CICS side of close will complete.

User response:

Investigate why the table is not available for access. Set the required table access, if possible, using RACF.

Destination:

Console

Modules:

DFHFCDO

XMEOUT Parameters: applid, dddd,filename, poolname

Start of changeDFHFC7072End of change
Start of changeapplid The request to set shared access for coupling facility data table dddd, file filename, pool poolname, at the end of a successful table load, has failed because the table cannot be found.End of change
Start of change
Explanation:

At the end of a coupling facility data table load the source data set is closed, and CICS File Control requests the server to change the table access from the exclusive access that was required for loading to shared access. The server has returned that the table cannot be found.

End of change
Start of change
System action:

Although the table was successfully opened and loaded, the load is not considered complete because the request to the server to set the access to shared has not occurred. The table is closed again ready for the next open attempt which will retry the load. The close will still get the error, but the CICS side of close will complete.

End of change
Start of change
User response:

Investigate why the table cannot be found. If it is still required open it again so that it will be recreated and reloaded.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7073End of change
Start of changeapplid The request to set shared access for coupling facility data table dddd, file filename, pool poolname, at the end of a successful table load, has failed because of a shared access conflict.End of change
Start of change
Explanation:

At the end of a coupling facility data table load the source data set is closed, and CICS File Control requests the server to change the table access from the exclusive access that was required for loading to shared access. The server has returned that it cannot process the request because of a shared access conflict.

End of change
Start of change
System action:

Although the table successfully opened and loaded, the load is not considered complete because the request to the server to set the access to shared has not occurred. The table is closed again ready for the next open attempt which will retry the load. The close will still get the error, but the CICS side of close will complete.

End of change
Start of change
User response:

Investigate the access mode of other table, and what other files are open against it, to determine if there is an error. The coupling facility data table server supports commands, such as DISPLAY TABLE, which will provide you with this information.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7079End of change
Start of changeapplid The request to set shared access for coupling facility data table dddd, file filename, pool poolname, at the end of a successful table load, has failed because the table has been destroyed.End of change
Start of change
Explanation:

At the end of a coupling facility data table load the source data set is closed, and CICS File Control requests the server to change the table access from the exclusive access that was required for loading to shared access. The server has returned that the request has failed because the table has been destroyed.

End of change
Start of change
System action:

All requests to use the table will return the same error.

End of change
Start of change
User response:

Investigate why the table has been destroyed. If it is still required open it again so that it will be recreated and reloaded.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7081End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because the key length or record length parameter on the file definition is inconsistent with the equivalent for the source data set.End of change
Start of change
Explanation:

The OPEN of coupling facility data table dddd has failed because before the call to the server to perform the actual open, CICS has found that the record length and/or keylength specified by the user on the file definition does not match that returned by VSAM when the associated source data set was opened.

End of change
Start of change
System action:

The table cannot be opened.

End of change
Start of change
User response:

Check whether the file definition is in error or whether the wrong data set has been specified. It is not necessary to specify the parameters on the file definition if there is a source data set. Clear the parameters or make them the same as the source.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7082End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because the key length or record length parameter for the source data set is inconsistent with the value already set for the table.End of change
Start of change
Explanation:

The OPEN of coupling facility data table dddd has failed because the values for record length and/or key length returned for the table on the open do not match those for the source data set specified in the file definition.

End of change
Start of change
System action:

The table cannot be opened.

End of change
Start of change
User response:

Check whether the wrong data set has been specified in the file definition. If the table is opened and loaded by another user, it is not necessary for this user to specify a source data set in the definition.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7083End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because the key length or record length parameter specified on the file definition is inconsistent with that already set for the table.End of change
Start of change
Explanation:

The OPEN of coupling facility data table dddd has failed because the values for record length and/or key length returned for the table on the open do not match those specified in the file definition for the table.

End of change
Start of change
System action:

The table is closed again.

End of change
Start of change
User response:

Check whether the wrong data set has been specified in the file definition. If the table is opened and loaded by another user, it is not necessary for this user to specify record length and key length on the file definition. Attention is drawn to the mismatch rather than ignoring it in case there is an error.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7084End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because the table cannot be found.End of change
Start of change
Explanation:

When a coupling facility data table server fails, all the files which were accessing tables in that pool are marked as requiring a re-open after connection to a new server instance. This is required so that a valid table token is obtained for the new instance. The re-open for coupling facility data table dddd for file filename, pool poolname, has failed because the table has gone away (possibly due to a failure of the coupling facility) since it was last opened for this file.

End of change
Start of change
System action:

The table cannot be opened. CICS closes and enables the file so that a full open can be tried later. The full open will recreate the table (unless the file definition specifies that the table must already have been recreated, in which case another file definition which specifies it is capable of recreating and loading the table must be opened first).

End of change
Start of change
User response:

Retry when the table is available.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7085End of change
Start of changeapplid On a request to process {OPEN |CLOSE | EXTRACT STATISTICS} for coupling facility data table dddd for file filename, it has been found that the server for coupling facility data table pool poolname, is down. The server should be restarted.End of change
Start of change
Explanation:

CICS has issued a request to a file which is defined to use a coupling facility data table which resides in the pool poolname. CICS did not currently have a connection established to the pool, so an attempt to connect to the pool has to be made. Before the connect, a query is issued to check whether the server for the pool is available. The query has failed because the server is currently down.

A coupling facility data table server is a separate address space which handles all requests made to coupling facility data tables that reside in the pool which it serves.

End of change
Start of change
System action:

If the request is an open, CICS fails the request to the coupling facility data table.

If the request is a close, CICS can complete close processing as normal.

If the request is to extract statistics, issued while gathering file control statistics, the request to obtain the statistics will fail. If the request is to extract statistics, issued as part of INQUIRE FILE processing in order to return the current MAXNUMRECS limit, then the INQUIRE FILE request can complete as normal, but the MAXNUMRECS value returned may differ from the current actual value.

New requests to coupling facility data tables which reside in this pool will check whether the server is available, and will attempt another connect if it is.

End of change
Start of change
User response:

Determine the reason for the failure. Diagnostic messages issued by the coupling facility data table server address space should assist you in doing this. The most likely cause of this error is a problem with the coupling facility. The coupling facility data table server does not automatically restart itself, so after you have corrected the cause of the error, you should resubmit the job which starts the server.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of change{1=OPEN, End of changeStart of change2=CLOSE, End of changeStart of change3=EXTRACT STATISTICS},End of changeStart of changedddd, End of changeStart of changefilename, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7086End of change
Start of changeapplid OPEN of coupling facility data table dddd for file filename, pool poolname, has failed because the {keylength | recordsize} of the source data set is greater than the supported maximum.End of change
Start of change
Explanation:

The OPEN of file filename, associated with coupling facility data table dddd in coupling facility data table pool poolname, has failed because the key length and/or record size of the source data set specified for the file is greater than the value supported.

For a coupling facility data table, the key length must be less than or equal to 16 bytes, and the record size must be less than or equal to 32767 bytes.

The message indicates whether it was the key length or the record size which was found to be too large.

End of change
Start of change
System action:

The file is left closed.

End of change
Start of change
User response:

Check whether the wrong data set has been specified for this file (either in the file definition or in the CICS start-up JCL), and whether this data table really requires pre-loading from a source data set.

If the correct data set was specified, then this file may not be suitable for use as a coupling facility data table. If this was because the key length was beyond the range supported for coupling facility data tables, then consider redefining the file as a user-maintained data table or as an RLS file.

If the data table does not need to be pre-loaded, then specify LOAD(NO) on the file definition, and a key length and record size which are in the supported ranges.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedddd,End of changeStart of changefilename, End of changeStart of changepoolname, End of changeStart of change{1=keylength,End of change Start of change2=recordsize}End of change

Start of changeDFHFC7090End of change
Start of changedate time applid CICS coupling facility data table load has started for data table dddd, file filename, pool poolname.End of change
Start of change
Explanation:

CICS file control has detected that an open request has been issued for coupling facility data table data table dddd, and a task has been attached to load the data table.

End of change
Start of change
System action:

CICS processing continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CSFL

End of change
Modules:

Start of changeStart of changeDFHFCDLEnd of changeEnd of change

Start of changeStart of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedddd, End of changeStart of changefilename, End of changeStart of changepoolnameEnd of changeEnd of change

Start of changeDFHFC7091End of change
Start of changedate time applid CICS coupling facility data table load has successfully processed all records in the source data set for table dddd, file filename, pool pool.End of change
Start of change
Explanation:

The task which was attached to load coupling facility data table dddd has successfully processed all of the records in the associated source data set. The load, however, is not complete until user exit XDTLC has been called, and the table has been marked as loaded, with its access changed from EXCLUSIVE to SHARED.

End of change
Start of change
System action:

The user exit XDTLC is invoked, if enabled, with the parameter UEPDTORC set to indicate a successful load. The coupling facility data table server is called to mark the table as loaded and to set the access to shared. Another message (DFHFC7095) will be issued indicating that these have completed and that the load is complete. CICS processing continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CSFL

End of change
Modules:

Start of changeStart of changeDFHFCDLEnd of changeEnd of change

Start of changeStart of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedddd, End of changeStart of changefilename, End of changeStart of changepoolEnd of changeEnd of change

Start of changeDFHFC7092End of change
Start of changedate time applid CICS data table load has terminated abnormally for coupling facility data table dddd, file filename, pool poolname, because the table has been closed.End of change
Start of change
Explanation:

The CICS task that is loading coupling facility data table dddd has found that CICS file control has requested that the load be abandoned because the file has been closed.

End of change
Start of change
System action:

The load transaction terminates. CICS processing continues. Any records already loaded will remain in the table. The next open will start the load transaction again which will continue the load.

End of change
Start of change
User response:

Investigate why the file has been closed.

End of change
Start of change
Destination:

Console and Transient Data Queue CSFL

End of change
Modules:

Start of changeStart of changeDFHFCDLEnd of changeEnd of change

Start of changeStart of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedddd, End of changeStart of changefilename, End of changeStart of changepoolnameEnd of changeEnd of change

Start of changeDFHFC7093End of change
Start of changedate time applid CICS data table load has terminated abnormally for coupling facility data table dddd, file filename, pool poolname, reason code = X'xx'.End of change
Start of change
Explanation:

The CICS task that is loading coupling facility data table dddd has received a reason code X'xx', where X'xx' has one of the following values:

X'02'
ILLOGIC - A VSAM error which does not fall into one of the other categories.
X'0C'
NOTOPEN - The file is CLOSED and UNENABLED, or still open and in use, but a CLOSE request has been received.
X'0D'
DISABLED - The file is DISABLED.
X'0F'
ENDFILE - The file is CLOSED and UNENABLED, or still open and in use, but a CLOSE request has been received.
X'80'
IOERR - I/O error.
X'84'
TABLE_FULL - Maximum records exceeded.
X'85'
RLS_DISABLED - RLS access currently not available.
X'86'
RLS_FAILURE - The RLS server has failed.
X'87'
PREVIOUS_RLS_FAILURE - The RLS server has been recycled in this unit of work.
X'88'
CACHE_FAILURE - Cache connectivity failure.
X'89'
CFDT_POOL_FULL - No more space available in the coupling facility structure for the table pool.
X'8A'
DATASET_BEING_COPIED - DSS is performing a sharp copy
End of change
Start of change
System action:

The user exit XDTLC is invoked, if enabled, with the parameter UEPDTORC set to indicate that loading completed abnormally. The user exit may ask for the file to be closed. No more records are loaded into the coupling facility data table.

If the user exit did not request the file to be closed (or if no user exit program was enabled at the XDTLC exit point), then API requests to access records within the range of keys which has already been loaded into the data table will succeed, but requests to access any record beyond the loaded range will receive the "LOADING" condition.

If the file has been closed, then API requests will receive a "NOTOPEN" condition.

CICS processing continues.

End of change
Start of change
User response:

Investigate the reason for the return code from CICS file control. For further information about the reason code, see the description of exception conditions for the STARTBR, READNEXT and WRITE commands in the CICS Application Programming Reference.

You may be able to correct the cause of the failure, for example by explicitly enabling the file if the reason is DISABLED, or re-cycling the RLS server if it has failed. If the error is TABLE_FULL, meaning that the number of records to be loaded into the table exceeds the MAXNUMRECS parameter, then you can increase this parameter using the coupling facility data tables server command SET TABLE=tablename,MAXRECS=n. (Note that although altering the MAXNUMRECS parameter on the file definition within CICS, using SET FILE for example, will not have any effect on the current setting for the data table, you should consider resetting it to the new value in order to avoid getting a warning message about the mismatch.) If the error is CFDT_POOL_FULL, then you can increase the size of the coupling facility data table pool that this data table resides in.

If it is possible to correct the problem which caused the load to fail, then you can complete the load of the coupling facility data table by closing the file which attempted the load (if it has not already been closed) and re-opening it, or any other file which is capable of loading the table; that is, which has access to the source data set. This will cause the load to be restarted from the point at which it failed.

End of change
Start of change
Destination:

Console and Transient Data Queue CSFL

End of change
Modules:

Start of changeStart of changeDFHFCDLEnd of changeEnd of change

Start of changeStart of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedddd, End of changeStart of changefilename, End of changeStart of changepoolname, End of changeStart of changeX'End of changeStart of changexxEnd of changeStart of change'End of changeEnd of change

Start of changeDFHFC7094End of change
Start of changedate time applid CICS data table load has terminated abnormally for coupling facility data table dddd, file filename, pool poolname, reason code = X'xx'.End of change
Start of change
Explanation:

The request to close the source data set at the end of load of coupling facility data table dddd has failed. The most likely cause of the failure is an error on the SET call to the coupling facility data table server to mark the table as loaded and to set the table access as shared, either because the server was down at the time of the SET or because of an error returned by file control during processing.

End of change
Start of change
System action:

The table and source are closed, leaving the table in a state such that a subsequent open may be able to complete the load.

CICS processing continues.

End of change
Start of change
User response:

Determine the cause of the failure using the diagnostic information provided by file control.

End of change
Start of change
Destination:

Console and Transient Data Queue CSFL

End of change
Modules:

Start of changeStart of changeDFHFCDLEnd of changeEnd of change

Start of changeStart of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedddd, End of changeStart of changefilename, End of changeStart of changepoolname, End of changeStart of changeX'End of changeStart of changexxEnd of changeStart of change'End of changeEnd of change

Start of changeDFHFC7095End of change
Start of changedate time applid CICS coupling facility data table load has completed successfully for data table dddd, file filename, pool pool.End of change
Start of change
Explanation:

The task that was attached to load coupling facility data table dddd has successfully completed loading.

End of change
Start of change
System action:

The user exit XDTLC has been invoked and has accepted the load. The table has been marked as loaded and the table access has been set to SHARED. CICS processing continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CSFL

End of change
Modules:

Start of changeStart of changeDFHFCDLEnd of changeEnd of change

Start of changeStart of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedddd, End of changeStart of changefilename, End of changeStart of changepoolEnd of changeEnd of change

Start of changeDFHFC7096End of change
Start of changedate time applid CICS has successfully performed the first connection to the Coupling Facility Data Table Server for pool pool.End of change
Start of change
Explanation:

The first connection to the coupling facility data table server has completed successfully.

End of change
Start of change
System action:

CICS processing continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CSFL

End of change
Modules:

Start of changeDFHFCDO DFHFCDREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changepoolEnd of change

Start of change
DFHFC7097
date time applid CICS has successfully reconnected to the Coupling Facility Data Table Server for pool pool.
Explanation:

A reconnection to the coupling facility data table server has completed successfully.

System action:

CICS processing continues.

User response:

The reason for the reconnection should be investigated by examining the joblog for the coupling facility data table server. Messages will have been output by the server detailing what events have occurred and whether there is a risk that any data has been lost.

Destination:

CSFL

Modules:

DFHFCDO DFHFCDR

XMEOUT Parameters: date, time,applid, pool

End of change
Start of changeDFHFC7100End of change
Start of changedate time applid CICS data table load has terminated abnormally for coupling facility data table name, file filename, pool poolname, a call to FCFR to BROWSE the source data set has failed for reason code = n.End of change
Start of change
Explanation:

The CICS task which is loading coupling facility data table dddd has failed while calling file control to browse the source data set. The value of the reason code n indicates the type of failure as follows:

  1. Response from FCFR was INVALID.
  2. Response from FCFR was DISASTER.
  3. Response from FCFR was PURGED.
  4. FCFR failed for some unexpected reason.
End of change
Start of change
System action:

The user exit XDTLC is invoked, if enabled, with the parameter UEPDTORC set to indicate that loading completed abnormally. The user exit may ask for the file to be closed. No more records are loaded into the coupling facility data table, and CICS terminates the loading transaction with abend code ACFA.

If the user exit did not request that the file be closed (or if no user exit program was enabled at the XDTLC exit point), then API requests to access records within the range of keys which has already been loaded into the data table will succeed, but requests to access any record beyond the loaded range will receive the "LOADING" condition.

If the file has been closed, then API requests will receive a "NOTOPEN" condition.

CICS processing continues.

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

End of change
Start of change
User response:

Determine the cause of the failure of the domain call using the diagnostic information provided by file control.

If it is possible to correct the problem which caused the browse to fail, then you can complete the load of the coupling facility data table by closing the file which attempted the load (if it has not already been closed) and re-opening it, or any other file which is capable of loading the table; that is, which has access to the source data set. This will cause the load to be restarted from the point at which it failed.

End of change
Start of change
Destination:

Console and Transient Data Queue CSFL

End of change
Modules:

Start of changeStart of changeDFHFCDLEnd of changeEnd of change

Start of changeStart of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changename, End of changeStart of changefilename, End of changeStart of changepoolname, End of changeStart of changenEnd of changeEnd of change

Start of changeDFHFC7101End of change
Start of changedate time applid CICS data table load has failed to close coupling facility data table dddd, file filename, pool poolname, a call to FCFS has failed for reason code = n.End of change
Start of change
Explanation:

The CICS task that is loading coupling facility data table dddd has failed while trying to close the file at the request of an exit program invoked at exit point XDTLC. The value of reason code n indicates the type of failure as follows:

  1. Response from FCFS was INVALID.
  2. Response from FCFS was DISASTER.
  3. Response from FCFS was PURGED.
  4. FCFS failed for some unexpected reason.
End of change
Start of change
System action:

CICS terminates the loading transaction with abend code ACFA.

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

End of change
Start of change
User response:

It is unlikely that the user exit invoked at the XDTLC exit point would request that the file should be closed unless a previous problem had occurred with the load. Determine the cause of any such previous problem by checking for earlier messages which may have been issued referring to data table dddd. Diagnostic information provided by file control may be used to investigate the failure of the close file call.

CICS processing continues.

Report the details of the symptom string given in message DFHME0116.

End of change
Start of change
Destination:

Console and Transient Data Queue CSFL

End of change
Modules:

Start of changeStart of changeDFHFCDLEnd of changeEnd of change

Start of changeStart of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedddd, End of changeStart of changefilename, End of changeStart of changepoolname, End of changeStart of changenEnd of changeEnd of change

Start of changeDFHFC7103End of change
Start of changedate time applid CICS data table load has terminated abnormally for coupling facility data table dddd, file filename, pool poolname.End of change
Start of change
Explanation:

The special CICS transaction that was loading coupling facility data table dddd has detected an abnormal termination.

End of change
Start of change
System action:

Depending on the cause of this abnormal termination, CICS may produce either a system dump or a transaction dump.

The user exit XDTLC is invoked, if enabled, with the parameter UEPDTORC set to indicate that loading completed abnormally. The user exit may ask for the file to be closed. No more records are loaded into the coupling facility data table, and CICS terminates the loading transaction with abend code ACFA.

If the user exit did not request that the file be closed (or if no user exit program was enabled at the XDTLC exit point), then API requests to access records within the range of keys which has already been loaded into the data table will succeed, but requests to access any record beyond the loaded range will receive the "LOADING" condition.

If the file has been closed, then API requests will receive a "NOTOPEN" condition.

CICS processing continues.

End of change
Start of change
User response:

Look at the system log for related CICS messages to determine the original abend detected by the loading transaction. Refer to the description of abend code ACFA for further information about the cause of the original termination.

For more information on how to determine system problems, refer to the CICS Problem Determination Guide.

If it is possible to correct the problem which caused the load to abend, then you can complete the load of the coupling facility data table by closing the file which attempted the load (if it has not already been closed) and re-opening it, or any other file which is capable of loading the table; that is, which has access to the source data set. This will cause the load to be restarted from the point at which it failed.

End of change
Start of change
Destination:

Console and Transient Data Queue CSFL

End of change
Modules:

Start of changeStart of changeDFHFCDLEnd of changeEnd of change

Start of changeStart of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedddd, End of changeStart of changefilename, End of changeStart of changepoolnameEnd of changeEnd of change

Start of changeDFHFC7104End of change
Start of changedate time applid CICS data table load has terminated abnormally for coupling facility data table dddd, file filename, pool poolname, a call to FCFR to WRITE a record has failed for reason code = n.End of change
Start of change
Explanation:

The CICS task that is loading coupling facility data table dddd has failed while calling file control to write to the data table. The value of the reason code n indicates the type of failure as follows:

  1. Response from FCFR was INVALID.
  2. Response from FCFR was DISASTER.
  3. Response from FCFR was PURGED.
  4. FCFR failed for some unexpected reason.
End of change
Start of change
System action:

The user exit XDTLC is invoked, if enabled, with the parameter UEPDTORC set to indicate that loading completed abnormally. The user exit may ask for the file to be closed. No more records are loaded into the coupling facility data table, and CICS terminates the loading transaction with abend code ACFA.

If the user exit did not request that the file be closed (or if no user exit program was enabled at the XDTLC exit point), then API requests to access records within the range of keys which has already been loaded into the data table will succeed, but requests to access any record beyond the loaded range will receive the "LOADING" condition.

If the file has been closed, then API requests will receive a "NOTOPEN" condition.

CICS processing continues.

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

End of change
Start of change
User response:

Determine the cause of the failure of the domain call using the diagnostic information provided by file control.

If it is possible to correct the problem which caused the write to fail, then you can complete the load of the coupling facility data table by closing the file which attempted the load (if it has not already been closed) and re-opening it, or any other file which is capable of loading the table; that is, which has access to the source data set. This will cause the load to be restarted from the point at which it failed.

End of change
Start of change
Destination:

Console and Transient Data Queue CSFL

End of change
Modules:

Start of changeStart of changeDFHFCDLEnd of changeEnd of change

Start of changeStart of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedddd, End of changeStart of changefilename, End of changeStart of changepoolname, End of changeStart of changenEnd of changeEnd of change

Start of changeDFHFC7110End of change
Start of changeapplid An attempt to connect to coupling facility data table pool poolname, issued by module modulename, has failed.End of change
Start of change
Explanation:

CICS has issued a request to a file which is defined to use a coupling facility data table which resides in the pool poolname. CICS did not currently have a connection established to the pool, so an attempt to connect to the pool has been made. This attempt has failed. The connect attempt was issued from module modulename.

A coupling facility data table server is a separate address space that handles all requests made to coupling facility data tables which reside in the pool which it serves. CICS must have a connection to the server before it can open and access coupling facility data tables in the pool.

End of change
Start of change
System action:

CICS fails the request to the coupling facility data table.

New requests to coupling facility data tables which reside in this pool will check whether the server is available and will attempt another connect if it is.

End of change
Start of change
User response:

Determine the reason for the failure to connect. Diagnostic messages issued by the coupling facility data table server address space should assist you in doing this. The most likely cause of this error is a problem with the coupling facility. The coupling facility data table server does not automatically restart itself, so after you have corrected the cause of the error, you should resubmit the job which starts the server.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDR, DFHFCDO, DFHFCDUEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changepoolname,End of change Start of changemodulenameEnd of change

Start of changeDFHFC7111End of change
Start of changeapplid An attempt to disconnect from the coupling facility data table server for pool poolname for connection token X'connecttoken', issued by module modulename, has failed.End of change
Start of change
Explanation:

CICS has detected that an instance of the coupling facility data table server for pool poolname has failed. CICS has therefore attempted to disconnect from this pool server, but this attempt has failed. The disconnect has been issued by module modulename, and connecttoken is the token which was associated with the connection to this pool server.

A coupling facility data table server is a separate address space that handles all requests made to coupling facility data tables which reside in the pool which it serves.

End of change
Start of change
System action:

CICS continues. As soon as a new instance of the pool server is available (which it might already be) then CICS can re-establish a connection to the server and continue to process coupling facility data table requests.

In many cases, CICS will later be able to disconnect from the server automatically. If not, the only effect of this failure is that some storage allocated by the server to the connection will not be freed until CICS terminates, at which time a disconnect message will be issued by the pool server for each instance from which CICS failed to disconnect.

End of change
Start of change
User response:

Determine the reason for the failure to disconnect. Diagnostic messages issued by the coupling facility data table server address space should assist you in doing this.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDR, DFHFCDO, DFHFCDUEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changepoolname,End of changeStart of changeX'End of changeStart of changeconnecttoken', End of changeStart of changemodulename,End of change

Start of changeDFHFC7112End of change
Start of changeapplid Resynchronization of coupling facility data table pool poolname issued from module modulename has failed.End of change
Start of change
Explanation:

CICS has issued a request to a file which is defined to use a coupling facility data table which resides in the pool poolname. CICS did not currently have a connection established to the server for this pool, so an attempt to connect to and resynchronize the pool server has been made, but the resynchronization has failed. The attempt to resynchronize was issued from module modulename.

A coupling facility data table server is a separate address space that handles all requests made to coupling facility data tables which reside in the pool which it serves. When CICS re-establishes its connection to a coupling facility data table pool server, it must perform resynchronization in order to complete recovery processing for any unresolved units of work which had made recoverable updates to coupling facility data tables residing in the pool.

End of change
Start of change
System action:

CICS fails the request to the coupling facility data table.

Other requests to coupling facility data tables which reside in this pool will succeed if they do not require the pool to have been resynchronized, or might attempt another resynchronization if they do.

End of change
Start of change
User response:

Determine the reason for the failure to resynchronize. Diagnostic messages issued by CICS components involved in the resynchronization and by the coupling facility data table server address space should assist you in doing this.

Depending on the stage during resynchronization at which the failure occurred, any subsequent request to a recoverable file which uses a coupling facility data table in the pool might trigger an attempt to retry the resynchronization. If such requests do not trigger a retry, then you should recycle the server region for this pool (by stopping or cancelling the server region using a server command, and then restarting it).

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDR, DFHFCDO, DFHFCDUEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changepoolname,End of change Start of changemodulenameEnd of change

Start of changeDFHFC7113End of change
Start of changeapplid An attempt to retry resynchronization of coupling facility data table pool poolname issued from module modulename has failed.End of change
Start of change
Explanation:

CICS has issued a request to the coupling facility data table server for pool poolname. This request requires the pool to have been resynchronized.

Although CICS currently has a connection established to the pool server, an earlier attempt to resynchronize the pool failed, so the resynchronization has been retried. This retry has also failed. The attempt to retry resynchronization of the pool was issued from module modulename.

A coupling facility data table server is a separate address space that handles all requests made to coupling facility data tables which reside in the pool which it serves. When CICS has re-established its connection to a coupling facility data table pool server, it must perform resynchronization in order to perform recovery processing for any unresolved units of work which had made recoverable updates to coupling facility data tables residing in the pool.

Certain requests require the coupling facility data table pool to have been resynchronized before they can succeed. Such requests include:

These requests do not require all the units of work to have been resolved, but they do require CICS to have successfully restarted its recoverable connection to the pool server.

End of change
Start of change
System action:

CICS fails the request to the coupling facility data table pool.

Other requests to this pool server will succeed if they do not require the pool to have been resynchronized, or will attempt another resynchronization if they do.

End of change
Start of change
User response:

Determine the reason for the failure to resynchronize. Diagnostic messages issued by CICS components involved in the resynchronization and by the coupling facility data table server address space should assist you in doing this.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDO, DFHFCDUEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changepoolname,End of change Start of changemodulenameEnd of change

Start of changeDFHFC7114End of change
Start of changeapplid Force purge of transaction trannum which made recoverable updates to coupling facility data table pool poolname has failed.End of change
Start of change
Explanation:

An attempt to force purge transaction trannum has failed. The system attempted to force purge the transaction because it had made recoverable updates to one or more coupling facility data tables residing in the coupling facility data table pool poolname, and the server for that coupling facility data table pool is undergoing resynchronization. The fact that this resynchronization is taking place is an indication that a failure has occurred which will have resulted in all recoverable updates made to the coupling facility data table pool poolname, which have not yet been committed, having been backed out. This transaction had therefore made updates which have since been backed out, so the transaction needs to be abended, in order to ensure that any updates which it made to other recoverable resources will also be backed out. However, it has not been possible to purge this transaction.

The effect of the failure to purge this transaction is that updates made to other recoverable resources may be committed, with the result that the overall unit of work will not be commit-consistent. It is also possible that the transaction will try to make subsequent updates to the coupling facility data table pool which will cause it to be abnormally terminated.

End of change
Start of change
System action:

Resynchronization of the coupling facility data table server pool continues.

End of change
Start of change
User response:

If the transaction is still active, then attempt to force purge the transaction using the CEMT master terminal command. However, as this should be a rare situation, consider performing an immediate shutdown of CICS followed by an emergency restart as an alternative solution. This causes all inflight transactions to be backed out.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDYEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changetrannum,End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7115End of change
Start of changeapplid The coupling facility data table server for pool poolname has failed and restarted. One or more in-flight transactions which had made recoverable updates to coupling facility data tables residing in the pool will be abended.End of change
Start of change
Explanation:

The coupling facility data table server for data table pool poolname is undergoing resynchronization. The fact that this resynchronization is taking place is an indication that a failure has occurred which will mean that any recoverable updates made to the coupling facility data table pool poolname that had not yet been committed will have been backed out. Any in-flight transaction which had made recoverable updates to one or more coupling facility data tables residing in data table pool poolname therefore needs to be abended, in order to ensure that any updates which it made to other recoverable resources will also be backed out.

This message is issued to inform you that one or more such in-flight transactions has been found, and that CICS will attempt to abend the transactions and cause them to back out by force purging them. You should therefore expect that one or more transactions will be abnormally terminated with an ATCH transaction abend code (or possibly, in some instances, with an AKC3 abend code).

End of change
Start of change
System action:

Resynchronization of the coupling facility data table server pool will complete, and one or more in-flight transactions will be abnormally terminated.

End of change
Start of change
User response:

None.

This message is purely informational, to indicate that transactions will be abended in order to preserve data integrity.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDYEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changepoolnameEnd of change

Start of changeDFHFC7120End of change
Start of changeapplid The coupling facility data table pool poolname has an unresolved unit of work X'UOWid' for this CICS region of which CICS has no knowledge.End of change
Start of change
Explanation:

CICS is resynchronizing the coupling facility data table server for pool poolname.

A coupling facility data table server is a separate address space that handles all requests made to coupling facility data tables which reside in the pool that it serves. When CICS has established its connection to a coupling facility data table pool server, it must perform resynchronization in order to perform recovery processing for any unresolved units of work which had made recoverable updates to coupling facility data tables residing in the pool. The resynchronization involves restarting the recoverable connection to the pool server, and completing any unresolved units of work known to the server for which the resolution is now known.

The server has an unresolved unit of work UOWid, but CICS has no knowledge of a link to the pool server for this unit of work. Knowledge of links will be lost when CICS performs an initial start, but in the case of unit of work UOWid there has not been a CICS initial start since the unit of work was created.

End of change
Start of change
System action:

CICS resolves the unit of work by backing out the updates that it made to coupling facility data tables within the pool, and completes resynchronization of the pool.

End of change
Start of change
User response:

Since CICS will have resolved the unit of work, you do not need to take any immediate action. This message is issued to provide diagnostic information which you may want to use to understand why CICS had no knowledge of the link.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHFCDYEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changepoolname,End of changeStart of changeX'End of changeStart of changeUOWidEnd of changeStart of change'End of change

Start of changeDFHFC7121End of change
Start of changeapplid CICS coupling facility data table load has terminated abnormally. A call to DFHXMIQ to retrieve the parameters for the load transaction has failed with response code = n.End of change
Start of change
Explanation:

The CICS task to load a coupling facility data table has failed while trying to inquire on the parameters passed to it during attach. The value of the reason code n indicates the type of failure as follows:

  1. Response from XMIQ was INVALID.
  2. Response from XMIQ was DISASTER.
  3. Response from XMIQ was PURGED.
  4. XMIQ failed for some unexpected reason.
End of change
Start of change
System action:

The user exit XDTLC is not invoked as failure to retrieve the attach parameters means the filename is not known. CICS terminates the loading transaction with abend code ACFD. No records are loaded into the data table.

Requests to access the table result in a "loading" response code.

CICS processing continues.

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

End of change
Start of change
User response:

Determine the cause of the failure of the domain call using the diagnostic information provided by file control.

The file should be closed so that a load may be attempted again when it is next opened.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeStart of changeDFHFCDLEnd of changeEnd of change

Start of changeStart of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changenEnd of changeEnd of change

Start of changeDFHFC7130End of change
Start of changedate time applid tranid trannum termid userid. Unit of work X'uowid' running in region owner-applid in MVS system MVSid holds a lock on key X'keyid' in coupling facility data table tablename in pool CFDTpool, which caused this request to wait.End of change
Start of change
Explanation:

This message is issued to aid problem determination when a transaction that has accessed, or attempted to access, a coupling facility data table is about to terminate abnormally with an AFCY abend code.

The message is issued when a request to a coupling facility data table times out waiting on a lock. A request that requires a lock on a coupling facility data table has been issued, but was forced to wait because the record was locked by another unit of work. The wait has been purged by one of the following actions:

The name of the transaction that has failed is tranid and it is running under task number trannum, at terminal termid, for user userid.

The message inserts identify the owner of the lock that caused this transaction to timeout:

The locks held against coupling facility data tables are always exclusive locks, and can only have one holder. Therefore, this message uniquely identifies the owner of the required lock.

End of change
Start of change
System action:

The transaction is abended with an AFCY abend code.

End of change
Start of change
User response:

This message identifies the unit of work that is holding the required lock and the region in which it is running. Examine this unit of work to see why it is not releasing the lock; for example:

End of change
Start of change
Destination:

CSFL

End of change
Modules:

Start of changeDFHFCDREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changetrannum, End of changeStart of changetermid, End of changeStart of changeuserid, End of changeStart of changeX'End of changeStart of changeuowid', End of changeStart of changeowner-applid, End of changeStart of changeMVSid, End of change Start of changeX'End of changeStart of changekeyid', End of changeStart of changetablename, End of changeStart of changeCFDTpoolEnd of change

[[ Contents Previous Page | Next Page Index ]]