Did you missing a line of code? Shouldn't your code have a on-error
opcode somewhere?

From what I can tell, you are trying to monitor the call to QCMDEXC.
When error occurred on the call to QCMDEXC, you want to use QMHRCVPM to
get all those errors in the joblog that generated by the call to
QCMDEXC. AFAIK, QMHRCVPM will not give me all the things that you see
in the joblog. If you want to browse thru joblog, you need to use
QMHLJOBL api.

"Jose Santana" <jsantana@xxxxxxxxxxxxx> wrote in message
news:<mailman.3122.1218489923.2545.rpg400-l@xxxxxxxxxxxx>...
I have an Rpg program that makes a call to a command from an CMS
application to
checkout some objects under certain circumstances. My RPG program
monitors for
any errors on the call to the checkout command in the event that an
object cannot be
checked out for some reason beyond its control. However, when I try
to
capture the
error I'm only getting the "program CHECKOUT ended Abnormally" message

that's
issued by the called command but it is not capturing the preceding
CPF2469 escape message.
This escape message then causes the main program MYPGM to crash.
Here's
a snippet
of my code:

c monitor
c call 'QCMDEXC'
c parm CmdStr
c parm CmdLen
c endif
c dow 1=1
c callp ReceiveMsg(Msg0200
c : %size(Msg0200)
c : 'RCVM0200'
c : '*'
c : 0
c : '*LAST'
c : *blanks
c : 1
c : '*REMOVE'
c : ApiError)
*ReceiveMsg makes a call to the QMHRCVPM
c if Msg0200.BytesAvail = 0
c Leave
c endif
c callp LogMessage
c enddo
c endmon

Can anyone please shed some light as to what I might be missing.
Aren't
all messages
thown by the QCMDEXC call supposed to be captured by the calling
program's Monitor /End-mon block?
Any help is greatly appreciated.

Jose




This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].