This happens because PIM cannot get full path for the program on PIM restart.
When PIM is restarting, PIM is getting process information from /proc and stores in internal process table.
If there is no full path information for the process in /proc, then PIM cannot get full path.
This causes that PIM recognizes only file name for the accessed program name and it doesn't match specialpgm/PACL definition.
If the program was executed in full path, then /proc stored the full path of the program.
However, the program was executed not in full path, there is no full path of the program in /proc.
PIM can get the full path when the program is executed after PIM startup though the program was executed not in full path, it is because the interception data has full path.
This is working as intended and product limitation now.
This happens on AIX and HP-UX, not on RHEL and Solaris.