Running order of threads

[Johnny Anderson]

CL 5.5,  Sun, Solaris 10.

I

Topic

[Max Drown (Infor)]

One way that might work for you is to turn off auto-start and use a script to turn on the process and threads.

Example1:

hcienginerun -p processName -s ‘thread1, thread2’

Example2:

hcienginerun -p processName

hcicmd -p processName -c ‘thread1 pstart’

hcicmd -p processName -c ‘thread2 pstart’

-- Max Drown (Infor)

[Jim Kosloskey]

Johnny,

Are the threads file protocol or fileset/local?

If file you might think about fileset/local and allow the directory parsing on thread2 to pickup the file when thread1 has placed it. Then it won’t matter which one starts first I think.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Johnny Anderson]

Max, Jim, we

[Serjik Jookar]

Max Drown wrote:

One way that might work for you is to turn off auto-start and use a script to turn on the process and threads.

Example1:

hcienginerun -p processName -s ‘thread1, thread2’

Example2:

hcienginerun -p processName

hcicmd -p processName -c ‘thread1 pstart’

hcicmd -p processName -c ‘thread2 pstart’

Max,

As Johnny explained above.

We need thread 1 start first and use the output of thread 1 to be input file for thread 2.

Will example 2 start thread 1 first and finish what it suppose to do before thread 2 kicks in and use thread 1 out put?

In other word, will thread 2 wait until thread 1 is finished and done before thread 2 starts?

Thanks,

SJ

On example 2.

[Max Drown (Infor)]

Negative. Those commands I supplied will only start up threads with no additional AI (artificial intelligence). Essentially, they are simply replacements for mouse clicks in the GUI.

-- Max Drown (Infor)

[Max Drown (Infor)]

Could you explain your work flow in more detail, please? Maybe a screenshot would be helpful, too.

-- Max Drown (Infor)

[Johnny Anderson]

CL 5.5,  Sun, Solaris 10.

Max, I have PowerPoint screen shots attached and the flow is: ORU Lab Results, 1 process, 2 threads- 1. xlate xml to hl7 as txt file.

Process all ip xml data like a batch until eof.  2. xlate same hl7 txt file to a frl friendly record file.  Process all ip txt data like a batch

until eof.

[Max Drown (Infor)]

Here’s your workflow as I understand it:

.xml –> xlate –> .txt –> xlate .hrl

Why don’t you do this instead?

.xml –> xlate –> .hrl?

Then, you wouldn’t need to worry about thread starting/stopping order.

-- Max Drown (Infor)

[Johnny Anderson]

Max, we have internal applications that require the txt version.

[Jim Kosloskey]

Why not 2 Xlates off of the single source?

One thread in 2 out – 2 routes from the inbound thread one to hrl one to txt.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Max Drown (Infor)]

That’s no problem either; you’d have something like this:

.xml –> xlate –> .hrl

-- Max Drown (Infor)

[Author]

Replies