|
Violaine, So far I've tried the button on the toolbar, right-clicking from the RSE tree or iSeries Table View, Ctrl+Shift+C, and with and without prompting from the Compile option on the menu bar. They all produce the same results. The iSeries Commands Log shows the following: 'SBMJOB CMD(.....' then on the line immediately following, it adds: 'Command has completed' If I submit a compile on my PC, I receive the 'SBMJOB ....' then mine has the message (or a similar one): 'Job 827151/xxxxxxx/JDAH submitted to job queue DEVELOP1 in library QGPL.' Thanks, Michael Quigley AS/400 Programming Section The Way International www.TheWay.org wdsci-l-bounces@xxxxxxxxxxxx wrote on 12/11/2006 10:08:09 PM:
date: Mon, 11 Dec 2006 14:19:57 -0500 from: Violaine Batthish <batthish@xxxxxxxxxx> subject: Re: [WDSCI-L] 'Compile in batch' does nothing Hey Michael, 1. How are you compiling (from RSE, Ctrl+Shift+C in RS LPEX, toolbar
button
etc) 2. Do you see any messages in the Command Log view? thanks, Violaine Batthish WebSphere Development Studio Client, IBM Toronto Lab wdsci-l-bounces@xxxxxxxxxxxx wrote on 12/08/2006 09:20:10 AM:I have checked the archives, but haven't found anything specific help. I just installed WDSC for another developer and applied all the
updates.
Everyone else here has 'Compile in batch' checked in the preferences
and
things work just fine. However if I check it on his setup, nothing happens: the job doesn't show up in the 'iSeries Job Status' view (the option is checked to add batch compiles to it), no job appears on the AS/400, no error messages appear anywhere that I can find. I could uncheck the option, but some of the compiles take a while and it ties
up
the workbench--the progress bar keeps going until retrieves the event file. Anyone have any suggestions on what else to check? If not, I'll put a call into IBM.
As an Amazon Associate we earn from qualifying purchases.
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.