These fire only when the options argument is a string literal; an options string built at run time is not inspected at compile time.
| Code | Message | Cause | Resolution |
|---|---|---|---|
| TRN2401 | Invalid {XML/DATA-INTO} option '{token}'; expected name=value | A token in the options string is not a name=value pair. Note that spaces around the = break the pair - allowmissing = yes is invalid. |
Write each option as name=value, with no spaces around the =, separated by spaces. |
| TRN2401 | Unknown {XML/DATA-INTO} option '{name}' | The option name is not recognized. The recognized names are path, doc, ccsid, case, trim, allowmissing, allowextra, countprefix, ns, nsprefix, and datasubf. |
Correct the option name. |
| TRN2401 | Invalid value '{value}' for option '{name}'; expected yes or no | allowmissing or allowextra was given something other than yes / no. |
Use yes or no. |
| TRN2401 | Invalid value '{value}' for option 'case'; expected lower, upper, any, or convert | case was given an unrecognized value. |
Use lower, upper, any, or convert. |
| TRN2401 | Invalid value '{value}' for option 'trim'; expected all or none | trim was given an unrecognized value. |
Use all or none. |
| TRN2401 | Invalid value '{value}' for XML option 'ccsid'; expected ucs2, job, or jobrun | ccsid was given a numeric or otherwise non-symbolic value. A numeric CCSID is not valid in %XML. |
Use ucs2, job, or jobrun. |
| TRN2401 | Option '{name}' is not valid for XML-SAX; only doc and ccsid are accepted | An XML-INTO-only option (case, trim, allowmissing, allowextra, path, countprefix) was used on XML-SAX. Mirrors IBM i RNF0224. |
Remove the option. XML-SAX accepts only doc and ccsid. |
| TRN2402 | XML option '{name}' is not supported by rpgc | The option is recognized but unimplemented. It is rejected rather than silently ignored, which would change how the document is parsed without telling you. | Remove the option, or restructure the document handling so it is not needed. |
| TRN2403 | {JSON-INTO/JSON-SAX} is not an ILE RPG operation code - IBM never defined it. Use DATA-INTO with a JSON parser | Triton RPG has no JSON-INTO or JSON-SAX operation. Use DATA-INTO, which reads any structured document - JSON included - through a parser your program names. |
Rewrite as DATA-INTO receiver %DATA(document) %PARSER(parser), supplying a JSON parser. See DATA-INTO. |