Start of change

Responding to IVP errors

If an adapter fails during the IVP, the IVP stops processing and records errors in the log, before moving on to the next adapter.

  1. Check the transient data queue (TDQ) CSMT for an error message to find out why the adapter failed. If CICS cannot write to CSMT, the message is redirected to the CICS job log.
  2. Follow the user response recommendations that are outlined in the error messages. For a list of IVP messages see The IVP messages.
  3. Rerun the IVP, selecting only the adapter that failed.
  4. If the adapter still fails, rerun the IVP against the adapter that has failed with auxiliary tracing switched on.
    1. In the CICS-supplied transaction CETR, select the master system and master user trace flags.
    2. Print the trace output and look for ('64'x). In particular look for any exceptions.
  5. Dump the error file DFHMAERF to find out what error messages have been reported in the runtime environment.
    1. Check that the sample module DFHMAEUP is located in the hlq.SCIZSAMP library and has been compiled.
    2. Dump the error file using the provided sample JCL job DFHMAMED. The job is also located in the hlq.SCIZSAMP library.
    3. Look up the error messages that have been reported in the Error messages section to see if you can take any actions to resolve the problem.
If you can't resolve the problem, contact IBM Software Support. You need to provide the trace output and the dump of the error file. It is also recommended that you provide a dump of the properties file. This is explained in Dumping the properties file.
End of change