Re: Providing Work Arounds for PDM/SEU

["Lennon_s_j@xxxxxxxxxxx" <lennon_s_j@xxxxxxxxxxx>]

You can define user commands in WDSc in much the same way you can in 
PDM.  Right click on a file or member, click User Actions, then Work 
With User Actions.  You can add new actions and use many/most of the 
substitution variables that you can in PDM.  Start with something 
simple, like copy a member from one file to another, for example from 
production source to a test library.

However, I'm not sure that if you call a program that invokes an 
interactive green screen program that it will work.  (You can associate 
a green screen session with a WDSc session, but I have not tried that so 
I don't know exactly what it does.  Maybe someone else can comment.)

And I don't believe anyone has managed to invoke WDSc to open a member 
from a green screen app, like we used to do when invoking Code/400 from PDM.

Sam

On 4/6/2011 5:10 PM, Douglas Belcher wrote:
> Booth,
>
> Oh, he has a list things like how to replace his User Defined options which
> he has linked to programs he wrote.  Also how to integrate WDSc/RDp into a
> utility he wrote that will locate any/all source on our development box.
> Currently it links to SEU display (option 5), SEU edit (option 2), it can
> retrieve a source from any of our production machines, etc.  Then how do
> you...
>
> I guress what I'm looking for is any standard list that someone has come up
> with that shows this is what I do in PDM/SEU and this is how to do it in
> WDSc/RDp.