× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: LDA-problem got solved
  • From: "alan shore" <SHOREA@xxxxxxxx>
  • Date: Wed, 11 Apr 2001 12:54:10 -0400

Sorry, I could'nt resist that prior reply. However, it seems that my previous 
comment that a Local Data Area (Object Type *LDA) is initialised with each sign 
on
and I quote
                       Data area (DTAARA) - Help                           
                                                                                
            
        outside the group.  The length of this character data     
        area is 512 bytes.                                           
                                                             
        *LDA                                                           
        The local data area is displayed.  The local data area  
        (*LDA) is a character data area 1024 bytes in length.   
        It is automatically associated with your job and               
        cannot be accessed from another job.                       
                                                             
end-quote.

>>> <michel.cuypers@newwave.be> 04/11/01 12:17PM >>>


Hi, Y'All,

Problem is cracked 'n solved.

Thanks to Mike & Alan
     (Alan, also: sorry for being somewhat sarcastic, earlier-on)

Even though processing seemed to work in pgm3, and (+- identically coded) in
pgm1,
You guys got me thinking about the *LDA definition itself,
and I changed the LDA-coding as follows:

PGM1:
     D* LDA (LAST USED ENTITY NR)
     D                 DS
     D  $LDA                   1   1024
     D  ENTITY              1020   1024
     . . .
     C     *DTAARA       DEFINE    *LDA          $LDA

     . . .  Calculating $ENTY ...
     C* FILL IN LDA
     C                   IN        $LDA
     C                   MOVEL     $ENTY         ENTITY
     C                   OUT       $LDA
     C*

PGM2: No LDA-processing, whatsoever.

PGM3:
     D* LDA (LAST USED ENTITY NR)
     D                 DS
     D  $LDA                   1   1024
     D  ENTITY              1020   1024
     . . .
     C     *DTAARA       DEFINE    *LDA          $LDA

      C* NEW ENTITY
     C* KEEP IN LDA
     C                   Z-ADD     0             $ENTY             5 0
     C*
     C                   IN        $LDA
     C                   MOVEL     ENTITY        $ENTY
     C                   ADD       1             $ENTY
     C                   MOVEL     $ENTY         ENTITY
     C                   OUT       $LDA
********
Finally,it works...
     Even though I still don't get it why it did work in pgm3 and NOT in pgm1.
(Pgm3 was ended after each processing, as You recall ...)

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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.