10 More Reasons to Like Arbutus (71-80)

  1. Fast XML conversion
  2. Apply conditional tests to multiple fields
  3. Choose alternate logs
  4. Long record lengths and long CRLF files
  5. Export to XLSX
  6. At() / Substring() functions applied to entire record
  7. Verify results can be drilled into
  8. Negative decimals
  9. Procedure editor auto-indent
  10. Ftype() function can limit types searched

Note: The following 10 More Reasons to Like Arbutus are aimed at technical or advanced users. Questions or comments? Please contact us.

See: 10 More Reasons to Like Arbutus (81-90)

 

71. Fast XML conversion

Arbutus does not rely on the Microsoft XML parser. Instead, it converts XML data using its own converter that is dramatically faster, resulting in conversions in seconds. In addition, the XML interface allows single-click inclusion or exclusion of any item or group.

5-4-fast-xml

72. Apply conditional tests to multiple fields

Table definitions may include fields that are conditional in nature, meaning they only take on a value when the specified condition is true. Where a table definition requires conditional fields, Arbutus offers an easy means to set the condition. You may select any set of fields, and in one operation, set a condition on all of them.

Where the table layout is coming from COBOL, additional sort options allow you to place related field definitions together, to simplify the selection of fields.

 

73. Choose alternate logs

Arbutus logs all processing activity in a log file as supporting documentation. When a project involves several separate documentation threads, you can switch between logs with a simple click in the Overview.

 

74. Long record lengths and long CRLF files

The maximum record length supported by Arbutus is 2GB. While you are unlikely to ever encounter a record length this long, the capability often allows an entire file to be read as a single record, for specialized processing.

In addition, it is not uncommon for normal text (CRLF) files to occasionally have unexpectedly long lines that will likely exceed the table definition. This may be due to data corruption or an unexpected or unusual situation. When this occurs, Arbutus automatically compensates, reading the entire line despite the fact that it violates the table layout.

 

75. Export to XLSX

Arbutus supports exports to all versions of Excel spreadsheets, including XLS and XLSX. Of course, when exporting to either of these formats, you can specify the sheet name to be created, and even create multiple sheets, if necessary.

 

76. At() / Substring() functions applied to entire record

Certain processing situations require that you inspect the entire record as a single unit. For example, you may be looking for something or extracting something. When looking for something, the At() function allows you to specify RECORD as the last parameter. When extracting something, the Substring() function allows the first parameter to be RECORD.

 

77. Verify results can be drilled into

The results of a Verify command are typically presented in a tabular format. This table includes the record number, field name, expected field type, as well as the contents of the field both in text and hex. In addition to displaying the error, this table includes drill-down links, so that you can immediately move to the selected record and evaluate the error in the context of other fields and records around the error.

5-4-verify-drilldown-1

78. Negative decimals

Certain field types store values as multiples of a larger value. For example, “Sales” might be the sales figure in thousands, so 125 stored in the field actually means 125,000.

One solution to this issue is to create a computed field to multiply by 1,000, but Arbutus offers another approach. In the same way that you can specify that a number includes decimals (effectively moving the decimal point to the left), you can specify negative decimals (effectively moving the decimal point to the right).

In this example, specifying decimals of -3 will ensure that the value is correct.

 

79. Procedure editor auto-indent

The procedure editor automatically indents commands in a Group.

 

80. Ftype() function can limit types searched

The Ftype() function is used to either validate user input (ensuring that the supplied information is valid) or to ensure that the prerequisites for a particular test or calculation are present. Usually this validation involves testing that an object has a specific type, or perhaps a limited range of values.

To address this situation, the Ftype() function includes an optional parameter that allows you to specify which types are valid. If the object does not exist, or is not one of the valid types, then the function returns “U” for “Unknown”.

 

10 More Reasons to Like Arbutus (81-90)