RE: QRPGLESRC Record Length

How important is it that the source member create & change date & times
remain as they were before moving them to a new source file?  All of that
will change to the current date and time when you copy members to a new
file.

Way, way back on the burner is a personal project to produce an MI program
to restore source member create & change date & times after a copy.
Hopefully by the end of the year.

BTW, save & restore won't work in this case because of the different record
lengths.  Tried it.

- Dan Bale
(I am *NOT* "Dale"
http://archive.midrange.com/midrange-l/200105/msg00281.html )
SAMSA, Inc.
989-790-0507
DBale@SAMSA.com <mailto:DBale@SAMSA.com>
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-----Original Message-----
From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
Behalf Of Bob Cozzi
Sent: Tuesday, June 11, 2002 12:44 PM
To: rpg400-l@midrange.com
Subject: RE: QRPGLESRC Record Length


Wouldn't CPYSRCF work just as well as all that mbropt(*...) stuff with
the old CPYF?

Bob COzzi

> -----Original Message-----
> From: rpg400-l-admin@midrange.com
> [mailto:rpg400-l-admin@midrange.com] On Behalf Of
> MWalter@hanoverwire.com
> Sent: Tuesday, June 11, 2002 11:00 AM
> To: rpg400-l@midrange.com
> Subject: Re: QRPGLESRC Record Length
>
>
>
> rename qrpglesrc to qrpgleold
> recreate qrpglesrc to 112
> cpyf fromfile(qrpgleold) tofile(qrpglesrc) frommbr(*all)
> tombr(*frommbr)
> mbropt(*replace) fmtopt(*map *drop)
>
> I think this should work.
>
>
> Thanks,
>
> Mark
>
>