What can you delete to free up disk space in IBM InfoSphere Information Server

What can you delete to free up disk space in IBM InfoSphere Information Server when disks are becoming full?

What to do ????

Here are some things you can do to clean up space:

• Clear the &PH& file in the Project directory. There is a &PH& directory in each DataStage project directory, which contains information about active stages that is used for diagnostic purposes. The &PH& directory is added to every time a job is run, and needs periodic cleaning out.
  

When datastage file system becomes full, RT_LOGxxx files can become corrupted. Here is a manual procedure to recreate them

When many datastage jobs are running for long time, the RT_LOGxxx files can become very big. If the log files are not regularly purged, in some cases, a file system full on the datastage file system can occur. If the corruption of datastage system files is restricted to the RT_LOGxxx files, a procedure to delete and recreate the RT_LOGxxx files can be attempted in order to recover from the corruption.

Selecting DataStage job log results in error: Error Selecting from log file RT_LOG

When trying to view a job log in DataStage Director, an error similar to the following is received:

Error selecting from log file RT_LOGnn
Command was: SSELECT RT_LOGnn WITH @ID LIKE '1NON' COUNT.SU
Error was: Internal data error. File <path_to>/RT_LOGnn/<filename>':
Computed blink of 0xnnnn does not match expected blink of 0xnnnn! Detected within group starting at address 0xnnnnnn!
The error message received indicates that the log file for the job is corrupted.

DataStage-Director: Unable to open DICT 'RT_LOG###'

When attempting to open a job log in Director, user gets the following error message: Error selecting from log file RT_LOG### Error was: Unable to open DICT 'RT_LOG###'. This is because the D_RT_LOG file is missing from the projects directory.

Changing Logs method in DataStage

DataStage logging was changed at release 8.1 to log job run detail records into the operational repository, (xmeta) rather than the local project level log files, (RT_LOGxxx).
In case XMETA repository logging causing problem (i.e not visible from designer), we able to change the logging method back to local project log files.