Strange entries in IMAGE DB

[Leonard_Berkowitz@harvardpilgrim.org]

--0__=4E4ApF909maX3LZ6xSyMeqdgQSd3G90gaEwNUdUeasBp7kao3uemHSr4
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline



There is nothing to stop some application from adding an entry to your data base
where the data for a particular field does not correspond to either the
TurboImage item definition or the PowerHouse definition.

For example, a COBOL program could move low-values (binary zeroes) to the 01
(record level) and DBPUT to the dataset and you would have all garbage as a
result. Nothing would cough until you tried to read the data in some formatted
way.

Check to see whether there is some way that data can be written not via
PowerHouse
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax:   617-509-3737
pager: 781-226-2431







Friedrich.Harasleben@oekv.com on 07/07/2000 05:37:21 AM
                                                                                
                                                                                
                                                                                


                                                              
                                                              
                                                              
 To:      powerh-l@sphere.swau.edu                            
                                                              
 cc:      (bcc: Leonard Berkowitz/CORP/HPHC)                  
                                                              
                                                              
                                                              
 Subject: Strange entries in IMAGE DB                         
                                                              







Dear Listers

We have a problem in our database, with some strange entries in an IMAGE
field.
We are using POWERHOUSE 8.19.C3.

RISOBPOSKEY   =1144  3964  169112
AENDATUM         =Ar 
--0__=4E4ApF909maX3LZ6xSyMeqdgQSd3G90gaEwNUdUeasBp7kao3uemHSr4
Content-type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-transfer-encoding: quoted-printable


=C1  <=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D this should actually b=
e a DATE!!!!

The field is defined as Z6 on TurboImage side and as ZDATE in the PH
Dictionary.

Is there any know problem??

regards
Friedrich

=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D=
 =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D=
 =3D =3D
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau=
.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.=
edu
This list is closed, thus to post to the list, you must be a subscriber=