If the data request was successful, a status of OK (and four space characters) is returned in positions 1 through 6, with the data commencing in position 153. Requested data is output in a similar format to the data displayed on a terminal screen, subject to the following rules and conditions:
The standard Agile Business Suite message header information is output in positions 153 through 178, as shown in the following table.
| Attribute | Length | Positions |
|---|---|---|
| Ispec | 5 | 153 through 157 |
| Glb.Source | 1 | 158 |
| TranNo | 6 | 159 through 164 |
| Input_Date | 7 | 165 through 171 |
| ActMth | 4 | 172 through 175 |
| Maint | 3 | 176 through 178 |
The remaining properties are output in screen display sequence.
Property lengths are as for Agile Business Suite-formatted GLI input (that is, as for screen display). Numeric attributes have the following special requirements:
Numeric attributes are always output right-justified, without decimal and separator characters. If the attribute has the Separator and/or DecimalCharacter property set, a leading zero is output for each separator and decimal character. In a transaction, Agile Business Suite replaces leading zeros in numeric attributes that have decimals with spaces, so that larger values cannot be moved back into the property.
Signed numeric attributes are output with their sign indicated by adjustment of the last digit of the property, as shown in the following table
Last digit position… | 0 1 2 3 4 5 6 7 8 9 |
|---|---|
Output value for positive values… | { A B C D E F G H I |
Output value for negative values… | } J K L M N O P Q R |
Although you must allow output positions for the one-character or two-character sign value for EDIT +, -, DR, and CR items, ignore any value in these positions.
Note: Input and output formats for signed data are different.