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



I have installed WDSC and brought up to current levels 5.1.2.2 and I still 
continue to have problems with errors being returned to WDSC when a program is 
compiled. 
I can verify and get error message back if I run a compile I get nothing back. 
I have to goto the AS/400 to check to determine if there were errors. 
I can see the following in the job log:

Message . . . . : Physical file EVFEVENT created in library QTEMP.
Cause . . . . . : A physical file was created for the to-file because the 
file did not exist and CRTFILE(*YES) was specified. 

Message . . . . : 4 records copied from member CU1202F2. 
Cause . . . . . : 4 records were copied from member or label CU1202F2 in 
file EVFEVENT in library MP1CAMPIA. The records were copied to member or 
label EVFEVENT in file EVFEVENT in library QTEMP. 0 records were not copied 
Message . . . . : Object copied. 
Cause . . . . . : Object /QSYS.LIB/QTEMP.LIB/EVFEVENT.FILE/EVFEVENT.MBR 
copied to object /home/MP1CAMPIA/.eclipse/RB/Q000000051.evf.
The following if from the Iseries job log on the WDSC.
SBMJOB CMD(CALL QDEVTOOLS/QRBRUNCL PARM(Q000000051)) JOBD(*USRPRF)
Command has completed
This indicates to me that they are seeing the event file and copying it to the 
IFS but WDSC is not picking it up. I am compiling in batch but previously I 
have used interactive compiles and the same thing. 
Anybody got any ideas what is causing this?



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.