Re: Running in-house commands -- WDSCI-L

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

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.

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.