Hey Dennis,
I use the CHGLIBL command which doesnt require inteactive screens. It also can be setup as a user action for your for different scenerios so just running a user actions sets you up for compiling but I found interactive compiling works best when changing library lists. Dont worry about system resources you should be verifying first anyway so one shot compiles are expected. I also have this multiple environment situation at my company and user actions plus Arcade's plugin keeps me happy and off iSeries Access.
Thanks
Don N.
PS: The WDSCi Debugger (service entry point) closes the deal for me hands down never going back.
----------------------------------------
From: DennisRootes@xxxxxxxxxxx
Sent: Thursday, October 11, 2007 3:47 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Fed up with green screen plodders
from: "Joe Pluta"
What are you looking for, Dennis? An emulator view in WDSC?
Compiling and so on can be done via WDSC, but I agree that testing green
screen requires an emulator. But do you want an embedded emulator just
for
running the program? Why is that any better than using iSeries Access?
Joe
----------------------------------------------------------------------
Well, I guess it's the lack of true interactivity that bothers me. I do
edtlibl a lot while working, (we have 4 production environments), and I
hate that I have to start an interactive session and attach it to my WDSc.
I.E.
A request to run an interactive command or program was received for the
RSE connection 10.1.1.2, but no interactive job is currently associated
with this connection. To associate an interactive job with this
connection:
1. Open a 5250 emulator,
2. Run the CL command STRRSESVR NAME(10.1.1.2)
3. This will associate the interactive job with this
connection, causing this dailog to close and your interactive command or
program to run.
My thought is if I have to do all that anyway, why bother? I can just
stay on the green screen. Of course, I love the WDSc code view so I do
use it for coding and doing research, but I can see why a lot of green
screen only programmers don't bother. I feel that it won't be universally
accepted until you can boot up WDSc and do EVERYTHING from the IDE. I
shouldn't have to attach an emulator to my pc session - it should take
care of it for me.
Maybe I'll work some more with the compiling, but like I said, I do an
edtlibl everytime before I compile to make sure I'm on the right session
and the right environment so it's just easier to do it and the compile at
the same time. Plus, there's no possibility of the WDSc hanging on me.
One can readily compile using RSE via Ctrl-C or the button or menu at
the top. 'Bites' seems a bit strong for alt-tab to an emulator session.
--buck
Ok, maybe "bites" was a little much. =) Change that to inconvenient.
Dennis,
Use the WDSc plugin emulator from Arcad. You can download it (for free)
from
here: http://www.arcadsoftware.com/content/view/201/316/
No more biting.
Trevor
------------------------------
Lol, Thanks! I just downloaded it. I'll let you know next week what I
think of it.
And one last thought from the original posters topic. Why is it that
management always gives us such cruddy computers? Would you ask a concert
pianist to join the symphony and then give him a ratty 40-yr old piano to
play on? Would you hand a plumber a box wrench? IT people should have
the best and fastest computers - it's the only tool we use. I think it's
sad when my kid's computer at home has more memory and power than most of
the pc's we are asked to work with. And I went cheap on it, the hardest
thing it does is play WoW. =)
Sorry for the rant, that particular topic always gets my goat....
midrange.com
