We've had a couple of instances recently of message IEF302A: jobname WTR WAITING TO START aaaaaaaa FOR JOBID nnnnnnnn
We sort of interpreted it as an ENQ conflict, except that there are no actual data sets involved. It seems to revolve around a job calling for a particular WTR, very unusual around here for an application job. The job gets hung and prevents other jobs from running that also specify a WTR name. The stickler is that the specified WTR is not available on that system. One of our housekeeping jobs (system log offload) waited for 12 hours before Ops noticed. I've been in this biz for decades and never saw this problem. The message allows several different replies. I'm inclined to reply-in effect-cancel automatically because I see no way to salvage the job. Any other ideas? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office <===== NEW [email protected]<mailto:[email protected]> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
