PCML API QYASPOL CPF24B4 - IBM AS400

This is a discussion on PCML API QYASPOL CPF24B4 - IBM AS400 ; Hello Forum I have a problem with running this api on y v5r3 box. Always I try to run this I get the well known CPF24B4. Here is my pcml doc. init="800" /> init="YASP0100" /> I'm very new in programming ...

+ Reply to Thread
Results 1 to 13 of 13

Thread: PCML API QYASPOL CPF24B4

  1. PCML API QYASPOL CPF24B4

    Hello Forum

    I have a problem with running this api on y v5r3 box. Always I try to
    run this I get the well known CPF24B4. Here is my pcml doc.






    init="800" />




    init="YASP0100" />










    I'm very new in programming with apis. ;-)

    Greetz Henrik



  2. Re: PCML API QYASPOL CPF24B4

    henrik.motzkus@googlemail.com wrote:
    > Hello Forum
    >
    > I have a problem with running this api on y v5r3 box. Always I try to
    > run this I get the well known CPF24B4. Here is my pcml doc.
    >
    >
    >
    >
    >
    >
    > > init="800" />
    >
    >
    >
    >
    > > init="YASP0100" />
    >
    >

    >
    >
    >
    >
    >
    >
    >

    >
    > I'm very new in programming with apis. ;-)


    Try these changes:

    1. Specify a structure for the YASP0100 format and use
    it for
    the "receiver" parameter:











    2. Specify this structure for the 'listinfo' parameter:
















    3. Change the usage on the 'receiverlength' parameter
    to 'input'.

    4. Change the program call line parameters:

    path="/QSYS.lib/QGY.lib/qyaspol.pgm"
    parseorder="listInfo receiver">
    usage="output"
    count="listInfo.rcdsReturned"
    outputsize="receiverLength" />
    usage="input" init="800" />
    usage="output" />
    init="100" />
    usage="input" init="1" />
    usage="input" />
    init="YASP0100" />
    usage="output" />


  3. Re: PCML API QYASPOL CPF24B4

    It would seem that the 4-byte errorCode is actually Input, and that
    it should pass a binary zero. As output, it requires at least an 8-byte
    declaration. See Table 1. Format ERRC0100 for the error code parameter at:

    http://publib.boulder.ibm.com/infoce...codeformat.htm

    Regards, Chuck
    --
    All comments provided "as is" with no warranties of any kind
    whatsoever and may not represent positions, strategies, nor views of my
    employer

    Jonathan Ball wrote:
    > <>
    > 4. Change the program call line parameters:
    >
    > <>
    >
    >


  4. Re: PCML API QYASPOL CPF24B4

    CRPence wrote:
    > It would seem that the 4-byte errorCode is actually Input, and that it
    > should pass a binary zero. As output, it requires at least an 8-byte
    > declaration. See Table 1. Format ERRC0100 for the error code parameter at:
    >
    > http://publib.boulder.ibm.com/infoce...codeformat.htm


    Yes. I copied that from the original post and didn't
    catch it.

  5. Re: PCML API QYASPOL CPF24B4

    On 15 Nov., 19:15, Jonathan Ball wrote:
    > CRPence wrote:
    > > It would seem that the 4-byte errorCode is actually Input, and that it
    > > should pass a binary zero. As output, it requires at least an 8-byte
    > > declaration. See Table 1. Format ERRC0100 for the error code parameter at:

    >
    > >http://publib.boulder.ibm.com/infoce...ndex.jsp?topic...

    >
    > Yes. I copied that from the original post and didn't
    > catch it.


    Thanks for the quick answer, but. I changed he specification to this,
    but it doesn't work. It's a mystery.




    init="14" />
    init="1" />
    init="2" />
    init="1" />



    init="64" />
    init="0" />
    init=" " />
    init=" " />
    init=" " />



























    parseorder="listInfo receiver">
    struct="yasp0100" usage="output" count="listInfo.rcdsReturned"
    outputsize="receiverlength" />
    length="4" usage="input" init="800" />
    struct="listInfo" usage="output" />
    length="4" usage="input" init="100" />
    length="4" usage="input" init="1" />
    struct="filter" usage="input" />
    length="8" usage="input" init="YASP0100" />
    length="4" usage="output" />





    Is there any additional debug data except the
    "Trace.setTracePCMLOn(true);" to gather to get to the root?

  6. Re: PCML API QYASPOL CPF24B4

    In the given, the parameter for the error code is still shown as
    passing the same 4-byte "output" without an initialization to binary
    zero; i.e. the new struct "error" is not used -- not to imply that I
    agree with the attempt to declare that structure "error", if only for
    its failure to initialize something called /reserved/, to binary zero.

    Regards, Chuck
    --
    All comments provided "as is" with no warranties of any kind
    whatsoever and may not represent positions, strategies, nor views of my
    employer

    henrik.motzkus@googlemail.com wrote:
    > <>
    > > <>
    > > length="4" usage="output" />
    >


  7. Re: PCML API QYASPOL CPF24B4

    On 19 Nov., 16:24, CRPence wrote:
    > In the given, the parameter for the error code is still shown as
    > passing the same 4-byte "output" without an initialization to binary
    > zero; i.e. the new struct "error" is not used -- not to imply that I
    > agree with the attempt to declare that structure "error", if only for
    > its failure to initialize something called /reserved/, to binary zero.
    >


    I changed the error element to input initialised with zero and deleted
    the error struct.

    Now it looks like this:




    init="14" />
    init="1" />
    init="2" />
    init="1" />



























    parseorder="listInfo receiver">
    struct="yasp0100" usage="output" count="listInfo.rcdsReturned"
    outputsize="receiverlength" />
    length="4" usage="input" init="16384" />
    struct="listInfo" usage="output" />
    length="4" usage="input" init="100" />
    length="4" usage="input" init="1" />
    struct="filter" usage="input" />
    length="8" usage="input" init="YASP0100" />
    length="4" usage="input" init="0"/>





    Same error.

  8. Re: PCML API QYASPOL CPF24B4

    henrik.motzkus@googlemail.com wrote:
    > On 15 Nov., 19:15, Jonathan Ball wrote:
    >> CRPence wrote:
    >>> It would seem that the 4-byte errorCode is actually Input, and that it
    >>> should pass a binary zero. As output, it requires at least an 8-byte
    >>> declaration. See Table 1. Format ERRC0100 for the error code parameter at:
    >>> http://publib.boulder.ibm.com/infoce...ndex.jsp?topic...

    >> Yes. I copied that from the original post and didn't
    >> catch it.

    >
    > Thanks for the quick answer, but. I changed he specification to this,
    > but it doesn't work. It's a mystery.
    >
    >
    >
    >
    > > init="14" />
    > > init="1" />
    > > init="2" />
    > > init="1" />
    >

    >
    >
    > > init="64" />
    > > init="0" />
    > > init=" " />
    > > init=" " />
    > > init=" " />
    >

    >
    >
    >
    >
    >
    >
    >
    >
    >
    >

    >
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >

    >
    > > parseorder="listInfo receiver">
    > > count="listInfo.rcdsReturned" outputsize="receiverlength" />
    >
    >
    >
    >
    >
    >
    >
    >

    >
    >
    >


    Try changing the last parameter to this:

    usage="input" init="0" />


  9. Re: PCML API QYASPOL CPF24B4

    > Try changing the last parameter to this:
    >
    > > usage="input" init="0" />- Zitierten Text ausblenden -
    >
    > - Zitierten Text anzeigen -


    Its already changed to this. Same result.

  10. Re: PCML API QYASPOL CPF24B4

    The filter is not correct according to the API doc. The following
    would seem to be more appropriate, where -1 is used to list; or a
    positive integer to get information about that specified ASP number.








    Regards, Chuck
    --
    All comments provided "as is" with no warranties of any kind
    whatsoever and may not represent positions, strategies, nor views of my
    employer

    henrik.motzkus@googlemail.com wrote:
    > <>
    >
    >
    >
    >
    >
    >

    > <>


  11. Re: PCML API QYASPOL CPF24B4

    On 19 Nov., 17:18, CRPence wrote:
    > The filter is not correct according to the API doc. The following
    > would seem to be more appropriate, where -1 is used to list; or a
    > positive integer to get information about that specified ASP number.
    >
    >
    >
    >
    >
    >
    >

    >
    > Regards, Chuck


    Thanks a lot but same error. Here is the trace data:

    Toolbox for Java - Open Source Software, JTOpen 5.3, codebase 5722-JC1
    V5R4M0.4
    Mo Nov 19 17:31:01:343 CET 2007 Writing data -- Offset: 0 Length: 4
    Name: "qyaspol.receiverlength" Byte data: 00004000 Thread[main,
    5,main]
    Mo Nov 19 17:31:01:359 CET 2007 /QSYS.lib/QGY.lib/qyaspol.pgm
    qyaspol.receiverlength
    Mo Nov 19 17:31:01:359 CET 2007 Offset : 0....... 4....... 8.......
    C....... 0....... 4....... 8....... C....... 0...4...8...C...
    0...4...8...C...
    Mo Nov 19 17:31:01:359 CET 2007 0 :
    00004000
    *.. . *
    Mo Nov 19 17:31:01:359 CET 2007 Writing data -- Offset: 0 Length: 4
    Name: "qyaspol.nbrrcd" Byte data: 00000064 Thread[main,5,main]
    Mo Nov 19 17:31:01:375 CET 2007 /QSYS.lib/QGY.lib/qyaspol.pgm
    qyaspol.nbrrcd
    Mo Nov 19 17:31:01:375 CET 2007 Offset : 0....... 4....... 8.......
    C....... 0....... 4....... 8....... C....... 0...4...8...C...
    0...4...8...C...
    Mo Nov 19 17:31:01:375 CET 2007 0 :
    00000064
    *.... *
    Mo Nov 19 17:31:01:375 CET 2007 Writing data -- Offset: 0 Length: 4
    Name: "qyaspol.nbrfilter" Byte data: 00000001 Thread[main,5,main]
    Mo Nov 19 17:31:01:375 CET 2007 /QSYS.lib/QGY.lib/qyaspol.pgm
    qyaspol.nbrfilter
    Mo Nov 19 17:31:01:375 CET 2007 Offset : 0....... 4....... 8.......
    C....... 0....... 4....... 8....... C....... 0...4...8...C...
    0...4...8...C...
    Mo Nov 19 17:31:01:375 CET 2007 0 :
    00000001
    *.... *
    Mo Nov 19 17:31:01:390 CET 2007 Writing data -- Offset: 0 Length: 4
    Name: "qyaspol.filter.size" Byte data: F1F64040 Thread[main,5,main]
    Mo Nov 19 17:31:01:390 CET 2007 Writing data -- Offset: 4 Length: 4
    Name: "qyaspol.filter.key" Byte data: F1404040 Thread[main,5,main]
    Mo Nov 19 17:31:01:390 CET 2007 Writing data -- Offset: 8 Length: 4
    Name: "qyaspol.filter.datasize" Byte data: F4404040 Thread[main,
    5,main]
    Mo Nov 19 17:31:01:390 CET 2007 Writing data -- Offset: c Length: 4
    Name: "qyaspol.filter.data" Byte data: 60F14040 Thread[main,5,main]
    Mo Nov 19 17:31:01:406 CET 2007 /QSYS.lib/QGY.lib/qyaspol.pgm
    qyaspol.filter
    Mo Nov 19 17:31:01:406 CET 2007 Offset : 0....... 4....... 8.......
    C....... 0....... 4....... 8....... C....... 0...4...8...C...
    0...4...8...C...
    Mo Nov 19 17:31:01:406 CET 2007 0 : F1F64040 F1404040 F4404040
    60F14040 *16 1 4
    -1 *
    Mo Nov 19 17:31:01:406 CET 2007 Writing data -- Offset: 0 Length: 8
    Name: "qyaspol.format" Byte data: E8C1E2D7F0F1F0F0 Thread[main,
    5,main]
    Mo Nov 19 17:31:01:406 CET 2007 /QSYS.lib/QGY.lib/qyaspol.pgm
    qyaspol.format
    Mo Nov 19 17:31:01:406 CET 2007 Offset : 0....... 4....... 8.......
    C....... 0....... 4....... 8....... C....... 0...4...8...C...
    0...4...8...C...
    Mo Nov 19 17:31:01:406 CET 2007 0 : E8C1E2D7
    F0F1F0F0
    *YASP0100 *
    Mo Nov 19 17:31:01:406 CET 2007 Writing data -- Offset: 0 Length: 4
    Name: "qyaspol.errorCode" Byte data: 00000000 Thread[main,5,main]
    Mo Nov 19 17:31:01:406 CET 2007 /QSYS.lib/QGY.lib/qyaspol.pgm
    qyaspol.errorCode
    Mo Nov 19 17:31:01:406 CET 2007 Offset : 0....... 4....... 8.......
    C....... 0....... 4....... 8....... C....... 0...4...8...C...
    0...4...8...C...
    Mo Nov 19 17:31:01:406 CET 2007 0 :
    00000000
    *.... *
    CPF24B4 - Schwerwiegender Fehler beim Adressieren der
    Parameterliste.
    ** Call to QYASPOL failed. See messages above **


  12. Re: PCML API QYASPOL CPF24B4

    That trace seems to show the filter data is still [declared and thus
    processed as] character data instead of bin-4:

    qyaspol.filter
    Offset
    : 0....... 4....... 8....... C.......
    : F1F64040 F1404040 F4404040 60F14040 *16 1 4 -1 *

    Perhaps only the /init/ were changed, and not the /type/ ?

    Regards, Chuck
    --
    All comments provided "as is" with no warranties of any kind
    whatsoever and may not represent positions, strategies, nor views of my
    employer

    henrik.motzkus@googlemail.com wrote:
    > On 19 Nov., 17:18, CRPence wrote:
    >> The filter is not correct according to the API doc. The following
    >> would seem to be more appropriate, where -1 is used to list; or a
    >> positive integer to get information about that specified ASP number.
    >>
    >>
    >>
    >>
    >>
    >>
    >>

    >>
    >> Regards, Chuck

    >
    > Thanks a lot but same error. Here is the trace data:
    >
    > <>


  13. Re: PCML API QYASPOL CPF24B4

    On 19 Nov., 18:22, CRPence wrote:
    > That trace seems to show the filter data is still [declared and thus
    > processed as] character data instead of bin-4:
    >
    > qyaspol.filter
    > Offset
    > : 0....... 4....... 8....... C.......
    > : F1F64040 F1404040 F4404040 60F14040 *16 1 4 -1 *
    >
    > Perhaps only the /init/ were changed, and not the /type/ ?
    >



    Oh yes! Great! I was working since a week on this issue. Thanks a
    lot.

    Regards Henrik

+ Reply to Thread