Which log file ?
As NBUTSE mentioned, Symantec have a utility that will help analise the nbjm/ pem/ rb /emm logs. This is internal only and does not necessary provide solid answers, but it does help greatly in finding the area of the potential issue.
The problem with the vx logs is that there are multi-threaded, so to be able to follow a job through them you need to know what should happen next, or, what should have happened previously, for example thread 5 may be doing something with a backup one moment, and a restore the next, whilst thread 2 has become available and is now doing the next stage of the backup.
If you happen to be looking at the raw logs (/usr/openv/logs) then yes, there is a command that makes these readable, vxlogview. eg.
vxlogview -a -p 51216 -o 111 -d all
The -o is the originator id, 111 is nbemm, The others can be found in the /usr/openv/netbackup/nblog.conf file
Martin