RPC Calls and Arguments

[Gavin Nesmith]

Is there a list or manual I can use to lookup RPC calls in vista to see the expected arguments?

I tried doing some googling and came up empty.

[Thurber, Joseph H]

You can look them up in the REMOTE PROCEDURE file using Fileman.  Some are defined very clearly and some are not well- commented.  It will also show the routine being called.  You can examine that for further clarification.  

On Sep 21, 2023, at 9:46 PM, Gavin Nesmith <grne...@gmail.com> wrote:



CAUTION: External email. Do not click links or open attachments unless verified. Report suspicious emails with the Report Message button located on your Outlook menu bar on the Home tab.

Is there a list or manual I can use to lookup RPC calls in vista to see the expected arguments?

I tried doing some googling and came up empty.

--
--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+u...@googlegroups.com

---
You received this message because you are subscribed to the Google Groups "Hardhats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hardhats/e08404b9-6df7-424b-ba66-fdcc7ba8fc3en%40googlegroups.com.

---

Email correspondence to and from this address is subject to the North Carolina Public Records Law and may be disclosed to third parties by an authorized State official. Unauthorized disclosure of juvenile, health, legally privileged, or otherwise confidential information, including confidential information relating to an ongoing State procurement effort, is prohibited by law. If you have received this email in error, please notify the sender immediately and delete all records of this email.

[Sam Habiel]

Luckily, we extract the file and put it in Vivian, so you can see all of it online.

https://vivian.worldvista.org/vivian-data/8994/All-RPC.html

--Sam

To view this discussion on the web visit https://groups.google.com/d/msgid/hardhats/E5F03322-47A7-4F0B-B3AA-97E11A8B2CC1%40dhhs.nc.gov.

[Sam Habiel]

Also, I forgot to answer the rest of your question:

There is NO WAY to see the arguments except if you actually read the routine that is called. RPCs are not "typed", and arguments only matter in the agreement between the caller and callee, which is sad, but that's the way it is.

--Sam

[Greg Kreis]

Join me in thanking:

• The OSEHRA team for creating Vivian, what a rich app!
• WorldVista for hosting it!
• Sam Habiel for continuing to support it!
• Nancy Anthracite for running it each month to keep the lists current!

Hip hip hurrah!

To view this discussion on the web visit https://groups.google.com/d/msgid/hardhats/CABHT963H%3DjTV6Hkh%3DMbYpF_jr%2B6RS037%3D68xbfv8GGCk86GnrA%40mail.gmail.com.

-- 
=================
Greg Kreis
Pioneer Data Systems, Inc.
770-509-2583
http://www.PioneerDataSys.com

[Gavin Nesmith]

Thanks all. I will have a look at these resources. I turned up the rpc debug level but for some reason I didn’t think to look into fileman for the rpc file. 

Thanks Sam for the link that looks really valuable for my needs. 

Sent from my iPhone

On Sep 22, 2023, at 9:16 AM, Greg Kreis <gkr...@pioneerdatasys.com> wrote:



You received this message because you are subscribed to a topic in the Google Groups "Hardhats" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/hardhats/TaI8uvIWZ5s/unsubscribe.
To unsubscribe from this group and all its topics, send an email to hardhats+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hardhats/b0ee9086-0c07-4c39-61c1-2b7c95eff02f%40pioneerdatasys.com.

[Benjamin Irwin]

Sorry I am a little late.  I have attached a RPC listing from the recently released FOIA release.

[leo]

hurrah!

To view this discussion on the web visit https://groups.google.com/d/msgid/hardhats/b0ee9086-0c07-4c39-61c1-2b7c95eff02f%40pioneerdatasys.com.

[Thurber, Joseph H]

Yep.  Hurrah!

To view this discussion on the web visit https://groups.google.com/d/msgid/hardhats/5cf8940e-9bf5-41b3-9ceb-f70421fc1178%40gmail.com.

[Paul Vandenberg]

I'll also join in and say hurrah to everyone involved is creating and maintaining Vivian. Thank you!!

[Nancy Anthracite]

Thanks! I would also like to point out that YottaDB also funded some work to
keep Vivian going.

--
Nancy Anthracite

