Problem on Script Logic

Question

Hi all,
I have write a script logic.
I have got this values like transactional data.
First data: how many vehicle that we need to produce in jan, feb?
  ACCOUNT--VEHICLE NOMATERIAL NOTIME--
VALUE
1)D003--142NAJAN--
4
2)D003--142NAFEB--
10
3)D003--940NAJAN--
3
4)D003--940NAFEB--
5
Secod data: which material and how many that we need for to form one vehicle.
  ACCOUNT--VEHICLE NOMATERIAL NOTIME--
VALUE
5)E001--142142OTONA--
100
6)E001--940142OTONA--
100
7)E001--14258RSNA--
60
8)E001--94058RSNA--
60
9)E001--94054RSNA--
40
Third, to calculate data: how many material that we need in Jan or Feb.
  ACCOUNT--VEHICLE NOMATERIAL NOTIME--
VALUE
10)F001--NA142OTOJAN--
700
11)F001--NA58RSJAN--
420
12)F001--NA54RSJAN--
120
For example 142OTO: 700(10)=100(5)4(1)+100(6)3(3)
(The numbers in parenthesis are line numbers.)
How can i write this logic?
Thanks in advance.
Edited by: boguner on Jun 22, 2010 10:49 AM

Answer 1

Hi Rohit,
This is not a problem.
If the resultant number of records is more than 300,000, then the records are not logged.
This can be controlled by the UNLIMIT_PRINT_LOG appset parameter. By default, this is set as NO. This will allow only 300k records to be logged.
You can set the above parameter as YES to log all the records for the execution of all logics across the appset in all applications.
Warning:
Of course, it will add slow down the logic execution. Logging the records will always slow down the execution. The system has to open the file and keep writing all the records in the flatfile, which is a slow process. You can increase the speed of your logics by disabling this logging completely by using the CALCULATE_DIFFERENCE statement in your script logic for each commit section. You can reduce the logic execution time by disabling this logging.
Karthik AJ