PM51011: Client daemon ends unexpectedly if a log file is removed while CICS TG is running.

CICS Transaction Gateway Desktop Edition - V8.1 -
CICS Transaction Gateway Desktop Edition - V8.1 -
IBM CICS Transaction Gateway for Multiplatforms - Version 8.1 - AIX
IBM CICS Transaction Gateway for Multiplatforms - Version 8.1 - Linux on zSeries
IBM CICS Transaction Gateway for Multiplatforms - Version 8.1 - Solaris
IBM CICS Transaction Gateway for Multiplatforms - Version 8.1 - HP-UX on Itanium
IBM CICS Transaction Gateway for Multiplatforms - Version 8.1 - Windows
CICS Transaction Gateway for Multiplatforms V9.0 (all supported platforms)
CICS Transaction Gateway Desktop Edition V9.0 (all supported platforms)
CICS Transaction Gateway for Multiplatforms V8.0 Fix Pack 6
CICS Transaction Gateway Desktop Edition V8.0 Fix Pack 6
CICS Transaction Gateway Desktop Edition - V8.1 - Linux on POWER
CICS Transaction Gateway Desktop Edition - V8.1 - Solaris
CICS Transaction Gateway for Multiplatforms V8.1 Fix Pack 4
CICS Transaction Gateway Desktop Edition V8.1 Fix Pack 4
CICS Transaction Gateway Desktop Edition V8.1 Fix Pack 5
CICS Transaction Gateway for Multiplatforms V8.1 Fix Pack 5

APAR status

• Closed as program error.

Error description

• If a Client daemon information or error log file is removed
  while CICS TG is running, the Client daemon might end
  unexpectedly.
  
  Additional search words:
  CCL2003 msgCCL2003I msgCCL2003
  
  The problem might occur more frequently if manually-scripted or
  built-in log rotation is used.
  

Local fix

• Stop CICS TG before removing log files.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of CICS Transaction Gateway.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Client daemon might end             *
  *                      unexpectedly if log files are removed   *
  *                      repeatedly while CICS TG is running.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If a Client daemon log file is removed, the next time a message
  is logged, CICS TG automatically regenerates the log file. CICS
  TG maintains a list of log files, and appends the names of
  regenerated files to the list. However CICS TG does not check
  whether a file already exists in the list, so the list might
  overflow its own reserved space and overwrite adjacent memory.
  If a process then attempts to access overwritten memory,
  unexpected results, such as a trap, might occur.
  
  Additional symptoms resolved by this APAR:
  If multiple threads attempt to write to the log at the
  same time, variables used by the logging mechanism can
  become corrupted and unexpected results, such as a trap,
  might occur.
  .
  When using secure TCP/IP connections to a CICS server,
  failures in security checking result in the following
  message being written to the CICS Client log:
  &#163;2153] CCL:CCL2003I Server '<server_name>' requires a security
  security identification
  followed by unexpected messages of the following format:
  /&#242;[YL2d/11/19 12:14:13.041 &#163;0012] :CCL
  /&#242;[YL/&#242;[YL02.2d/11 19:12:14.013 &#163;0041] :
  /&#242;[YL/&#242;[YL/&#242;[YLd/11 19:12:14.013 &#163;0041] :
  /&#242;[YL/&#242;[YL/&#242;[YL/&#242;[YL2.2d 11:19:12.014 &#163;0013] :
  /&#242;[YL/&#242;[YL/&#242;[YL/&#242;[YL/&#242;[YL 11:19:12.014 &#163;0013] :
  /&#242;[YL/&#242;[YL/&#242;[YL/&#242;[YL/&#242;[YL/&#242;[YL.2d:11:19.012 &#163;0014] :
  .
  

Problem conclusion

• CICS TG has been changed so that it checks for the existence
  of a log file name in the list and does not append a file name
  if it already exists in the list. Additional locking has been
  added to prevent variables used by logging becoming corrupted
  when multiple threads attempt to write to the log at the same
  time.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• CTGV8DUM
  

Fix information

• Fixed component name

  CICS TRNS GATE

• Fixed component ID

  5724I8102

Applicable component levels

• R800 PSY

     UP

• R810 PSY

     UP