Db2

Db2

Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only

  • 1.  COBOL STORED PROC RECEIVING -444 SQLSTATE 42724 called thru Java

    Posted Fri April 04, 2025 11:57 AM
    Hallo, Developer has created a COBOL STORED PROCEDURE using BLOB . When he calls it thru a Java program he gets -444 . External name is correct. SP loadlib is in WLM address space STEPLIB. I checked and Module is in LOADLIB .  Is there anything on the JAVA side that needs to be configured ?  
    Input parameter is defined as a type of BLOB ( 2  G)  with a blank between the 2 and the G . Can this be the cause ?  There are other SP which work. Only difference is the BLOB . 
    TIA

    Thanks ! Xie Xie ! Magizchi! Obrigada ! Gracias! Merci ! Salamat !

     

    Vacation Alert :

    OOO : DEC 25 JAN 1;2,27

     

    Claudia Cristina Paredes Nunes                                                                   

    ZOS DB2 DBA

    KYNDRYL  

    E-mail: claudiacpn@kyndryl.com  

    mobile: +5521986536311

    Technical Specialist Profession Certification - Level 1                                     Professional Certification: Certified Technical Specialist, Product Support

     



  • 2.  RE: COBOL STORED PROC RECEIVING -444 SQLSTATE 42724 called thru Java

    Posted Fri April 04, 2025 12:35 PM
    Edited by Jan Nelken Fri April 04, 2025 12:36 PM

    Did you consider -444 explanation?

    https://www.ibm.com/docs/en/db2-for-zos/13.0.0?topic=codes-444


    I would replace "2 G" with "2G" or whatever format is correct...

    ------------------------------
    Jan Nelken
    Support engineer
    Persistent Systems Ltd
    Cracow
    +48 783 109 863
    ------------------------------

    Original Message


  • 3.  RE: COBOL STORED PROC RECEIVING -444 SQLSTATE 42724 called thru Java

    Posted Fri April 04, 2025 01:22 PM

    hallo,I checked with the other DBA & she said the blank was DB2's . That she wrote 2G. I have looked at the steplibs in the WLM job, the compile job, checked the existence of  modules in the load llib . 



    ------------------------------
    Claudia Cristina Paredes Nunes
    ------------------------------

    Original Message


  • 4.  RE: COBOL STORED PROC RECEIVING -444 SQLSTATE 42724 called thru Java

    Posted Fri April 04, 2025 01:47 PM

    I think I have found it. It is lack of storage in the WLM address space. 



    ------------------------------
    Claudia Cristina Paredes Nunes
    ------------------------------

    Original Message


  • 5.  RE: COBOL STORED PROC RECEIVING -444 SQLSTATE 42724 called thru Java

    Posted Fri April 04, 2025 02:43 PM

    Updating as It might help someone else . The programme had been linkedited with RMODE 24 so it was being loaded below the bar. It should be AMODE as 31 and RMODE as ANY . 



    ------------------------------
    Claudia Cristina Paredes Nunes
    ------------------------------

    Original Message


  • 6.  RE: COBOL STORED PROC RECEIVING -444 SQLSTATE 42724 called thru Java

    Posted Sat April 05, 2025 05:46 AM
    Edited by Jan Nelken Sat April 05, 2025 05:47 AM

    I am very rusty in m/f world - been there xxxty years ago. I thought that AMODE(31) and RMODE(ANY)  are default setting for any decent compiler/LE.
    Glad that you solved it...



    ------------------------------
    Jan Nelken
    Support engineer
    Persistent Systems Ltd
    Cracow
    +48 783 109 863
    ------------------------------

    Original Message


  • 7.  RE: COBOL STORED PROC RECEIVING -444 SQLSTATE 42724 called thru Java

    Posted Mon April 07, 2025 04:21 AM

    Olá Claudia Cristina, Jan, 

    I had the same -444 sqlcode while executing the sample SP, DSN8.DSN8ED2 (language C).

    In my case, at the end, the problem was that I hadn't sent the new built module to the WLM load library.

    So for me the explanation for -444 sqlcode was totally right, the routine was fine, the package was there, but not the module:

    Db2 received an SQL CALL statement for a stored procedure or an SQL statement containing an invocation of a user-defined function, and found the row in the SYSIBM.SYSROUTINES catalog table associated with the requested procedure name. However, the MVS load module identified in the EXTERNAL_NAME column of the SYSIBM.SYSROUTINES row could not be found.

    Thanks,



    ------------------------------
    Soledad Martinez
    Db2 z/OS System Programmer
    Volkswagen Group Services
    Salinas - Asturias
    ------------------------------

    Original Message


Related Content