Re: some questions on compile commands...

Violaine,

I beg to differ as to the first point you mention.

Here's our custom compile command, which does retrieve the events file and 
populate the error list:

OVRCMP SRCFILE(&F) SRCLIB(&L) SRCMBR(&N) OBJLIB(&L) MBRTYPE(&T) 
SUBMIT(*NO) LOCREM(*REMOTE) /* *EVENTF SRCMBR(&N) */

Apparently, having *EVENTF SRCMBR(&N) somewhere in your command string, 
even in a comment, is enough for RSE to pick up what it needs.

Provided of course that the actual compile commands inside your custom one 
have the OPTION(*EVENTF) parameter.

IIRC, I even got this tip from someone on this list.

Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we.  Futile is resistance, assimilated will you be.
-----



Violaine Batthish <batthish@xxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
14/12/2006 18:56
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] some questions on compile commands...






Hi Michael, Peter,

1) Its not a good idea to use user actions instead of compile commands, as
user actions will not retrieve the events file and populate the error 
list.
Also there are preferences for Command execution which only affect compile
commands.

2) I believe if you share connections (ie use team profiles), then the 
user
actions and compile commands are also shared.
If you don't want to use team connections, then you may just want to try
copying over the contents of  following folder to other team members'
workspaces (I haven't tried this, but I don't see why it wouldn't work)
workspace\RemoteSystemsConnections\profileName\CompileCommands
It appears that the compile commands are stored in an XML file, so copying
it over will cause any previously compile command settings to be lost.

I have opened a requirement for easier import/export of user actions.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab