WDSC stores source in the IFS as a text file with the line number and
change date as the first 12 characters of each line. When sending changes
up there must be a way for it to manage that. Probably deletes all the
records from the member and inserts the new records as they are stored in
the file. This is different from how CPYF works with source files. I
suspect that what we need to use is an RPG program, or find the one that
already exists for WDSC, and use that to get the source to the iSeries
without loosing line numbers and date stamps.
I know uploading source in the standard manner will not work.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
From: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 05/28/2010 11:44 AM
Subject: Re: Subversion and RPG source change managemen
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Just a thought here...
I agree with Mark W. regarding date stamps on each line, and the
usefulness of the source last changed info in the object.
I see a couple of possibilities:
The Change Object Description (QLICOBJD) API can be used to change the
source file name, library and date/time on a compiled object.
Also, remember that a SRC-PF is still a PF. If your SVN client
supports source PF, when the latest version of a source is pulled into
a developers working copy your SVN client could go ahead and call a
utilities that updates the source member date time with the
appropriate date.
HTH,
Charles
On Fri, May 28, 2010 at 9:53 AM, Mark S. Waterbury
<mark.s.waterbury@xxxxxxx> wrote:
I do not consider it a "big deal" or worry about the date stamps in each
source line. I am more concerned with the source file, library and
member name and source last changed date/time stamps reflected in the
OIR information of objects created from source, including: *PGMs,
*MODULEs, *SRVPGMs (for binder source), *FILEs, *CLDs, *CMDs, *PNLGRPs,
*QMFORMs, *QMQRYs, and *TBLs.
midrange.com
