|
You must have compile in batch set. We don't use that here - in fact, we run green screen compiles interactively, too. When you have a lot of developers running tests of batch programs, trying to run compiles in batch is an exercise in frustration. Compiles run so fast on modern hardware it isn't worth submitting them, anyway. Plus, the RDi connection job is already batch, so there's no advantage we can identify in submitting compiles. Dave Shaw Sent from my Windows phone -----Original Message----- From: "Greg Wilburn" <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> Sent: 5/7/2015 3:57 PM To: "'Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries'" <wdsci-l@xxxxxxxxxxxx> Subject: Re: [WDSCI-L] Next release Not in this case... it is empty. -----Original Message----- From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave Shaw Sent: Thursday, May 07, 2015 3:54 PM To: Rational Developer for IBM i / Websphere Development Studio Clientfor System i & iSeries Subject: Re: [WDSCI-L] Next release The Commands Log view shows the joblog. That's its purpose. Dave Shaw Sent from my Windows phone -----Original Message----- From: "Greg Wilburn" <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> Sent: 5/7/2015 3:39 PM To: "'Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries'" <wdsci-l@xxxxxxxxxxxx> Subject: Re: [WDSCI-L] Next release Neither one of those RFE's address my simple issue. I had the binding directories listed in lower case. Oops, it won't compile - But in RDi, I have no idea why. I do not want a joblog every time I compile a program. If a program fails during the binding step, the joblog should be 1. Created 2. Displayed in RDi IBM is (and has been) pushing the use of RDi and modular programming (service programs and the like). Very ironic that they are "not compatible" and this was somehow overlooked. I've been using RDi for well over a year now... many times I find myself going back to the green screen (several times today) because of silly issues with RDi. One of those issues is errors during the binding step. The other is the quirky implementation of copying/pasting a blocks of text (overlaying) like you can do with SEU. Don't get me wrong... there are many advantages. But some days it feels like there are just as many disadvantages. Sorry for the rant. -----Original Message----- From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Edmund Reinhardt Sent: Thursday, May 07, 2015 1:35 PM To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries Subject: Re: [WDSCI-L] Next release We don't have a specific RFE on that. The problem is that the CRTPGM command doesn't have a *EVENTF option so it doesn't emit errors in a compatible way with the the other compile commands. This would take some doing to work around. But there are some relevant ones. https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=25183 https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=50961 From: Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> To: "'Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries'" <wdsci-l@xxxxxxxxxxxx> Date: 05/07/2015 11:30 AM Subject: Re: [WDSCI-L] Next release Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> Add this to the list: When a compile fails during the binding step, how about giving us a way to see that in RDi? There is no job log, no errors (other than a generic "failed to compile"). To see anything useful, you need to compile on the green screen. I did report this, and basically got nothing but excuses as to why it behaved like that. Greg -----Original Message----- From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Murphy/STAR BASE Consulting Inc. Sent: Thursday, May 07, 2015 9:11 AM To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries Subject: [WDSCI-L] Next release To the developers of RDi, For the next release of RDi, it would be nice if you would work on some of the picky little things that kinda work but not really. Here is a partial list: Source Compare feature - Doesn't always compare nicely, particularly if one source member has a bunch of spaces at the end of lines, and the other does not. Not real sure how that happens, just that it does. And why does the i Projects perspective source compare tool have the ability apply changes from one source to the other, but not the RSE tool? Seems a little silly to me for that feature to be missing from RSE since it is so useful. Screen/Report designer - I hate to call any DDS keywords new features as there really hasn't been anything added for quite some time, but it would be nice if the Screen/Report designer would support "newer" keywords. Quite a few things work better than they did with CODE, but not. Pushbuttons render as a 2 digit field rather than the pushbutton. Better than CODE that didn't render anything, but still not much help. AFP and IPDS keywords like Barcode and line do not render nicely, and even Font does not render properly (RDi is a GUI, and should be able to render these things). Position would be harder, but just about anything would be nicer than everything being placed at 1,1. And what is with the problems with a horizontal subfile not rendering properly when it is contained in a window. the subfile flows past the edge of the window, out to the edge of the screen. Mark Murphy STAR BASE Consulting, Inc. mmurphy@xxxxxxxxxxxxxxx -- This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. -- This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
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.