When a member is logged out for the first time, a History member is created. This member contains an abstract of the member, language, description, and the name of the system where it belongs. Each time a login function is performed for that member, this history member is updated to reflect the changes, the number of the change request requesting the changes, and the programmer responsible. Therefore, another required LIB/CCF file is the history master file.
There must be a history master file for each production master file. Several production master files can share one history master file, as long as duplicate member names do not exist.
In this model system, the login function compiles the source after the member is moved to production. Therefore, a production object/relocatable library is required for each production master file. Several production master files can share the same object library, as long as there are no duplicate member names.
|
Copyright © 2010 CA.
All rights reserved.
|
|