Re: External DS in RPG 400

You have the option of defining the DS based on the record format and only
the input fields like so:

d screenDS e ds extname(displayfile: rcdfmt:
*input)


EXTNAME(file-name{:format-name}{:*ALL| *INPUT|*OUTPUT|*KEY})

The EXTNAME keyword is used to specify the name of the file which contains
the field descriptions used as the subfield description for the data
structure being defined.

The file_name parameter is required. Optionally a format name may be
specified to direct the compiler to a specific format within a file. If
format_name parameter is not specified the first record format is used.

The last parameter specifies which fields in the external record to extract:

- *ALL extracts all fields.
- *INPUT extracts just input capable fields.
- *OUTPUT extracts just output capable fields.
- *KEY extracts just key fields.

If this parameter has not specified, the compiler extracts the fields of the
input buffer.


On Tue, Jun 17, 2008 at 8:51 AM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
wrote:

David Gibbs wrote:

David FOXWELL wrote:

I've declared a data structure based on the DSPF that is already in
the F specs of my program. ( what I really wanted was to do a LIKEREC
format name ).

I don't think external data structures based on display files are a
great idea ... or even if they will work at all ... primarily because
indicators are defined in the DDS and thus imported included in the
generated structure.

If you use INDARA on your display file, that will alleviate some of the
discomfort. As David says, it's not an ideal use of ExtDS, but it can
be done.

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