Extract Utility User's Guide - Supra - Cincom

ConsiderationsConsider the examples in the following table:Extracted data Format mask Output file value43715 # 4371543715 -# 4371543715 -#.## 437.1543715 -#.####### 0.4371500-43715 # 43715-43715 -# -43715-43715 -#.## -437.15-43715 -#.####### -0.4371500♦♦♦♦♦♦♦Subfield names are not expected to correspond to any entities defined onthe SUPRA Directory. The choice of name is up to the user and is notchecked against any directory physical field names.All of the data from a field may be included in the output by specifyingsubfields whose total length is equal to the length of the parent field. Thiswould be desirable when the data types of the subfields differ from eachother and you need to have the FORMAT parameter for at least one of thesubfields.Each XML tag must appear within a pair of XML tags and, which directs Extract to extract the subfield data from theidentified field.When you code tags, you must omit the Type, Length, Format,and Null attributes from the controlling tag. See the description ofthe tag above.If you wish to extract only certain parts of a Physical Field from a givenFile, or if you wish to extract parts of a Physical Field in an order otherthan the one in which they appear in the File, then supply the appropriate elements between the and tags.The sum of the Length attributes within the elements for agiven must not exceed the data length of that Physical Field in thedatabase.You must not nest tags within other tags. In other words, you cannot request extractionof subfields of subfields.Extract Utility User's Guide, P25-9513-03 58Chapter: 5. Coding the Extract functionSection: Coding the XML for the Layout Control file