Hex x'00' data and the .NET provider

I'm working on an iSeries Experts Journal article and I've run into an
interesting situation.

It seems that the .NET data provider has an issue with character fields
that contain a x'00' value. In my case I'm returning the list section of
a user space generated from the list job schedule entry API. Some of the
fields can contain x'00'. 

When I attempt to use these fields on the .NET side I get an
iDB2ConversionException exception thrown. And I don't see a way to test
for this problem before I use the field. I've gotten around this problem
by using the fields in a try/catch block, but I'd rather solve the root
problem. 

Has anyone see this issue before and found a way around it? Perhaps
something on the connection string.

It would seem to be that x'00' is still valid character data.

-Walden

------------
Walden H Leverich III
President & CEO
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)