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

Joep - not sure about my thoughts on *EXEC having to be interactive - except that all the other items were interactive, so for that command (WRKAUT), *EXEC would only work in interactive - I think I'm only slightly crazy here!! If the other items said batch environments, then my statement would not hold.

Vern
-------------- Original message --------------
From: J.Beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx

Vern,

I would be perfectly happy if WDSC looked at the ALLOW property of the
command, but it doesn't.

As for the *EXEC element: why would that have to be in an interactive job?
*EXEC is also needed when you want to run the command from another system,
e.g. RMTCMD from a PC.

Joep Beckeringh


wdsci-l-bounces@xxxxxxxxxxxx wrote on 08-04-2008 16:00:48:

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

--
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.