On Friday, September 22, 2023 10:08:52 PM EDT Paul Vandenberg wrote:
> I'll also join in and say hurrah to everyone involved is creating and
> maintaining Vivian. Thank you!!
>
> On Friday, September 22, 2023 at 3:20:19 PM UTC-5 Thurber, Joseph H wrote:
>
> > Yep. Hurrah!
> >
> > On Sep 22, 2023, at 2:53 PM, leo <leo...@gmail.com> wrote:
> >
> > 
> > CAUTION: External email. Do not click links or open attachments unless
> > verified. Report suspicious emails with the Report Message button located
> > on your Outlook menu bar on the Home tab.
> >
> > hurrah!
> > On 9/22/23 12:15, Greg Kreis wrote:
> >
> > Join me in thanking:
> >

> > - The OSEHRA team for creating Vivian, what a rich app!
> > - WorldVista for hosting it!
> > - Sam Habiel for continuing to support it!
> > - Nancy Anthracite for running it each month to keep the lists current!

> >
> > Hip hip hurrah!
> > On 9/22/2023 10:12 AM, Sam Habiel wrote:
> >
> > Luckily, we extract the file and put it in Vivian, so you can see all of
> > it online.
> >
> > https://vivian.worldvista.org/vivian-data/8994/All-RPC.html
> >
> > --Sam
> >
> > On Fri, Sep 22, 2023 at 7:08 AM Thurber, Joseph H <joe.t...@dhhs.nc.gov>
> > wrote:
> >
> >> You can look them up in the REMOTE PROCEDURE file using Fileman. Some
> >> are defined very clearly and some are not well- commented. It will also
> >> show the routine being called. You can examine that for further
> >> clarification.
> >>
> >> On Sep 21, 2023, at 9:46 PM, Gavin Nesmith <grne...@gmail.com> wrote:
> >>
> >> 
> >> CAUTION: External email. Do not click links or open attachments unless
> >> verified. Report suspicious emails with the Report Message button located
> >> on your Outlook menu bar on the Home tab.
> >>
> >> Is there a list or manual I can use to lookup RPC calls in vista to see
> >> the expected arguments?
> >>
> >> I tried doing some googling and came up empty.
> >>

> >> ---
> >> You received this message because you are subscribed to the Google Groups
> >> "Hardhats" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an
> >> email to hardhats+u...@googlegroups.com.
> >> To view this discussion on the web visit
> >> https://groups.google.com/d/msgid/hardhats/e08404b9-6df7-424b-ba66-fdcc7ba8fc3en%40googlegroups.com

> >> <https://groups.google.com/d/msgid/hardhats/e08404b9-6df7-424b-ba66-fdcc7ba8fc3en%40googlegroups.com?utm_medium=email&utm_source=footer>
> >> .
> >>
> >>
> >> ------------------------------

> >>
> >> Email correspondence to and from this address is subject to the North
> >> Carolina Public Records Law and may be disclosed to third parties by an
> >> authorized State official. Unauthorized disclosure of juvenile, health,
> >> legally privileged, or otherwise confidential information, including
> >> confidential information relating to an ongoing State procurement effort,
> >> is prohibited by law. If you have received this email in error, please
> >> notify the sender immediately and delete all records of this email.
> >>

> >> ---
> >> You received this message because you are subscribed to the Google Groups
> >> "Hardhats" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an
> >> email to hardhats+u...@googlegroups.com.
> >> To view this discussion on the web visit

> >> https://groups.google.com/d/msgid/hardhats/E5F03322-47A7-4F0B-B3AA-97E11A8B2CC1%40dhhs.nc.gov
> >> <https://groups.google.com/d/msgid/hardhats/E5F03322-47A7-4F0B-B3AA-97E11A8B2CC1%40dhhs.nc.gov?utm_medium=email&utm_source=footer>
> >> .

> >>
> >
> > ---
> > You received this message because you are subscribed to the Google Groups
> > "Hardhats" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to hardhats+u...@googlegroups.com.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/hardhats/

CABHT963H%3DjTV6Hkh%3DMbYpF_jr%2B6RS037%3D68xbfv8GGCk86GnrA%40mail.gmail.com
> > <https://groups.google.com/d/msgid/hardhats/
CABHT963H%3DjTV6Hkh%3DMbYpF_jr%2B6RS037%3D68xbfv8GGCk86GnrA%40mail.gmail.com?
utm_medium=email&utm_source=footer>
> > .

> >
> >
> >
> > ---
> > You received this message because you are subscribed to the Google Groups
> > "Hardhats" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to hardhats+u...@googlegroups.com.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/hardhats/

