Hi Ravi,
Yes, you're right SAR is capturing CLASS=Q, somehow the JESMSGLG and
msglog not being archived to SAR.
From another source, I found that OUTDISP parameter in JOBCLASS
statement in JES2 parm has a part in it too. It caused the system data
sets for jobs in that class to be HOLD which prevented them to be
processed by SAR.
I changed that to OUTDISP=(WRITE,WRITE), and do a cold start of JES2,
and it works now.
Thanks for your leads and help.
Regards Lim ML
On 08/10/11 6:51 PM, Ravi Gaur wrote:
Hi Lim,
I believe at your environment Outclass Q has been defined for the SAR to
accumulate the output and keep in database and when you running a job with
msgclass=q it get written in sar however SAR stc might not have authority to
purge the job and that's where it stay in hold class...could you check the
following.
1. SAR Task is up and accumulating jobs from SDSF.
2. Any message printed in syslog if nothing is seen please on $t debug=y and
rerun the job and see if SAR capture it with any ICH408I Message in syslog.
Please let me know how it goes..thanks,Ravi
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
