Difference: 0LASubrTextParseLine (7 vs. 8)

Revision 82018-05-07 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPXRuntimeSubroutineAPI"

.TEXT PARSE LINE

Line: 25 to 25
 <no_of_fields> returns the number of fields that were found in <text_to_parse> (Optional). This must be PASSed with Share "Y" to return a value.

The parsed data will be available in the --- .TEXT PARSE RESULT work field. You do not have to PASS this field. This is a multi occurence work field, each occurence is 512 bytes and there are a maximum of 100 occurrences. If one of the parsed fields is larger than 512 bytes, then --- .TEXT PARSE RESULT will contain 'Data Truncation'. If there are more than 100 fields parsed, then --- .TEXT PARSE RESULT will contain 'Max Occur Exceeded' and only the first 100 fields will be returned.

Changed:
<
<

Updates starting in 6.0.1

>
>

Changes in 6.0.1

  Starting in Release 6.0.1, this routine has been enhanced:

- All processing has been moved to the APPX engine for faster performance

Changed:
<
<
- A file called --- PARSED is returned containing one record for each column. There are no size or number of columns limitations when results are returned in this file. If your application references the --- .TEXT PARSE RESULT field, it will also be populated subject to the restrictions above.
>
>
- A file called --- PARSED is returned containing one record for each column. There are no size or number of columns limitations when results are returned in this file. If the current process references the --- .TEXT PARSE RESULT field, it will also be populated (subject to the restrictions above).
  - Fields surrounded by quotes will have the quotes removed (unless they are embedded in the the field).
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback