CPC3206 becomes CPF32C6?!? When and why did THAT happen? -- MIDRANGE-L

Subject: CPC3206 becomes CPF32C6?!? When and why did THAT happen?
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Tue, 30 Jun 2009 16:30:15 -0700
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Given a CL program that disengages a bunch of triggers, I suddenly find a malfunction that I traced to the error message being completely different from what I was expecting: I was monitoring for CPC3206, but on the customer box, I'm getting CPF32C6 (which our development box has never heard of) instead.

Anybody know when and/or why this change happened?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.