× 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
  • From: "alan shore" <SHOREA@xxxxxxxx>
  • Date: Wed, 11 Apr 2001 10:33:04 -0400

My apologies. You are correct.

>>> "Mike Collins (syan)" <mike.collins@syan.co.uk> 04/11/01 09:41AM >>>
Yes you are wrong. Batch jobs inherit the *LDA from the submitting job. This is
why the *LDA is so commonly used to pass parameters between programs.




alan shore <SHOREA@dime.com>@INTERNET@midrange.com> on 11/04/2001 14:28:56
Please respond to RPG400-L <RPG400-L@midrange.com>@INTERNET
Sent by: owner-rpg400-l <owner-rpg400-l@midrange.com>
To: RPG400-L <RPG400-L@midrange.com>@INTERNET
cc:

Subject: Re: LDA-problem

The other thing to consider, is, are ALL of these programs Interactive. If any
of these programs are run in QBATCH, That is another job, and I believe (I may
be wrong) that the *LDA is initialized.

>>> <MBarton@pink.co.uk> 04/11/01 07:55AM >>>

>Hi, I'm having *LDA trouble ...

Michel
     when using the LDA in RPG the program remembers the value
in the LDA unless you use the IN opcode to force it to read the new value
put in by your pgm3.

What I beleive is happening is that if you are not doining an IN in pgm2
after the call to pgm3, pgm2 will ignore the new values put in by pgm3 &
will update the LDA (on LR) with what it thought the values were when it
ran.
Hence you end up back at zero.
You will need to put an IN in pgm1 if you want this program to start at the
updated value set by pgm3

Mike

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

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