Oh, I was thinking there was a a QSYS.QCMDEXC which required the second
   parameter while the QSYS2 version did not.
    
   Nope, the QSYS2 version was just enhanced to not require a length to be
   passed. I think you have to use the QSYS2 version (which is basically a
   wrapper around the QSYS CL command).
    
    
   Sorry for the noise.
    
     ----- Original message -----
     From: "Tyler, Matt" <matt.tyler@xxxxxxxxxxxxxx>
     Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
     To: Midrange Systems Technical Discussion
     <midrange-l@xxxxxxxxxxxxxxxxxx>
     Cc:
     Subject: RE: CL Commands in SQL
     Date: Mon, Mar 4, 2019 2:56 PM
      
     Odd, because I do not find a QSYS version of QCMDEXC stored procedure.  
     So if you are allowed to run QSYS.CMDEXC() then IBM is doing something
     to the call and finding the QSYS2 version.  For me i cannot run a
     procedure named QSYS.QCMDEXC().   Its not found.
     -Matt
     -----Original Message-----
     From: MIDRANGE-L [[1]mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
     Behalf Of Kevin Adler
     Sent: Monday, March 4, 2019 1:49 PM
     To: midrange-l@xxxxxxxxxxxxxxxxxx
     Subject: Re: CL Commands in SQL
        The second, actually. Dave previously said he was using the QSYS2
     version
        while I was trying to suggest using the QSYS version.
         
          ----- Original message -----
          From: John Yeung <gallium.arsenide@xxxxxxxxx>
          Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
          To: Midrange Systems Technical Discussion
          <midrange-l@xxxxxxxxxxxxxxxxxx>
          Cc:
          Subject: Re: CL Commands in SQL
          Date: Mon, Mar 4, 2019 2:28 PM
           
          On Mon, Mar 4, 2019 at 2:54 PM Kevin Adler <kadler@xxxxxxxxxx>
     wrote:
          >
          >    The only thing I could think of is using QSYS.QCMDEXC instead
     of
          >    QSYS.QCMDEXC.
          I think the first of those was supposed to be QSYS2.QCMDEXC?
          John Y.
          --
          This is the Midrange Systems Technical Discussion (MIDRANGE-L)
     mailing
          list
          To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
          To subscribe, unsubscribe, or change list options,
          visit: [1][2]
https://lists.midrange.com/mailman/listinfo/midrange-l
          or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
          Before posting, please take a moment to review the archives
          at [2][3]
https://archive.midrange.com/midrange-l.
          Please contact support@xxxxxxxxxxxx for any subscription related
          questions.
          Help support midrange.com by shopping at amazon.com with our
     affiliate
          link: [3][4]
https://amazon.midrange.com
           
         
     References
        Visible links
        1. [5]
https://lists.midrange.com/mailman/listinfo/midrange-l
        2. [6]
https://archive.midrange.com/midrange-l
        3. [7]
https://amazon.midrange.com/
     --
     This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
     list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
     subscribe, unsubscribe, or change list options,
     visit: [8]
https://lists.midrange.com/mailman/listinfo/midrange-l
     or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
     Before posting, please take a moment to review the archives at
     [9]
https://archive.midrange.com/midrange-l.
     Please contact support@xxxxxxxxxxxx for any subscription related
     questions.
     Help support midrange.com by shopping at amazon.com with our affiliate
     link: [10]
https://amazon.midrange.com
     --
     This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
     list
     To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
     To subscribe, unsubscribe, or change list options,
     visit: [11]
https://lists.midrange.com/mailman/listinfo/midrange-l
     or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
     Before posting, please take a moment to review the archives
     at [12]
https://archive.midrange.com/midrange-l.
     Please contact support@xxxxxxxxxxxx for any subscription related
     questions.
     Help support midrange.com by shopping at amazon.com with our affiliate
     link: [13]
https://amazon.midrange.com
      
    
References
   Visible links
   1. mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx
   2. 
https://lists.midrange.com/mailman/listinfo/midrange-l
   3. 
https://archive.midrange.com/midrange-l
   4. 
https://amazon.midrange.com/
   5. 
https://lists.midrange.com/mailman/listinfo/midrange-l
   6. 
https://archive.midrange.com/midrange-l
   7. 
https://amazon.midrange.com/
   8. 
https://lists.midrange.com/mailman/listinfo/midrange-l
   9. 
https://archive.midrange.com/midrange-l
  10. 
https://amazon.midrange.com/
  11. 
https://lists.midrange.com/mailman/listinfo/midrange-l
  12. 
https://archive.midrange.com/midrange-l
  13. 
https://amazon.midrange.com/
As an Amazon Associate we earn from qualifying purchases.