varbinary(max) column using OpenESQL in .NET Core VS COBOL

Hi Peter,

I am not sure why you would need to convert the logic of the program as you should be able to recompile it for .NET as is and use the SQL Server ADO provider instead of ODBC. Are you having problems with this?

According to the OpenESQL docs, the max size of a column that can be used with a varbinary(max) column is 450MB.

I just tested this here, using static SQL instead of dynamic and it worked just fine and inserted a 400MB data item into my varbinary(max) column.

The following is from the docs:

SQL [TYPE] [IS] BLOB(lob-length)

Hi Chris,

Thanks for getting back to me. Yes I have changed my connection to use ADO instead of ODBC.

In the Native COBOL application we read the column in 65k blocks (the limit in OpenESQL) and store each of these blocks in a field pic x(65535). These are then output/appended to a character array using the withByteLengthValue option. This loop continues, appending to the character array until the read is complete.

When inserting/updating the information is extracted, in blocks, from a character array using “getValueWithSizeAtPosition”

I guess what I am looking at is what type of .NET object I can use to replace the native character array which I can interact with allowing me to continue using OpenESQL

I have tried the static SQL statements fetching the result into a byte array and that does seem to work correctly however we rely on the dynamic SQL quite heavily, via a generic program that gets used by a number of programs and to change this logic to use static statements is, unfortunately, not feasible.

Peter

For information, Peter your colleague Neil contacted me via email about this post, we have located the missing sample files and will provide that to Neil directly.