How to enable RDT and PTY logging

Following are the steps to enable and validate RDT & PTY logging:

1. Launch Putty
2. Login to the server using credentials with admin access
3. Go to directory $DCS_HOME/dcs 
4. Open hidden file “.dcs_profile” file
5. Search for below 3 environment variables and enable them by removing the “#” from the front (Uncomment)

           export CRT_LOG="$DCS_TMPDIR"                    # Log file for ritch processes (also need to enable Function Access)
           export PTY_LOG="$DCS_TMPDIR"                         # Log file for ptysvr processes
           export CRTRDT_LOG="$DCS_TMPDIR"                 # Log file for crtrdt processes           dcsdba@uk1svcvlnx37.dev.corp.local bash[1123]: sga -h|grep -i CRT_LOG_ENABLED
          CRT_LOG_ENABLED      RDT - Enable CRT_LOG ritch screen logging              N 
          dcsdba@uk1svcvlnx37.dev.corp.local bash[1124]: sga -f CRT_LOG_ENABLED -e -y 
          Checking function id... done
          Updating function access... done 
          dcsdba@uk1svcvlnx37.dev.corp.local bash[1125]: sga -h|grep -i CRT_LOG_ENABLED
          CRT_LOG_ENABLED      RDT - Enable CRT_LOG ritch screen logging              Y 

To validate the changes, follow the below steps

1. Log off from application server putty session
2. Log back into the application server putty
3. Restart the application from APPCONTROL
4. Log into any RDT and perform some operation
5. Go to path $DCS_TMPDIR and validate that files like PTY****_DCS and CRT****_DCS are getting created

Enabling RDT and PTY logging would increase the disk space consumption, hence housekeeping and purging the log files is very important. The following information provides more details around the housekeeping and purging log files

• Script purgerdtlogs available in directory $DCS/server/bin is meant for purging the RDT, PTY and CRT log files
• Purgerdtlogs needs to be scheduled as crontab job and should execute at least once a day. The frequency can be increased/decreased based on disk space analysis
• The first run of the job would truncate the original log files and archives them by adding “.OLD” extension to the files. During next run, it would truncate the files with “.OLD” extension

Notes: 

• Test in lower environments (TEST,DEV or Pre Prod) before enabling in Live environment
• In LIVE monitor the disk space for initial 2-3 days and based on the observations Purge script frequency can be altered accordingly
• Enabling RDT and PTY logging might not cause any performance issue apart from filling up the disk space. Proper schedule and execution of the purge script would take care of the disk space