In a message dated 7/6/2005 5:22:42 A.M. Central Daylight Time, [EMAIL PROTECTED] writes: > In the case of an ABEND or CICS "close immediate" situation, what information would you like Mark to write to the file? And where is this information supposed to come from?
I think you are assuming there is only one way to "fix" this problem. E.g., in the case of SMF data the solution is called interval accounting. Every X minutes SMF records are written to reflect the activity during the last X minutes. The VSAM statistics in question could be updated on intervals. You will miss all the activity that occurs during the last partial interval just before a system crash. Application programs or even access methods (e.g., at OPEN time) could be enhanced to add ABEND recovery routines that invoke a new service which would add the last partial interval's stats into the proper buckets. This assumes the stats are kept in storage that was not trashed as part of the error leading to the ABEND. If the operator FORCEs the job or the system crashes, there is no hope. But for most abnormal ends there are ways to "fix" the stats. The information comes from the same place where it comes from now in the case of normal CLOSE. The minimum we would need is a new service which the user would invoke to update stats. Bill Fairchild ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
