Re: Comet Services 16

[ Follow Ups ] [ Post Followup ] [ Forum ]

Posted by Barbara Brazil on May 03, 2016 at 10:35:55:

In Reply to: Re: Comet Services 16 posted by Tom Fulton on May 03, 2016 at 08:40:43:


This is weird. There are only a couple of ways you can get E32 on a WRITE:
1) Doing REWRITE and the key doesn't already exist
2) Doing WRITE with no key specified and no EXTRACT pending on legacy keyed file
Neither of these seem to apply to you.

Some questions:
It looks like this program was compiled with C16. Is that correct?
Do you know if the error occurred on the first write for customer RO6202? Is that a valid customer number?
Is this file accessed by any program other than WWCCSF that may have been running concurrently?

I really would like to see a compiled listing that matches the error address. If you made a change to an include file in the declarative section that would not affect executable addresses. Something seems to be different in the executable code.

We don't think there's an incompatibility between the newer Comet release and the older Server release. But if you want to revert their Comet back to whatever they were on previously I can get you whichever version you want. That might be an interesting test.

Follow Ups:

Post a Followup



What is the name of the main Signature System's Product?  


Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):

Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.

[ Follow Ups ] [ Post Followup ] [ Forum ]