PxPlus User Forum

Twitter Twitter Twitter

Author Topic: Strange error 2  (Read 1229 times)

michaelgreer

  • Diamond Member
  • *****
  • Posts: 129
    • View Profile
Strange error 2
« on: December 08, 2020, 12:58:44 PM »
Customer running PVX 15.10.  This line of code is throwing an error 2:  2060 read (slist,key=this_name$,dom=2020).  Slist is a memory file.  No special attributes.  What would cause this to throw an error 2? I would think with a key specified (even if slits is 0 in length) the dom would trap an error 11.

Mike King

  • Diamond Member
  • *****
  • Posts: 3817
  • Mike King
    • View Profile
    • BBSysco Consulting
Re: Strange error 2
« Reply #1 on: December 08, 2020, 04:12:48 PM »
We looked at the logic in memory files and could not an error 2.  The only thing we can think of, assuming its really a memory file, might be if you had a pending IO to a file that returned an error 2 due to space exhaustion or the like.  Some file IO operations are buffered to improve performance.  Its possible when flushing a ending IO operation in background we received an error condition.

It could also be some form of embedded IO for the memory file that itself had the error 2. 

Can you also confirm you are running PVX 15.10 -- To the best of my knowledge there never was a PVX 15.10 -- there was a PxPlus 15.10 but not PVX 15.10.
Mike King
President - BBSysco Consulting
eMail: mike.king@bbsysco.com

michaelgreer

  • Diamond Member
  • *****
  • Posts: 129
    • View Profile
Re: Strange error 2
« Reply #2 on: December 10, 2020, 09:05:12 AM »
Mike,

My mistake. It was PxPlus 15.10. We only run PxPlus at this point.

Michael