10-Sep-2004 20:31:41.348325 GMT,10948482980479,1,Test Ready stor01
10-Sep-2004 20:31:42.379952 GMT,10948482980479,1,Wildcard registration 
10-Sep-2004 20:31:42.562846 GMT,10948482980479,1,Test Ready stor01
10-Sep-2004 21:42:42.585339 GMT,10948525590362,1,Test Ready stor01
10-Sep-2004 21:42:42.816157 GMT,10948525590362,1,Wildcard registration 
10-Sep-2004 21:42:42.889101 GMT,10948525590362,1,Test Ready stor01
10-Sep-2004 21:43:28 GMT,10948525590362,3,Test Start stor01,10-Sep-2004 21:43:28 GMT
10-Sep-2004 21:43:28.45828 GMT,10948525590362,2,Test Question stor01 stor01.001
10-Sep-2004 21:43:28.57303 GMT,10948525590362,2,Test Question stor01 stor01.002
10-Sep-2004 21:43:28.69743 GMT,10948525590362,2,Test Question stor01 stor01.003
10-Sep-2004 21:43:28.82121 GMT,10948525590362,2,Test Question stor01 stor01.004
10-Sep-2004 21:43:28.94468 GMT,10948525590362,2,Test Question stor01 stor01.005
10-Sep-2004 21:43:28.106728 GMT,10948525590362,2,Test Question stor01 stor01.006
10-Sep-2004 21:43:28.119163 GMT,10948525590362,2,Test Question stor01 stor01.007
10-Sep-2004 21:43:28.130458 GMT,10948525590362,2,Test Question stor01 stor01.008
10-Sep-2004 21:43:28.141829 GMT,10948525590362,2,Test Question stor01 stor01.009
10-Sep-2004 22:11:55 GMT,10948525590362,3,Test Complete stor01,10-Sep-2004 22:11:55 GMT
10-Sep-2004 22:11:55.572404 GMT,10948525590362,9,Q:9:::::A:?0=0?1=0?2=0?3=0?4=0?5=0?6=0?7=0?8=0::undefined.0:1:1:0::::R:?0?1?xxx?3?4?5?6?xxx?8
10-Sep-2004 22:11:55.574582 GMT,10948525590362,9,Q:9:::::C:We are a little unique in our approach to remotely mirroring for DR purposes in that we remotely mirror all of our mainframe production data to a box that maintains 3 copies of the data.  At DR time, two copies are deinstalled from the remote box (approximately 7 miles from our main data center) and transported to our DR site several hundred miles away where it is then installed into a DASD frame that we own but rent floor space and environmentals for at our DR vendor site.  While this would not allow for virtually non-disruptive operations in the event of a disaster, business needs do not require that kind of turn-around.  (If, in the future, those business needs change, the data could be remotely mirrored directly to the DR site.)  This arrangement allows for continuous remote mirroring of our production data, even while we perform our DR testing on a regular schedule.
10-Sep-2004 22:11:55.583030 GMT,10948525590362,9,Q:9:::::A:?0=0?1=0?2=0?3=0?4=0?5=0?6=0?7=0?8=0::undefined.0:1:1:0::::R:?0?1?xxx?3?4?5?6?xxx?8
10-Sep-2004 22:11:55.585754 GMT,10948525590362,9,Q:9:::::C:We are a little unique in our approach to remotely mirroring for DR purposes in that we remotely mirror all of our mainframe production data to a box that maintains 3 copies of the data.  At DR time, two copies are deinstalled from the remote box (approximately 7 miles from our main data center) and transported to our DR site several hundred miles away where it is then installed into a DASD frame that we own but rent floor space and environmentals for at our DR vendor site.  While this would not allow for virtually non-disruptive operations in the event of a disaster, business needs do not require that kind of turn-around.  (If, in the future, those business needs change, the data could be remotely mirrored directly to the DR site.)  This arrangement allows for continuous remote mirroring of our production data, even while we perform our DR testing on a regular schedule.
10-Sep-2004 22:11:55.594369 GMT,10948525590362,9,Q:9:::::A:?0=0?1=0?2=0?3=0?4=0?5=0?6=0?7=0?8=0::undefined.0:1:1:0::::R:?0?1?xxx?3?4?5?6?xxx?8
10-Sep-2004 22:11:55.596615 GMT,10948525590362,9,Q:9:::::C:We are a little unique in our approach to remotely mirroring for DR purposes in that we remotely mirror all of our mainframe production data to a box that maintains 3 copies of the data.  At DR time, two copies are deinstalled from the remote box (approximately 7 miles from our main data center) and transported to our DR site several hundred miles away where it is then installed into a DASD frame that we own but rent floor space and environmentals for at our DR vendor site.  While this would not allow for virtually non-disruptive operations in the event of a disaster, business needs do not require that kind of turn-around.  (If, in the future, those business needs change, the data could be remotely mirrored directly to the DR site.)  This arrangement allows for continuous remote mirroring of our production data, even while we perform our DR testing on a regular schedule.
10-Sep-2004 22:11:55.605143 GMT,10948525590362,9,Q:9:::::A:?0=0?1=0?2=0?3=0?4=0?5=0?6=0?7=0?8=0::undefined.0:1:1:0::::R:?0?1?xxx?3?4?5?6?xxx?8
10-Sep-2004 22:11:55.607441 GMT,10948525590362,9,Q:9:::::C:We are a little unique in our approach to remotely mirroring for DR purposes in that we remotely mirror all of our mainframe production data to a box that maintains 3 copies of the data.  At DR time, two copies are deinstalled from the remote box (approximately 7 miles from our main data center) and transported to our DR site several hundred miles away where it is then installed into a DASD frame that we own but rent floor space and environmentals for at our DR vendor site.  While this would not allow for virtually non-disruptive operations in the event of a disaster, business needs do not require that kind of turn-around.  (If, in the future, those business needs change, the data could be remotely mirrored directly to the DR site.)  This arrangement allows for continuous remote mirroring of our production data, even while we perform our DR testing on a regular schedule.
10-Sep-2004 22:11:55.614964 GMT,10948525590362,9,Q:9:::::A:?0=0?1=0?2=0?3=0?4=0?5=0?6=0?7=0?8=0::undefined.0:1:1:0::::R:?0?1?xxx?3?4?5?6?xxx?8
10-Sep-2004 22:11:55.617141 GMT,10948525590362,9,Q:9:::::C:We are a little unique in our approach to remotely mirroring for DR purposes in that we remotely mirror all of our mainframe production data to a box that maintains 3 copies of the data.  At DR time, two copies are deinstalled from the remote box (approximately 7 miles from our main data center) and transported to our DR site several hundred miles away where it is then installed into a DASD frame that we own but rent floor space and environmentals for at our DR vendor site.  While this would not allow for virtually non-disruptive operations in the event of a disaster, business needs do not require that kind of turn-around.  (If, in the future, those business needs change, the data could be remotely mirrored directly to the DR site.)  This arrangement allows for continuous remote mirroring of our production data, even while we perform our DR testing on a regular schedule.
10-Sep-2004 22:11:55.624519 GMT,10948525590362,9,Q:4:::::A:?0=0?1=0?2=0?3=0?4=0?5=0::undefined.0:1:1:0::::R:?xxx?1?2?xxx?4?xxx
10-Sep-2004 22:11:55.631832 GMT,10948525590362,9,Q:6:::::A:?0=0?1=0?2=0?3=0?4=0::undefined.0:1:1:0::::R:?0?xxx?2?3?xxx
10-Sep-2004 22:11:55.639157 GMT,10948525590362,9,Q:4:::::A:?0=0?1=0?2=0?3=0?4=0?5=0::undefined.0:1:1:0::::R:?xxx?1?2?xxx?4?xxx
10-Sep-2004 22:11:55.646760 GMT,10948525590362,9,Q:6:::::A:?0=0?1=0?2=0?3=0?4=0::undefined.0:1:1:0::::R:?0?xxx?2?3?xxx
10-Sep-2004 22:11:55.654200 GMT,10948525590362,9,Q:1:::::A:::undefined.0:1:1:0::::R:Really ILM can be thought of as Hierarchical Storage Management, i.e., the correlated %27aging%27 of data and the corresponding depreciation of its value over time.  Corresponding with this aging, the data is moved to less and less expensive (albeit slower) media for its residence until its value becomes zero at which time it should be deleted from the system.
10-Sep-2004 22:11:55.655893 GMT,10948525590362,9,Q:1:::::C:Marty Penhorwood<BR>Lead Systems Programmer<BR>American General Financial Services<BR>email: mpenhorwood@agfinance.com
10-Sep-2004 22:11:55.662859 GMT,10948525590362,9,Q:4:::::A:?0=0?1=0?2=0?3=0?4=0?5=0::undefined.0:1:1:0::::R:?xxx?1?2?xxx?4?xxx
10-Sep-2004 22:11:55.670280 GMT,10948525590362,9,Q:6:::::A:?0=0?1=0?2=0?3=0?4=0::undefined.0:1:1:0::::R:?0?xxx?2?3?xxx
10-Sep-2004 22:11:55.678098 GMT,10948525590362,9,Q:9:::::A:?0=0?1=0?2=0?3=0?4=0?5=0?6=0?7=0?8=0::undefined.0:1:1:0::::R:?0?1?xxx?3?4?5?6?xxx?8
10-Sep-2004 22:11:55.680238 GMT,10948525590362,9,Q:9:::::C:We are a little unique in our approach to remotely mirroring for DR purposes in that we remotely mirror all of our mainframe production data to a box that maintains 3 copies of the data.  At DR time, two copies are deinstalled from the remote box (approximately 7 miles from our main data center) and transported to our DR site several hundred miles away where it is then installed into a DASD frame that we own but rent floor space and environmentals for at our DR vendor site.  While this would not allow for virtually non-disruptive operations in the event of a disaster, business needs do not require that kind of turn-around.  (If, in the future, those business needs change, the data could be remotely mirrored directly to the DR site.)  This arrangement allows for continuous remote mirroring of our production data, even while we perform our DR testing on a regular schedule.
10-Sep-2004 22:11:55.687603 GMT,10948525590362,9,Q:1:::::A:::undefined.0:1:1:0::::R:Really ILM can be thought of as Hierarchical Storage Management, i.e., the correlated %27aging%27 of data and the corresponding depreciation of its value over time.  Corresponding with this aging, the data is moved to less and less expensive (albeit slower) media for its residence until its value becomes zero at which time it should be deleted from the system.
10-Sep-2004 22:11:55.689084 GMT,10948525590362,9,Q:1:::::C:Marty Penhorwood<BR>Lead Systems Programmer<BR>American General Financial Services<BR>email: mpenhorwood@agfinance.com
10-Sep-2004 22:11:55.696510 GMT,10948525590362,9,Q:2:::::A:?0=0?1=0?2=0?3=0?4=0?5=0::undefined.0:1:1:0::::R:?xxx?xxx?2?xxx?xxx?xxx
10-Sep-2004 22:11:55.703687 GMT,10948525590362,9,Q:5:::::A:?0=0?1=0?2=0?3=0::undefined.0:1:1:0::::R:?xxx?xxx?xxx?3
10-Sep-2004 22:11:55.712073 GMT,10948525590362,9,Q:7:::::A:::undefined.0:1:1:0::::R:Sarbanes-Oxley is currently the biggest regulatory %27hurdle%27 we have, with not fully understanding all its implications for us regarding what it applies to and what it may not apply to.  Better to err on the side of %27safe than sorry%27.
10-Sep-2004 22:11:55.720142 GMT,10948525590362,9,Q:8:::::A:::undefined.0:1:1:0::::R:Approximately 8 Terabytes.  All of it is mirrored locally and we remotely mirror approximately 2.3 Terabytes.
10-Sep-2004 22:11:55.727808 GMT,10948525590362,9,Q:3:::::A:?0=0?1=0?2=0?3=0?4=0?5=0::undefined.0:1:1:0::::R:?0?xxx?2?3?4?xxx
10-Sep-2004 22:11:55.735653 GMT,10948525590362,9,Q:3:::::A:?0=0?1=0?2=0?3=0?4=0?5=0::undefined.0:1:1:0::::R:?0?xxx?2?3?4?xxx
10-Sep-2004 22:11:55.743709 GMT,10948525590362,9,Q:3:::::A:?0=0?1=0?2=0?3=0?4=0?5=0::undefined.0:1:1:0::::R:?0?xxx?2?3?4?xxx
10-Sep-2004 22:11:55.751730 GMT,10948525590362,9,Q:3:::::A:?0=0?1=0?2=0?3=0?4=0?5=0::undefined.0:1:1:0::::R:?0?xxx?2?3?4?xxx
10-Sep-2004 22:11:55.759739 GMT,10948525590362,9,Q:9:::::A:?0=0?1=0?2=0?3=0?4=0?5=0?6=0?7=0?8=0::undefined.0:1:1:0::::R:?0?1?xxx?3?4?5?6?xxx?8
10-Sep-2004 22:11:55.762010 GMT,10948525590362,9,Q:9:::::C:We are a little unique in our approach to remotely mirroring for DR purposes in that we remotely mirror all of our mainframe production data to a box that maintains 3 copies of the data.  At DR time, two copies are deinstalled from the remote box (approximately 7 miles from our main data center) and transported to our DR site several hundred miles away where it is then installed into a DASD frame that we own but rent floor space and environmentals for at our DR vendor site.  While this would not allow for virtually non-disruptive operations in the event of a disaster, business needs do not require that kind of turn-around.  (If, in the future, those business needs change, the data could be remotely mirrored directly to the DR site.)  This arrangement allows for continuous remote mirroring of our production data, even while we perform our DR testing on a regular schedule.
10-Sep-2004 22:11:55.769377 GMT,10948525590362,9,Q:9:::::A:?0=0?1=0?2=0?3=0?4=0?5=0?6=0?7=0?8=0::undefined.0:1:1:0::::R:?0?1?xxx?3?4?5?6?xxx?8
10-Sep-2004 22:11:55.771752 GMT,10948525590362,9,Q:9:::::C:We are a little unique in our approach to remotely mirroring for DR purposes in that we remotely mirror all of our mainframe production data to a box that maintains 3 copies of the data.  At DR time, two copies are deinstalled from the remote box (approximately 7 miles from our main data center) and transported to our DR site several hundred miles away where it is then installed into a DASD frame that we own but rent floor space and environmentals for at our DR vendor site.  While this would not allow for virtually non-disruptive operations in the event of a disaster, business needs do not require that kind of turn-around.  (If, in the future, those business needs change, the data could be remotely mirrored directly to the DR site.)  This arrangement allows for continuous remote mirroring of our production data, even while we perform our DR testing on a regular schedule.