One or more Ispec records define an Ispec for GLI input. Succeeding DATA records for that Ispec is processed in the defined format until end-of-input, or until any new Ispec records redefine that format.
Persistent Ispecs which do not have presentations are not valid.
Positions 1 through 5 must contain the value Ispec, and position 6 must be left blank. The remaining positions are free-format, containing commands and valid operands.
If there is an error in an Ispec record, the GLI program returns a FATAL message and goes to EOJ at that point. All data preceding the error will have been successfully loaded.
Your Ispec input data can be in one of two types of format:
Agile Business Suite-formatted (conversion is bypassed)
User-formatted (conversion for Agile Business Suite is required)
You can redefine Ispec format or format type by including new Ispec records in your GLI input. Data input records for an Ispec must correspond to the most recent format.
Ispec Record for Agile Business Suite-Formatted Input
Ispec record commands for Agile Business Suite-formatted GLI input are shown in the following table. Refer to Agile Business Suite-Formatted GLI Input Data for more information and examples of Data records.
| Command | Abbreviation | Operands | Notes |
|---|---|---|---|
| COMPONENT; | COMP; | ispec | Mandatory for an Ispec |
| EVENT; | event | Mandatory for an Event | |
| FORMATTED; | (none) | Mandatory for Agile Business Suite-formatted data. You can use BYPASS; or BY; in place of FORMATTED; |
For Agile Business Suite-formatted input, specify the Ispec type, Ispec name, and the FORMATTED; command. No other commands are valid.
Example
An example of an Ispec record follows.
ISPEC EVENT; SALE FORMATTED; ISPEC COMP; PROD BYPASS;
Copy.From Ispecs
To use GLI with Copy.From Ispecs, it is recommended that you use Agile Business Suite-formatted input.
You can submit input data to only one copy of a Copy.From Ispec defined as user-formatted, although all copies are processed. The data for all copies but the first is automatically zeros or spaces. This is the same as a screen-entered Copy.From Ispec, where only the first copy has been entered.
To submit input to all copies of a Copy.From Ispec, your input must be in Agile Business Suite format.
Ispec Record for User-Formatted Input
Valid Ispec record commands for user-formatted GLI input are listed in the following table. All commands end with a semicolon.
| Command | Abbreviation | Operand/s | Notes and References |
|---|---|---|---|
| COMPONENT; | COMP; | ispec | Mandatory for an Ispec. |
| EVENT; | event | Mandatory for an Event. | |
| DATA; | DA; | item or Glb.Spaces | Mandatory if input required. Glb.Spaces for fillers. Refer to Mandatory attributes. |
| SETUP.DATA; | SD; | item (literal) | literal is literal value. Refer to SETUP.DATA Command. |
| LENGTH; | LE; | length | Mandatory with DATA; or SETUP.DATA;. Refer to Attribute Rules. Must not exceed the length in your Specification. |
| EDIT; | ED; | edit | Optional with DATA;. Invalid with SETUP.DATA;. Refer to Attribute Rules. |
| DECIMALS; | DE; | decimals | Required if in input data. Refer to Attribute Rules. |
For user-formatted data, you can use one or more Ispec records to define edit characteristics and the sequence of attributes in your input data records for that Ispec, subject to the following rules. (Refer to User-Formatted GLI Input Data in GLI Data Records for more information and examples of actual input data.)
General Rules
The following general rules apply to Ispec records defining user-formatted GLI input:
At least one DATA; or SETUP.DATA; command is required.
All attributes declared for the Ispec (except Direction None, Persistence items) are valid.
Attribute names must be as declared for the Ispec in your Specification.
Data values in GLI DATA records must be input in the exact order they are declared in the most recent GLI Ispec record (for that Ispec).
Attributes need not be specified in the order they are declared in your Specification.
You do not have to include all attributes from the associated Ispec. Input values for any attributes not declared in the GLI Ispec record defaults to blanks or zeros.
You must include all attributes that are loaded by your GLI program.
Glb.Spaces might also be declared between attributes, to allow your GLI input data to contain spaces. You must specify a length. For example, DATA; Glb.Spaces LE; 2.
Mandatory Attributes
The following attributes are mandatory in Ispec records defining user-formatted GLI input:
ActMth must be specified (without an EDIT; command).
Maint is required for Standard, Table, and Multiple Ordinate Memo Components.
Attributes declared with the REQUIRED; Data attribute in Ispecs must be included in the relevant Ispec records, otherwise input data for these Ispecs are rejected.
LAST-LINE is a required attribute for Repeat.From Ispecs.
Invalid Attributes
The following attributes are invalid in Ispec records defining user-formatted GLI input:
Input_Date and TranNo
Direction None, Persistence items. (Unpredictable results occur if these are used.)
Attribute Rules
The following rules apply to GLI Ispec records defining user-formatted GLI input:
Each data name must have an associated LENGTH; command. This length must be less than or equal to that specified in your Specification.
The EDIT; command is optional, although it must not be present for ActMth. EDIT; A is the default. The edit type for an item must match that defined in your Specification.
The DECIMALS; command is required if you want to input decimal digits. The operand must not exceed the decimals declared for that attribute in your Specification.
Refer to User-Formatted GLI Input Data in GLI Data Records for more information.
SETUP.DATA Command
The SETUP.DATA; command differs from that in logic. For GLI user-formatted input, it specifies a common input value that applies for every DATA; input record for an Ispec, so that it does not have to be repeated in each record. The following rules apply to the GLI SETUP.DATA; command:
The literal value and its enclosing brackets are mandatory. Neither leading nor trailing spaces are permitted in the literal value.
LENGTH; is required. The length value must equal the number of characters within the parentheses, and must be less than or equal to the length specified in your Specification.
EDIT; and DECIMALS; are not valid. The literal value must be the correct type, with the correct number of decimal digits (if any), and without a decimal point and separator characters.
No space is reserved for these attributes in GLI DATA; records.
Example
An example of an Ispec record defining user-formatted GLI input data follows.
ISPEC EVENT; ETEST 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; 9 ED; C DE; 2 ISPEC DA; AMOUNT3 LE; 9 ED; - DE; 2 ISPEC SD; ACTMTH (0006) LE; 4
The corresponding GLI DATA; record input for this example is shown under “User-Formatted GLI Input Data” in GLI Data Records.