Best Practices for Host Integrator Modeling

Pre-Modeling Activities

 Review the host application and take advantage of host system experts to determine:  Determine the Number of Models Needed
You cannot access more than one host application with one model. If the application you want to develop needs to access data from more than one host application, you must create two models and develop an application that can share variables, which will allow you to integrate host data from two or more Host Integrator models.


Modeling Practices

As a common practice, you should avoid using both schemes together in one model because entity navigation paths and cursor positions can become out of synch.

 If the host supports command driven navigation, use it. This can greatly reduce navigation.

 Do not model a blank entity.

Modeling blank entities can cause undesired side effects. Some command-driven hosts use blank entities to accept commands. In these cases, you can write your commands to a blank entity as part of a command sequence without actually having it exist as an entity.

 Use tables to manipulate host application data

 Set naming conventions

 Determine global settings

 Create concise operations

Break large operations into a sequence of smaller operations, using alternate and intermediate destinations. Modeling is very like programming. Do not be in a hurry. Be careful and meticulous. It is often advantageous to work on a pair of screens at a time, the second screen being the destination of the first, and get each pair working error-free before moving to the next set. Sometimes you may have to capture a lot of screens quickly; if this is the case, import them one by one into what will become your carefully crafted model.

 Minimize patterns used to identify an entity

 Parameters and Constants

 Timing for 5250 Models

By defining these patterns for the input fields, the screen recognition process waits until these fields are ready for input. This ensures proper screen recognition and enhances model performance.


Optimizing the Model for Deployment

After you have completed your model, take these steps to prepare the model for optimum performance before deploying it to Host Integrator Server.

 Delete unnecessary entities

  Delete unnecessary or unused attributes

To improve performance and reduce memory consumption, make sure that the attributes of each entity contain necessary data or input fields.

  Delete all unnecessary operations

Validate the paths between entities to ensure they are traversable by the shortest route.

 Reduce the screen signature

Review the screen signature of every entity in the model and reduce it to the minimum number of patterns required to uniquely identify the entity.

 Optimize Traversal Operations

Before deploying the model, make sure the traversal operations are as efficient as possible. Open the model in off-line mode and follow these steps to review the operations for each entity:


Troubleshooting Models

 Validate the model using Validator

 Use Web Builder to Create a Web Client

Use Web Builder to quickly and easily generate a Web application of the host application model. Use this application to test your model functionality.


 Test possible error conditions for each operation
You can test possible error conditions for each operation by inputting bad data or by reproducing mainframe error conditions.


 Test the model parameters  Recognizing Screens as Entities  Synchronizing with the Host

Working with Character Mode Host Applications

Related Topics
Bullet Creating a host application model
Bullet Troubleshooting