Re: LDA-problem, adding more specs.

[michel.cuypers@xxxxxxxxxx]

You'd better get your foot out again, Alan,
coz' You really did it again...

No:
A user starts a certain job (Order-processing,  in this case)

     So, first he defines which order he'll start working on (Pgm1: also initial
LDA-defn, see further)

     After defining the order, pgm 1 automatically calls pgm2:    To select
which orderline is to be processed

     After defing the order line, pgm2 calls pgm3:           To process the
selected line.
                                         (incl: rtv LDA, prc LDA, sav LDA)

Sometimes, the user has to process such a large order, that he 'll split
processing
(for instance: over 2 days)

So the next day, I want him to pick up where he left off:
     Firstly, pgm1 reads all records processed, to get the highest value of a
certain entity.
     After finding it, this value is saved in the LDA

Now You got it ?

Greetings, Michel
                    ___________________________________________________

Michel Cuypers,  Analyst Programmer

 New Wave Logistics  (BELGIUM) NV
 2 Keetberglaan  Haven 1089  9120 Melsele
 Tel +32.3.570.69.13  Fax +32.3.570.69.95
 GSM +32.478.33.72.16

 mailto:michel.cuypers@newwave.be
___________________________________________________



|--------+----------------------->
|        |          "alan shore" |
|        |          <SHOREA@dime.|
|        |          com>         |
|        |                       |
|        |          11/04/01     |
|        |          16:40        |
|        |          Please       |
|        |          respond to   |
|        |          RPG400-L     |
|        |                       |
|--------+----------------------->
  >----------------------------------------------------------------------------|
  |                                                                            |
  |       To:     RPG400-L@midrange.com                                        |
  |       cc:     (bcc: Michel Cuypers/New Wave Logistics Belgium)             |
  |       Subject:     Re: LDA-problem, adding more specs.                     |
  >----------------------------------------------------------------------------|




In other words, the user signs off (or is automatically signed off). The Local
Data Area (object type *LDA) is automatically initialised EACH time the user
signs on. (Again, I may be wrong on this, but this time I'm fairly sure[ says he
ready to insert foot into mouth ONCE AGAIN])

>>> <michel.cuypers@newwave.be> 04/11/01 09:40AM >>>


Hi, Y'All,

I think I must elaborate a bit on the processing codes & - circumstances

1. First of all, all pgms are interactive.
2. To code the *LDA I use following instructions.

In pgm 1, I use
138.00 D* LDA
139.00 D                UDS
140.00 D  ENTITY              1020   1024
141.00 C****************************************************
                             ...
1015.00 C* FILL IN LDA
1016.00 C     *LOCK         IN        *DTAARA
1017.00 C                   MOVEL     $ENTY         ENTITY
1018.00 C                   OUT       *DTAARA
1019.00 C*

In pgm 2, I don't use anything

And in pgm 3, I use

0145.00 D* LDA
0146.00 D                UDS
0147.00 D  ENTITY              1020   1024
0148.00 C*********************************************
          ...
0568.00 C* NEW ENTITY
0569.00 C* ----------
0570.00 C* KEEP IN LDA
0571.00 C                   Z-ADD     0             $ENTY
0572.00 C     *LOCK         IN        *DTAARA
0573.00 C                   MOVEL     ENTITY        $ENTY
0574.00 C                   ADD       1             $ENTY
0575.00 C                   MOVEL     $ENTY         ENTITY
0576.00 C                   OUT       *DTAARA

Pgm 3-coding seems to be working, since during toggling through pgms2-3  the
ENTITY-value is incremented ...

On the other hand, In pgm-1  $ENTY is calculated and supposedly put in *LDA:
ENTITY
to calculate & pick up the entity-value where it was left off (for instance, the
day before)
This calculation is OK (debugging) , but ...

Greetings, Michel
___________________________________________________


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---




+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---