b0ee9086-0c07-4c39-61c1-2b7c95eff02f%40pioneerdatasys.com
> > <https://groups.google.com/d/msgid/hardhats/
b0ee9086-0c07-4c39-61c1-2b7c95eff02f%40pioneerdatasys.com?
utm_medium=email&utm_source=footer>
> > .

> >
> >
> > ---
> > You received this message because you are subscribed to the Google Groups
> > "Hardhats" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to hardhats+u...@googlegroups.com.
> >
> > To view this discussion on the web visit

> > https://groups.google.com/d/msgid/hardhats/5cf8940e-9bf5-41b3-9ceb-f70421fc1178%40gmail.com
> > <https://groups.google.com/d/msgid/hardhats/5cf8940e-9bf5-41b3-9ceb-f70421fc1178%40gmail.com?utm_medium=email&utm_source=footer>
> > .
> >
> >
>
>

[Kevin Toppenberg]

Gavin,

Sorry for the late reply.

In the TMG library, we have a RPC utility that tries to give one as much info as possible, by looking in the REMOTE PROCEDURE file, and also by showing the entry point in the code, so one can see how many parameters there are, and any following likes if they contain comments, as sometimes coders will put hints there about expected input.  We also let the user add entries to specify the typing of each parameter, once figured out.  And then the user can step through the code with a debugger...

Another technique that can be used is as follows.  We do this commonly at our site. 

Insert the following code at the top of the code you want to debug.

ENTRY^SAMPLERPC(OUT,A,B,C,D) ;

; A,B,C,D are parameters

;

;==start wedge=====
NEW ZZZDEBUG SET ZZZDEBUG=0

IF ZZZDEBUG=1 DO

. KILL A,B,C,D

. MERGE A=^TMP($J,"ENTRY^SAMPLERPC","A")
. MERGE B=^TMP($J,"ENTRY^SAMPLERPC","B")
. MERGE C=^TMP($J,"ENTRY^SAMPLERPC","C")
. MERGE D=^TMP($J,"ENTRY^SAMPLERPC","D")

ELSE  DO

.  KILL ^TMP($J,"ENTRY^SAMPLERPC")

. MERGE ^TMP($J,"ENTRY^SAMPLERPC","A")=A

. MERGE ^TMP($J,"ENTRY^SAMPLERPC","B")=B
. MERGE ^TMP($J,"ENTRY^SAMPLERPC","C")=C
. MERGE ^TMP($J,"ENTRY^SAMPLERPC","D")=D
;==end wedge=====

<normal code continues here>.....

So first you do whatever process would normally call the RPC in question.  This will effect the storage of input variables into ^TMP(...

Then, come back with a step-by-step debuger, and pause (or set a breakpoint) on the line:

    IF ZZZDEBUG=1 DO

Then, manually set ZZZDEBUG=1, i.e. at the command line or however your debugger allows, which now change the behavior of the code, allowing you to recover the previously stored variables, and then you can continue stepping through the code, seeing how it works with typical input.

Hope that helps.

Kevin

[Kevin Toppenberg]

Sam,

I'm not sure I agree with you here, or I don't understand what you are saying.   Arguments definitely ARE typed by convention.  There are literals, arrays, etc.  There is a field in the REMOTE PROCEDURE file that specifies the type of an argument. It is true that many developers are slack in proper documentation, so often it takes some effort figure out what their intent was.  But it achievable, and we do it all the time.  We then add this information into the REMOTE PROCEDURE file for future reference.

Because Mumps is not typed, it would be possible to use mumps code to call mumps RPC's with whatever type (number, string, array, date etc) one wants.  But when calling from a strongly-typed language, such as Pascal, they typing is even more clear.  I am not aware of any RPC where some callers will send in one type of data on a particular argument, and then other callers send in something different on that same argument.  I think that once you figure it out, the type of each argument will be stable.  This is not to say that they won't pass data strings (e.g. "1^abc^elephant^T+1") which contain mixed information. But still this would be considered a "literal" string.

Anyway, that is my understanding.

Kevin

[David Whitten]

One of the WorldVistA projects has been to enhance the information in
the REMOTE PROCEDURE file to include more information on possible
calls to share to the community.

Please help us collect that information
Dave Whitten
713-870-3834

> To view this discussion on the web visit https://groups.google.com/d/msgid/hardhats/2c6f658d-1ab9-47d8-9eea-78c66c414974n%40googlegroups.com.