RE: QCAPCMD and DSPINPUT(*NO)

["Gary Monnier" <gary.monnier@xxxxxxxxxxxxx>]

Brad,

>From the API documentation.

2 Prompt the command if selective prompting characters are present in
the command string. A CPF0008 exception is sent if this value is
specified with types of command processing values 4 through 8. 

If you are supplying a "command line" try using option 2 with a leading
?.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brad Stone
Sent: Wednesday, May 11, 2005 3:55 PM
To: Midrange Systems Technical Discussion
Subject: Re: QCAPCMD and DSPINPUT(*NO)


No.  I used the prompt parameter option on it.  I would
think that should work.

I was able to get around it by using QCMDEXC instead and
using the ?.  But still, I think that's working incorectly
with QCAPCMD.

Brad

On Wed, 11 May 2005 15:00:44 -0700
 "Gary Monnier" <gary.monnier@xxxxxxxxxxxxx> wrote:
> Brad,
> 
> Have you tried using ? with QCAPCMD?
> 
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Brad Stone
> Sent: Wednesday, May 11, 2005 12:08 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: QCAPCMD and DSPINPUT(*NO)
> 
> 
> Interestingly enough, if I change it to use QCMDEXC and
> insert a ? to the front of the command to force a prompt
> it
> works as expected and hides the hidden field.
> 
> Any thoughts on why QCAPCMD doesn't hide the PW (using
> option 1 to force a prompt)?
> 
> Brad
> 
> On Wed, 11 May 2005 13:45:42 -0500
>  "Brad Stone" <brad@xxxxxxxxxxxx> wrote:
> > Trying to figure out what's going on here.
> > 
> > I'm using QCAPCMD to let a user prompt on a command
> from
> > within an RPG app.
> > 
> > There is a field that is defined as DSPINPUT(*NO) and
> > using
> > this from the command line the parameter is hidden as
> > expected.
> > 
> > But, being called from QCAPCMD the parameter is not
> > hidden.
> > 
> > 
> > I'm not talking about the jog log (found a thread on
> > that),
> > but on the actual command prompt itself.
> > 
> > What's up with that?  Any way to make it work the way
> "it
> > should" and be hidden?
> > 
> > Brad
> > -- 
> > This is the Midrange Systems Technical Discussion
> > (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit:
> > http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the
> > archives
> > at http://archive.midrange.com/midrange-l.
> > 
> 
> Bradley V. Stone
> BVS.Tools
> www.bvstools.com
> -- 
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
> http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/midrange-l.
> 
> 
> -- 
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
> http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/midrange-l.
> 

Bradley V. Stone
BVS.Tools
www.bvstools.com
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.