What is the &PH& directory used for in DataStage and does it need to be cleaned out

-

Question

What is the &PH& directory used for and does it need to be cleaned out?

Answer

In each project there is an &PH& directory. This is used to write entries by the phantom process and they have this form:

DSD.RUN_InternalDate_InternalTime
DSD.STAGERUN_ InternalDate_InternalTime

This directory can become large and affect the performance. There is no exact number that could cause a problem due to variances in computing power. Generally this should be cleaned as regular maintenance. The more jobs running the quicker it will grow. You can check how many exist with the command: ls |wc -l. There are a couple ways to fix this problem:

  • Log into Administrator-->Projects-->Command and type:
    CLEAR.FILE &PH&

    This command can SHOULD ONLY be run when you have no jobs running or users logged into DataStage clients.


  • From $DSHOME:

    1. source the dsenv file:
    . ./dsenv
    2. type:
    ./bin/uvsh
    3. type:
    LOGTO <ProjectName>
    4. type:
    CLEAR.FILE &PH&

  • You can create a shell script to manually delete the files. To ensure there are no locks only delete files that are from finished jobs. You need to make sure the files are older than the longest running job. Generally you can just delete files older than a week.


Source: http://www-01.ibm.com/support/docview.wss?uid=swg21414210

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more