NJE is RACF & Jess2 sensitive. Look into the other side syslog. The sysout might not be found on their spool because Jes deleted it. Ask your business partner to search the log and also to see if they changed Jes2 Node definition, for example, RECEIVE=SYSOUT.
Itschak -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mark Zelden Sent: Thursday, January 11, 2007 4:38 PM To: [email protected] Subject: Re: NJE output not reaching destination On Thu, 11 Jan 2007 15:56:12 +0200, גדי &#1489;ן אבי <[EMAIL PROTECTED]> wrote: >Yes, There are HASP530 messages. > and.... Do they tell you the output went to the destination you expected? If so then it sounds like you need help from someone on the other end if you don't have access to that system. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - GITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
