Re: RDi /COPY Edit/Browse not working

Yes, that is what we're talking about, but the commands log view command line only works for commands that are set for batch execution on the i. It complains about DSPxxx commands that don't already have the OUTPUT parameter set to a batch-compatible value, at least in WDSCi 7.0. It's somewhat of a nuisance that way.
Dave Shaw
Mohawk Industries


________________________________
From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Sent: Thursday, July 4, 2013 1:34 PM
Subject: Re: [WDSCI-L] RDi /COPY Edit/Browse not working

I believe the commands log view has always had a batch option - and
commands can always be prompted there, so the output parameter can be
set to whatever.

Am I talking about the same as you guys are?

:)

On 7/4/2013 11:50 AM, Dave Shaw wrote:

I don't know if it makes a difference that I'm still using WDSCi, but using DSPxxx with OUTPUT(*PRINT) works for me, as long as I don't prompt OR enter the OUTPUT(*PRINT) before I prompt. The prompter gets finicky otherwise.

Dave Shaw
Mohawk Industries


________________________________
From: Brian Parkins <goodprophet.bp@xxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio Clientfor System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Sent: Thursday, July 4, 2013 8:54 AM
Subject: Re: [WDSCI-L] RDi /COPY Edit/Browse not working

<snip>

Side Note: It would be handy to issue DSPxxx commands with OUTPUT(*PRINT) or
OUTPUT(*FILE) from the COMMANDS LOG View. (We could then view the spooled
output or file contents without leaving RDP/RDi.) Unfortunately executing
DSPxxx commands is only possible if RDP/RDi has a "slave" 5250 session
through STRRSESVR.