PCML Specification Errors using JT400

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • seligerasmus
    New Member
    • Jun 2007
    • 12

    #1

    PCML Specification Errors using JT400

    Greetings!

    My scenario is such - I'm wrapping a Java web service around a set of RPG programs that live on one of my company's i-Series (AS/400) midrange computers. To faciltate the connectivity between the Java application server and the i-Series box, I'm using IBM's Toolbox for Java.

    My circumstances allow me to use previously-written PCML specification files in my code. I can verify that these PCML files are in use in my company's production environment.

    The PCML files work for all but one RPG program, which throws an exception at the ProgramCallDocu ment initialization statement.

    The specific error thrown is -
    Code:
    "File 'getAccountInfo' contains PCML specification errors."
    With the finer details of the exception being -
    Code:
    "Attribute length="9" is not allowed when type="int" is specified....."
    ...
    "Attribute length="9" is not allowed when type="int" is specified....."
    ...
    "Attribute length="3" is not allowed when type="int" is specified....."
    The PCML document has worked in the past, so I'm skeptical that anything is wrong with the document itself.

    A handful of the approaches I've tried to fixing this problem -
    • Changing the PCML version in the PCML document
    • Rolling back to a previously-used version of the JT400.jar library
    • Verifying that the RPG programs output parameter datatypes match those found in the PCML document specification.


    My environment specs -
    • Sun Java System Application Server v. 9
    • J2EE 1.4
    • OS/400 (i5/OS) V5R4


    Any help or insight would be greatly appreciated.
  • r035198x
    MVP
    • Sep 2006
    • 13225

    #2
    Originally posted by seligerasmus
    Greetings!

    My scenario is such - I'm wrapping a Java web service around a set of RPG programs that live on one of my company's i-Series (AS/400) midrange computers. To faciltate the connectivity between the Java application server and the i-Series box, I'm using IBM's Toolbox for Java.

    My circumstances allow me to use previously-written PCML specification files in my code. I can verify that these PCML files are in use in my company's production environment.

    The PCML files work for all but one RPG program, which throws an exception at the ProgramCallDocu ment initialization statement.

    The specific error thrown is -
    Code:
    "File 'getAccountInfo' contains PCML specification errors."
    With the finer details of the exception being -
    Code:
    "Attribute length="9" is not allowed when type="int" is specified....."
    ...
    "Attribute length="9" is not allowed when type="int" is specified....."
    ...
    "Attribute length="3" is not allowed when type="int" is specified....."
    The PCML document has worked in the past, so I'm skeptical that anything is wrong with the document itself.

    A handful of the approaches I've tried to fixing this problem -

    • Changing the PCML version in the PCML document
    • Rolling back to a previously-used version of the JT400.jar library
    • Verifying that the RPG programs output parameter datatypes match those found in the PCML document specification.

    My environment specs -
    • Sun Java System Application Server v. 9
    • J2EE 1.4
    • OS/400 (i5/OS) V5R4

    Any help or insight would be greatly appreciated.


    You said the file worked before.
    When did it start to show the errors? i.e after making which changes?

    Comment

    • seligerasmus
      New Member
      • Jun 2007
      • 12

      #3
      Originally posted by r035198x
      You said the file worked before.
      When did it start to show the errors? i.e after making which changes?
      The PCML file works in old legacy code (currently running in the production environment), but has never functioned in this new project.

      The file itself remains unchanged.

      Comment

      • JosAH
        Recognized Expert MVP
        • Mar 2007
        • 11453

        #4
        Just a silly guess (I know nothing about PCML): what happens if you remove
        that attribute 'lengt="x"'? It seems to me that it's a format specifier of some
        sort like the old COBOL 'pic 999' thing. It makes sense that such a format
        wouldn't make sense for just ints.

        I might be totally wrong though.

        kind regards,

        Jos

        Comment

        • seligerasmus
          New Member
          • Jun 2007
          • 12

          #5
          Originally posted by JosAH
          Just a silly guess (I know nothing about PCML): what happens if you remove
          that attribute 'lengt="x"'? It seems to me that it's a format specifier of some
          sort like the old COBOL 'pic 999' thing. It makes sense that such a format
          wouldn't make sense for just ints.

          I might be totally wrong though.

          kind regards,

          Jos
          Yes, sir. I tried changing the length attribute (same error) and removing it entirely (and received a "attribute NULL is not allowed for type int" error message)

          Comment

          • JosAH
            Recognized Expert MVP
            • Mar 2007
            • 11453

            #6
            Originally posted by seligerasmus
            Yes, sir. I tried changing the length attribute (same error) and removing it entirely (and received a "attribute NULL is not allowed for type int" error message)
            Does this link help a bit?

            Sorry that I can't really help you with this; best of luck.

            kind regards,

            Jos

            Comment

            • r035198x
              MVP
              • Sep 2006
              • 13225

              #7
              Originally posted by seligerasmus
              Yes, sir. I tried changing the length attribute (same error) and removing it entirely (and received a "attribute NULL is not allowed for type int" error message)
              Well I'm stumped. I wonder if running it with a java 1.4 JVM would help.

              Comment

              • seligerasmus
                New Member
                • Jun 2007
                • 12

                #8
                Originally posted by r035198x
                Well I'm stumped. I wonder if running it with a java 1.4 JVM would help.
                I will give that a try ASAP and report my results.

                Oh, and thanks for the link, Jos. It didn't address this particular issue, but it did help me with another unrelated problem I was experiencing.

                Comment

                Working...