|
Folks,
I don't remember all the parameters to commands off of the top of my head.
I prompted RCVMSG to get MSGDTA and MSGDTALEN. Then, when I determined he
wanted the combo of MSGDTA and the message text I prompted RCVMSG again
and got MSG.
How do we help people like the OP learn and develop problem solving
skills? Instead of suggesting MSG suggest, instead, that they prompt
RCVMSG and see if they can figure it out?
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Paul Therrien <ptherrien@xxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 01/15/2013 02:33 PM
Subject: RE: get MSGID of error that caused abend (instead of
CPF9999 errorID)
Sent by: midrange-l-bounces@xxxxxxxxxxxx
You can retrieve the actual message from the job. If you are able to pull
in the MSGDTA then you can pull in the MSG.
Paul
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
Sent: Tuesday, January 15, 2013 12:41 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: get MSGID of error that caused abend (instead of CPF9999
errorID)
Thanks -
RCVMSG returns "CUSTFILETESTLIB *N"
RTVMSGD returns " File &1 in library &2 in use. "
I would like to return the following string:
' File CUSTFILE in library TESTLIB in use. "
Is this possible - to merge the text message with the variables?
Thanks
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, January 15, 2013 12:05 PM
To: Midrange Systems Technical Discussion
Subject: RE: get MSGID of error that caused abend (instead of CPF9999
errorID)
Don't use RTVMSGD, that just pulls it from QCPFMSG message file. See
these parameters for RCVMSG:
MSGDTA
MSGDTALEN
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Stone, Joel" <Joel.Stone@xxxxxxxxxx>
To: "midrange-l@xxxxxxxxxxxx" <midrange-l@xxxxxxxxxxxx>,
Date: 01/15/2013 01:01 PM
Subject: RE: get MSGID of error that caused abend (instead of
CPF9999 errorID)
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Well I tried this again and it worked well - it returned CPF3202.
RTVMSGD MSGID(&RTNCODE) FSTLVL(&ERRMSG)
I am using the above to retrieve the error text.
It returns
' File &1 in library &2 in use. "
How can I get the variables to be replaced with their values?
For example
"File CUSTFILE in library TESTLIB in use"
Thanks
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
Sent: Tuesday, January 15, 2013 11:56 AM
To: midrange-l@xxxxxxxxxxxx
Subject: get MSGID of error that caused abend (instead of CPF9999 errorID)
I have a CL with MONMSG(CPF9999) as the first line.
MONMSG MSGID(CPF9999) EXEC(GOTO CMDLBL(ABENDPGM))
At the end of the CL, I would like to retrieve the actual MSGID which
caused the problem (NOT the CPF9999 ID, but the msg previous to that).
ABENDPGM:
RCVMSG MSGID(&RTNCODE)
I tried the obvious *PREV to get the previous msgID, but no luck.
For example, I want to retrieve CPF3202 "File CUSTFILE in library TESTLIB
in use".
Any ideas?
Thanks
______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs
Skyscan service.
For more information please visit http://www.symanteccloud.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 inbound email has been scanned for all viruses by the MessageLabs
SkyScan
service.
________________________________________________________________________
______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs
Skyscan service.
For more information please visit http://www.symanteccloud.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.
________________________________________________________________________
This inbound email has been scanned for all viruses by the MessageLabs
SkyScan
service.
________________________________________________________________________
______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs
Skyscan service.
For more information please visit http://www.symanteccloud.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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
