<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c">
    <title>gmane.comp.lang.as400.c</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1842"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1841"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1840"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1839"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1838"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1837"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1836"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1835"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1834"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1833"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1832"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1831"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1830"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1829"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1828"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1826"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1825"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1824"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1823"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.lang.as400.c/1822"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1842">
    <title>Re: AS400 C++ calling COBOL - MCH0802</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1842</link>
    <description>&lt;pre&gt;It would appear that you might need to also from that same api figure out if it is a CBL program because they look like they might be the ones that are the strictest on parms.
 
But the issue with the whole thing, is what if I have a using 1 2 3 that calls a using 1 2 3 4 5 from the cobol program?  or the called program has variable space right behind the parms?  You would need also to save your leftover parms or refresh them between each call, right?  cuz I am thinking I got some trashed parms there coming back into the programs all over for the next call.     
 

       
&lt;/pre&gt;</description>
    <dc:creator>Ron Unknown</dc:creator>
    <dc:date>2013-05-10T17:58:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1841">
    <title>Re: AS400 C++ calling COBOL - MCH0802</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1841</link>
    <description>&lt;pre&gt;   The Opening Post provided a complete CBLLE source for the "CALLEE" 
[and two sources for the CALLER; one is CBLLE] for which the compiled 
*PGM object as created with the Create Bound COBOL Program (CRTBNDCBL) 
command effects min=0\max=3 for the "Number of parameters".  A snippet 
of that complete CBLLE source, for which apparently the "USING" effects 
the explicitly defined /hard/ number of parameters rather than a more 
/theoretical/ or /soft/ limit for the maximum, is included here:

        ------- CALLEE.CBL --------
        ...
        LINKAGE SECTION.
        01 P1 PIC X(5).
        01 P2 PIC X(5).
        01 P3 PIC X(5).
        PROCEDURE DIVISION USING P1 P2 P3.
        ...

Regards, Chuck

On 09 May 2013 23:32, Jevgeni Astanovski wrote:
&lt;/pre&gt;</description>
    <dc:creator>CRPence</dc:creator>
    <dc:date>2013-05-10T13:51:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1840">
    <title>Re: AS400 C++ calling COBOL - MCH0802</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1840</link>
    <description>&lt;pre&gt;Sargey,
are you sure that minimum number of parameters and maximum number of parameters returned by QCLRPGMI are somehow "related to reality"?

I just had a look at ILE/RPG programs (attribute RPGLE). They all (OK, all that I looked at) have the following:

Program statistics:                                                  
  Number of parameters . . . . . . . . . . . . . :   0            255

And this is for a program, that I know, needs exactly 5 parameters.
I recall that before ILE this value reflected actual number of parameters.

Once again, talking about ILE/RPG, as I could not find any COBOL programs on our box...

Jevgeni.


-----Original Message-----
From: c400-l-bounces-Zwy7GipZuJhWk0Htik3J/w&amp;lt; at &amp;gt;public.gmane.org [mailto:c400-l-bounces-Zwy7GipZuJhWk0Htik3J/w&amp;lt; at &amp;gt;public.gmane.org] On Behalf Of Sergey Kashyrin
Sent: Thursday, May 09, 2013 8:59 PM
To: c400-l-Zwy7GipZuJhWk0Htik3J/w&amp;lt; at &amp;gt;public.gmane.org
Subject: Re: [C400-L] AS400 C++ calling COBOL - MCH0802

Hi Chuck,


It is not possible in my case. I have 1 ca&lt;/pre&gt;</description>
    <dc:creator>Jevgeni Astanovski</dc:creator>
    <dc:date>2013-05-10T06:32:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1839">
    <title>Re: AS400 C++ calling COBOL - MCH0802</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1839</link>
    <description>&lt;pre&gt;code a switch (it wont be large)
 
call (QCLRPGMI) API with format pgmI0100 check the program you want for min max parms and then call &amp;amp;Varnam depending on max within the switch, it shouldn't be messy really just copy and paste.
 
Or am I missing the deal?   
 

       
&lt;/pre&gt;</description>
    <dc:creator>Ron Unknown</dc:creator>
    <dc:date>2013-05-09T19:51:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1838">
    <title>Re: AS400 C++ calling COBOL - MCH0802</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1838</link>
    <description>&lt;pre&gt;Hi Chuck,


It is not possible in my case. I have 1 caller and more than 3000 of callee-s
Caller let say have "all information", and "callees" accepting only what they want.
And of course all of that is dynamic, so I don't know who I will call next.
To rewrite 3000+ COBOL programs could require a good budget :-)

Thanks,
Sergey

