× 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.






Bruce, those are the only two parms you need. Are you trying the compiles
in batch? Have you tried in non-batch? Right click on iSeries Objects, then
select Properties, select the Command Execution page and uncheck compile in
batch. Then run the compile command.

Does that make a difference?

Kushal Munir
Websphere Development Studio Client for iSeries
IBM Toronto Lab, 8200 Warden Ave., Markham, ON
Phone: (905) 413-3118        Tie-Line: 969-3118
Email: kmunir@xxxxxxxxxx



                                                                           
             "Bruce Guetzkow"                                              
             <bruceg@unitedcre                                             
             ditservice.com>                                            To 
             Sent by:                  <wdsci-l@xxxxxxxxxxxx>              
             wdsci-l-bounces@m                                          cc 
             idrange.com                                                   
                                                                   Subject 
                                       Subject: Re: [WDSCI-L] WDSc for     
             05/14/2004 11:34          iSeries 5.1 and compile commands    
             AM                                                            
                                                                           
                                                                           
             Please respond to                                             
                 Websphere                                                 
                Development                                                
             Studio Client for                                             
                  iSeries                                                  
                                                                           
                                                                           




On May 13, Mark Phippard wrote:

>>Does the command string defined in WDSC contain OPTION(*EVENTF) and
>>SRCMBR(mbr_name)?  It isn't good enough for those to be parms on the
>>commands with the default value set, WDSC has to see those in the
"string"
>>itself.

I, too, have created my own command which is a front-end to a compile
command.  I have modified my command to contain parameters:
             SRCMBR(mbr_name)
             OPTION(*EVENTF)

When I added a user action (member) for my command and execute the
command through WDSC I still do not get the events file results to
appear in the iSeries Error List.  I have verified that file EVFEVENT in
the object library has a member with the name mbr_name.  Is there any
documentation that I can reference to see if there are any other steps
to this process that I am missing?

Thanks in advance,
Bruce Guetzkow
Information Services Director
United Credit Service, Inc.
Phone: 262-723-2902
Fax: 262-723-5568
Email: bruceg@xxxxxxxxxxxxxxxxxxxxxxx
Web: www.unitedcreditservice.com


_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.