|
midrange.com
This is the code for the calling program. CALD value is the called program
"DODATE".
0103.00 C *ENTRY PLIST
0103.01 C PARM PA 128
0103.02 C PARM PRM1 256
0103.03 C PARM PRM2 256
0326.00 C CALL CALD
0326.01 C PARM PA
0326.02 C PARM PRM1
0326.03 C PARM PRM2
---------------------------------
John Jones
IBM AS/400 Lansa Developer
Pacific Information Systems - An IBM Premier Business Partner
Cell 503-784-4422
Fax 503-244-5300
"WE KNOW TECHNOLOGY"
johnj@pacinfosys.com
---------------------------------
"Peter Dow"
<pcdow@MailAndNew To: <RPG400-L@midrange.com>
s.com> cc:
Sent by: Subject: Re: RPGIV MoveA
issue.
owner-rpg400-l@mi
drange.com
01/22/2001 12:37
PM
Please respond to
RPG400-L
Hi John,
You showed us everything except how PA, PRM1 and PRM2 are defined in the
calling program. If they are defined as shorter fields than in the program
you showed, you may very well get overlapping fields. For example, if PRM1
and PRM2 are defined as 10A in the calling program, they will most likely
be
placed in 20 bytes of contiguous storage. Your RPG program's references to
PRM1 will overwrite PRM2, and some undefined storage beyond that.
HTH,
Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax
> It sounds funny, but when a "movea" instruction occurs for one
> field, another field is updated. Its all outlined in the "movea
> issue.txt" file. The fields updated are defined within the program and
> defined as parameters. I have included the code listing and RPG dump for
> reference. This code is working currently running on a AS/400 Advanced
36
> Machine.
> Why is PRM1 updated when a movea instruction for PRM2 occurs?
> Position 34 to 87 are blanked out. Why?
> ---------------------------------
> John Jones
> IBM AS/400 Lansa Developer
> Pacific Information Systems - An IBM Premier Business Partner
> Cell 503-784-4422
> Fax 503-244-5300
> "WE KNOW TECHNOLOGY"
> johnj@pacinfosys.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 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.
