Problem solving for generic resource

Trace TC level 1, 2 & exception in the ranges AP FA50-FA59, FAB0-FABA and FB87-FB8F.

Messages DFHZC0170 to DFHZC0185 are written to the console and CSNE logs.

Information output by DFHZNAC following BIND failures.

If a dump is produced examine the generic resource status and generic resource flag bytes.

The following symptoms may indicate that an affinity should be ended and has not been.
  • Sessions failing to acquire with message DFHZC2405 "Node not activated". This may also indicate a setup error.
  • Sessions failing to acquire with various instances of DFHZC2411. This may also indicate that a rule has been violated.
  • CICS® fails to register as a generic resource when it has previously been a member of a different generic resource. Message DFHZC0171 is written to the console with z/OS® Communications Server rtncd X'14' fdb2 X'86'.
  • Connections autoinstalling unexpectedly. If a non-generic resource is addressing a generic resource member by its member name this may also indicate that the first ACQUIRE was issued from the generic resource side.


dfhs3c001100.html | Timestamp icon Last updated: Monday, 5 June 2017