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" <[email protected]> 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:[email protected]] On > Behalf Of Dno > Sent: Wednesday, May 21, 2014 11:14 AM > To: [email protected] > 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" <[email protected]> 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:[email protected]] On >> Behalf Of Staller, Allan >> Sent: Wednesday, May 21, 2014 9:11 AM >> To: [email protected] >> 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. >> </snip> >> >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> >> 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 [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > 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 [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
