Do you really mean WaveView (which is a Synopsys viewer), or Wavescan?
Anyway, what you're seeing is that you're unable to use "schematic" names (any name starting with a / is treated as a schematic name, and you give each element in the hierarchical name by whatever it's called in the schematic), and are having to use "netlist" names (i.e. the names which actually appear in the netlist - which may get mapped if reserved words etc are used) including the simulator's hierarchy delimiter (which is ".").
If you can't use the schematic names, it generally means that it can't find the map or amap directories in the netlist directory - these are used to do the schematic to netlist (and vice-versa) mapping. To find this mapping, it looks in the runObjFile in the psf directory, for an entry saying netlistDir. If the runObjFile isn't found, it simply looks for "../netlist" (I believe) from the psf directory - and looks for amap within there.
So usually this is because the results have been copied elsewhere, or the simulation has been run standalone and the results stored somewhere other than the usual ADE structure, or the amap dir omitted when the netlist directory was copied. Something like that.
We (as Application Engineers) often see this kind of problem because customers send us their OCEAN script and the netlist file, and nothing else - so we end up having to modify all the signal references to use netlist names to make a testcase work.
Hope that helps to pin-point the problem.
The only thing I can think of then is that the subckt you've got containing L0 is coming from a model file, rather than a schematic (perhaps something changed?) and so it doesn't have any details about a schematic name for L0 (because it's not in a schematic).
Probably a wild guess, and unlikely...
So best thing would be to contact Customer Support, ideally providing the netlist and psf directory - then we can investigate. Might need me to take a look to dig a little, so if you do this, mention to whoever picks up the service request that I'm happy to take a look at the data.
Note that you should not use the userCmdLineOption to change the format. This is because the ADE netlister (and various things) need to know what format is being used, in order to do mapping appropriately.
In IC5141 this should be set by:
envSetVal("spectre.envOpts" "simOutputFormat" 'string "psfbin")
In IC613/IC614 it is:
envSetVal("spectre.outputs" "simOutputFormat" 'string "psfbin")
In IC613/4 it is also settable on the Outputs->Save All form (as is the +rtsf flag).
In IC5141, it's OK to put +rtsf on the userCmdLineOption field, because the netlister doesn't need to know about this.