&lt;/pre&gt;</description>
    <dc:creator>Sergey Kashyrin</dc:creator>
    <dc:date>2013-05-09T17:59:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1837">
    <title>Re: AS400 C++ calling COBOL - MCH0802</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1837</link>
    <description>&lt;pre&gt;
   I am obviously unaware of the details... But IMO a more obvious 
resolution to avoid any logic in the CALLER, would be to code the CALLEE 
to accept the additional two parameters regardless they are unused.

   Of course I generally prefer having the caller use a distinct 
invocation for each different parameter-style, so which type of 
invocation has failed is very conspicuous; i.e. if there is just one 
generic CALL PGMX (&amp;amp;Addr_of_Parm_List), then every variation of the CALL 
that fails on the same HLL statement, and therefore only by debug or 
good logging will I learn which variation of the invocation had been 
established.

&lt;/pre&gt;</description>
    <dc:creator>CRPence</dc:creator>
    <dc:date>2013-05-08T23:49:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1836">
    <title>Re: AS400 C++ calling COBOL - MCH0802</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1836</link>
    <description>&lt;pre&gt;
Hi Chuck,


Thanks, I've also figured out that my test is incorrect - just messed playing with 3-5 parms on many platforms,
so I'm getting MCH on COBOL call COBOL also if I use 5 parms.
For now I see the only way to avoid this issue (which does not exist on the platforms other than AS400) is to do
the call to

QCLRPGMI(&amp;amp;info, ...
and figure out the expected number of parameters (info.Max_Parameters) 
and than code a huge switch with calls :-)))

Regards,
Sergey

&lt;/pre&gt;</description>
    <dc:creator>Sergey Kashyrin</dc:creator>
    <dc:date>2013-05-08T18:44:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1835">
    <title>Re: AS400 C++ calling COBOL - MCH0802</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1835</link>
    <description>&lt;pre&gt;
   The source shown will be created with *three* parameters for which 
its compiled program object will accept a minimum of zero parameters and 
a maximum of three parameters; i.e. per the declarative:
       PROCEDURE DIVISION USING P1 P2 P3.


   The example given shows the CALL passing *three* parameters, not 
five; i.e. per the USING:
       CALL SUB USING P1 P2 P3.


   That call is coded to pass *five* parameters; i.e. P1 to P5 are the 
arguments passed on the function invoked by address:
       os_fct_ptr(p1, p2, p3, p4, p5);

   The MCH0802 for its second level text apparently read: "Program 
CALLER attempted to call program CALLEE with 5 parameters. Program 
CALLEE expects a minimum of 0 and a maximum of 3 parameters."

   Had the following call been coded within the program CBCALLER, to 
truly pass *five* parameters, then that invocation would have effected 
the same MCH0802 [of course with the proper name appearing for the 
"caller"]:
       CALL SUB USING P1 P2 P3 P4 P5.


   Call from the C pro&lt;/pre&gt;</description>
    <dc:creator>CRPence</dc:creator>
    <dc:date>2013-05-08T02:05:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1834">
    <title>Re: AS400 C++ calling COBOL - MCH0802</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1834</link>
    <description>&lt;pre&gt;
The closest I've been to your situation is ILE C calling OPM MI, and I'd 
have to wake up the box the relevant source code is on, but:

Are you sure the parameter-passing protocol matches?

--
JHHL
&lt;/pre&gt;</description>
    <dc:creator>James H. H. Lampert</dc:creator>
    <dc:date>2013-05-07T23:16:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1833">
    <title>AS400 C++ calling COBOL - MCH0802</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1833</link>
    <description>&lt;pre&gt;Good day,

Here is the problem:

1. I have ILE COBOL program (*PGM) with let say 3 parameter
2. I am calling this program (dynamically) from other COBOL program let say
with 5 parameters - call is going thru, everything is okay.
3. I need to do the same call from C++  - I am getting MCH0802 (number of
parameters mismatch).

What is wrong and how to avoid that ?

Regards,
Sergey

-------------- CALLEE.CBL ------------
        IDENTIFICATION DIVISION.
        PROGRAM-ID. CALLEE.
        ENVIRONMENT DIVISION.
        DATA DIVISION.
        WORKING-STORAGE SECTION.
        LINKAGE SECTION.
        01 P1 PIC X(5).
        01 P2 PIC X(5).
        01 P3 PIC X(5).
        PROCEDURE DIVISION USING P1 P2 P3.
        0000-MAIN.
            DISPLAY 'P1=' P1 ';'.
            DISPLAY 'P2=' P2 ';'.
            DISPLAY 'P3=' P3 ';'.
            MOVE 'RET1' TO P1.
            MOVE 'RET2' TO P2.
            MOVE 'RET3' TO P3.
            GOBACK.
