1822896 Members
3456 Online
109645 Solutions
New Discussion юеВ

CATIA V4 problem

 
Justin_116
New Member

CATIA V4 problem

Client: HP-UX B.11.11
Server: Linux 2.4.20-18.7custom

Hello,
This is a CATIA V4 problem. When CATIA on the client tries to read a model from an automounted server directory, we get the following error:

MEMBER NOT FOUND FOR THE MODEL:
IN FILE "name_of_the_file.model", DDNAME=MOH
THE READ/WRITE OPERATION CANNOT BE PERFORMED.

However, on the client, I can open a UNIX shell and "cd" into the automounted directory, move and copy files, etc., so the problem is within CATIA and not NFS.

I know that this is not a CATIA forum, but if any other HP-UX CATIA users have run into this problem and know of a solution/workaround, I would very much appreciate hearing from you.

Thanks.
-J.K.
2 REPLIES 2
Steven E. Protter
Exalted Contributor

Re: CATIA V4 problem

I believe the client is looking for a file it does not have permissions for.

There is a file, perhaps name_of_the_file.model on the Linux server that is not available even for read to the HP-UX client.

Hence the error message.

See if the user name that owns the process on the Linux server associated with the client has permissions to read the file in question.

It would appear on the surface that the error message is direct and not cryptic.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Oliver Schwank
Valued Contributor

Re: CATIA V4 problem

Hello,

I had a similar problem once upon a time... perhaps it is related.

As far as I know the HPUX rpc.lockd implementation answers requests on UDP ports higher than 1024, the Linux rpc.lockd does it by default on ports lower than 1024. Please try to export the NFS volume on the Linux server with the option unsecure. After that the Linux box should answer to NFS lock requests on higher portnumbers.

CATIA does excessive file locking, so I assumme this could be the reason why you can write/read without CATIA. You should be able to reproduce the error without CATIA, if you do a file lock on a test file. This should lead to the same error as in CATIA.

Regards

Oli