Re: WDSC doesn't know an interactive command when it sees one

Kevin

Even in PDM, if you try to run WRKAUT in a job you started with SBMJOB, you get an error.WRKAUT requires an interactive display - that is an interactive command.

If you execute the DSPCMD command on a command, there is a section called 'where allowed to run' - the WRKAUT has only interactive elements there - *INTERACT, *IPGM, *IREXX, *EXEC (I wonder about the last one - that allows being run with QCMDEXC - guess it'd better be in an interactive job!)

If you want to run an interactive-only command (it's "normal" mode, maybe - gotta look at WDSC help), you need an interactive session that WDSC can use - not too big a deal but unhandy. Now you CAN get a plugin for WDSC from ArCad that puts a 5250 session into a view in WDSC - and you could use that - fairly handy.

Server jobs are all batch - not interactive.

And I also love PDM - will never stop using it. But I use WDSC a lot - it's fantastic for working with lots of source members, as I do. It lets me see a lot more code. I can select an entire procedure or subroutine or If-ENDIF block in basically one mouse move and one key sequence (position at either end of the block and press Ctrl-M) and then print that block only. I did that just yesterday to locate a bug. You can indent RPG source and see it immediately in a view. Yes, it probably runs a compile *NOGEN - and you COULD do that and look at the spooled output. It is definitely handier in WDSC.

Not everything is as smooth - but so much of WDSC is good. Let me recommend the site

http://www.systemideveloper.com/wdscqanda.html

for an FAQ by Susan Gantner on WDSC. And on that page is a link to her favorite shortcuts.

And Aaron Bartell has like 45 favorite tips for WDSC - not sure if it's readily available - did not see it at his site www.mowyourlawn.com but I'm in a hurry right now.

Anyhow, there's a lot to like about WDSC - and don't give up the green screen - it's often my best way to do something.

HTH
Vern

At 02:04 AM 4/8/2008, you wrote:

I tried to avoid running command/program from WDSC. When I change the library list by Command - normal, it changes the library list of session of WDSC. If I change the library list by Command - interactive, it changes the library list of the session of the Remote Service. For me, I know the difference but it is easy to make mistake. I am beginner of WDSC. I don't know whether there is reason to have 3 types of command (batch, normal and interactive). I guess it is because of the connection of WDSC to AS/400 (I like the original name) is through socket of the server job. I don't know.... but I really don't like it. I just want to run command that is same as I run in the green screen. Command - batch??? If I need to submit a job, I will use sbmjob command. Sorry, I still like PDM, it's simple to use and fast. I'll force myself keep using WDSC, I hope 2 months after, I will say "after using WDSC, you won't look back.....". never know....

Kevin



----- Original Message ----
From: "J.Beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx" <J.Beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx>
To: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
Sent: Monday, April 7, 2008 7:43:54 AM
Subject: [WDSCI-L] WDSC doesn't know an interactive command when it sees one

Today I discovered something very silly about WDSC: In RSE I tried to
define an 'iSeries command', using a command called STRPFO. WDSC insisted
that this was an interactive command which I could only execute with the
help of STRRSESVR from a 5250 session. Strange, because I made sure the
command was able to run in batch. When I created a copy of the command and
called it #STRPFO, everything was fine.

So, apparently WDSC thinks a command is interactive when it starts with
STR. END is OK (how inconsequent!), DSP and WRK are also considered
interactive. GO, on the other hand, is accepted.

Sigh.

Joep Beckeringh
--
This is the Websphere Development Studio Client for 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 Websphere Development Studio Client for 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.