DFHDP0100 applid An unexpected exception response with reason code X'code' has been returned by CICS file control to module modname. The debugging profiles file, filename, is not usable.

System action

The file given in the message is not usable.

The application debugging profiles manager will fail until the problem has been corrected. It the CICS supplied transaction, CADP, is being used to define debugging profiles it will fail with an ADPA abend.

The meaning of the reason code in the message is given below:

• X'08' (FCFR_CACHE_FAILURE)

  There has been an input/output(IO) error trying to access the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. Examine the console to find file control or VSAM messages that will indicate the reason for the error.

• X'15' (FCFR_DATASET_BEING_COPIED)

  The data set for the debugging profiles file, DFHDPFMB, is currently unavailable because it is being copied. Retry when it becomes available.

• X'1F' (FCFR_FILE_DISABLED)

  The file definition for the debugging profiles base data set, DFHDPFMB, or path data set, DFHDPFMP, is disabled. Enable the disabled file and retry.

• X'20' (FCFR_FILE_NOT_OPEN)

  The file definition for the debugging profiles base data set, DFHDPFMB, or path data set, DFHDPFMP, cannot be opened. Examine the console to find file control or VSAM messages that will indicate the reason for the error. Note that Debug Profile support is deactivated following a file not open response.

• X'22' (FCFR_FILENOTFOUND)

  A definition for the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP, could not be found. Sample definitions for these files are available and should be defined and installed before retrying.

• X'27' (FCFR_INSUFFICIENT_SPACE)

  The debugging profiles base file, DFHDPFMB, is full. Investigate whether there are debugging profiles that can be deleted. Or, increase the storage allocation for the underlying VSAM data set, and recreate. Existing profiles could be backed up on another data set and then copied to the newly defined debugging profiles data set as part of the JCL to recreate it. To achieve this, replace REPRO INFILE with REPRO INDATASET in the JCL and replace SYS01 with the name of the data set containing the backed up profiles.

• X'2B' (FCFR_IO_ERROR)

  There has been an IO error trying to access the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. Examine the console to find file control or VSAM messages that will indicate the reason for the error.

• X'2D' (FCFR_ISC_NOT_SUPPORTED)

  An attempt has been made to ship a file control request but ISC=NO for the system. Determine if ISC should be YES or if the file definition should be changed so that shipping is not required and retry.

• X'31' (FCFR_LOCKED)

  An attempt has been made to write a record to the debugging profiles base file, DFHDPFMB, but a retained lock exists against the key of the record being written.

• X'32' (FCFR_LOST_LOCKS)

  There has been an IO error trying to access the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. Examine the console to find file control or VSAM messages that will indicate the reason for the error.

• X'33' (FCFR_LOCK_STRUCTURE_FULL)

  There has been an IO error trying to access the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. Examine the console to find file control or VSAM messages that will indicate the reason for the error.

• X'37' (FCFR_NOTAUTH)

  The user is not authorized to use the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. If the user should have access to the files, allow access and retry.

• X'39' (FCFR_PREVIOUS_RLS_FAILURE)

  The debugging profiles file, DFHDPFMB, has been defined as record level sharing(RLS) but RLS is currently unavailable due to a failure. Investigate the reason for the RLS failure by looking for messages from file control and VSAM on the console. Retry when RLS is available.

• X'3B' (FCFR_READ_NOT_AUTHORISED)

  The external security manager would not allow the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP, to be accessed. If the user should have access to the files, allow access and retry. .

• X'3D' (FCFR_RECLEN_EXCEEDS_LOGGER_BFSZ)

  A journal referenced in the definition for the debugging profiles file, DFHDPFMB, is using an MVS which in turn, is using a coupling facility structure that has been defined with a MAXBUFSIZE parameter less than the recommended 64000. Redefine the coupling facility structure that the logstream is using with a MAXBUFSIZE parameter of 64000. The journal in error can be the forward recovery log or the journal used for auto-archiving.

• X'46' (FCFR_RLS_DISABLED)

  The debugging profiles file, DFHDPFMB, has been defined as record level sharing(RLS) but RLS is currently disabled. Investigate why RLS is disabled by examining the console for file control and VSAM messages. Retry when RLS is available.

• X'47' (FCFR_RLS_FAILURE)

  The debugging profiles file has been defined as record level sharing(RLS) but RLS is currently unavailable due to a failure. Investigate the reason for the failure by examining the console for file control and VSAM messages. Retry when RLS is available.

• X'4B' (FCFR_SERVREQ_VIOLATION)

  The definition for the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP, does not allow all types of file request to be issued. Alter the file definitions to allow all file requests and retry.

• X'4E' (FCFR_SUPPRESSED)

  A user exit has suppressed the writing of records to the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. The exit should not be allowed to suppress records being written to these files. Correct the exit and retry.

• X'4F' (FCFR_SYSIDERR)

  The SYSID for the file definition for the debugging profile base file, DFHDPFMB, or path file, DFHDPFMP, specifies a name that is neither the local CICS region nor a remote system defined to CICS by a CONNECTION definition. SYSIDERR can also occur if the link to the remote system is closed. Correct the SYSID or reopen the link and retry.

• X'52' (FCFR_TIMEOUT) A request to file control has timed out. Investigate the reason for the timeout by examining the console for messages.

• X'58' (FCFR_UPDATE_NOT_AUTHORISED)

  The external security manager would not allow the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP, to be accessed. If the user should have access to the files, allow access and retry. .

• X'59' (FCFR_VSAM_REQUEST_ERROR)

  There has been an IO error trying to access the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. Examine the console to find file control or VSAM messages that will indicate the reason for the error.

• X'61' (FCFR_RREPL_VIOLATION)

  The file is flagged as RREPL and the program is not a REPLICATOR. If the program should be allowed to modify the file then change the file or program attributes.