5.8 System Partition Definitions
A system partition is a means of 'dividing up' or 'partitioning' one LANSA system. Each partition is completely separate from other partitions.
Points to note about partitions:
- There is very little 'inter-partition' communication. Files, fields and processes defined in one partition are not directly accessible from another partition.
- Each partition has a separate dictionary. Having too many partitions violates the concept of a corporate dictionary and increase maintenance.
- Each partition has a separate security system. If you have too many partitions or too many users accessing multiple partitions this can become a maintenance problem.
Generally partitions should only be used to:
- Separate large classes of users from one another (e.g.: production from development).
- Create 'standalone' application systems or software packages.
Generally partitions should NOT be used to:
- Divide up applications or software packages unless they are (and will remain) completely independent from one another.
- Satisfy a developer's urge to start new applications with a 'blank page'. The downstream effect of satisfying such an urge may be poor reuse of existing objects and unnecessary and avoidable maintenance and deployment issues.
The steps involved in creation, review, change or deletion of a system partition definition are:
1. Select the option to create | |
or change system partition | HOUSE- |
definitions on the house- | KEEPING |
keeping menu. | MENU |
2. Select the partition to be | |
changed or deleted, or use | SELECT |
the ADD function key to | PARTITION|
indicate that a new | REQUIRED |
partition is to be defined. |__________|
3. Review, change, delete the | |
existing partition or | REV,CHG |
specify details of the | DLT,CRT |
new partition definition. | PARTITION|
5.8.1 Partition Definition Maintenance
5.8.2 Partition Definitions - Create, Change or Delete
5.8.3 If you Enable a Partition for RDMLX
5.8.4 If you Comply with SAA/CUA Standards and Guidelines.