Tier Aware and Platform Aware Subroutines
Example 148 - Rating: advanced
Example 148 - Rating: advanced
| The Things that Make Up this Example | To Execute this Example |
This form (VL_SAM148) acts as a simple interface to the tier and platform aware subroutine VSAM145.
VSAM145 returns a list of iSeries objects and descriptions, so it can only do it's job if it is running on an iSeries server. It cannot actually do anything viable on non-iSeries platforms. The need to be specifically running on an iSeries server means that VSAM145 is both a tier and platform aware subroutine.
The easiest way to understand all of the preceding points is to cut/paste/compile the examples and then combine execution of them with reading of the comments contained within them.
Keywords
VSAM145 returns a list of iSeries objects and descriptions, so it can only do it's job if it is running on an iSeries server. It cannot actually do anything viable on non-iSeries platforms. The need to be specifically running on an iSeries server means that VSAM145 is both a tier and platform aware subroutine.
- Some programming techniques that can be used in tier managed subroutines.
- Use of the APPL (application) tier.
- How the use of a tier management scheme can change the performance characteristics of an application.
- Techniques for passing long lists between application tiers.
- Platform awareness. VSAM145 is required to return a list of iSeries object names and descriptions. If it is executed in a non-iSeries environment it can still behave sensibly by returning a null list and a message.
The easiest way to understand all of the preceding points is to cut/paste/compile the examples and then combine execution of them with reading of the comments contained within them.
Keywords
| Tier | Management |
| Multi-Tier | Remote Procedure |
| Database | Client |
| Server | n-Tier |
| Platform | Subroutine |
| Example 148 |