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



https://www.ibm.com/support/pages/samepos-keyword-73-ptf has the ptf level and RDi level you need to be on. Pos(1) should work if that is all you have in your data structure.

On Fri, 2021-03-12 at 16:58 +0000, (WalzCraft) Jerry Forss wrote:

RDi doesn't like the SamePos.

I'm on 7.3 tr6.


-----Original Message-----

From: RPG400-L <

<mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx>

rpg400-l-bounces@xxxxxxxxxxxxxxxxxx

On Behalf Of Scott Klement

Sent: Friday, March 12, 2021 10:53 AM

To:

<mailto:rpg400-l@xxxxxxxxxxxxxxxxxx>

rpg400-l@xxxxxxxxxxxxxxxxxx


Subject: Re: File Fields In Array


Jerry,


I think you're on the right track. personally, I'd try to avoid hard-coding the size/positions of the fields, though. If the various

SlOthCtr1 fields are externally defined, I'd do this:


dcl-ds *n;

SlOthCtr1;

SlOthCtr2;

.

.

SlOthCtr28;

Containers like(SlOthCtr1) dim(28) samepos(SlOthCtr1); end-ds;


That way, you keep the external definitions of SlOthCtrXX, and the size of Containers will be the same size as well. Instead of hard-coding the position in the DS, I used SamePos, so if extra stuff is added/removed from the DS, it won't matter. The only thing that's still hard-coded is the DIM statement,.


The other thing you might consider is using the name SlOthCtr for the array rather than Containers. That way, someone who is already familiar with the field will recognize it. They won't have to know/remember that 'Containers' is equivalent.


On 3/12/2021 10:10 AM, (WalzCraft) Jerry Forss wrote:

Hi All,


I know this is a simple question but is escaping me at the moment.


I have a file that contains fields SLOTHCTR1 - SLOTHCTR28, each 40 char.


I want to have these loaded into an array because I need to change some, print label, change again, print and so on.


Changing by index would be immensely less coding then changing the field directly.


This is basically what I what it to look like.


Dcl-DS *n;

Containers Dim(28);

SlOthCtr1 Char(40) Overlay(Containers);

SlOthCtr2 Char(40) Overlay(Containers : *Next);

SlOthCtr3 Char(40) Overlay(Containers : *Next);

SlOthCtr4 Char(40) Overlay(Containers : *Next);

SlOthCtr5 Char(40) Overlay(Containers : *Next);

SlOthCtr6 Char(40) Overlay(Containers : *Next);

SlOthCtr7 Char(40) Overlay(Containers : *Next);

SlOthCtr8 Char(40) Overlay(Containers : *Next);

SlOthCtr9 Char(40) Overlay(Containers : *Next);

SlOthCtr10 Char(40) Overlay(Containers : *Next);

SlOthCtr11 Char(40) Overlay(Containers : *Next);

SlOthCtr12 Char(40) Overlay(Containers : *Next);

SlOthCtr13 Char(40) Overlay(Containers : *Next);

SlOthCtr14 Char(40) Overlay(Containers : *Next);

SlOthCtr15 Char(40) Overlay(Containers : *Next);

SlOthCtr16 Char(40) Overlay(Containers : *Next);

SlOthCtr17 Char(40) Overlay(Containers : *Next);

SlOthCtr18 Char(40) Overlay(Containers : *Next);

SlOthCtr19 Char(40) Overlay(Containers : *Next);

SlOthCtr20 Char(40) Overlay(Containers : *Next);

SlOthCtr21 Char(40) Overlay(Containers : *Next);

SlOthCtr22 Char(40) Overlay(Containers : *Next);

SlOthCtr23 Char(40) Overlay(Containers : *Next);

SlOthCtr24 Char(40) Overlay(Containers : *Next);

SlOthCtr25 Char(40) Overlay(Containers : *Next);

SlOthCtr26 Char(40) Overlay(Containers : *Next);

SlOthCtr27 Char(40) Overlay(Containers : *Next);

SlOthCtr28 Char(40) Overlay(Containers : *Next);

End-Ds;


That way I can change the fields by changing the Containers(x);


What should this look like?




--

This is the RPG programming on IBM i (RPG400-L) mailing list To post a message email:

<mailto:RPG400-L@xxxxxxxxxxxxxxxxxx>

RPG400-L@xxxxxxxxxxxxxxxxxx

To subscribe, unsubscribe, or change list options,

visit:

<https://lists.midrange.com/mailman/listinfo/rpg400-l>

https://lists.midrange.com/mailman/listinfo/rpg400-l


or email:

<mailto:RPG400-L-request@xxxxxxxxxxxxxxxxxx>

RPG400-L-request@xxxxxxxxxxxxxxxxxx


Before posting, please take a moment to review the archives at

<https://archive.midrange.com/rpg400-l>

https://archive.midrange.com/rpg400-l

.


Please contact

<mailto:support@xxxxxxxxxxxxxxxxxxxx>

support@xxxxxxxxxxxxxxxxxxxx

for any subscription related questions.


Help support midrange.com by shopping at amazon.com with our affiliate link:

<https://amazon.midrange.com>

https://amazon.midrange.com





Subject to Change Notice:


WalzCraft reserves the right to improve designs, and to change specifications without notice.


Confidentiality Notice:


This message and any attachments may contain confidential and privileged information that is protected by law. The information contained herein is transmitted for the sole use of the intended recipient(s) and should "only" pertain to "WalzCraft" company matters. If you are not the intended recipient or designated agent of the recipient of such information, you are hereby notified that any use, dissemination, copying or retention of this email or the information contained herein is strictly prohibited and may subject you to penalties under federal and/or state law. If you received this email in error, please notify the sender immediately and permanently delete this email. Thank You


WalzCraft PO Box 1748 La Crosse, WI, 54602-1748

<http://www.walzcraft.com<http://www.walzcraft.com>>

www.walzcraft.com<http://www.walzcraft.com>

Phone: 1-800-237-1326



[https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com



CONFIDENTIALITY NOTICE

This document and any accompanying this email transmission contain confidential information, belonging to the sender that is legally privileged. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, or the employee of agent responsible to deliver it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or action taken in reliance on the contents of these documents is STRICTLY PROHIBITED. If you have received this email in error, please notify the sender immediately to arrange for return or destruction of these documents.

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.