Re: Running in-house commands

Hi Justin,

Try adding the comment   /* output(*print) */ to your command string.
I believe that will circumvent the checking.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab



wdsci-l-bounces@xxxxxxxxxxxx wrote on 01/10/2007 12:30:39 PM:

Hi Justin,

The RSE currently performs a check for commands starting with GO, STR*,
EDT* and WRK* and if you try to run one of these commands it displays the

dialog you are seeing (the [sometimes incorrect] assumption is that these

commands are always interactive.  We are looking at making this check

more

intelligent.

In the meantime, if you qualify the command with the library name
(QSYS/WRKACTJOB) then it will by-pass the check and run directly in the
RSE communications server job.

Don Yantzi
Technical Lead
WebSphere Development Studio Client for iSeries
IBM Toronto Lab





"Justin Taylor" <JUSTIN@xxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
01/10/2007 10:33 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
<wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] Running in-house commands






The commands run CL programs that have no interactive components.  I can
call the CL programs from WDSc.

I changed one of the commands to not allow *INTERACT but WDSc still
would not run it.