Re: Indicator set on call to qcmdexec

[John McKee <jmmckee@xxxxxxxxxxxxxx>]

That was what I thought happened.  The called program does set LR on.  Why
the thing works in production is another riddle.  Point of the futility is
there is a program that is run to set up a batch job.  We never override
the the settings presented by that program, so boss wants that to be run
from scheduler and no display or operator needed.

Thanks for clarifying the indicator on the QCMDEXC.  I don't recall which
indicator column is involved.

John McKee


On Wed, Sep 11, 2013 at 4:03 PM, Needles,Stephen J <
SNEEDLES@xxxxxxxxxxxxxxxx> wrote:

> It depends on which column the result indicator is in.
>
> If the indicator in column 76 is on, then the called program is at LR.  If
> column 74, then the call program failed for some reason.
>
> If I remember this right...it will only tell you if the API call was
> successful, not whether or not the command being executed was successful.
>  So I don't think a failing ALCOBJ command run by the QCMDEXC API will
> result in the indicator being set to an error condition.  This is because
> the API did not fail...the command it was passed failed.  Two different
> events.  The API can successfully manage the error and return to the caller
> with a positive, "I did my task"  indicator even though the ALCOBJ command
> itself failed.
>
> Steve Needles
>
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
> On Behalf Of John McKee
> Sent: Wednesday, September 11, 2013 3:40 PM
> To: RPG programming on the IBM i / System i
> Subject: Indicator set on call to qcmdexec
>
> This code appears to work.  Except when I try to use it.  Too long a story.
>
> This is an RPG III program.
>
> CALL 'QCMDEXC'                   60
> PARM                         CL,1
> PARM                         XXCLEN
>
> The first parm is an ALCOBJ command.  As far as I know, this code works
> great, and has for many years.  This is vendor code.
>
> Simple question (I think):  Is 60 getting turned on if the ALCOBJ command
> fails?  Command attempts to set an *EXCL lock.
>
> John McKee
> --
> This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
> mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
> http://archive.midrange.com/rpg400-l.
>
> ________________________________
> This communication, including attachments, is confidential, may be subject
> to legal privileges, and is intended for the sole use of the addressee. Any
> use, duplication, disclosure or dissemination of this communication, other
> than by the addressee, is prohibited. If you have received this
> communication in error, please notify the sender immediately and delete or
> destroy this communication and all copies.
>
> TRVDiscDefault::1201
> --
> This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
> mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.