Image modification & PDL impact

[Deskin, Bob]

We read IMAGE data using the complete record method (I forget the exact
intrinsic syntax - it's been so long since I actually coded an intrinsic).
You're right when you say the positions must match. Also, the types must be
reasonably compatible if you want consistent results. Names do not have to
match. We do DBINFO calls to determine exactly what's in the database
whenever we need to know.

Bob Deskin              
PowerHouse Web Product Manager, Application Development Tools, Cognos Inc.
bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613) 727-1178
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA

-----Original Message-----
From: Leonard_Berkowitz@harvardpilgrim.org
[mailto:Leonard_Berkowitz@harvardpilgrim.org]
Sent: Wednesday, June 20, 2001 10:01 AM
To: Deskin, Bob
Subject: RE: Image modification & PDL impact




Bob Deskin wrote:

<<Well, the politically correct response is to keep your dictionary always
consistent with your database. Of course PowerHouse allows you to define
substructures in IMAGE even though IMAGE doesn't provide that.>>

Something else I've discovered. The field name in the TurboImage data base
and
the element name in the corresponding PHD record layout do not have to
match.
Apparently Powerhouse uses byte (column) offset for handling data. I do not
know
whether this applies if the field is a TurboImage key, but I suspect that
the
names do have to match in this instance.

I reviewing PDL source files and their matching data bases I found certain
inconsistencies in production. So I fixed them and some jobs blew up.

This note is not intended as a recommendation to introduce inconsistencies .
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax:   617-509-3737
pager: 781-226-2431