|
On Aug 2, 2018, at 5:43 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:
Jon,
Well it sounded like a good idea...and RDi likes it...but the compiler
doesn't. PMR time I suppose....
dcl-ds origEstData extname('SD1405P':'ORIGEST':*OUTPUT);
hideApprovalContactInfo ind pos(1);
doubleSpace ind pos(2);
end-ds;
128600 dcl-ds origEstData extname('SD1405P':'ORIGEST':*OUTPUT);
*--------------------------------------------------------------------------------------------*
* Data structure . . . . . . : ORIGESTDATA
*
* External format . . . . . : ORIGEST : DTCWILT/SD1405P
*
*--------------------------------------------------------------------------------------------*
000001=D *IN31 1N
======> aaaaa
*RNF3314 20 a 54000001 The Name entry is a reserved word; defaults to
blanks.
000002=D *IN32 1N
======> aaaaa
*RNF3314 20 a 54000002 The Name entry is a reserved word; defaults to
blanks.
On Thu, Aug 2, 2018 at 3:15 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
Could you perhaps use ExtName instead of LikeRec? A DS created in that--
way can have fields added to it, which would allow you to use Overlay to
name the indicator fields.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Aug 2, 2018, at 3:48 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:indicators
OK,
So for those on midrange-l, you might have saw my post about SCS spool
files.
My "it's not working" ended up being caused by the fact I was using a
LIKEREC() DS to write to the printer file; the indicators used by the
record are included in the LIKEREC() DS.
I had forgotten (maybe never realized) this.
so now I've got
dcl-ds myrec likerec(MYPRTFR);
myrec.IN32 = *ON;
write myprtfr myrec;
Except, I'm not fond of the IN32 :)
Is there anyway give that indicator a name?
I realize I could use INDDS() on the f-spec; But this is an existing
program and I'd rather not have to retrofit names onto the other
right now.one
Declaring a standalone variable based on the %addr(myrec.in32) would be
solution I suppose. But I'd need one for every indicator used. Orperhaps
since the indicators are at the start of the LIKEREC() DS I could justuse
it's address...mailing list
Any other ideas?
Thanks!
Charles
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
To post a message email: RPG400-L@xxxxxxxxxxxxquestions.
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
link: http://amzn.to/2dEadiD
Help support midrange.com by shopping at amazon.com with our affiliate
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
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.