Re: AW: Re: What is JES2 waitning for after $TSPL(volser),SPACE=MAX?
In ez-1315458279.1520887...@gmx.ch, on 12/10/2014 at 08:00 AM, Peter Hunkeler p...@gmx.ch said: I didn't look at the I/O rate; just was mislead by the AWAITING(E2) thinking that there is something to be done before JES2 starts formatting. The message could be better. The message could be better, but in the meantime the explanation could be better, e.g., it could list member formatting as a possible cause for AWAITING(member). Have you sent an RCF? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
AW: Re: What is JES2 waitning for after $TSPL(volser),SPACE=MAX?
Thanks for all the help, everyone It turned out I was simply too impatient. As someone suggested, JES2 was still about to format the additional space. It just took so much longer that I had expected and the AWAITING(E2) is not very helpful. Anyway, no need for a PMR. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
AW: Re: What is JES2 waitning for after $TSPL(volser),SPACE=MAX?
That was me. I remember the AWAITING() from a similar action 1 year ago. Since E2 was the member you gave the commands, this member did the formatting and you should have been able to see that JES2 doing an abnormally large amount of I/O on the volume. The MAS was waiting for E2 to finish the formatting. I didn't look at the I/O rate; just was mislead by the AWAITING(E2) thinking that there is something to be done before JES2 starts formatting. The message could be better. I hope that while this formatting was going on that the systems were not hung up and that they were running normally using the original extents while the E2 system was formatting the new extent (but not yet using it). Once the format finished the extra space could then have been added to the available space on that volume and this information would then be passed to the other member(s). I didn't specificlly look for, but have not seen or heard of any problems while the space was being formatted. In summary, the expansion ran smooth. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AW: Re: What is JES2 waitning for after $TSPL(volser),SPACE=MAX?
Peter Hunkeler wrote: I didn't look at the I/O rate; just was mislead by the AWAITING(E2) thinking that there is something to be done before JES2 starts formatting. The message could be better. Indeed. Raise a PMR for progress message, something like this 'Expanding name of object - 10% completed.'. I hope that while this formatting was going on that the systems were not hung up and that they were running normally using the original extents while the E2 system was formatting the new extent (but not yet using it). Monitors like RMF or JES2MON (?) could tell you, but I prefer progress messages or messages about changing rate of progress. Something like this 'Expanding 20% complete. Now processing x bytes per second.' I didn't specificlly look for, but have not seen or heard of any problems while the space was being formatted. In summary, the expansion ran smooth. Good. Better. Excellent! ;-) Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
