If CICSPlex® SM has run successfully in the past, review any changes
that have been made to your data processing environment since that time. Think
about your operating systems, CICSPlex SM itself, the CICS® systems it manages, the hardware
they run on, and any related operational procedures.
- If an APAR or PTF was applied to any of your operating systems, CICS, or CICSPlex SM,
check for error messages related to the installation. Also check for any unresolved
++HOLD ACTION items associated with the SMP/E maintenance. If the installation
of maintenance was successful, check with your IBM® Support Center for any known APAR
or PTF error.
- If a hardware modification was made, it may have affected the systems
on which CICSPlex SM runs or the connectivity between systems in a CICSplex.
- If your initialization procedures changed, check for messages sent to
the console during CICSPlex SM or CICS initialization. It could be that changes
to JCL, CICS system initialization parameters, or CICSPlex SM system parameters
are causing a problem.
- If the configuration of one or more CICSplexes has changed, check the EYULOG
consolidated message log for messages describing incorrect or incompatible
definitions. For example, if you are migrating additional CICS systems to management
by CICSPlex SM, ensure that the topology definitions for the new systems have been
added to the CICSplex.
[[ Contents Previous Page | Next Page Index ]]