The Transform-Browse model reads the specifications for a browse module (module generated by a Browse, Browse-Subp, Browse-Select, or Browse-Select-Subp model) and generates object browse modules for use in a client/server environment. As the modules generated by Browse models contain a combination of UI, data, and business logic, they cannot be used in a client/server environment. The Object-Browse models, however, generate separate modules for these layers. The Transform-Browse model uses the following models to generate the object browse modules:
Object-Browse-Subp (generates the module containing data and business logic)
Note:
This model also generates the object PDA, key PDA, and restricted
PDA.
Object-Browse-Dialog (generates the module containing the user interface information)
Object-Browse-Dialog-Driver (generates a driver program for the dialog module)
Note:
The driver program maintains the same interface into the object
browse module as was used for the browse module. You do not need to modify
modules that used the original browse module.
To preserve the original browse module, the Transform-Browse model does the following:
Reads the data for the browse module.
Moves the browse module to the archived module library.
Generates the specifications for the object modules.
Generates all the object modules in the current library.
Moves the object browse modules to the transformed module library.
By default, the archived module library name is B + the first seven characters in the current library name and the transformed module library name is T + the first seven characters in the current library name. These standards are implemented in the WTRNAME module and validated in the CUTRVAL module and can be changed if desired.
Note:
If Natural Security is being used, you must
have access to both libraries (there is a validation check to ensure you have
access to both).
