I've got a bit of PML that basically does a CHECK CE as well as a clash check and pipes the output to a log file.
Now I've been having some problems with it but after investigation it turns out to be related to the CHECK CE command rather than the PML itself.
The Issue is that for some users I can sit at a PIPE called /A1 and CHECK CE, with a number of warnings/errors as you might expect
The problem is that when other users sit at the same PIPE, do a CHECK CE they are presented with a larger number of errors.
They are all running the same command, sitting at the same PIPE, have all done a get work.
The extra errors are all relating to not finding a particular SKEY and so are grabbing a default SKEY.
I've located the SKEY file and confirmed that the PDMS DEsigner group has full access to the SKEY file.
First, where are extra SKEY file locations defined in Design, obviously in IsoDraft you add a line into the default set but I can't see where (or indeed if you need to do it) that is defined in Design.
Secondly does anyone have any ideas where I should be looking or has come up with this problem before?
My initial thought was that there may be some access to the User Defined SKEY file, so I checked that all of the users had the same level of access to the network resource (we have a PDMS Designer Group that they are all members of).
All I can think of now is checking how PDMS accesses the SKEY file in design, and possibly there is some minor difference in the local installs and I have been unable to find where you define the location of additional SKEY files in design.
