Forum Replies Created
-
AuthorReplies
-
we are running cloverleaf 6.0.2 should we be running SNA 6.4 instead of the version verified byt the same command as the user in this posting. We are having issues with the connection when one side or the other goes down then starts back up. We are also on Mainframe Invision 27.5 of SMS.
[hci@aixhaserv]:/home/hci> lslpp -l | grep sna
bos.net.snapp 6.1.6.0 COMMITTED System Networking Analysis and
sna.dlcmpc 6.3.1.0 COMMITTED MPC Data Link Control
sna.gsk_jre 6.3.1.0 COMMITTED Custom JRE for gskit
sna.lu0 6.3.1.0 COMMITTED Logical Unit 0 (LU0)
sna.msg.en_US.rte 6.3.1.0 COMMITTED SNA Base Messages – U.S.
sna.msg.en_US.snapi 6.3.1.0 COMMITTED SNAPI TP Development Tool –
sna.msg.en_US.wa 6.3.1.0 COMMITTED SNA Web Admin Tool Messages –
sna.msg.en_US.xsna 6.3.1.0 COMMITTED SNA X Tool Messages – U.S.
sna.rte 6.3.1.0 COMMITTED Communications Server Base
sna.rte64 6.3.1.0 COMMITTED 64-bit support for
sna.snapi 6.3.1.0 COMMITTED Communications Server SNAPI TP
sna.wa 6.3.1.0 COMMITTED Web-based Administration for
sna.xsna 6.3.1.0 COMMITTED X-Windows Management Tool for
bos.net.snapp 6.1.6.0 COMMITTED System Networking Analysis and
sna.dlcmpc 6.3.1.0 COMMITTED MPC Data Link Control
sna.lu0 6.3.1.0 COMMITTED Logical Unit 0 (LU0)
sna.msg.en_US.rte 6.3.1.0 COMMITTED SNA Base Messages – U.S.
sna.msg.en_US.snapi 6.3.1.0 COMMITTED SNAPI TP Development Tool –
sna.msg.en_US.wa 6.3.1.0 COMMITTED SNA Web Admin Tool Messages –
sna.msg.en_US.xsna 6.3.1.0 COMMITTED SNA X Tool Messages – U.S.
sna.rte 6.3.1.0 COMMITTED Communications Server Base
sna.rte64 6.3.1.0 COMMITTED 64-bit support for
sna.snapi 6.3.1.0 COMMITTED Communications Server SNAPI TP
sna.wa 6.3.1.0 COMMITTED Web-based Administration for
sna.xsna 6.3.1.0 COMMITTED X-Windows Management Tool for
sna.docs.Ja_JP.data 6.3.1.0 COMMITTED SNA PDF documentation –
sna.docs.de_DE.data 6.3.1.0 COMMITTED SNA PDF documentation – German
sna.docs.en_US.data 6.3.1.0 COMMITTED SNA PDF documentation – U.S.
sna.docs.es_ES.data 6.3.1.0 COMMITTED SNA PDF documentation –
sna.docs.fr_FR.data 6.3.1.0 COMMITTED SNA PDF documentation – French
sna.docs.ko_KR.data 6.3.1.0 COMMITTED SNA PDF documentation – Korean
sna.docs.pt_BR.data 6.3.1.0 COMMITTED SNA PDF documentation –
sna.docs.zh_CN.data 6.3.1.0 COMMITTED SNA PDF documentation –
sna.docs.zh_TW.data 6.3.1.0 COMMITTED SNA PDF documentation –
sna.ecl.data 6.3.0.0 COMMITTED Host Access Class Library
sna.man.en_US.rte.data 6.3.1.0 COMMITTED SNA Server Manual Pages – U.S.
sna.man.en_US.xsna.data 6.3.1.0 COMMITTED SNA Server X Tool Manual Pages
[hci@aixhaserv]:/home/hci>
This issue first came about in 5.8.5 when there was an attempt to lock the smat file to a single user where before it was opened as read only to multiple uses. You could toggle and edit the message and resend it with the only evidence of the edit was in the /hci/cis5.8/integrator/temp directory in a file named with a random name beginning with tmp. It did not save the message you edited in smat as it does with this change. You never know when the cycle happens. You can be in it perform various tasks get out back in then out again and back in an hour later and all of a sudden it cycles with out notification/error or any mention of it you only notice that it has 0 records or that it has 1 record. Between the last time you got out and getting back in you do not know what happened to any and all messages between that time. If they are lost that is critical, there is no way of knowing.
Rob Abbott, when I asked about a webx for the new version you had indicated that once the on the road show was over that there would be one. The last show was at the end of November. I was wondering if the webx has been completed to be ready to present it.
Will there be a webx or recording of the proceedings for this for those that may not be able to make any of the events?
Look at release notes as they had changed handling of smat files in 5.8.5 that is why we did not apply it as well as the issue of the netmonitor thread labels no lonnger have the option of being inside the thread.
Could there be a creation of a new section in the release notes to handle those customer under HA that have the option that on a fail over from prod to test so that on the test side you can have the two version running, the version from live and the testing version of the upgrade. I do know that there is a descrition of how to have two versions running under another section but could you include unser the install of the new release for HA customers instructions for running the PROD version on the PROD box and on the TEST box be running the same verson as the PROD at the same time running the new released version. November 16, 2009 at 4:04 pm in reply to: Has anyone dealt with Phillips Vital sign interfaces at all? #67642Has there been further use of cloverleaf to interface between phillips vital devices and charting systems? One system being EDIS from AllScripts.
we have alerts running 5.7 and are experiancing the same issue of two emails per alert. This does appear to be a healthvision issue that needs to be resolved for all versions.
I have to agree that it is cumbersome as to how may screens you must go through to get the desired result especially when you want to do just a quick search. Not sure where the views are saved to or how to get them back from site to site and message file to message file. Would like an option to have the old format. As it was indicated that this is requesting clovertech ideas but I was wondering if there is already a suggestion box for CLOVERLEAF or could there be one created as there was for alerts a what you might call a wish list for CLOVERLEAF the Interface.
If I sign in I can view it. Before with version 5.6 and below when the documentation was posted when it was a pdf we could download it. When you went to the new format with 5.6 we could still download the document as an internet type document that we could email to others here at Crouse that may need to review it.
Thanks,
Bill Marsch
It appears you have locked up the document not allowing it to be downloaded in advance of receiving the software update or allowing to be able to send the link to the document for others to view?
Bill Marsch
Crouse Hospital
Here is a tcl that you can pass a field to it and remove the left and right parens from and replace them using the “string map” command:
######################################################################
# Name: tpsremoveparen
# Purpose:
# UPoC type: xltp
# Args: none
# Notes: All data is presented through special variables. The initial
# upvar in this proc provides access to the required variables.
# The expected InVal is a field to remove left and right parens
#
# This proc style only works when called from a code fragment
# within an XLT.
#
proc tpsremoveparen {} {
upvar xlateId xlateId
xlateInList xlateInList
xlateInTypes xlateInTypes
xlateInVals xlateInVals
xlateOutList xlateOutList
xlateOutTypes xlateOutTypes
xlateOutVals xlateOutVals
set fld1 [lindex $xlateInVals 0]
if { [clength $fld1] > 2 } {
set y [string map {( “” ) “”} $fld1]
}
#echo n “range is ” $y
set xlateOutVals “$y”
}
Charlie, I know I asked this before though that was about a while ago. There appears to have been no postings since december 2007. I was wondering if was posible for a status of the wish list and modifications that we might expect or options/documentation/summary of what is to come and when. We have just recently implemented in our production area some alerts. We are runing under 5.6 of cloverleaf. Thanks, bill are there any command line commands for debuging your java rmi in unix? -
AuthorReplies