If there is a publish related problem, how can trace be enabled to help troubleshoot further?

The pserver trace can be enabled by editing the <installationdirectory>\pw\server\etc\pserver.trace and uncommenting the last 2 sections in that file so it looks like this :

# messages of level DEBUG or above in the package
log4j.logger.com.bmc.sms.ar=DEBUG
log4j.logger.com.bmc.sms.arnotify=DEBUG
log4j.logger.com.bmc.sms.aros=DEBUG
log4j.logger.com.bmc.sms.imapi=DEBUG
log4j.logger.com.bmc.sms.imcomm=DEBUG
log4j.logger.com.bmc.sms.imobject=DEBUG
log4j.logger.com.bmc.sms.logging=DEBUG
log4j.logger.com.bmc.sms.ps=DEBUG, IPSERROREVENTS

# messages of level DEBUG or above in the subpackages
log4j.logger.com.bmc.sms.ps.automated=DEBUG
log4j.logger.com.bmc.sms.ps.cdmMap=DEBUG
log4j.logger.com.bmc.sms.ps.cellpublish=DEBUG
log4j.logger.com.bmc.sms.ps.config=DEBUG
log4j.logger.com.bmc.sms.ps.cp2cmdb=DEBUG
log4j.logger.com.bmc.sms.ps.env=DEBUG
log4j.logger.com.bmc.sms.ps.export=DEBUG
log4j.logger.com.bmc.sms.ps.im=DEBUG
log4j.logger.com.bmc.sms.ps.imevents=DEBUG
log4j.logger.com.bmc.sms.ps.imgateway=DEBUG
log4j.logger.com.bmc.sms.ps.log=DEBUG
log4j.logger.com.bmc.sms.ps.logger=DEBUG
log4j.logger.com.bmc.sms.ps.oscomm=DEBUG
log4j.logger.com.bmc.sms.ps.publish=DEBUG
log4j.logger.com.bmc.sms.ps.publishcomm=DEBUG
log4j.logger.com.bmc.sms.ps.request=DEBUG
log4j.logger.com.bmc.sms.ps.util=DEBUG
log4j.logger.com.bmc.sms.ps.validation=DEBUG

Then restart the publishing server with command 'pw p r pserver' and once it is up (confirmed by positive response from command 'psstat'), perform the publish again. Zip and return the following to BMC Customer Support for further investigation:

<installationdirectory>\pw\server\log\ps_<host>
<installationdirectory>\pw\server\tmp\ps_<host>