@robert-gordon
Forum Replies Created
-
AuthorReplies
-
Not only can tcl libs cause problems, DST changes can cause time errors on tcl code, as well as unix i.e. primary write on a file is -1:00 hr less than pc time. Solution bounce server, host server.
Once your ready for go-live, copy the NetConfig.date to NetConfig do a reload of your monitor screen, then start your thread, n.b. this only works if the thread is under the same process.
A simple copy and past should work, in other words open the netconfig in the test site, copy the thread, and in the same gui session go to ‘live’ open the netconfig and paste. The last things you should change are your port numbers. Have a few days before go live save the new netconfig with the go-live date i.e. ‘NetConfig.20101102’ and check it everyday until the go-live date to make sure you got all the procs and xlates into the live environment.
The easiest transition to DOS/Windoze is getting a Unix Shell in Dos and running the scripts from there, of course each script would still have to be tested and reviewed, but then again its better than translating everything into TCL if you don’t have time on you side.
Marcus;
It looks like the vendor is using either html or rtf tags in an xml style, you can filter them out or find out if your receiving application can use them. In the receving application needs only text results then filter then out, if your receiving application can receive formated text then convert the information.
filter out
regsub -all “\E\|\.br\…” $xlateOutVals “” xlateOutVals
translate
|
________________________________________________________________________________________________________________________and
NotesA teacher leaves a crossword puzzle to a bunch of kindergarden students. One student figures out the solution and then lets all the other students copy the answer. The students continues to do this all year. Today the students a year latter still can’t spell cat or dog…
This works but now you have to create ump-teen different logins to hold one variable, related to each site this person has…
I hope he has full unix rights to create all the users and then have them for cron…
In Windoze/Unix/Aix/Linux everything borders on permissions. Systems admins can get a little too strict with system permissions, i.e. you can start a job, but can’t stop a job. Tell them cloverleaf requires permissions to start and stop processes under the hci supperuser account. Limiting functionality means the system Admins can now be included for cloverleaf alerts including the one’s that occur in the middle of the night. Shortly some system admins will learn what 120 hours awake feels like.
Everyone has been told they need a tcl/tk class for years. Everyone believes that it will cost them thousands. The secret tcl/tk is free, in google type “Tcl Pro”, click on the first link, look for “Free Keys” on the page, install the software and use the help file. Over a lifetime it will still cost you thousands, but it will be spread out over time. Take that to your boss the next time you have a review or they try to fire you, tell them “I saved this organization millions and you don’t realize it; I’m one of your best resources because I know the business, and I have done everything intentionally for the benefit for the business. What have you done that saves this business one cent besides recommending cutting benefits.”
I’m sure everyone has heard of the first proc in tcl called hello world. With the tips tester your can do the same the commands are documented and can be found in the help file for “Tcl Pro”. Go to google type “Tcl Pro” click on the first link; on the page that follows click on “Free Keys”. Get a lifetime license, install it on your workstation, use the help file to get the information you need. I could just give you the answer, and charge everyone thousands for a tcl class, but then again I’m only one person and a limited resource. The best thing would be to tell you how you can find solutions within tcl itself. Good luck and happy tcl’ing.
p.s.: “Half the answer is looking into the info command”
The internet during peak moments of the day has different requirements, according to the “lowest cost route” rule that is used for the internet your message packet can either be more or less time according to how many users are online. i.e. Its 12:01pm here and in England it is 6:01pm, usually people should be eating, but then again they could be logging into Facebook and so your message packet which had a travel route to Germany from New York, has a travel itinerary from Florida, to California, to Hawii, to Russia, to China, to India, and finally Germany. The evidence will become clear if you ping the external host, from inside your network, and from outside your network. And remember that even conventions with those snazy display screens, are usually hocked up to the office somewhere in Patagonia.
:::;;;|||
Your VPN router should have a port routing table, make sure that messages coming from the host ip/port are pointing to your cloverleaf server ip/port address. Port number mismatches usually do not work and your communication on the VPN should be bi-directional. Yup some lan guys think that sending data does not require an ack or (confirmation), and remember the recovery_33 tcl procs and the generic ack proc on this site.
Denial can keep a person awake at night.
When was the last time your ran a hardware diagnostic on the NIC. There are several factors that can be happening, finding the right solution is not something that is straight forward. So here is some ideas which you might want to try in order.
1. Have the network person check the configuration of the NIC compared to the communication rate of the switch or router, yup your network folks might have updated and or upgraded a router and created and off balance condition on the network called collisions.
2. Check the bandwidth of your NIC and the bandwidth of your backup server, and make sure the settings are synchronized. If the backup server is a 1000mb connection then your server should be the same. If not purchase a new NIC and use the new NIC for backups only.
3. Have the network people check peak bandwidth utilization and optimize and dedicate more resources during high availability. Some people have switched over to fiber optics and some have not, but then all routers do have a setting which is beyond the default settings from the box which is a yes or no question for the router.
4. Do a physical segment test, it could be an early indication of network failure. Consider talking to facility engineering to see if they had any repairs, renovations, or problems in the suspicious areas. In one place I saw a broken toilet bring down a network two years later, sounds ironic but true.
5. Check the backup batteries on the router equipment. Some batteries have to constantly talk to minitoring equipment, if not they cause an electrical surge or spike and sometimes a brownout. Film the hospital hallways during the incident, make sure to set the camera date and time, set your focal point to include at least 3 to 4 panels (A bulb is not a panel, one panel is several bulbs), hit the record button, tell the nurse or tech person to watch the camera and walk away. Route the alert to your beeper or phone, wait for the beep and stop the recording on the camera after you recorded the text of the beep. Go home, rewind the tape, forward to the end, and do a slow motion of the last 10 to twenty seconds of the tape. If the camera was pointed at your flourescent lights you will catch a slight dimming of the light on the film. You might have to do this serveral times to prove your point.
6. Talk to your Radiology department and check the time of last usage for MRI, X-Rays, Cat Scan, and Pet Scans. All hospitals have special colored plugs for power circuts and consumption requirements. A simple thing as radio or lamp in the wrong plug can cause a problem especially when powering down an MRI. You probably heard of cell phones bringing down planes, I have seen a clock radio give a normal person a brain tumor.
The problem with the Fin_Wait condition can be solved with an OS patch, which I know still exists for Unix, AIX, Windoze.
The second problem regarding the lab field is really simple, if your not using the field in cloverleaf for a calculation, in which case 99.999% of the time your not, change the field in your variant definition and up the size by at least 1 or 2 characters, since your variant definition probably is concating the lab result since the number is greater. Or use a TCL proc on the field in question to be a shorter value i.e. 1.0000000 can still be represented as 1.00, but check with your hospital lab people before doing any form of rounding or truncation as all numeric places in lab results do have meaning.
Had the problem a decade ago, the problems stems from the DNS auto cycle routine, UNIX is more timely than Windows. We tied the UNIX server to a Windoze server and so the problem began when we cleaned up our host file. Luckily we could recover quickly since we only uncommented the entries and then rebooted the server. Also make sure your loopback entry reflects your server ip i.e. you ping 127.0.0.1 you should get your server ip ???.???.???.??? not 127.0.0.1. for some reason those OS patches sometimes fix or break the problem more and server monitoring software can cause a real headach along with tweaking the kernel parameters and a system reboot.
-
AuthorReplies
