Good News Everybody!
The new search engine is LIVE!
Please report any problems to david (at) midrange.com.
|
We put our custom compile commands under "User actions" instead of "Compile". Maybe that can be a work-around. HTH, Peter Colpaert Application Developer PLI - IT - Kontich, Belgium ----- Yoda of Borg are we. Futile is resistance, assimilated will you be. ----- "Michael Rosinger" <mrosinger@xxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 14/12/2006 12:10 Please respond to Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx> To wdsci-l@xxxxxxxxxxxx cc Subject [WDSCI-L] some questions on compile commands... List, 1) I have set up custom compile commands based on our shop's needs/standards. I added them to the list of available commands using "Work with compile commands". Is there a way to make these commands available to other users without having to manually add the commands at each workstation where WDSC is used? (not a big deal if not - just wanted to save some work) 2) Is there a way to disable or hide the compile commands that are supplied with WDSC? (it won't let me delete them) I want to force our programmers to use the custom command and not one of the others. I know that I can change the security on the other commands on the iSeries which will not allow them to execute it, but in the GUI world, if a user is not allowed to do or see certain things, those things shouldn't appear available to them. Any ideas?
This mailing list archive is Copyright 1997-2026 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.