RE: RSLVSP extended template definition help

Thanks Barbara. I wondered if that might be my problem but didn't know where to find the bit order information. I'll switch it around and give it a try.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: Friday, October 22, 2010 6:48 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: RSLVSP extended template definition help

On 2010/10/22 4:51 PM, Rick.Chevalier@xxxxxxxxxxxxxxx wrote:

I am trying to use the RSLVSP MI instruction to check object existence from a procedure at run time. If the object exists everything is fine. If the object doesn't exist I get a MCH error. If I understand the documentation correctly I can set a value in the extended template under the options section to not return the MCH error and just return a null pointer instead.

d dsUsrIdxDesc ds Qualified
d TypeCode 1a Inz(x'0E')
d SubtypeCode 1a Inz(x'0A')
d ServicePgm 30a Inz('UT1025UI')
d ReqAuth 2a Inz(x'0001')
d TemplateVer 1a Inz(x'00')
d SearchMethod 1a Inz(x'00')
d Options 1a Inz(x'02')
d Reserved1 7a Inz(x'00')
d ASPToSearch 2a Inz(x'00')
d ASPOfContext 2a
d PtrToContext * ProcPtr
d Reserved2 64a Inz(x'00')

Rick, the Do-not-signal-not-found bit is the second bit in the Options, b'0100 0000', but you've set the second-last bit, b'0000 0010'. Try x'40'.

You have the ReqAuth initialization correct; the use-extended bit is bit(15).

It's always confusing to talk about bit numbers, because they could mean either left-to-right or right-to-left. The MI documentation describes them in storage terms, left-to-right, with bit(0) being the high-order bit.
--
This is the RPG programming on the IBM i / System i (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.



Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.