The given test case relies on components of the Zend Framework.

Simple test case:
-----------------

//CREATE TABLE
//    newTestTable
//    (
//        col1 INTEGER,
//        col2 lvarchar,
//        PRIMARY KEY (col1)
//    )
//INSERT INTO newTestTable (col1, col2) VALUES (1, 'Das ist ein langer Text. Das ist ein langer Text. Das ist ein langer Text.');


$dbh = new PDO("ibm:DRIVER={IBM DB2 ODBC DRIVER};HOSTNAME=ourhostname;PORT=1234;DATABASE=dbname;PROTOCOL=TCPIP;", "", "");

print "Connection Established!\n";
print "Driver name: " . $dbh->getAttribute(PDO::ATTR_DRIVER_NAME) . "\n\n";

$stmt = $dbh->prepare("select col1, col2 from newTestTable where col1 = 1;");
$stmt->execute();

while ($row = $stmt->fetch(PDO::FETCH_ASSOC)) {
    print_r($row);
    print "\n";
}

print "After Fetch\n";

print "PDO Error: " . $dbh->errorCode() . "\n";
print_r($dbh->errorInfo());
print "\n";

print "Statement Error: " . $stmt->errorCode() . "\n";
print_r($stmt->errorInfo());
print "\n";

$dbh = null;

Output:
-------

Connection Established!
Driver name: ibm

After Fetch
PDO Error: 07006
Array
(
    [0] => 07006
    [1] => -99999
    [2] => [IBM][CLI Driver] CLI0102E  Invalid conversion. SQLSTATE=07006 (SQLFetchScroll[-99999] at /builddir/build/BUILD/PDO_IBM-1.3.2/ibm_statement.c:1156)
)

Statement Error: 07006
Array
(
    [0] => 07006
    [1] => -99999
    [2] => [IBM][CLI Driver] CLI0102E  Invalid conversion. SQLSTATE=07006 (SQLFetchScroll[-99999] at /builddir/build/BUILD/PDO_IBM-1.3.2/ibm_statement.c:1156)
)

I added the patch add-long-varchar-support which I found at http://www.iiug.org/opensource/ "The Open-Source for Informix Project".

We already patched the driver and installed it on our development server. The test script I posted now runs without an error. With this patch it is possible to read data from LVARCHAR columns in Informix with this driver.

What's the status here?  Has that been fixed in the meantime?  If
not, I suggest to submit a pull request[1].

[1] <https://github.com/php/pecl-database-pdo_ibm>

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.