We just setup a new company with a new porting sent and license manager on Solaris 11. When we try to compile a program we get an "Fatal error cannot open pacc fd file for b40c_prd". We checked the fd6.1 files out in $BSE/lib and they are wide open right now (more so that our normal test companies). We get nothing in any of the log files. All of the directory structures are open also to the BSP user and group. Any clue what else we can check?

Hi Mark,

you could try logging from bw configuration:
-- -keeplog -logfile /tmp/files.log -dbgfdev -dbgfile

Regards
Günther

That is a good idea. Going to have to look for some other options to try to set with that. It logs a lot of stuff but nothing with an error in it - seems to be a whole bunch of this. I almost think he needs to rebuild the DD, but that worries me since he has always been a file edit type of admin.

F:0004137:::(00005):_explode_fname: context 'sopen' (F_OBJ:ottdllfilehand)
F:0004138:::(00005): _explode :(/apps/baan/baaniv/bse/tools/ttB40_c4/ottdll/odllfilehand)
F:0004139:::(00005):explode: F_OBJ:ottdllfilehand, /apps/baan/baaniv/bse/tools/ttB40_c4/ottdll/odllfilehand, /apps/baan/baaniv/bse/tools/ttB40_c4/ottdll/odllfilehand
F:0004140:::(00005):open(/apps/baan/baaniv/bse/tools/ttB40_c4/ottdll/odllfilehand,"r "), fd 5 errno 0
F:0004141:::(00005):open ("r ") /apps/baan/baaniv/bse/tools/ttB40_c4/ottdll/odllfilehand
F:0004142:::(00005):_explode_fname: context 'sopen' (F_OBJ:ottdllfilehand)
F:0004143:::(00005):sopen(/apps/baan/baaniv/bse/tools/ttB40_c4/ottdll/odllfilehand, "r ") 0x10137f930
F:0004144:::(00005):_explode_fname: context 'sopen' (/apps/baan/baaniv/bse/tmp/tmp339742520)
F:0004145:::(00005): _explode :(/apps/baan/baaniv/bse/tmp/tmp339742520)
F:0004146:::(00005):explode: /apps/baan/baaniv/bse/tmp/tmp339742520, /apps/baan/baaniv/bse/tmp/tmp339742520, /apps/baan/baaniv/bse/tmp/tmp339742520
F:0004147:::(00005):open(/apps/baan/baaniv/bse/tmp/tmp339742520,"x "), fd 5 errno 0
F:0004148:::(00005):open ("x ") /apps/baan/baaniv/bse/tmp/tmp339742520
F:0004149:::(00005):_explode_fname: context 'sopen' (/apps/baan/baaniv/bse/tmp/tmp339742520)
F:0004150:::(00005):sopen(/apps/baan/baaniv/bse/tmp/tmp339742520, "x ") 0x10137f930
F:0004151:::(00005):_explode_fname: context 'sopen' (/apps/baan/baaniv/bse/tmp/tmp384991297)
F:0004152:::(00005): _explode :(/apps/baan/baaniv/bse/tmp/tmp384991297)
F:0004153:::(00005):explode: /apps/baan/baaniv/bse/tmp/tmp384991297, /apps/baan/baaniv/bse/tmp/tmp384991297, /apps/baan/baaniv/bse/tmp/tmp384991297

Hi Mark,

another idea: Are you able to compile from command line?
e.g. bic6.1 test.bc -o test.obj

Regards
Günther

Actually what I just did for a test was copy the fd6.1.B40C_prd file to fd6.2.B40C_prd - the compile actually tried to work. So I poked around some more and I see in $BSE/lib bic6.2 - I do not even see bic6.1. So when I compile it shows up as bic6.1, but in $BSE/lib I see nothing but 6.2 objects. I included a screen shot of the last compile that almost worked.

I am beginning to think the company is only half way converted to the new licensing manager and porting set. I actually think the compile would have worked if he gave me prd permission to the test compile object.

Actually günther I was able to compile just using the "real" 6.2 binary. And trying what you recommended got us pointed to what I actually think is the problem - qkey installed in the environment. Waiting to get that removed so I can try normal compiles. And then see if we can find a solution for our qkey sessions for that portingset.

Okay - long story short. We had in-install qkey and then install a patch (not sure which one) that updated all the include files. Once that was done we could compile normally with out qkey. Then when we put qkey back in it broke the compile again with the same error message. Then I fixed it (I guess you could say) by just copying the fd6.1 b40c_prd file to fd6.2 b40c_prd. Note sure (nor would I recommend) I like the solution. But we only have to last another year (so they say) on baan.