I agree with you completely. Quite frankly it scares me that I can't
find anything as having changed to cause this problem - especially when
I got multiple good suggestions as to what I could check and everything
seems to be set up properly. That was why I came to the list - to see
if anybody anywhere could give me a suggestion as to what could be
causing this behavior, not to tell me the obvious that I opened up a big
hole in my system.
Rex
> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of Pommier, Rex R.
>
> For everybody else on the list, I apologize in advance for my
> ranting back but I am looking for help, not ranting about
> everything I apparently did wrong.
Be all that as it may, it remains that you reported a significant change
in behavior of a computing system about which you state that, to the
best of your knowledge so far, "nothing was changed".
However, ALL of us **RELY ON** consistent behavior from unchanged
computing systems; indeed, most if not all of us would bet our salaries
that it is impossible for a computing system to change its behavior
without some behavioral parameter having been changed.
Thus, the inescapable conclusion is that SOMETHING, SOMEWHERE on or
affecting your system got changed, and you just haven't found it yet.
If you can truly refute that conclusion, then we are ALL in VERY SERIOUS
TROUBLE!
-jc-
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
