Eric Lehti
VIP Member
Disk (DASD) on mirror maxed out by Echo2 jobs temporary space usage
We use Vision Solutions iTera Echo2 to mirror our i5 to a high-availability i5. Began using it ten months ago (July 2006) when we went live on i5 model 520s.
On two occasions, April 04, and May 24, the disk filled up on the mirror machine. The mirror machine disk space is always in the 45%-49% range (this is a 210GB ASP machine). On April 04, disk space got up to 92%. Only recovery was to power down the i5 and IPL, thus freeing up the tempory space that the Echo2 jobs had allocated. Worst offending job was ZM_A1JRND. Its Temporary storage used=87,308,427,264 Bytes
IBM's tech support had us run these steps
STRSST command
1. Start a service tool
2. Display/Alter/Dump
2. Dump to printer
2. Licensed Internal Code (LIC) data
page down and select option 14.
On the blank input line at top, key this macro
1 processinfo -frames 0 and press <enter>
on next screen press Enter and create a spooled report.
Repeat the above process from (14) for this macro:
1 taskinfo <press enter> and on the next screen key:
-ALL -STG- -FRAMES 0 -NOWAITOBJ -NOLR -NOEX -SORT 7
<press enter> to create the second spooled report.
Used Ops navigator to drag the spooled report to the Windows desktop into a .txt file and sent it to IBM. They sent back a list of all the Echo2 jobs and their temporary storage usage.
After the April 04 incident we the latest PTFS from Echo2. We are surprised that the problem occurred again yesterday on May 24, disk space used got up to 82%. We performed the same power down and IPL yesterday.
If any of you have experienced this also, let's talk!.
ericl 918-292-9142
We use Vision Solutions iTera Echo2 to mirror our i5 to a high-availability i5. Began using it ten months ago (July 2006) when we went live on i5 model 520s.
On two occasions, April 04, and May 24, the disk filled up on the mirror machine. The mirror machine disk space is always in the 45%-49% range (this is a 210GB ASP machine). On April 04, disk space got up to 92%. Only recovery was to power down the i5 and IPL, thus freeing up the tempory space that the Echo2 jobs had allocated. Worst offending job was ZM_A1JRND. Its Temporary storage used=87,308,427,264 Bytes
IBM's tech support had us run these steps
STRSST command
1. Start a service tool
2. Display/Alter/Dump
2. Dump to printer
2. Licensed Internal Code (LIC) data
page down and select option 14.
On the blank input line at top, key this macro
1 processinfo -frames 0 and press <enter>
on next screen press Enter and create a spooled report.
Repeat the above process from (14) for this macro:
1 taskinfo <press enter> and on the next screen key:
-ALL -STG- -FRAMES 0 -NOWAITOBJ -NOLR -NOEX -SORT 7
<press enter> to create the second spooled report.
Used Ops navigator to drag the spooled report to the Windows desktop into a .txt file and sent it to IBM. They sent back a list of all the Echo2 jobs and their temporary storage usage.
After the April 04 incident we the latest PTFS from Echo2. We are surprised that the problem occurred again yesterday on May 24, disk space used got up to 82%. We performed the same power down and IPL yesterday.
If any of you have experienced this also, let's talk!.
ericl 918-292-9142
