In addition to the KCS outbox, the KCS Journals can help you to identify sending or reception errors: Do they mainly have problems for large documents (check the file size and the page counter)?.Are the problems related to a specific (ISDN) line or group of lines (check the used Channels)?.Are the problems related to specific counter parties (senders or recipients), for example – do you face a higher error rate for send orders addressed to countries in the Far East?.Which error rate (amount of errors compared to the total number of send orders) do you have for each error code?.Which types of errors are reported (XT, XQ, XO, XY, or others)?.Do they have transmission errors or reception errors or both?.Export the outbox to CSV format (using menu option “Folder – Export fields”) and import it into Excel to have better Filter possibilities: Check especially the columns “Error”, “Response”, “Reception Error”, “To:”, “Local address”, “Channel number” and “Pages”.Īfter this step you should be able to answer the following questions: Apply filter settings to also include the Send attempts. Journals should be configured to write at least 3 line journal entries (Configuration line 38 of the FAX channels set to ‘0A 03’), they are located in the +MAIL5V folder (KCS System folder) and are typically named as follows:ĪJyymmdd: outbound journal for one specific day, e.g. Step 5: Setup proper Traces for the KCS TCOSS Server AI210824 is the inbound journal of 24th August, 2021 AJ210917 is the outbound journal of 17th Sept, 2021ĪIyymmdd: inbound journals for one specific day, e.g. If the trace levels are set too high, it is very likely that the traces are already overwritten before the customer even realizes that there’s a problem or before you have the possibility to check the available trace information.Setting up proper traces can be quite difficult: On the other hand, if the trace levels are too low, you do not have enough information to find out the reason for the problems.binary traces for all channels of a primary rate line might also cause performance issues, which means that binary traces might drop trace information in order to not cause timing problems with the FAX protocol. In this trx, messages are routed depending on three fields within a message: the account number, requesting and performing department.Good values (if they fit into the available disk space) are: When setting up traces, check the available disk space and increase the number and the size of Trace Files depending on the available disk space using registry values listed below. Note that this uses TCL and mimics the engine! This is an example of how I have tested the trx code we use. I like Ultra-Edit enough that I bought my own copy for my home computer. I originally got Ultra-Edit so new team members did not have to learn something like vi right away and could edit UNIX files from their comfy MS Windows world. I have found the FTP/edit feature to be nice becuase you can edit file(s) on different platforms across the world as if they were integrated on your local PC. I have found if it is configured to save the file in the same format of the original file then most problems are avoided. Ultra-Edit is smart enough to get you in the sort of trouble we’ve been talking about but you can stay out of trouble if you understand the various conversion from UNIX, DOS, & MAC. Ultra-Edit has a free trial period which can be made permanent buy purchasing a license key. The editor I’ve been using (Ultra-Edit) came from this type of clovertech post many years ago. You guys have me curious to take a look at the PSPad editor. Thank you in advance – any help would be GREATLY appreciated! My test file is attached. The file looks to be formatted well still. I used hcihd on my test file and there is a “0a” at the end of each segment as I believe there should. Now I know that there are some issues with line breaks between the UNIX and Windows world. I opened it up in the IDE’s script editor (thinking that this would be a perfectly acceptable way to edit a plain text file) and changed just one character in PID-3.4 (changed it from “SFHG” to “SFGA”) and when I try to test it I’m now getting this output:Ġ(0).MSH(0) : >|^~&|RAD|SFHG||SFHG|20070502105100.0000-0400||ORU^R01|RMS|P|2.3||PID|1|05|00” at the end of my MSH and it is not correctly parsing the PID segment or the OBR and OBX segments that appear later in the file. I had a properly formatted and working test file. I’m trying to test an xlate and i’ve been trying to edit my test file to see setup a proper test case and then run it through my xlate using the testing tool. Alright, my frustration has peaked and I’ve decided it best to throw in the towel and ask for some advice on this one.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |