T.R | Title | User | Personal Name | Date | Lines |
---|
1213.1 | Cache flush timer??? | SSDEVO::RMCLEAN | | Thu Feb 20 1997 09:36 | 1 |
| What is the value you have as the cache flush timer set to?
|
1213.2 | using default of 10 seconds | CSC32::L_SOBCZYNSKI | | Thu Feb 20 1997 10:06 | 9 |
|
Hello Ronald,
The default value, 10 seconds.
Regards
Leonard
|
1213.3 | !!!! HELP !!!! | CSC32::L_SOBCZYNSKI | | Tue Feb 25 1997 06:32 | 7 |
|
Hopefully this is not a dead note, I do need assist on this.
Thank you.
Leonard
|
1213.4 | Not a clue without being able to debug it... | SSDEVO::RMCLEAN | | Tue Feb 25 1997 09:06 | 2 |
| Haven't got a clue but... I would suggest you wait a couple of weeks and try
V3.1. I guarantee that the results will be different ;-.]
|
1213.5 | Release Notes available yet?? | KERNEL::LOANE | Comfortably numb!! | Tue Feb 25 1997 23:03 | 4 |
| >I would suggest you wait a couple of weeks and try V3.1.
...are the V3.1 release notes available yet so we can see what
major features'n'functions are available??
|
1213.6 | *Ok, then* | CSC32::L_SOBCZYNSKI | | Wed Feb 26 1997 06:00 | 14 |
|
Ronald,
Thank you for reply in .4.
As questioned in .5, if the released version of the release notes are
not available as yet, can an advance copy be had?
Cheers
Leonard
[EOB]
|
1213.7 | Not yet | SSDEVO::RMCLEAN | | Wed Feb 26 1997 09:34 | 2 |
| No release notes yet. It is not a released product yet. (read this it isn't
written yet ;-.])
|
1213.8 | *What info can be gathered to troubleshoot?* | CSC32::L_SOBCZYNSKI | | Thu Feb 27 1997 06:14 | 25 |
|
Hello Ronald,
Hopefully my attempts to further the inquiry on the situation that has
been encounterd at my customer's site is not being viewed as, its back
again?
As yet I have not mentioned the upgrading to version 3.1 as a possibility,
I'll wait until its released and I have a copy in hand.
In a discussion with the customer it was stated that when the situation
was experienced originally it was the HSJ that was powered cycled and a
decrease in job process time was observed. The latter experience involved
a number of other hardware entities shall we say not interacting together
properly that ultimately led to the HSJ being rebooted, so no factual
information could be gathered from that incident.
What information could be gathered from the HSJ should the situation be
observed again to aid in getting to the root cause of the increased
job cycle time?
Regards
Leonard
|