We are on 9.1 and have not experienced that either. Only time I every
experienced that was back when Screen Designer was a separate product(not
built in) for .DSPF files and it reset all the source dates. Never had any
issues with .cbl, sqlcbl, cblle, sqlcblle, clp, clle, pf, or lf members.
What type of member are you working with, maybe someone who has work with
that member type can weigh in?
From: Buck Calabro <kc2hiz@xxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Date: 01/07/2015 01:19 PM
Subject: Re: [WDSCI-L] Source line change dates
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
On 1/7/2015 11:52 AM, Dean Eshleman wrote:
Is there a preference somewhere that controls how RDI treats the change
dates in the source files? It appears to be changing all the dates when
you save the member. I thought there was a preference that would control
whether or not it would track the change dates at the line level. I looked
for it, but I couldn't find anything.
This has never happened to me that I can recall, but I have a very
simplistic environment. No Change Management, no Source Version
Control, no iProjects.
--
--buck
'I had nothing to offer anybody except my own confusion' - Jack Kerouac
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
Jeff Buening
Sr. Developer
P: 419.586.8599
| F: 419.586.8997
Celina Insurance Group
800.552.5181 | 1 Insurance Square, Celina, Ohio 45822
www.celinainsurance.com
................................................................................
...................................................
The information contained in this message (including any attachments) is
confidential and may be privileged.
Unauthorized disclosure, copying, or use of this information is prohibited and
may be unlawful.
If you are not the intended recipient, please delete this message and notify
the sender.
As an Amazon Associate we earn from qualifying purchases.