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




Thanks for the feedback.  It's good to here that I'm not the first.  My
code is moving the parm-fields to other fields, however, since I'm
returning the requested data back to the calling program via parameters, I
must update the parm-fields.  It is at that time when the error occurs on
the movea statement.   Since this method of calling programs is almost 1000
programs, I would like to find the best solution.

Thanks.

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




                                                                                
           
                    Kevin Howcroft                                              
           
                    <kevinh@kmtcinc.c        To:     RPG400-L@midrange.com      
           
                    om>                      cc:                                
           
                    Sent by:                 Subject:     Re: RPGIV MoveA 
issue.           
                    owner-rpg400-l@mi                                           
           
                    drange.com                                                  
           
                                                                                
           
                                                                                
           
                    01/22/2001 01:44                                            
           
                    PM                                                          
           
                    Please respond to                                           
           
                    RPG400-L                                                    
           
                                                                                
           
                                                                                
           




A few years ago I had a similar problem,
does not matter who looked at the code, the parms kepts getting messed up.

The only work-around I resolved to in the end was to
MOVE the parm-fld  into another new-field,
then reference that new -field throughout the program.

just my experience.
kmh



At 12:37 PM 01/22/2001 -0800, you wrote:
>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
>+---

********************************************************
Kevin M Howcroft                www.kmtcinc.com
AS/400 Technical Consultant     Voice:407.830.5960
kevinh@kmtcinc.com              Fax: 407.650.2638

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