Topic
  • 3 replies
  • Latest Post - ‏2016-02-05T07:29:28Z by Kirsi
Kirsi
Kirsi
8 Posts

Pinned topic WebService generation problem when Stored Procedures have OUT parameters

‏2012-10-23T07:48:53Z |
Hi all!

Hope you can help me with my problem this time too.

I tried to generate a Web Service from Stored Procedure with two OUT parameters following with seven IN parameters (all were char datatypes).

Operation M123TEST: parameter count in statement string (9) does not match parameter count of statement metadata (27)

Can you help? If you have found any workarounds for this I would really appreciate if you share it. We really need to build a WebService on top of this SP and I thought this would be the easiest way. It seems that I just found another bug with Data Studio WebService part again...

Enthusiastically waiting for new version of Data Studio :), Best Regards:

Kirsi
Updated on 2012-10-23T11:08:17Z at 2012-10-23T11:08:17Z by Kirsi
  • Kirsi
    Kirsi
    8 Posts

    Re: WebService generation problem when Stored Procedures have OUT parameters

    ‏2012-10-23T11:08:17Z  
    Sorry about the inconvenience!
    It is not about the OUT parameters, it is the number of parameters.

    I will create another thread of this.

    Br,
    Kirsi
  • Loydarrr
    Loydarrr
    2 Posts

    Re: WebService generation problem when Stored Procedures have OUT parameters

    ‏2016-02-05T00:24:19Z  

    What was the resolution on this topic, the other thread?

    I' running Data Studio 4.1.2 using z/OS Connect to deploy SQL that will call DSNUTILU SP.

    I can call it fine from SQL Editor , and get the results from the RUNSTATS just fine but when I tried Deployment for z/OS Connect I get the following message:  

    "Deploying Web Service 'Webservive2' has encountered a problem.

     Operation DSNUTILURUNSTATS: parameter count in statement string (1) does not match parameter count of statement metadata (928)

    Can someone help clarifying what is going on here? DataStudio is not helpful when you encounter issues like this (very frustrating).

     

    Here is the successful execution from SQL Editor :

     

    CALL SYSPROC.DSNUTILU( 'IDBXSLRRST', 'NO','RUNSTATS TABLESPACE DSN8D10A.DSN8S10E TABLE ALL SHRLEVEL CHANGE SORTDEVT SYSDA SORTNUM 6 SAMPLE 25 INDEX ALL', ? )

    and the result from the call:

    SEQNO TEXT                                                                                                               
     ----- ------------------------------------------------------------------------------------------------------------------ 
         1 1DSNU000I    035 12:17:41.87 DSNUGUTC - OUTPUT START FOR UTILITY, UTILID = IDBXSLRRST                             
         2  DSNU1045I   035 12:17:42.08 DSNUGTIS - PROCESSING SYSIN AS UNICODE UTF-8                                         
         3 0DSNU050I    035 12:17:44.08 DSNUGUTC -  RUNSTATS TABLESPACE DSN8D10A.DSN8S10E TABLE ALL SHRLEVEL CHANGE SORTDEVT 
         4  SYSDA SORTNUM 6 SAMPLE 25 INDEX ALL                                                                              
         5  DSNU610I  DABA 035 12:18:05.35 DSNUSUTP - SYSTABLEPART CATALOG UPDATE FOR DSN8D10A.DSN8S10E SUCCESSFUL           
         6  DSNU610I  DABA 035 12:18:05.59 DSNUSUPT - SYSTABSTATS CATALOG UPDATE FOR DSN81010.EMP SUCCESSFUL                 
         7  DSNU610I  DABA 035 12:18:05.70 DSNUSUPC - SYSCOLSTATS CATALOG UPDATE FOR DSN81010.EMP SUCCESSFUL                 
         8  DSNU610I  DABA 035 12:18:06.05 DSNUSUTB - SYSTABLES CATALOG UPDATE FOR DSN81010.EMP SUCCESSFUL                   
         9  DSNU610I  DABA 035 12:18:06.45 DSNUSUCO - SYSCOLUMNS CATALOG UPDATE FOR DSN81010.EMP SUCCESSFUL                  
        10  DSNU610I  DABA 035 12:18:06.50 DSNUSUTS - SYSTABLESPACE CATALOG UPDATE FOR DSN8D10A.DSN8S10E SUCCESSFUL          
        11  DSNU610I  DABA 035 12:18:09.18 DSNUSUIP - SYSINDEXPART CATALOG UPDATE FOR DSN81010.XEMP1 SUCCESSFUL              
        12  DSNU610I  DABA 035 12:18:09.21 DSNUSUPI - SYSINDEXSTATS CATALOG UPDATE FOR DSN81010.XEMP1 SUCCESSFUL             
        13  DSNU610I  DABA 035 12:18:09.84 DSNUSUPC - SYSCOLSTATS CATALOG UPDATE FOR DSN81010.XEMP1 SUCCESSFUL               
        14  DSNU610I  DABA 035 12:18:09.85 DSNUSUIP - SYSINDEXPART CATALOG UPDATE FOR DSN81010.XEMP2 SUCCESSFUL              
        15  DSNU610I  DABA 035 12:18:09.85 DSNUSUCO - SYSCOLUMNS CATALOG UPDATE FOR DSN81010.XEMP1 SUCCESSFUL                
        16  DSNU610I  DABA 035 12:18:09.87 DSNUSUIX - SYSINDEXES CATALOG UPDATE FOR DSN81010.XEMP1 SUCCESSFUL                
        17  DSNU610I  DABA 035 12:18:09.87 DSNUSUCO - SYSCOLUMNS CATALOG UPDATE FOR DSN81010.XEMP2 SUCCESSFUL                
        18  DSNU610I  DABA 035 12:18:09.87 DSNUSUIX - SYSINDEXES CATALOG UPDATE FOR DSN81010.XEMP2 SUCCESSFUL                
        19  DSNU610I  DABA 035 12:18:11.52 DSNUSUCD - SYSCOLDIST CATALOG UPDATE FOR DSN81010.XEMP2 SUCCESSFUL                
        20  DSNU620I  DABA 035 12:18:11.57 DSNUSEOF - RUNSTATS CATALOG TIMESTAMP = 2016-02-04-12.17.45.989047                
        21  DSNU010I    035 12:18:13.80 DSNUGBAC - UTILITY EXECUTION COMPLETE, HIGHEST RETURN CODE=0  

    Any help or suggestions will be greatly appreciated.

  • Kirsi
    Kirsi
    8 Posts

    Re: WebService generation problem when Stored Procedures have OUT parameters

    ‏2016-02-05T07:29:28Z  
    • Loydarrr
    • ‏2016-02-05T00:24:19Z

    What was the resolution on this topic, the other thread?

    I' running Data Studio 4.1.2 using z/OS Connect to deploy SQL that will call DSNUTILU SP.

    I can call it fine from SQL Editor , and get the results from the RUNSTATS just fine but when I tried Deployment for z/OS Connect I get the following message:  

    "Deploying Web Service 'Webservive2' has encountered a problem.

     Operation DSNUTILURUNSTATS: parameter count in statement string (1) does not match parameter count of statement metadata (928)

    Can someone help clarifying what is going on here? DataStudio is not helpful when you encounter issues like this (very frustrating).

     

    Here is the successful execution from SQL Editor :

     

    CALL SYSPROC.DSNUTILU( 'IDBXSLRRST', 'NO','RUNSTATS TABLESPACE DSN8D10A.DSN8S10E TABLE ALL SHRLEVEL CHANGE SORTDEVT SYSDA SORTNUM 6 SAMPLE 25 INDEX ALL', ? )

    and the result from the call:

    SEQNO TEXT                                                                                                               
     ----- ------------------------------------------------------------------------------------------------------------------ 
         1 1DSNU000I    035 12:17:41.87 DSNUGUTC - OUTPUT START FOR UTILITY, UTILID = IDBXSLRRST                             
         2  DSNU1045I   035 12:17:42.08 DSNUGTIS - PROCESSING SYSIN AS UNICODE UTF-8                                         
         3 0DSNU050I    035 12:17:44.08 DSNUGUTC -  RUNSTATS TABLESPACE DSN8D10A.DSN8S10E TABLE ALL SHRLEVEL CHANGE SORTDEVT 
         4  SYSDA SORTNUM 6 SAMPLE 25 INDEX ALL                                                                              
         5  DSNU610I  DABA 035 12:18:05.35 DSNUSUTP - SYSTABLEPART CATALOG UPDATE FOR DSN8D10A.DSN8S10E SUCCESSFUL           
         6  DSNU610I  DABA 035 12:18:05.59 DSNUSUPT - SYSTABSTATS CATALOG UPDATE FOR DSN81010.EMP SUCCESSFUL                 
         7  DSNU610I  DABA 035 12:18:05.70 DSNUSUPC - SYSCOLSTATS CATALOG UPDATE FOR DSN81010.EMP SUCCESSFUL                 
         8  DSNU610I  DABA 035 12:18:06.05 DSNUSUTB - SYSTABLES CATALOG UPDATE FOR DSN81010.EMP SUCCESSFUL                   
         9  DSNU610I  DABA 035 12:18:06.45 DSNUSUCO - SYSCOLUMNS CATALOG UPDATE FOR DSN81010.EMP SUCCESSFUL                  
        10  DSNU610I  DABA 035 12:18:06.50 DSNUSUTS - SYSTABLESPACE CATALOG UPDATE FOR DSN8D10A.DSN8S10E SUCCESSFUL          
        11  DSNU610I  DABA 035 12:18:09.18 DSNUSUIP - SYSINDEXPART CATALOG UPDATE FOR DSN81010.XEMP1 SUCCESSFUL              
        12  DSNU610I  DABA 035 12:18:09.21 DSNUSUPI - SYSINDEXSTATS CATALOG UPDATE FOR DSN81010.XEMP1 SUCCESSFUL             
        13  DSNU610I  DABA 035 12:18:09.84 DSNUSUPC - SYSCOLSTATS CATALOG UPDATE FOR DSN81010.XEMP1 SUCCESSFUL               
        14  DSNU610I  DABA 035 12:18:09.85 DSNUSUIP - SYSINDEXPART CATALOG UPDATE FOR DSN81010.XEMP2 SUCCESSFUL              
        15  DSNU610I  DABA 035 12:18:09.85 DSNUSUCO - SYSCOLUMNS CATALOG UPDATE FOR DSN81010.XEMP1 SUCCESSFUL                
        16  DSNU610I  DABA 035 12:18:09.87 DSNUSUIX - SYSINDEXES CATALOG UPDATE FOR DSN81010.XEMP1 SUCCESSFUL                
        17  DSNU610I  DABA 035 12:18:09.87 DSNUSUCO - SYSCOLUMNS CATALOG UPDATE FOR DSN81010.XEMP2 SUCCESSFUL                
        18  DSNU610I  DABA 035 12:18:09.87 DSNUSUIX - SYSINDEXES CATALOG UPDATE FOR DSN81010.XEMP2 SUCCESSFUL                
        19  DSNU610I  DABA 035 12:18:11.52 DSNUSUCD - SYSCOLDIST CATALOG UPDATE FOR DSN81010.XEMP2 SUCCESSFUL                
        20  DSNU620I  DABA 035 12:18:11.57 DSNUSEOF - RUNSTATS CATALOG TIMESTAMP = 2016-02-04-12.17.45.989047                
        21  DSNU010I    035 12:18:13.80 DSNUGBAC - UTILITY EXECUTION COMPLETE, HIGHEST RETURN CODE=0  

    Any help or suggestions will be greatly appreciated.

    Other thread mentioned in earlier post is this:

    https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014900879&ps=25

    At that time, I found the reason by myself. It was  not about the out parameters, it was about the number of parameters that was a problem in version 3.2.x. I believe they made lots of corrections to WS generation to the version 4.0 and this must have been one of them. 

    No idea though what would be wrong in your WS generation.

    Br, Kirsi