topic Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA in QlikView

Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

Mon, 26 Jan 2026 21:26:37 GMT

Hello, please I need someone who knows about this give me a hand.

I spent several days trying to connect from the QlikView with some Cobol extension files. DAT, SEL, FD, VIX.

After much work and research and I have been able to connect using JDBC and HXTT Cobol JDBC driver.

But I did not return any data, and I get the error QVX_UNEXPECTED_END_OF_DATA

My connection is:

CUSTOM CONNECT TO "Provider = JDBCConnector.dll; jdbc: cobol 😕 / / C 😕 cfactura.dat; XUserId = fEDDLOD; XPassword = DQLERBB;"

Therefore selected the data as follows:

test:
SQL SELECT * FROM cfactura;/ /

At compile I get the following error:

"Customer reading error

test:

SQL SELECT * FROM cfactura.

And then I get the following window where I recognized the names of the fields and the structure but no data

I thank you very much any help on this topic.

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

rbecher — Sat, 05 May 2012 20:37:15 GMT

Hi Ricardo,

I played around a bit with it. The load is stopping because of dirty data in a numerical field. I changed all formats in the FD file to PIC X for test (see attachement) and it's loading. Of course, it's all dirty then..

I think something is wrong, either with the file encoding or the record format.

From which COBOL environment/dialect are the files?

- Ralf

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

Mon, 07 May 2012 15:38:19 GMT

Hi Ralf

Thanks for your help, I commented that my client is a Unix server platform

4.2.0 ACUCOBOL GT

The file types listed above and flat files where the table index is

separate and has a. vix correspond to a native form of a database on Fox that

handles the base as and the index table as .

Thanks.

RE.

2012/5/5 Ralf Becher <qliktech@sgaur.hosted.jivesoftware.com>

**
QlikCommunity <http://community.qlik.com/index.jspa> Re: Error
in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA created by Ralf
Becher <http://community.qlik.com/people/rbecher> in *Connectivity
and Data Sources* - View the full discussion<http://community.qlik.com/message/216586#216586>

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

rbecher — Mon, 07 May 2012 16:27:39 GMT

Hi Ricardo,

there are some wrong links in your answer by email. Please correct..

- Ralf

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

Mon, 07 May 2012 16:30:35 GMT

Hi Ralf

Thanks for your help, I commented that my client is a Unix server platform

4.2.0 ACUCOBOL GT

The file types listed above and flat files where the table index is

separate and has a. vix correspond to a native form of a database on Fox

that handles the base as .dba and the index table as . idx.

Thanks.

RE.

2012/5/7 Ralf Becher <qliktech@sgaur.hosted.jivesoftware.com>

**
QlikCommunity <http://community.qlik.com/index.jspa>
Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA created by Ralf
Becher <http://community.qlik.com/people/rbecher> in *Connectivity
and Data Sources* - View the full discussion<http://community.qlik.com/message/216882#216882>

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

rbecher — Tue, 08 May 2012 16:56:15 GMT

I read in the HXTT docu that only AcuCOBOL version 3 is supported. I sent a request to HXTT if they can give an advice..

- Ralf

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

rbecher — Wed, 09 May 2012 05:24:02 GMT

Hi Ricardo,

this is what I got from HXTT support:

"Checked. It's 108250 rows in that cfactura.dat file. Itseems that indices.fd and indices.sel has no relation with cfactura table.

cfactura.dat missed its index file, for instance,cfactura.vix .

Because cfactura.data is using unknown compression, andwe need an uncompression dat file( or txt output file) to verify. If possible,please provide such a sample."

So, please take a look after the file cfactura.vix and upload it here or send it to me for building the test case:

ralf.becher@tiq-solutions.de

- Ralf

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

Wed, 09 May 2012 17:25:10 GMT

Hi Ralf

Thank you very much for your help on this issue.

I commented that I do not have the file factura.vix, I have only one file

that I uploaded secuenci.vix.

I have tried to connect using the following link:

"CUSTOM CONNECT TO" Provider = JDBCConnector.dll; jdbc: cobol 😕 / / C 😕

secuenci.vix; XUserId = IZdCAQC; XPassword = EBNeRbB; "

But I get the following error.

"Need Cobol source code file, Copybook file, file FD, SEL file, or CREATE

TABLE sql table to define the structure of C: \ secuenci.vix

SQL SELECT * FROM secuenci ".

That is what I understand is that the connector uses file extension needs

FD. SEL.TXT, but does not recognize those who have the. Vix

The only solution I see is ask the customer to realize a manual labor to

export data to txt extension by vutil32 program, and make a connection in

the QlikView to take those flat files.

Waiting for your comments

Thank you.

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

rbecher — Wed, 09 May 2012 17:34:27 GMT

Hi Ricardo,

I will try to play around with this .vix file.

The support also stated that the data file cfactura.dat has an unknown compression. Is there any uncompressed version of the file?

- Ralf

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

Wed, 09 May 2012 17:52:49 GMT

Hi Ralf

I have attached the original files that I sent the customer, are 3 files, a

indice.dat, secuenci.dat and secuenci.vix.

Apparently secuencia.vix and index.dat are complements

I translated what the client told me about this topic:

"Attached is a text file but has included the index. It's called INDEXES.

This file type corresponds to a version lower than we currently have.

In our Unix server platform handle ACUCOBOL GT 4.2.0 file types mentioned

above and flat files where the table index is separate and has a. Vix. As I

was saying is the native form of a Fox database that handles the base as [.

Dba] and the index table as . An example of this is the file that

secuenci.vix secuenci and attachment."

thanks

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

Wed, 09 May 2012 17:56:25 GMT

I correct the brackets I get error

Hi Ralf

I have attached the original files that I sent the customer, are 3 files, a

indice.dat, secuenci.dat and secuenci.vix.

Apparently secuencia.vix and index.dat are complements

I translated what the client told me about this topic:

"Attached is a text file but has included the index. It's called INDEXES.

This file type corresponds to a version lower than we currently have.

In our Unix server platform handle ACUCOBOL GT 4.2.0 file types mentioned

above and flat files where the table index is separate and has a. Vix. As I

was saying is the native form of a Fox database that handles the base as .

Dba and the index table as . Idx. An example of this is the file that

secuenci.vix secuenci and attachment."

thanks

Saludos cordiales

Ricardo Escobar Duque

*Qlikview Consultant Specialist *

QlikView - Authorized reseller

tfno. (593-2) 227 1333

cel. (593) 09 90 48 997

e-mail: rescobar@cliksoft.com.ec <hpelaez@cliksoft.com.ec>

www.cliksoft.com.ec

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

rbecher — Thu, 10 May 2012 06:03:57 GMT

The file secuenci.vix doesn't belong to cfactura.dat .

Please check whether there's a vutil (vutil32.exe for Windows) on AcuCobol installationdirectory, which can rebuild vix for it.

- Ralf

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

Thu, 10 May 2012 17:14:27 GMT

Hi Ralf

I talked to my client and we think a solution, which includes transforming

the data into flat files that can read QlikView, using vutil32.

My client has an aging infrastructure and old that needs to be modernized,

we expect this project of QlikView will be a start to helps changes this

infrastructure.

Thank you very much all your support on this issue.

Best regards.

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

rbecher — Sun, 13 May 2012 18:26:40 GMT

Hi Ricardo,

however, can you create a .vix file for cfactura.dat that I can finish this test case? I'm still working out a solution for this with HXTT. Could be helpful for other clients also.

Best regards,

Ralf

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

rbecher — Mon, 14 May 2012 08:21:24 GMT

Ricardo,

the problem is fixed now after HXTT sent a new version. You can download the example here: http://bit.ly/JaT1zp

Although there are still some corrupted or incorrect numericals in the file which are skipped with the parameterignoreDirtyData=true.

I hope this helps!

- Ralf

Re: Error in connection JDBC-COBOL --- QVX_UNEXPECTED_END_OF_DATA

Mon, 14 May 2012 16:55:50 GMT

Hi Ralf

Thanks for the information!

I downloaded the new version of HXTT, modify the URL of the connection

including :

ignoreDirtyData=true & connector.ignoreFetchErrors=true

The URL Connection :

CUSTOM CONNECT TO

"Provider=JDBCConnector.dll;jdbc:cobol:///C:/cfactura.dat?ignoreDirtyData=true&connector.ignoreFetchErrors=true;XUserId=XKfTSeB;XPassword=ALadULC;";

It works!, Get information cfactura.dat.

thank you very much Ralf.

RE.