3.16.4 Detailed Batch Control Logic Maintenance
- The Display Batch Control Logic screen is displayed when reviewing existing access batch control logic in detail.
- The Create Batch Control Logic screen is displayed when specifying the details of new batch control logic.
|
DC@P201002 Create Batch Control Logic
File : XXXXXXXXXX XXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (XXXX )
Description . . . . . . . . . __________________________________
Batch Control File Name . . . . __________
Linked Batch Control fields -In this file . . . . ____________________________________ -In control file . . ____________________________________
Key to Access Control file . . ____________________________________ ____________________________________ ____________________________________ ____________________________________ ____________________________________
Fnn=Help Fnn=Exit Fnn=Cancel Fnn=Messages
|
Note: The Delete function key is only enabled when reviewing existing batch control.
Working from the Create Batch Control Logic screen you can:
- Review the full details of existing batch control logic.
- Delete existing batch control logic. Use the Delete function key to indicate that the batch control logic should be deleted. On the resulting display enter YES to confirm that the batch control logic should be deleted. If YES is not entered the batch control logic will not be deleted.
Input Options
These input options apply when defining new batch control logic to be included into a file definition:
Description
Specifies a description that will aid other users of this file definition in identifying the purpose of the batch control logic. Entry of some form of description is mandatory.
Batch Control File Name
Specifies the name of the physical or logical file that is to be maintained by this batch control logic. The physical or logical file specified must have already been defined to the LANSA system and made operational.
The file specified cannot contain batch control logic itself. If this causes a problem, investigate moving the batch control logic from the "batch control file" to this file (the file definition currently being worked with). In most cases this technique will satisfy all batch control requirements.
File name can be entered in full, partially or left blank. If required a list of available files will be displayed and the required file chosen.
Linked Batch Control Fields
Specifies the "pairing" of the batch control fields from this file (i.e. the file definition being worked with) with those from the file nominated as the "batch control file name". At least one pair of fields is required.
Note that while LANSA will check that all fields nominated exist in their respective files, and are numeric, it will not check the sizes. Thus it is possible to accumulate a field with 4 decimal positions into a field with no decimal positions. All decimal precision would be lost and the accumulation would probably be "rubbish".
Likewise a field with 15 significant digits could be accumulated into a field with 1 significant digit. Again the accumulation would almost certainly be "rubbish".
Note: The checking (and testing) of accumulated field precision is a user responsibility and is not performed by LANSA.
In this file
Specifies from 1 to 4 fields in this file (i.e. the file definition currently being worked with) that are to be accumulated into the "batch control file". All fields nominated must be defined in this file and must be numeric.
In control file
Specifies from 1 to 4 fields in the "batch control file" that are to hold the accumulations of the fields from this file ( nominated directly above). All fields nominated must be defined in the "batch control file" and must be numeric.
By entering a partial name or a '?' in these fields the single field selection screen will be displayed for each. The selection list will be built from the real fields in the current file or control file as appropriate. Refer to 3.10.1 Select Fields When Working from File Definition Menu for more details.
Keys to Access Control File
Specifies the fields or values that should be used to form the key that will be used to access the appropriate record in the file named as the "batch control file". If field names are used then they must be defined in this file (i.e. the file definition that is being worked with - not the file named as the "batch control" file).
At least one key field or value is required. Up to 20 key fields or values can be specified. Use the ROLL UP key to enter more.
Entries made can be:
- An alphanumeric literal (in quotes) such as 'NSW', 'BALMAIN'
- A numeric literal such as 1, 14.23, -1.141217.
- Another real field name such as CUSTNO, INVNUM, etc. As mentioned the field must be defined in the current file definition. Please note that you must not use a virtual field. If you need to use a virtual field in the key, then code the batch control update logic into a trigger. Use of virtual fields may lead to unpredictable and/or unexpected results. (A '?' will display the single field selection screen. The selection list will be built from all the real fields in the current file. Refer to 3.10.1 Select Fields When Working from File Definition Menu for more details.)
- A system variable name such as *BLANKS, *ZERO, *DATE or any other system variable defined at your installation.
Key values are checked for type and length compatibility. The entire key list supplied is checked for compatibility with the actual key(s) of the "batch control file". The key list specified can be a full or partial key to the file.
A warning is issued if a partial key list is specified. The use of a partial key in this particular situation would be rare. If a warning message is issued carefully check/reconsider exactly what batch control logic has just been defined.