|
Violaine, I did another search of the mailing list archive. This time I searched on 'Command has completed' and found a post by Eric Simpson. It was in a thread where someone else had a similar problem. Eric queried, "Do you have an IFS home directory and do you have write access to it?" The program who's having the problem had a home directory on their profile, but the directory didn't exist. I had our system admin set up the directory and his compiles now work. Thanks for pointing me in the write direction. FWIW- We use a custom compile command which deletes prior compile spoolfiles, tracks compile parameters, etc. Here it is: "SBMJOB CMD(COMPILE OBJECT(ARDEV/FRBSTMT1) DELETE(*YES) SRCF(ARDEV/STMTSRC) SRCMBR(FRBSTMT1) OPTION(*EVENTF) DBGVIEW(*SOURCE) REPLACE(*YES)) JOBD(*LIBL/JDAH)" Thanks once again for your help, Michael wdsci-l-bounces@xxxxxxxxxxxx wrote on 12/12/2006 01:00:05 PM:
date: Tue, 12 Dec 2006 12:41:36 -0500 from: Violaine Batthish <batthish@xxxxxxxxxx> subject: Re: [WDSCI-L] 'Compile in batch' does nothing Hey Michael, Hmmm, I vaguely recall seeing something like this before. 1. Do you have any preferences set for the SBMJOB additional parameters
in
the Command Execution preference page? 2. Would you mind posting the whole command that appears in the Command Log? thanks, Violaine Batthish WebSphere Development Studio Client, IBM Toronto Lab
. . . . . . . . .
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
. . . . . . . . .
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.