--------------------------- CBCALLER.CBL -----------------
        IDENTIFICATION&lt;/pre&gt;</description>
    <dc:creator>Sergey Kashyrin</dc:creator>
    <dc:date>2013-05-07T22:56:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1832">
    <title>Guidelines for C400-L mailing list</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1832</link>
    <description>&lt;pre&gt;Monthly posting of the guidelines for participation in the C/400 Language
Mailing List.

Keep to the subject.  The topic of the list is C and C++ Programming on and
for the AS/400. This includes programming on other platforms in C/C++ when
it RELATES to the AS/400.  Eg: Considerations of Sockets programming from
Windows to the AS/400 using MSVC &amp;amp; ILE/C is allowed and encouraged.  How to
manipulate a ClistView object in the Windows world is not allowed.

When quoting messages, do not quote the entire message.  Just quote the
parts that are needed to make the appropriate references.

Flames are absolutely prohibited.  If you disagree with someone, feel
free to argue the facts, but no personal attacks will be tolerated.

The official language of the C/400 Programming Mailing List is English.

Do not post personal messages.  Please use direct E-Mail.  This list is
international in scope and personal messages just end up costing money.

Please do not use HTML to format messages ... not everyone has a HTML
enabled&lt;/pre&gt;</description>
    <dc:creator>mailman-Zwy7GipZuJhWk0Htik3J/w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-05-01T11:31:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1831">
    <title>Guidelines for C400-L mailing list</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1831</link>
    <description>&lt;pre&gt;Monthly posting of the guidelines for participation in the C/400 Language
Mailing List.

Keep to the subject.  The topic of the list is C and C++ Programming on and
for the AS/400. This includes programming on other platforms in C/C++ when
it RELATES to the AS/400.  Eg: Considerations of Sockets programming from
Windows to the AS/400 using MSVC &amp;amp; ILE/C is allowed and encouraged.  How to
manipulate a ClistView object in the Windows world is not allowed.

When quoting messages, do not quote the entire message.  Just quote the
parts that are needed to make the appropriate references.

Flames are absolutely prohibited.  If you disagree with someone, feel
free to argue the facts, but no personal attacks will be tolerated.

The official language of the C/400 Programming Mailing List is English.

Do not post personal messages.  Please use direct E-Mail.  This list is
international in scope and personal messages just end up costing money.

