Re: S/36 Flat file question

I would suggest -
1. create DDS file with proper fields, same name, with a proper format
name, in a temporary library for the file, matching current f & i specs
2. cpyf *nochk to move data to newly create dds file
3. to expand columns, change source of new file, and use CHGPF on new file
to end up with a DDS file with expanded columns
4. either change the RPGII to RPGIV (you can still have F&I specs or now E
(external definition) or update I and o specs in RPGII to match your new
file.
5. move/delete the old version and install new version of file and programs
I've had to do this several times, so that now this system has only native
DDS files, but still has some old RPGII that they won't spend hours writing
new code.
Hoping Project Bob provides a reasonable conversion option.

Jim Franz

On Fri, Mar 6, 2026 at 2:45 PM Rob Berendt <robertowenberendt@xxxxxxxxx>
wrote:

On the S/36 we could use IDDU. There is a menu displayed on IBM i when you
type in STRIDD which does the same thing. Then you can use it with WRKQRY,
etc.

Wait, now I understand. You want the reverse.
Can you use a create index in sql to concat the desired individual columns
into one string and get the same file, rcdfmt and column name as the
previous flat file had?


On Fri, Mar 6, 2026 at 1:39 PM DEnglander--- via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I have a S/36-era flat file that I am working on. It has one "field" in
it, and the file name, record format, and the one field are all the same
name. The file is created with a CRTPF statement with no DDS and using

the

RCDLEN parameter.

I want to know if it is possible to somehow create a "compatibility"

style

LF over this, and update the flat file to a DB2 table or a DDS PF if
needed. Fields need to be enlarged and added.

I can't get an LF to compile using the file name, field, and format all
the same name. Has anyone done this: Create an LF to mimic a flat file
over a DB2/DDS file? I have done it successfully before over an existing
DB2/DDS file, but never a flat file.

Thank you,

Doug



"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the

attachments

accompanying it) contain confidential information belonging to the

sender.

The information is intended only for the use of the intended recipient.

If

you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution or the taking of any action in reliance
on the contents of the information is strictly prohibited. Any
unauthorized interception of this transmission is illegal under the law.
If you have received this transmission in error, please promptly notify

the

sender by reply e-mail, and then destroy all copies of the transmission."
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.