RE: CCSID of rplacement data in QMHRTVM

Thank you. I changed the To CCSID parameter to 0 so that is would convert to
the job CCSID and it worked great.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Richter
Sent: Friday, July 22, 2011 3:17 PM
To: Midrange Systems Technical Discussion
Subject: Re: CCSID of rplacement data in QMHRTVM

I would experiment with the ToCcsid set to a value other than 65535. Set it
as the ccsid of the job. 65535 means "no ccsid. hex data". I would think
the api would throw an exception if you tried to convert from something to
nothing.



On Fri, Jul 22, 2011 at 3:38 PM, Bob Kohlndorfer
<bkohlndorfer@xxxxxxxxxx>wrote:

Can someone help?

We have been putting the joblog information of our daily backup to an
*outfile for a few months now.

We would like to retrieve certain messages that we know are problems with
the data formatted in a readable format.

I am using the QMHRTVM API to format the data but am having problems with
CPFA09E messages. The message is that ?Object is in use?. My problem is
that
the replacement data is not showing up correctly.

The file that contains the joblog information has a field (QMHCID) that
specifies the CCSID that the message replacement data is stored in.

For most records the CCSID is 65535 but for the CPFA09E records the CCSID
is
1200.

The QMHRTVM API has a parameter to let it know what the CCSID of the
replacement data is stored in and I pass that along from the file but it
does not give me valid data in return.



Here is how the raw Replacement data looks in SQL:

¢ %

?

Å



And here is how it looks when ?formatted? by the API:

Object in use. Object is
% ? Å.Cause . . . . . : An operati?



Here is my call to the API:

* Retrieve Message API...

C call 'QMHRTVM'

C parm DsMessage

C parm MsgInfoLen

C parm FormatName

C parm MsgID

C parm MsgFileName

C parm MsgDataValue

C parm MsgDataLen

C parm ReplSubstValue

C parm RtrnFmtCtlChar

C parm APIErrorDS

C parm RtvOption

C parm CCSIDTo

C parm CCSIDFrom



The CCSIDTo is always 65535, CCSIDFrom comes from the file and is normally
65535 but for CPFA09E messages it is 1200.



Thanks,

Bob Kohlndorfer





--
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.