TURNOVER® for LanTurn v100 the TURNOVER® for iSeries v100 - LANSA
™ Interface, lets you manage LANSA changes within the framework of the TURNOVER® for iSeries v100 Change Management system. LANSA definitions are checked out from a production partition into a development partition, changed and promoted the same way other System i source and objects are managed by TURNOVER® for iSeries v100. TURNOVER® for LanTurn v100 provides a more productive LANSA development environment with features like LANSA cross-reference, RDML compare and distribution. Manage the Web with ease as TURNOVER® for LanTurn v100 supports both LANSA for the Web and Visual LANSA.
TURNOVER® for iSeries v100 allows you to analyze and change LANSA applications and your 3GL applications on the same Worklist. Functions such as source compare are fully supported with TURNOVER® for LanTurn v100. With just one software change management system to learn, your staff will be productive quickly. Whether your development and production are on the same computer or you distribute changes, your LANSA objects will be installed reliably, every time.
Developers will appreciate the fact that they will not need to import or export LANSA objects between production, test and development partitions; this is done behind the scenes by TURNOVER® for LanTurn v100 commands. Furthermore, it handles modification of all data library names within the data model during checkout - eliminating the problems that occur when definitions are copied between partitions.
Setup
LANSA "object types" - field, file, function, process, application template, system variable, multi-lingual variable, Visual component, and Web component - are all known to TURNOVER® for iSeries v100. These are activated automatically for you during installation of TURNOVER® for LanTurn v100.
LANSA applications are identified by TURNOVER® for iSeries v100 application definitions the same way 3GL applications are defined. Any number of development steps (development-to-test, test-to-QA, and so on) are supported. Sample application definitions are provided so you can quickly create your own definitions by copying the sample.
If you distribute changes using TURNOVER® for iSeries v100 now, no additional setup is required to distribute LANSA objects. If you are new to TURNOVER® for iSeries v100, distribution to one or more production systems can be done efficiently and quickly.
USING THE TURNOVER® for LanTurn v100 INTERFACE
Analyze LANSA definitions more efficiently
You can analyze LANSA RDML easily using TURNOVER® for LanTurn v100's powerful definition compare facilities. Once you identify the definitions you need, add them to your Programmer Worklist. Browse the definitions on your Worklist without starting up another LANSA session, and without opening the definition for update. Want to compare RDML to see what changed last time? A powerful compare utility is built into TURNOVER® for LanTurn v100.
Checkout definitions
Checkout LANSA definitions and get to work. Checkout provides you with a record of which LANSA definition each developer is using and, optionally, can lock them so nobody else can change them while they are checked out to you. An audit trail is maintained of all checkout activity. An emergency change feature, used when you need to fix a production object currently being revised, is included.
Make LANSA code changes
Select any definition on your Worklist and modify your LANSA RDML, just as you would normally do. After testing in development, you are ready to promote for further testing, or back into production, as desired.
Build a promotion request
Once you are satisfied with your changes, select the LANSA definitions you want to promote and submit a TURNOVER® for iSeries v100 form. You can schedule your promotions to run any time. When a promotion runs, LANSA definitions are exported from your development partition into the target partition. System i objects are generated into your target libraries. TURNOVER® for LanTurn v100's cross-reference system protects you from the potential of level checks. If problems occur during the promotion, changes can be rolled back automatically. You can even roll back changes after they are installed, if necessary.
Distributing LANSA objects
You can schedule and distribute System i objects and, conditionally, LANSA definitions, to any number of production computers any time after the promotion is done. TURNOVER® for iSeries v100 will send back confirmation messages and update the project status on your development computer.
Security
Only people authorized to use TURNOVER® for iSeries v100 can work with LANSA applications. You authorize each developer only to those applications and TURNOVER® for LanTurn v100 functions they need.
Link to LANSA Task Tracking
When a TURNOVER® for iSeries v100 task is created, TURNOVER® for LanTurn v100 can be configured to automatically create a corresponding LANSA task and to update that task as work progresses. Once a developer's work is complete, TURNOVER® for LanTurn v100 is used to filter objects by LANSA task ID and to build a TURNOVER® for iSeries v100 Worklist, ensuring all related changes are captured for checkout and promotion through TURNOVER® for iSeries v100.
TURNOVER® for LanTurn v100 is licensed separately from TURNOVER® for iSeries v100.
Interface & Application Software Support
You can use TURNOVER® for iSeries v100's many APIs or built-in interfaces to bridge to any software package, including: