× 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 again, Barbara.


Best Regards,

Thomas Garvey



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Barbara Morris
Sent: Wednesday, July 30, 2008 11:41 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: DDS Starting Line Number (SLNO)

Thomas Garvey wrote:
Thanks, Barbara, for your answer. I never thought of looking in the
RPG manual for a DDS specification. Can I presume I can use a
different field for different display record formats? (Assuming I
need to have different formats, using the SLN(*VAR) feature, on the
display at the same time.)


RPG's SLN keyword applies to the whole file. I guess you'd have to keep
separate variables for the start line for each record, and set the SLN
variable before you EXFMT or WRITE each record. I assume this would
work, but I've never tried having two SLNO formats in the same file.

Fmydspf cf e workstn sln(mydspfSlnVar)

mydspfSlnVar = headerSln;
write header;
mydspfSlnVar = footerSln;
write footer;

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.



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.