Wow. I was packing my bags for a new place of employment when I finally read the text. Oh well. I can't tell you what's wrong, but comparing JESPARMS can be misleading. There are a slew of parameters these days that can be changed by command but are ignored if read on a warm start, even all-sys. I suggest issuing some JES2 displays in the area of output management to see if JES2 is really configured the way you think it is.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Jimmy Pace <[email protected]> To: [email protected], Date: 02/27/2014 10:19 AM Subject: JES2 Job Listings Sent by: IBM Mainframe Discussion List <[email protected]> z/OS 1.13 A job is run on this LPAR and uses a MSGCLASS other than one set in JESPARMS that is (HOLD,HOLD), the sysprint and the JESJCL, JESYSMSG, and JESMSGLG are separated. If the msgclass is (WRITE,WRITE) then the sysprint goes to the output queue and the JES* goes to the held queue with a HOLD ODISP. With a MSGCLASS (HOLD,HOLD) : everything goes to held queue. Job is a IDCAMS listcat with one step and one sysprint. There are 4 LPARs (all are z/OS 1,13), 2 of them have this problem and 2 do not. When this same job is run on an LPAR that is not having this problem using a MSGCLASS with (WRITE,WRITE), all the output goes to the OUTPUT queue. The JESPARMS have been compared between the LPARs and MSTJCL to see if there were differences, nothing obvious. The only JES2 exit running is EXIT0 which I think, comes as a default. The only SMF exits customized are IEFU29 and IEFACTRT. The LPAR with the problem doesn't have any product like $avrs active, also, it doesn't appear any messages are being suppressed from the syslog. Thanks in advance for any insight. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
