Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 1475
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

dbWriteSkill encounter : error close:error closing file

rockyicer

hi, 

  i am using the code:

cvId=dbOpenCellViewByType("test" "otcind" "layout" "maskLayout")

dbWriteSkill(cvId "/home/s01/a.il" "w" "4.4") 

to dump a graphical pcell skill code in IC616,

when i run the first skill sentence: cvId=dbOpenCellViewByType("test" "otcind" "layout" "maskLayout") 

the feedback is OK.  but when i run the second one: dbWriteSkill(cvId "/home/s01/a.il" "w" "4.4") 

 the CIW feedback the following error:

*Error* close: Error closing file

I have check the path:/home/s01/a.il and its disk space is not full.  This post (support.cadence.com/.../ArticleAttachmentPortal;pageName=ArticleContent&sq=005d0000005nekwAAA_201722416744619) says it has relation to the /tmp file. (I don't have access to the /tmp file.) Is it ture? and how can I solve this problem?

thanks in advance!

  • That article is about the stream interface, and not dbWriteSkill - so it's not really relevant when talking about /tmp. I don't believe dbWriteSkill writes anywhere other than the path you specify - it writes two files if it's a pcell - the cellView dump, plus the pcell code. Both are in the same directory.

    I've found no reports of this. It might be that the disk isn't full, but maybe your quota is exceeded and so you can't write any more data? Errors during closing of files are pretty rare... the most likely situation is that when trying to flush the buffer and actually write to disk it can't because it's not allowed to write any more to the disk. Generally commands such as "quota -v" would tell you your quota situation - but it's probably best to check with your IT in case the quotas have been set up differently (if that's what it is).

    Regards,

    Andrew.

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.