× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The *LDA is always duplicated to a batch job from a which issues a SBMJOB 
command.   Have you modified or set up your command to include the SRCMBR 
and OPTION(*EVENTF) parameters?  These are required for the RSE server job 
to monitor a compile job for completion.  It's been some time since we did 
much of this, but I believe I believe the process also monitors for the 
'xxx created successfully' messages.  I know our System Administrator 
modified our compile command to make sure it sent these back to the 
issuing job.  Sorry, but I don't have any of my notes handy on the process 
we went through.

wdsci-l-bounces@xxxxxxxxxxxx wrote on 11/13/2006 01:00:04 PM:

date: Mon, 13 Nov 2006 12:20:32 -0500
from: phil.groschwitz@xxxxxxxxx
subject: Re: [WDSCI-L] Trouble with IT Jungle tip for adding *EVENTF
   to   CRTPGM/CRTSRVPGM


Read further and follow the links provided. "How is the events file

produced in this case? You would write one yourself."

I've not go so far as to try to produce an events file, but we have
gotten
successful/failed compile messages back in the 'iSeries Commands Log'

view.

I've done that, and the member is being created and written to.  But, 
it's
not showing up in WDSC.  It says to set the *LDA so that WDSC will know 
the
location of the EVENTF file, which I'm doing, but I'm not sure if its 
the
corect *LDA since the command gets submitted to batch.
Phil



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.