DFHZC0121I    applid VTAM sessions persisted for a WARM start. Sessions terminated. Inquires issued icount, sessions persisting spcount, sessions terminated stcount.

Explanation

CICS is initializing with a WARM start, but some VTAM sessions unexpectedly persisted from a previous CICS with a nonzero PSDI value.

CICS has attempted to terminate all persisting sessions. The message inserts are as follows:

  • icount is the number of VTAM INQUIRE OPTCD=PERSESS commands issued.

  • spcount is the number of VTAM sessions that persisted.

  • stcount is the number of sessions that CICS has terminated with a CLSDST or TERMSESS macro. This should be equal to spcount. If it is not, persistent session recovery probably failed. Earlier messages explain why.

    If there are no earlier messages, it is possible that the count obtained from the VTAM INQUIRE counts macro, indicating the number of active sessions, was not equal to the number of sessions that VTAM held persisting. This is not a problem.

System action

CICS continues.

User response

Examine the JOBLOG from the previous run to determine why sessions persisted despite a WARM shut down.

Module

DFHZGRP

XMEOUT parameters/Message inserts

  1. applid
  2. icount
  3. spcount
  4. stcount

Destination

Console



DFHZC0121I.html | Timestamp icon Last updated: Sunday, 4 June 2017