Explanation The external writer is waiting for the operator to validate writer name aaaaaaaa. The writer name was specified on a SYSOUT DD statement in JOBID j. Operator response
If the writer name is valid and is to be used by the external writer, then enter REPLY xx,‘U’ and the external writer will use the name. If the writer name is invalid and the external writer is not to use the name and is to bypass and delete this data set, enter REPLY xx,‘N’. If the external writer is to use another writer name, enter REPLY xx, ‘N,cccccccc’, where cccccccc is the other writer name. Finally, if aaaaaaaa is not valid and the operator wants the external writer to use the IBM-supplied default writer name, enter REPLY xx,‘D’ and the external writer will use the default writer name to write the data set. https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieam800/gg302a.htm So, it would seem the correct response is R xx,D to use the default writer. Joe On Thu, Dec 31, 2020 at 12:50 PM Jesse 1 Robinson <jesse1.robin...@sce.com> wrote: > 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 > robin...@sce.com<mailto:robin...@sce.com> > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
