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



Vern,

When I move MyDS to a global declaration, I get RNF3804 field not renamed on two of the fields when I compile. There are 6 others that don't give this problem. All are type B in the DDS of the DSPF.

-----Message d'origine-----
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Vern Hamberg

Be sure to check whether the data structure needs to be
global - if it is local, it won't be known to the F-spec at
the program level, seems to me.

Vern

David FOXWELL wrote:
Hi, all.

I just added a DS to a procedure with the idea that it
would be populated automatically when the user enters data.
In the record MyFormat is one zoned decimal field, all the
rest are character fields.
At the EXFMT MyDSPF, I get MCH1202.

The code is basically this :
D MyDS E DS EXTNAME ( MyDSPF :
MyFormat:*INPUT )

/FREE
MyNumField = 0;
EXFMT MyFormat;

While debugging, there seems to be confusion between
MyNumField of MyDS and MyNumField of MyDSPF. If I do EVAL
MyNumField at the EXFMT, I see that MyNumFld = 0. If I step
into the EXFMT, and then type EVAL MyNumField, I then see
that MyNumFld = blank. I've tried INZ on the MyDS declaration
and also CLEAR MyDS.

What am I doing wrong? Is there a better way?

In the DSPF there are many many field names that occur in
different record formats.
For that reason, I wanted to store the contents of MyFormat
in a global qualified DS.



Thanks


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.