Bill Westland wrote:
Last time I had this problem was on an OS/390 2.4 system. I found a CA product (CA-1 or CA-7) that had corrupted the initiators. I was able to FORCE the initiators and JES was able to restart the initiators (new ASID of course) and we ran throughout the week without any further problems. I think that we were making a large update to the TMC for a migration or demigration that initiated the problem. The TMC update ricocheted into the CA-7 hooks that clobbered the initiators and fortunately we were only limited to three inits that took hits. We needed to get the inits restarted to avoid making changed to our automation for the batch window changes
Miklos Szigetvari <[EMAIL PROTECTED]> wrote: Hi
If someone has seen something like this:
Two of our inactive initiators don't want to accept job's, they are just
hung.
- z/OS 1.5
- Non WLM managed initiators,
- no MAS ,
- no SYSPLEX ,
- init stop/start seems to not help
- we have applied two day's before some JES2 SYSPLEX MAS PTF's
- the other initiators are working properly
Hi
Thank you,
I'm searching for some kind of FORCE, but till now I was unable to find
--
Mit freundlichen Grüßen / Best regards
Miklos Szigetvari
ISIS Information Systems GmbH
Alter Wienerweg 12
2344 Maria Enzersdorf
Austria
---------------------------------------------------------------
This e-mail is only intended for the recipient and not legally
binding. Unauthorised use, publication, reproduction or
disclosure of the content of this e-mail is not permitted.
This email has been checked for known viruses, but ISIS accepts
no responsibility for malicious or inappropriate content.
---------------------------------------------------------------
----------------------------------------------------------------------
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
