Troubleshooting data for Service Flow Runtime (SFR) problems

CICS® MustGather for Service Flow Runtime (SFR) problems

If you are a new user to the SFR, you can use SupportPac CH1C to test whether program links that use a CICS channel and Link3270 bridge invocations can be made from within a service flow. These tests help you ensure that the CICS Service Flow Runtime is installed and configured correctly. After that, gather the following diagnostic information before contacting the CICS support team to troubleshoot your CICS SFR problems.

Required data:
  1. The CICS message log that contains the SFR error messages. See Messages and codes issued by CICS Service Flow Runtime V3.2 for more information.
  2. If you experience a problem with a Link3270 server adapter, see Steps 4 through 6 under Troubleshooting Link3270 server adapters for instructions on how to turn on vector logging, populate the vector log file, and dump the vector log file.
  3. The MVS™ system dump that is taken at the point of failure. The CICS internal trace is included in the MVS system dump if tracing is active. Ensure that the internal trace table size is big enough to contain sufficient data for diagnosis; for example, you can use a table size of 20480K. Activate the CICS auxiliary trace, and turn on level 1 tracing for all components, with an exception of ALL for EI, AP, BA, BR, EM, PI, SH, TC, and WB. Then re-create the error and capture a system dump by using the CEMT P SNAP command. For more information, see Using dumps for CICS problem determination on z/OS® and Using trace for CICS problem determination on z/OS.

    For information on application domain (AP) trace points that are written by CICS SFR, see CICS Service Flow Runtime: Trace points. For information on trace points that are written by CICS Business Transactions Services (BTS), see Trace entries. BTS consists of business application manager (BA), event manager (EM), and scheduler services (SH).

  4. The non-compiled generated service flow that is produced by the Rational® Developer for System z® modeler. This is the generated COBOL code that is the code equivalent of what the user modeled on the modeler.
Optional data:
  1. The MVS system dump that is taken at the point of failure. For more information, see Using dumps for CICS problem determination on z/OS.
  2. An archive file that contains the Service Flow Projects. Perform the following steps from IBM® Rational Developer for System z that contains the Service Flow Projects:
    1. Click File > Export.
    2. In the Export window, select General > Archive File.
    3. In the Archive file wizard, select the base Service Flow Project and all its associated projects. The following examples are possible project names:
      • serviceprojectname
      • serviceprojectname.Interface
      • serviceprojectname.Nonterminal
      • serviceprojectname.OutboundWebService
      • serviceprojectname.Terminal
    4. Complete the Archive file wizard to produce the archive file that contains the Service Flow Projects.