Re: RDi /COPY Edit/Browse not working

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

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.