|
|
|
One of the major benefits of ENF r12 is the switch from an older relational database technology to CA Datacom/AD for optional event recording and possible future event playback. Previous versions of ENF used a database technology based on CA-Universe to record ENF event activity. CA Datacom/AD provides many benefits over CA-Universe technology.
CA-Universe operated as an internal subtask to the ENF main task, and all CA-Universe database activity was performed "under the covers" completely within the ENF address space.
CA-Datacom/AD, through its Multi-User Facility (MUF), is generally run as a batch job or started task in its own address space. User communication with a MUF is provided through the CA Datacom/DB Application Programming Interface (API). The ENF r12 address space uses this API to manage its event recording database and under typical ENF operation, this requires the target MUF (the one ENF will be communicating with) to have been manually started and active in a separate address space before ENF is started.
Requiring ENF users to start up another address space to service the ENF database may be viewed as an imposition since additional started task JCL must be maintained and security settings planned for.
To address these concerns, ENF r12 is designed with an optional feature that approximates the same "under the covers" database operation as previously implemented with CA-Universe.
This feature is called Imbedded MUF (IMUF) and it removes the necessity of starting up a separate MUF address space to support ENF's database management requirements.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |