DFHIS2011    date time applid {PURGE | FORCEPURGE | KILL} issued successfully for num_purged tasks using the sesstype sessions of IPCONN ipconn. There are currently num_active tasks active of which num_purging are currently being purged.

Explanation

In response to a connection error or to the SPI command SET IPCONN, the IS domain has purged num_purged tasks that were using a sesstype session on IPCONN ipconn and, if the connection is still available for use, has sent an IS purge command message to the conversation partner of each task that it has successfully purged.

There were num_active sesstype sessions associated for the IPCONN of which num_purging are now being purged specifically by this operation. In total, there were found to be num_purged tasks using this session type that were being purged at that time: some that might have been purged because they had themselves detected an error with the connection.

System action

Those tasks that are waiting for a message to arrive over the connection are resumed and abended. An attempt is made to abend any other tasks that are using this connection.

If an SPI command was issued to perform the purge, then those IPCONN sessions belonging to tasks that were successfully purged can now be allocated by new tasks.

User response

If a normal PURGE was issued and the message shows that the number of active tasks was greater than the number being purged, some tasks might persist because they are purge protected. It might be necessary to issue a FORCEPURGE to remove them.

KILL can only be used after a FORCEPURGE has been attempted.

Module

DFHISEM

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. Value chosen from the following options:
  5. num_purged
  6. sesstype
  7. ipconn
  8. num_active
  9. num_purging

Destination

CISO



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