Mystery solved. It is Jobtrac that is changing the output class. We use class J for the sysout capture class. This enables Jobtrac to keep an online history. We only specify MSGCLASS for class J. Jobtrac also has a requeue class (5 in our case), after the job is captured, it is requeued to class 5. The requirement for Jobtrac sysout capture is the class must be held (class J). When it's requeued to class 5, it's retaining the held status until the $oq is issued. Sysout written directly to class 5 goes to $avrs.
Thanks for the feedback.... Dean Sent from my iPhone > On May 21, 2014, at 5:35 PM, "Pommier, Rex" <rpomm...@sfgmembers.com> wrote: > > Hmm, this is odd. Are you using ACCMTBLs in $AVRS? How about JNREQRD? > > The $OJOQ,Q=5 is simply telling JES to release any held data in class 5. It > has nothing to do with stuff sitting in class J as you already know. > > One thing I found in the $AVRS manual that is rather confusing is in the > definition of the ACCMCLS parm where it says > > <quote> > The job to be accumulated must have its > "MSGCLASS" parameter in the JCL assigned to one of these classes. Any > associated SYSOUT datasets in the job to be accumulated must also have > their "SYSOUT" assigned to these classes. > </quote> > > When I read the above, I get the idea that for anything from batch to go to > $AVRS, the MSGCLASS on the JOBCARD needs to be a $AVRS class. This isn't > true. I just ran a job with MSGCLASS=X (a held class) and SYSOUT=Y (output > class serviced by $AVRS) on one of my DD cards. The output from the DD card > went immediately to $AVRS - and the "$AVRS JOB SELECTION" screen shows the > CCODE of PARTIAL to indicate the entire job didn't get saved ($AVED???). > > This may be a time to open a case with SEA. > > Rex > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Dno > Sent: Wednesday, May 21, 2014 3:48 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: $OJ > > Thanks Rex, > > $avrs is class 5 only, jes2 for class 5 is: > write,write output=print. Still researching this.... > > Dean > > Sent from my iPhone > >> On May 21, 2014, at 4:09 PM, "Pommier, Rex" <rpomm...@sfgmembers.com> wrote: >> >> Dean, >> >> Check your $AVRS startup parms. Specifically ACCMCLS. What is that parm? >> You can have up to 8 classes defined to $AVRS for having output sent to it. >> Also, what is your JES2PARM of OUTCLASS(5)? >> >> Rex >> >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of Dno >> Sent: Wednesday, May 21, 2014 11:14 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: $OJ >> >> It was a question because I can not find where the output class is being >> changed. >> >> Sent from my iPhone >> >>> On May 21, 2014, at 10:53 AM, "Pommier, Rex" <rpomm...@sfgmembers.com> >>> wrote: >>> >>> Allan, >>> >>> The OP gave a command of $OJOBQ,Q=5. Wouldn't this command be dealing only >>> with releasing held output that is already in class 5? It has nothing with >>> class J output. I'm not sure where the idea that this command is releasing >>> class J to class 5 comes from. >>> >>> Rex >>> >>> -----Original Message----- >>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >>> Behalf Of Staller, Allan >>> Sent: Wednesday, May 21, 2014 9:11 AM >>> To: IBM-MAIN@LISTSERV.UA.EDU >>> Subject: Re: $OJ >>> >>> Is it possible $AVRS is collecting both Class 5 *AND* Class J? >>> >>> Class 5 would be collected immediately and class J when $OJOBQ'ed. >>> Yes changing Class J to (WRITE,WRITE) would eliminate the need for $OJOBQ >>> >>> HTH, >>> >>> <snip> >>> We have our production batch jobs with MSGCLASS=J and SYSOUT=5 to direct >>> the class 5 to $AVRS. We issue a $OJOBQ,Q=5 which re-queues and releases >>> the class J to class 5. I've looked all over over system (exits, commands, >>> etc.) to see if and where the class J is being re-queued prior to the >>> release, but I'm not coming up with anything. So my question is: is the $O >>> command re-queuing the output? I don't see this documented in the JES2 >>> manuals and have googled the topic as well. >>> >>> My observations so far: >>> >>> This is part of the OUTCLASS definition from our JES2 parms: >>> OUTLASS(J),OUTDISP=(HOLD,HOLD) >>> >>> HOLD รจ Hold the output. JES2 does not process the output until you either >>> change the disposition to WRITE or KEEP, or release the output. When the >>> output is released ($OQ), the disposition changes to WRITE. >>> >>> Re-queuing the job will retain the output disposition from the originating >>> class. If output class J was changed to OUTDISP= (WRITE, WRITE), then >>> re-queuing to class 5 would send it immediately to $AVRS and we would not >>> need to issue the $OQ every 60 seconds. > > The information contained in this message is confidential, protected from > disclosure and may be legally privileged. If the reader of this message is > not the intended recipient or an employee or agent responsible for delivering > this message to the intended recipient, you are hereby notified that any > disclosure, distribution, copying, or any action taken or action omitted in > reliance on it, is strictly prohibited and may be unlawful. If you have > received this communication in error, please notify us immediately by > replying to this message and destroy the material in its entirety, whether in > electronic or hard copy format. Thank you. > > > ---------------------------------------------------------------------- > 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
