I had a friend just call and ask me to post this question. He works for a vendor (unnamed) and one of the things that they do in one of their functions is "clip" DASD volsers by dynamically invoking (LINK?) the IBM ICKDSF program. When they installed some z/OS 2.2 maintenance, all of sudden, this results in a 100% CPU loop. If they back out the maintenance, it works. Neither he nor I have any access to IBMLink. So he (and to an extend, I too) am curious if anyone here has had a 100% CPU loop with a LINK'd to invocation of ICKDSF. This is all that I know. I don't know the CPU type or the DASD type.
Yes, I know the above is really far too little information for any sort of diagnosis. This request is more along the lines of "has anybody else experienced this? If so, did you get some sort of fix for it?" If it were me having the problem (& I had the source), I'd look for some sort of mistake in my invocation of ICKDSF which is causing it to misbehave. -- Heisenberg may have been here. Unicode: http://xkcd.com/1726/ Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
