RE: Different definitions for the same record format

I would create the physical unkeyed, with the first byte as the code, and
one long field for data, and have select/omit logicals that do a substring
over the field in the physical. I've done this before, but our system is
down due to Katrina and I can't post it, but here is an idea:

A     S     CODE        COMP(EQ 'A')
A     O                 ALL

Do the same for 'C' in a different logical. In each logical, you define the
fields using the SST keyword.

http://publib.boulder.ibm.com/iseries/v5r1/ic2924/index.htm?info/rzakb/rzakb
mst38.htm
http://publib.boulder.ibm.com/iseries/v5r1/ic2924/index.htm?info/rzakb/rzakb
mst71.htm

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Charles St-Laurent
Sent: Thursday, September 8, 2005 10:59 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Different definitions for the same record format

Hi!

I want to convert a S/36 file to a file with a DDS. The problem is: for the
same record format, there is 3 different way to define the fields, depending
on the record identification code. Is there any way to create a physical
file that wil contain the 3 different ways to define the fields for the same
record format? If the record ientification is, for example, A, I want the
record format to be defined like this:

1         1 Code
2       31 Name
32    362MNT

but if the record identification code is C, I want the record format to be
defined like that:

1         1 Code
2       100JulDat
11     180RegDat

Any example of a DDS file allowing to do that?

Charles St-Laurent



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