Data records are passed to your application by the GLI program.
The following points apply to both types of input format:
Data records might be inserted at any time after the Ispec record defining the associated format.
Positions 1 through 5 must contain the name of an Ispec previously defined to GLI. The name must be left-justified and space-filled. Position 6 should be left blank.
The remainder of the record is formatted as specified in the relevant Ispec record, depending on the current format type for that Ispec. Refer to GLI Ispec Record for more information.
Always right-justify numeric values (including those with the LEFTFILL attribute).
Spare character positions should be left blank, and spare numeric positions zero-filled.
Add, Bac, Chg, Del, Fir, Inq, Las, Nex, Pur, and Rec are valid values for the attribute Maint, unless these have been translated by using multiple language facilities (Refer to Multiple Language and Translation Capabilities).
Do not enter decimal or separator characters for an attribute (whether or not, it has Separator or Decimal properties).
You might submit input to only one copy of a Copy.From Ispec defined as user-formatted. To submit input to all copies of a Copy.From Ispec, input must be Agile Business Suite-formatted.
Signed numeric data values are input differently for Agile Business Suite-formatted and user-formatted input, as explained in the following subsections.
Agile Business Suite-Formatted GLI Input Data
Input data format is similar to that received from a terminal, subject to the following rules and conditions:
Positions 1 through 5 contain the Ispec name.
Position 6 (reserved for Glb.Source) should be left blank.
The next four positions must contain the value of ActMth.
For Standard, Table, and Multiple Ordinate Memo Components, the next three positions contain the value for Maint.
The remaining properties must be in screen display sequence.
Input property lengths are as for screen display. However, numeric attributes have the following special requirements:
Input of numeric attributes must never include decimal and separator characters. If the attribute has the Separator and/or DecimalCharacter property set, you must add a leading zero for each separator and decimal position. In a transaction, Runtime replaces leading zeros in numeric attributes that have decimals with spaces, so that larger values cannot be moved back into the property.
Signed numeric attribute values must be followed by their appropriate sign (+, - , DR, CR). Do not enter spaces.
Example of Agile Business Suite-formatted GLI Data Records
In this example, the attributes for an Event ETEST are defined as follows:
DATA; CNUMBER LE; 10 ED; N DATA; PCODE LE; 5 ED; A DATA; AFILLER LE; 2 ED; A DATA; AMOUNT1 LE; 9 ED; - DE; 2 DATA; AMOUNT2 LE; 9 ED; C DE; 2 DK; DATA; AMOUNT3 LE; 9 ED; S DE; 2 DK; SP; ,
The GLI Ispec record and an example of a Data record follow.
ISPEC EVENT; ETEST FORMATTED; ETEST 00061234567890ABCDExx123456789+0123456789CR000123456789DR
The resulting data values input to the application for ETEST are as follows:
| Attribute | Resulting Value |
|---|---|
| ActMth | 0006 |
| CNUMBER | 1234567890 |
| PCODE | ABCDE |
| AFILLER | xx |
| AMOUNT1 | +1234567.89 |
| AMOUNT2 | -1234567.89 |
| AMOUNT3 | +1234567.89 |
User-Formatted GLI Input Data
Input data format is as specified in the relevant GLI Ispec records, subject to the following rules:
Attributes in DATA; records for the Ispec must be in the same order and have the same property lengths as declared in the GLI Ispec record.
Spare character positions should be left blank.
A leading zero is not necessary for decimal items.
All decimal points are implied.
Only one copy of a Copy.From Ispec can be entered. The remaining copies are treated as spaces or zeros. (Agile Business Suite-formatted input is recommended for Copy.From Ispecs, refer to Ispec Record for User-Formatted Input in GLI Ispec Record.)
All logic declared in the Ispec (except _Construct method) is performed on data entered through GLI. This includes all automatic logic such as editing and validation (for example, LINK; IF.PRESENT, EDIT; D, and so on).
To reverse the default sign for a signed numeric data values, adjust the first digit of the input property, as shown in the following table.
| First digit: | 0 1 2 3 4 5 6 7 8 9 |
| Adjusted value to reverse sign: | } J K L M N O P Q R |
Examples of signed properties are shown in the following table. The Screen Display column shows equivalent values as they would appear on an input screen.
Data Attributes | Numeric Value | Input Required | Screen Display |
|---|---|---|---|
LENGTH; 5 ED; - | -54321 | 54321 | 54321- |
LENGTH; 5 ED; - | 12345 | J2345 | 12345 + |
LENGTH; 8 ED; + | -54321 | }0054321 | 54321 - |
LENGTH; 7 ED; C | -7766554 | 7766554 | 7766554 CR |
LENGTH; 7 ED; C | 4556677 | M556677 | 4556677 DR |
LENGTH; 7 ED; S | -7766554 | P766554 | 7766551 CR |
Example of User-formatted Data
In this example, attribute specifications for Event ETEST are as follows:
DATA; CNUMBER LE; 10 ED; N DATA; PCODE LE; 5 ED; A DATA; AFILLER LE; 2 ED; A DATA; AMOUNT1 LE; 9 ED; - DE; 2 DATA; AMOUNT2 LE; 9 ED; C DE; 2 DK; DATA; AMOUNT3 LE; 9 ED; S DE; 2 DK; SP; ,
The corresponding GLI Ispec records and an example of a DATA record for ETEST follow.
SPEC EVENT; ETEST SD; ACTMTH (0006) LE; 4 ISPEC DA; CNUMBER LE; 10 ED; N ISPEC DA; PCODE LE; 5 ED; A ISPEC DA; GLB.SPACES LE; 2 ED; A ISPEC DA; AMOUNT1 LE; 9 ED; - DE; 2 ISPEC DA; AMOUNT2 LE; 8 ED; C DE; 2 ISPEC DA; AMOUNT3 LE; 9 ED; S DE; 2 ETEST 1234567890ABCDEyyJ2345678922222222123456789
The resulting data values from this GLI input to ETEST in the application are as follows:
ACTMTH 0006 AMOUNT1 +1234567.89 CNUMBER 1234567890 AMOUNT2 -222222.22 PCODE ABCDE AMOUNT3 +1234567.89 AFILLER yy
Note: The value of ActMth is not entered in the GLI DATA record. The SD; (SETUP.DATA;) value (0006) applies for all input for that Ispec (until it is changed).