Re: ALDON vs Turnover

Sudha,

Your client can turn this feature on/off in TurnOver.  Have them go into
their TurnOver application definition and access the "Version and Stamping
defaults".  Then have them change the value for "Stamp Project/task
reference" to "N".  Then the object control level will not change.

Of course this also assumes that they are not recompling your objects on
their system, in which case all of the values in the object description
would be reset and you would lose any information that had been added on
your system by Aldon.

Hope this helps.

Mark Phippard
Director of Development
SoftLanding Systems






                    Sudha Ramanujan
                    <SRamanujan@sungardfu        To:     
"'midrange-l@midrange.com'" <midrange-l@midrange.com>
                    tures.com>                   cc:
                    Sent by:                     Subject:     ALDON vs Turnover
                    midrange-l-admin@midr
                    ange.com


                    09/27/01 11:22 AM
                    Please respond to
                    midrange-l






This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Hi all,
We are using Aldon for our config management and so go by the 'object
control level' on dspobjd for version numbers.  But when we send out
program
to our clients, and they pull it in Turnover, it erases this.  Is there a
way to avoid this problem?  I believe turnover puts in a 'PTF number' on
object, instead and there is an api that can swap this information to
object
control field but I cannot find any of this info in IBM site.  Could anyone
kindly help?
Thanks,
Sudha

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