Installed on our test system is the CA7 Web client and Job Flow Monitor. Up until we have been recording CA7LOG events (generated by CA7) into an ENF DATACOM Database. When the recording (not the generation of events) of these evens was stopped we were STILL able to view CA7 job flows from the Web Client and everything in the Web Client worked the same as it did before the recording was stopped.
My questions are :
1. MUST we record the CA7LOG events into an ENF DATACOM database?
2 What functionality do we lose if we no longer record CA7LOG events to the ENF DATACOM database?
Release : 11.3
Component : CA-7
Regarding your questions:
1. MUST we record the CA7LOG events into an ENF DATACOM database?
Answer: NO
2 What functionality do we lose if we no longer record CA7LOG events to the ENF DATACOM database?
Answer: You will not be able to recover all required data to rebuild the critical paths.
Let me explain my answers further……
With your CA 7 Jobflow Monitor (JFM) are you using Critical Path Monitoring (CPM)?
With “NO” set for Critical Path Monitoring (CPM) and only ever do a start of TYPE=COLD, you can change the CA7LOG event to NOREC.
When JFM starts it will put out a message startup stating that events are not being recorded. If you did a TYPE=WARM start, it will not be able to track current active flows, this is because the recording of events enables a (WARM) start of JFM so that it recovers CA 7 log event information.
Warm attempts to recover any critical path data (with YES set for Critical Path Monitoring (CPM)). If TYPE=WARM is specified and critical paths are active, Jobflow Monitor reads the CAIENF records trying to recover all possible information about the critical path. The retention period of the CAIENF records and the age of the critical paths determine whether Jobflow Monitor can recover all the required data to rebuild the critical paths. Also if you use CAIENF to transport the CA7LOG event across other Lpars, you must ensure that CAIENF is capable of recording events.