JMP0811I-U Fujitsu runtime error after compiling Fujitsu COBOL with DB2 SQL: cause/remedy?

JMP0811I-U Fujitsu runtime error after compiling Fujitsu COBOL with DB2 SQL: cause/remedy?

Im able to on Windows XP precompile, compile and link a sample Fujitsu NetCobol COBOL test program which contains embedded SQL. This test program is to read and display the number of rows in a DB2 UDB 9.5 on Linux database table. At runtime I get following error message: JMP0811I-U PID:... TID:... FAILURE IN LINKAGE RULES OR PARAMETER OF THE sqlgstrt PROGRAM. PGMDB2TST1 The precompile source code this error refers to looks as follows: ... in WORKING-STORAGE section: 01 SQLA-PROGRAM-ID. 05 SQL-PART1 pic 94 COMP-5 value 172. 05 SQL-PART2 pic X6 value AEAMAI. 05 SQL-PART3 pic X24 value gBSdTdJY01111 2 . 05 SQL-PART4 pic 94 COMP-5 value 13. 05 SQL-PART5 pic X13 value ADMINISTRATOR. 05 SQL-PART6 pic X115 value LOW-VALUES. 05 SQL-PART7 pic 94 COMP-5 value 8. 05 SQL-PART8 pic X8 value COBOLDB. 05 SQL-PART9 pic X120 value LOW-VALUES. .. in PROCEDURE DIVISION: EXEC SQL CONNECT TO :DB-SERVER USER :DB-USER USING :DB-PWD END-EXEC CALL sqlgstrt USING BY CONTENT SQLA-PROGRAM-ID BY VALUE 0 BY REFERENCE SQLCA Does anybody know what this error message means

The error description was due to: the CHECKLINKAGE compiler option only available in NetCOBOL for Windows, not for Linux without this option, the error is still there, but even less descriptive The actual error was due to: the CALL sqlgstrt USING ... generated by the DB2 precompiler implies the wrong COBOL calling convention manually changing the calls to CALL sqlgstrt WITH STDCALL LINKAGE USING... has resolved the runtime error This solution implies changing the precompiler results though, so Im still in search of a DB2 precompiler option to generate the right CALLs.

Комментарии

Отправить комментарий

Популярные сообщения из этого блога

Skipping acquire of configured file 'contrib/binary-i386/Packages' as repository … doesn't support architecture 'i386'

Skipping acquire of configured file 'contrib/binary-i386/Packages' as repository … doesn't support architecture 'i386' I installed Ubuntu 18.04 and then while installing Virtualbox i get the i386 error message after I did: sudo apt-get update Get:1 http:nl.archive.ubuntu.comubuntu bionic InRelease 242 kB Hit:2 http:security.ubuntu.comubuntu bionic-security InRelease Hit:3 http:ppa.launchpad.netdanielrichter2007grub-customizerubuntu bionic InRelease Hit:4 http:nl.archive.ubuntu.comubuntu bionic-updates InRelease Hit:5 http:nl.archive.ubuntu.comubuntu bionic-backports InRelease Get:6 http:download.virtualbox.orgvirtualboxdebian bionic InRelease 4429 B Get:7 http:download.virtualbox.orgvirtualboxdebian bioniccontrib amd64 Packages 1426 B Fetched 248 kB in 1s 209 kBs Reading package lists... Done N: Skipping acquire of configured file contribbinary-i386Packages as repository http:download.virtualbox.orgvirtualboxdebian bionic InRelease doesnt support architecture i386 ...
Далее...

Connection string for MariaDB using ODBC

Connection string for MariaDB using ODBC What is the connection string for using MariaDB with ODBC Im guessing its something like DRIVERMariaDB ODBC 5.1 Driver; SERVERLOCALHOST; PORT3306; DATABASEDatabaseName; UIDroot; PASSWORDpassword;OPTION3; Connection strings seems to show strings for MySQL but not MariaDB. MariaDB seems to have a lot of connection strings for Access, SQL Lite, excel, etc ... What have I missed Although this is late answer, but MariaDB have that documented here SQLWCHAR ConnStr LDriverMariaDB ODBC 2.0 Driver;Serverlocalhost;UIDodbc_user;PWDodbc_pw;DBodbc_test;Port3306;
Далее...

Celery like system based on django channels

Celery like system based on django channels According to the docs of django channels: http:channels.readthedocs.ioenlatestconcepts.htmlhighlightcelerynext-steps One thing channels do not do, however, is guarantee delivery. If you need certainty that tasks will complete, use a system designed for this with retries and persistence e.g. Celery, or alternatively make a management command that checks for completion and re-submits a message to the channel if nothing is completed rolling your own retry logic, essentially. I worked with celery some years ago. Yes, it is great, it is big, it is too much. I would like to avoid it. I am searching a simple tasks queue with guarantee delivery and a re-submission on failure. An other alternative would be python-rq. But this has other disadvantages like using pickle data format instead of json. A friend gave me an advice: https:github.comfurious-lukedjango-cq Looks good. From the docs An attempt to implement a distributed task queue ...
Далее...