For the rscd.log, if you are accessing it via the CM gui or nsh you need to use the 'bllogman' tool to open it. you can create a custom command in the gui for this.
For the system mapping, you may have other permissions issues, typically you don't need this if your acls are setup to map the user running the acl check to a local administrator. Depending on how the blcli call is being run you may be losing the credentials passed down through the job and that's why it's failing.
There is a bladelogic 'SYSTEM:SYSTEM' role:user (nothing to do w/ the windows 'localsystem' account) that is sent when the appserver starts up and talks to the file server agent, but I don't think you are running into that problem here.