[Sam Craig]

Jim, would you please email me the FTP tclproc that you mention in the post.

My email is scraig@uh.org

[Sam Craig]

Here is a link to the 5.6 Rev2 Release Notes.

https://usspvlclovertch2.infor.com/files/docs/56_rev2/ReleaseNotes.htm#_Supported_Environments_and

Hope this helps…

[Sam Craig]

We are on 5.3 version of AIX on a P6-520 IBM server.

Cloverleaf 5.5 version.

Using IBM’s VIO (Virtual I/O Server) to virtualize all hardware.

Been running on it since early 2009.

Have had no issues and love the virtualization.  Can move from our primary physical P6-520 server to our secondary physical P6-520 without having to stop the Cloverleaf engine.  Users cannot tell when move is happening and it has been great.  Server guys set it up to use virtual CPU’s.  I think we have one allocated, but if needed, it will automatically use more CPU’s.

If you can, I would highly recommend using virtual CPU’s and hardware with AIX.

[Sam Craig]

We run the Cloverleaf server on an AIX system.

There is a user called hci that is setup on the server during Cloverleaf install.

When logging in as the hci user in AIX, there is a .profile file that runs and sets up the environment variables.

Here is a quote from the .profile file……

# This file is used to set up a per-user login environment.  Since this

# .profile is in the hci user’s home directory, it is used to set up the

# environment for the hci user.

Found this in the Windows system install instructions.

hciuser account

The hciuser account must be created before Cloverleaf

[Sam Craig]

You have to login to the telnet session as user hci.

[Sam Craig]

Thanks for all the info….. 😀

Just seems weird that I have not seen this happen to a process since I started working with Cloverleaf about 6 years ago.

I have other processes in our test region that don’t have any activity overnight, after the automated job runs, and they all go back to either opening or up state.

Thanks,

Sam

[Sam Craig]

Hate to argue with THE Cloverleaf guru…. 🙂

But, I have tried to use a counter without a %g, %s, %f, or %l and the xlate won’t compile.

Like this simple action:

COPY       =1 -> {$%d98}

COPY       {$%d98} -> 0(0).OBX(0).#1

Produces this error in XLT testing tool:

[0:TEST] Unrecognized field name ‘Invalid interpolation variable  %d98’

[0:TEST] Unable to compile OUT list ‘{$%d98}’

[0:TEST] Unable to compile statement ‘

{ OP COPY }

   { ERR 0 }

   { IN =1 }

   { OUT {{$%d98}} }

‘

[0:TEST] Unrecognized field name ‘Invalid interpolation variable  %d98’

[0:TEST] Unable to compile IN list ‘{$%d98}’

[0:TEST] Unable to compile statement ‘

{ OP COPY }

   { ERR 0 }

   { IN {{$%d98}} }

   { OUT 0(0).OBX(0).#1 }

‘

[0:TEST] Unable to compile XLT ‘Midas_MDM_to_HPF_play.xlt’.

Is there a way to use the %d98 as a counter in an Xlate?

❓

[Sam Craig]

We went with a different approach to the character limitation in the GUI.

And it avoids the slight bug encountered if you “touch” the field with the GUI.

We are 5.5 Rev1 and 5.3 AIX.

As Jim and Bob mentioned, you have to edit manually.

We set our particular field to 500,000 characters.  The GUI will not reset the field length back to zero with this method.

Here is what it looks like in the fields file…..

{ITEM 100161} {NAME ZTF3} {TYPE ST} {LEN 500000}

I know it is not unlimited, but better than having the field reset to zero if someone “touches” the field using the GUI.  Especially if the person does not notice that the field has been reset to zero.  As you can imagine, not a good thing…. 😯

You can probably put in a larger number like 1,000,000 or whatever your heart desires for the field length.

Just food for thought or another way to skin the cat. 😈

[Sam Craig]

Here is code from one of our cron jobs.

It sets the environment variables and we use the full path for the hcicmd.

Might be over kill, but it works.

## Setup hci environment

export ROOT=”/quovadx/qdx5.5/integrator”

export FPATH=$FPATH:/quovadx/qdx5.5/integrator/kshlib

export PATH=$PATH:$ROOT/bin

export SITE=”pimprod”

setroot $ROOT

## Run the setsite command to the region you want to process

setsite $SITE

## Start the thread

/quovadx/qdx5.5/integrator/bin/hcicmd -p process_2 -c “nextgen5_ob pstart”

Hope this helps…..

[Sam Craig]

Correct, I know it matches the HL7 standard, but some vendors seem to ignore the standard.

The engine we used here many years ago did not care about field lengths for delimted messages.  So, we never had truncation issues.

Anyway, thanks for your response.

Later,

Sam

[Sam Craig]

Did support say anything about why dumping the errors caused the site to hang?  ❓

Thx,

Sam

[Sam Craig]

Check and see if you have the IMArchive5 files in the /quovadx/qdx5.4/integrator/sbin directory.

There is a Readme_IMArchive.txt file that will help you get the archiving setup.

This code came with the Cloverleaf product from vendor.

We have been using this code for about six years, since version 5.2 of Cloverleaf.  It works great and very easy to get setup.

Currently on 5.5 running on 5.3 AIX.

[Sam Craig]

I think you missed your calling as a writer!!  😀

Thanks, that was great…..

Hope all have a safe and good Holiday……

[Sam Craig]

Search the SMAT file for the message ID listed in the error message and see what is in MSH-9.  Is it setup as a Wildcard for ORU in Thread config?

[Sam Craig]

For SMAT file viewing, we use a product called NEOBROWSE.

Not free, but not to expensive.  

It is great for viewing HL7 messages.

Email me if you want more info on cost and send you some screen shots.

scraig@uh.org

[Author]

Replies