Please do not use HTML to format messages ... not everyone has a HTML
enabled&lt;/pre&gt;</description>
    <dc:creator>mailman-Zwy7GipZuJhWk0Htik3J/w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-04-01T11:31:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1830">
    <title>Re: Locales and regular expressions</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1830</link>
    <description>&lt;pre&gt;Last time I looked (http://archive.midrange.com/c400-l/201011/msg00007.html) regerror() was an exception however and blatantly ignored the locale setting and always used CCSID 37. Nice touch. 



On 23 mar 2013, at 07:16, Tim Bronski &amp;lt;tim.bronski-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>Erik Olsson</dc:creator>
    <dc:date>2013-03-24T03:24:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1829">
    <title>Re: Locales and regular expressions</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1829</link>
    <description>&lt;pre&gt;Thanks Thomas. It looks like the conversion of the value is my only 
option. I was hoping for a "locale" safe version or option since the 
original string has an associated mac and I didn't want a "temp" stored 
version.
Thanks.

On 3/23/2013 1:30 PM, Thomas Raddatz wrote:

&lt;/pre&gt;</description>
    <dc:creator>Tim Bronski</dc:creator>
    <dc:date>2013-03-23T13:16:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1828">
    <title>Re: Locales and regular expressions</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1828</link>
    <description>&lt;pre&gt;The regular expression functions belongs the group of function that are 
locale sensitive. From the IBM i Information Center:

"Locale Sensitive: The behavior of this function might be affected by the 
LC_CTYPE and LC_COLLATE categories of the current locale. This function is 
not available when LOCALETYPE(*CLD) is specified on the compilation 
command. For more information, see Understanding CCSIDs and Locales."

I always convert the pattern and the value to the CCSID of the current 
locale using ...

   nl_langinfo(CODESET) to get the CCSID

   QtqIconvOpen(), iconv() and iconv_close() to convert the CCSID


... before I use regcomp(), regexec() and regfree() to apply the regular 
expression to the value.

Thomas.


Am 22.03.2013 15:24, schrieb Tim Bronski:
&lt;/pre&gt;</description>
    <dc:creator>Thomas Raddatz</dc:creator>
    <dc:date>2013-03-23T12:30:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1826">
    <title>Guidelines for C400-L mailing list</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1826</link>
    <description>&lt;pre&gt;Monthly posting of the guidelines for participation in the C/400 Language
Mailing List.

Keep to the subject.  The topic of the list is C and C++ Programming on and
for the AS/400. This includes programming on other platforms in C/C++ when
it RELATES to the AS/400.  Eg: Considerations of Sockets programming from
Windows to the AS/400 using MSVC &amp;amp; ILE/C is allowed and encouraged.  How to
manipulate a ClistView object in the Windows world is not allowed.

When quoting messages, do not quote the entire message.  Just quote the
parts that are needed to make the appropriate references.

Flames are absolutely prohibited.  If you disagree with someone, feel
free to argue the facts, but no personal attacks will be tolerated.

The official language of the C/400 Programming Mailing List is English.

Do not post personal messages.  Please use direct E-Mail.  This list is
international in scope and personal messages just end up costing money.

Please do not use HTML to format messages ... not everyone has a HTML
enabled&lt;/pre&gt;</description>
    <dc:creator>mailman-Zwy7GipZuJhWk0Htik3J/w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-03-01T12:31:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1825">
    <title>Re: Creating temporary table</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1825</link>
    <description>&lt;pre&gt;2013/2/23 aec &amp;lt;cfuture-Wuw85uim5zDR7s880joybQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt;:

The OP wants to stick to the _Ropen family of OS/400 specific
functions and not use SQL. If SQL was an option, which I guess it's
not, I would suggest using a DECLARE GLOBAL TEMPORARY TABLE statement
to begin with as the _R-family has many drawbacks such as not being
portable and not supporting all datatypes in db2 (LOBs for instance).
&lt;/pre&gt;</description>
    <dc:creator>Erik Olsson</dc:creator>
    <dc:date>2013-02-23T19:29:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1824">
    <title>Re: Creating temporary table</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1824</link>
    <description>&lt;pre&gt;Does embedded SQL work in C the same as in RPG? Such as, running a DROP 
QTEMP/MYFILE statement. In RPG this just returns a negative SQLCODE. 
Don't have to capture the message.


On 2/15/13 3:07 AM, Jevgeni Astanovski wrote:

&lt;/pre&gt;</description>
    <dc:creator>aec</dc:creator>
    <dc:date>2013-02-23T13:41:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1823">
    <title>Re: QXXPTOD API from an ILE CL program</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1823</link>
    <description>&lt;pre&gt;   I agree with the situation about those having only CL available [I 
have even been in situations where that was the effective scenario], and 
that the value in knowing how to do the work in CL irrespective of its 
potential usefulness generally... because they are educational.

   I just want to clarify however, that the OP noted [and to what and 
why I responded was] that the issue involved an educational example of 
ILE CL calling a procedure with CALLPRC; i.e. for a "presentation" that 
was being prepared.  I was of the opinion that FLOAT was an unnecessary 
complexity which could easily be avoided; i.e. there was no reason to 
use that "rather complicated sample as a good representation of what ILE 
is", when so many other examples could be had without needing to pass a 
FLOAT data type.  And FWiW the "system I have used lately", although 
left unmentioned, is one which has no access fees and also gives free 
access to an RPG compiler.  Thus I could have created the module, saved 
the object, and tran&lt;/pre&gt;</description>
    <dc:creator>CRPence</dc:creator>
    <dc:date>2013-02-18T00:46:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1822">
    <title>Re: QXXPTOD API from an ILE CL program</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1822</link>
    <description>&lt;pre&gt;Okay, but how many of those people who only have access to CL need to 
know the hypotenuse of something?

Seems to me that function is really only useful for graphics programming 
&lt;/pre&gt;</description>
    <dc:creator>Scott Klement</dc:creator>
    <dc:date>2013-02-17T21:47:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.lang.as400.c/1821">
    <title>Re: QXXPTOD API from an ILE CL program</title>
    <link>http://permalink.gmane.org/gmane.comp.lang.as400.c/1821</link>
    <description>&lt;pre&gt;I personally agree with the view that using the math functions from CL,
though certainly possible, is generally more work than it's worth. But over
the years I have also met quite a few developers who only have CL available
to them. So documenting how to do it in CL, even though I would most likely
call some RPG or C code if doing it myself, is certainly a worthwhile
discussion. Doing it in another ILE language just isn't an option for some
users.

Bruce

On Sun, Feb 17, 2013 at 2:23 PM, Rory Hewitt &amp;lt;rory.hewitt-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>Bruce Vining</dc:creator>
    <dc:date>2013-02-17T21:35:33</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.lang.as400.c">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.lang.as400.c</link>
  </textinput>
</rdf:RDF>
