How to configure maximum size of different frequently used log files created by TXSeries runtime.
Nageswararao V Gokavarapu 2700013B8D Visits (4987)
TXSeries creates different log files like installation logs, runtime logs, trace and dump logs. Trace files are created only when user enables the trace for different components involved in TXSeries runtime. Dump files are created when the TXSeries runtime or application running in CICS runtime receives an exception.
TXSeries runtime creates multiple log files in the system and some of the following logs files will grow if user does not configure its maximum file size. If maximum file size is not configured for these logs files, then there is a possibility of loosing the critical logs during a critical situation.
sarpcd.log : Used by RPC component used by TXSeries runtime. If the regions running for long time then sarpcd.log file size will grow continuously. You can configure its maximum file size limit by setting the CICS_SARPC_LOG_SIZE environment variable in /var
console.nnnnnn and symrecs.nnnnnn : These are the primary logs files for all activities performed in the CICS region. If application executing in the CICS region writes any application logs to 'stderr', those logs also routed to console.nnnnnn file. Maximum size of these files can be configured by setting the 'MaxConsoleSize' in region definition. Restart the region with 'cold' mode to reflect the modified changes in runtime.
CSMT.out and CCIN.out: TXSeries runtime writes the terminal related log/error messages to CSMT.out file and client connection related information in CCIN.out file. These files sizes can be controlled by setting the MaxSize attribute in the corresponding entry in TDD stanza. Restart the region with 'cold' mode to reflect the modified changes in runtime.