Re: Why does node's Toolkit for i, use a database connection to execute CL commands?

To add a little more detail of how I think it works:

If I set ipcvalue =/tmp/xmlservicei in an XMLCGI URL request, a new XTOOLKIT job fires on the i in QSYSWRK and stays active until I kill the IPC job using the same ipcvalue that started it.

I believe all DB activity and command or program call activity use the same job so it feel persistent.

It would seem that XMLSERVICE continues to use the same XTOOLKIT active job until terminated which allows some persistence of session such as library list, qtemp, etc.

I don't claim to fully understand the XMLCGI / IPC method, but it seems to work nicely.

If you do an experiment, specify the same IPC value for each call and see if that improves performance. It should because the XTOOLKIT jobs should stay active between calls to the IBMi which you can monitor via WRKACTJOB. The first call with an IPC value launches a new XTOOKLIT job and the next xxx number of calls should all use that job.

Hope this helps.

You could always put an email in to Tony Cairns at IBM if you have any plumbing questions. His email address is on the Yips site.

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
Visit me on: Twitter | LinkedIn

-----Original Message-----
Subject: Re: Why does node's Toolkit for i, use a database connection to execute CL commands?
*From: Kevin Turner <kevin.turner@xxxxxxxxxxxxxxx>
*Date: Sun, 11 Oct 2015 20:43:57 +0000

That's interesting stuff - thanks. I'm not entirely sure how to dig deeper but I will try :)


On 11 Oct 2015, at 17:47, Richard Schoen <Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

I wonder if the loop is forcing a new job start each time on the i.

With XMLCGI, there is an IPC service that takes a few seconds each time it's re-initiated and I could see this being intensive if you had to create a new session for each interaction.

You can start the IPC session with a unique name and use the same job over and over if I want to maintain state and use the same job on the I which should improve performance I think.

Not sure how the node toolkit works, but this works good with .Net and should be similar depending on how the toolkit was implemented.

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
Visit me on: Twitter | LinkedIn