gtps4m0b | System Generation |
The requirements of your TPF system determine which features to include. In some cases certain functions are mandatory, while others are optionally selected by the user. Unique inputs or variables must be provided for the mandatory support (such as hardware addresses). However, the optional software support required for the system being installed is even more important (for example, unit record support). A significant consideration is the interdependencies of the software. If, for example, 3270/SDLC support is required, systems network architecture (SNA) support is mandatory. Once interdependencies are sorted out, the various options in a given area may be chosen.
One approach to this problem is to review this publication, decide on the options needed, and then go through the publication again to determine how to actually generate the system. Another approach, which can be combined with the first, is to break down the system into its major components: database support, communications support, and applications support. A problem with this approach is that there are many interrelationships between these areas (for instance, to determine the DASD requirements, the file resident record requirements of the communications protocol being used must be known.)
The mandatory portion of the basic system includes the fixed and pool record support. While fixed and pool file records must be stored on DASD, users select the DASD model. Some fixed and pool records are required by the system and some are required by the optional software packages. In addition, users must define the application database, including room for expansion in order to determine what other record types are required and how many of each type are necessary. A significant consideration, which is almost completely dependent on application requirements, is the type and total number of pool records that are required.
Those portions of the optional software support required by the system must be chosen before system generation. Some examples are unit record support and many of the application support packages. In addition, the users are faced with deciding on options in the given software packages. More significant are the requirements for whether or not the generated system will operate under the control of VM. VM support presents a number of options that are explained separately.