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

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