|
Hey Adam, This is a bug in the Command Log View. I have opened APAR SE26138. As for events files, these are used for compiling actions (I don't believe that user actions will download events files). You should be able to find the format of events files in the WDSC help, and there is a FAQ on the WDSC web page about having WDSC automatically download events files for user defined compile commands. thanks, Violaine Batthish WebSphere Development Studio Client, IBM Toronto Lab wdsci-l-bounces@xxxxxxxxxxxx wrote on 07/19/2006 12:30:51 PM:
Hi all, I've done some poking around in the archives and the IBM infocenter, but while learning some interesting things about figuring out which RZRCSRVS jobs are associated with your current WDSc session and log levels, I've had no luck with my initial problem. We currently don't use any sort of versioning software in our development
process. In order to avoid problems with developers making different changes to the same code, we have a roll-your-own 'checkout' type command
that checks developer libraries for a given source file before copying to
one's own development library to be worked on and tested. I modified
this
program a bit to make it suitable to be called from a User Action, and it
has worked pretty well, but the messages such as 'Source in use by Adam' don't appear in the iSeries Commands Log. All I get is the command completion message. The messages are sent using SNDPGMMSG, and end up in the RZRCSRVS job
log.
Can anyone offer some guidance about how to make these messages show up in the Commands Log? Alternatively, can User Actions use an EVENTF to communicate with WDSc? Adam
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.