Versions Compared

Old Version 1

changes.mady.by.user Fabiola Arias Navia

Saved on

compared with

New Version 2

changes.mady.by.user Fabiola Arias Navia

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

[ Image Removed |../../index.htm#lansa/l4winsb2_0360.htm]
You are here:

...


Pros

  • IBM i centric development. It's the model of choice for development shops with a major focus on IBM i.
  • Existing IBM i change management systems may be used.
  • Can develop without a connection to the Master System.
  • It's the model you've been using.
  • The LANSA development team has used this model extensively for developing LANSA in LANSA. (Not sharing the database with Repository Synchronization.)
  • All developers can be kept up to date using Repository Synchronization.
  • Using Individual PC databases and Repository Synchronization together provides for some control over receiving other developer's changes as they are only received when connecting to Host Monitor.

...

Note: The redundancy afforded by having the Master System reduces the importance of backing up individual PC databases. If a PC database is lost, then only the changes up to the last check in will be lost. If developer's check in frequently then little is exposed.
[ Image Removed |../../index. htm#lansa/l4winsb2_0360.htm]