@ken-seachrist
Forum Replies Created
-
AuthorReplies
-
Elisha,
Thank you for the great info! I agree that it will mostly depend on the downstream system, but since we generally use the doctor number as the key, we may be able to get away with using these in the name field.
I am going to experiment with the control characters and see how it looks coming out of Cloverleaf. Thanks again…and …..Oy! Oy! Oy! 😀
One of the members of our team has parsed the NetConfig so we can see much of the thread info on the web as we need. we are able to stop, start, view the documentation, set monitoring parameters (such as only send a message if the lab gets over 100 behind between 10PM and 6 AM). We also created Word documents that our Ops department maintains. They create PDFs from those, and then we create a link on our portal to those PDF documents. That way there is only one set of documentation to maintain.
Our goal, on the integration team, was to keep the off hour calls to the on call person to a minimum by allowing the operations staff the ability to handle most of it on their own by using the documentation.
Dennis, what we have are several systems that can generate orders. Each of these orders goes to other systems as well, that ALSO have order numbers that THEY assign. So by the time we get to the 4th system, we now have 4 order numbers and only 2 fields to keep them. If System A wants to cancel an order in System D, System A needs to know what System D’s order number is. It could be that MULTIPLE systems need to be notified of this cancel. So now I need to have 3 or 4 order number available and only 2 fields to store them where they are useable. Hope this clears it up a bit. We wrote our own monitor for the operators. It has a file it reads and we have set thresholds on it to determine when the operators should be notified that there is a problem. We have a GUI type view on a web portal part that shows nothing if all is okay, yellow if it is a warning state, and red if there is a problem, meaning that something has exceeeded the set threshold. We tried using the netmonitor.exe, but it just didn’t work because of all of the threads and having to move from site to site to check everything out. It was easier to have them notified by exception. Thank you all for your help! That got it working! I never thought that I would be glad to see 25 OBX segments in a message! Thanks again! I tried to get it copied from the Hex editor, but that didn’t work. I also couldn’t get it into Notepad. What I can tell you though is that there are double CR at the end of each message. I have been doing some research and it may be coming from the sending application. Thanks for your help though. I tried that method using both octal and hex and neither worked. Is there something that would prevent that change since the characters are at the very end of the message? I would think there would be a simple way in TCL to go to the very end of a message, remove 1 character, and replace it with another character. we are looking to do the same thing, except that we are kind of being “forced” into 5.4 because our Unix group wants to upgrade the AIX to 5.3, which would require us to move to 5.4. I haven’t heard of any issues, but then, I am not sure how many people are using it right now! What are the differences between the outbound directory on the fileset tab and the inbound on the FTP tab? Will a fileset FTP protocol accept transactions from another thread, or does it HAVE to read from a inbound file? I don’t believe you need to buy those scripts. They were provided by QDXi, but they don’t support them. You are pretty much on your own with these, other than users who currently are using them. we run it in a Cron job each night, but you can adapt to whatever configuration you want. The code is pretty straight forward, but I would be glad to provide whatever help I can. I will get them to you. Please e-mail me where to send them. That is what I thought, but the OBR IS optional in the outbound variant. I even went so far as to add the OBR to the inbound variant as optional, but I still have the same message. What was most confusing was that before I put the OBR in the MDM (inbound) variant, the message was telling me that the OBR can’t be found in the MDM, even though there was no OBR in the inbound message! We took a script that Charlie Bursell provided and modified it to our needs. It has been working fine. Each night it takes the .msg and .idx old files and copies them to an archive directory using the date as an extension so we can identify them later. We are currently only keeping 2 weeks worth, due to storage limitations. If you think this might be something you can use, I would be glad to send it to you. Are you using the failover scripts that QDXi provides? They have shutdown and startup scripts with that as well. I am a Sr. EDI/Integrations Analyst Yes, it would! I would like to set up an alert that will stop and start a thread if there has been no activity on it for a period of time. -
AuthorReplies
