× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Set up like this:  (o.k. it's fixed length on this example, somebody help me
with the varying field here)

01  ********************************************************************
02  *  CALLP PROTOTYPES                                                *
03  ********************************************************************
04  * QCMDEXC
05 D
06 D CMD             PR                  EXTPGM('QCMDEXC')
07 D  COMMANDSTR                 1024A   CONST
08 D  COMMANDLENGTH                15P 5 CONST
09 D
10 D COMMAND         S           1024A
11 D LENGTH          S             15P 5 INZ(1024)
12  ********************************************************************
03 C                   EVAL      COMMAND = 'OVRDBF MILUPSI1 SHARE(*YES)'
04 C                              + ' SEQONLY(*NO)'
05 C                   CALLP     CMD(COMMAND:LENGTH)


 -----Original Message-----
<snip>

the
problem is?  You CANNOT pass a variable length field to QCMDEXC
using the CALL/PARM opcodes. It can only be a fixed-length field.
Making it variable length in this context is of no value, but if you
really, really want to use a variable length field, then you MUST
create a prototype for the call to QCMDEXC with each parm being a
CONST value. Then you can pass your varying field without a problem.
But it will continue to fail on the CALL/PARM every time as long as
your parameter is VARYING.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.