{"component": "clause", "props": {"groups": [{"samples": [{"hash": "ljumnooGpnC", "uri": "/contracts/ljumnooGpnC#error-codes", "label": "Voluntary Data Sharing Agreement", "score": 35.1877761679, "published": true}, {"hash": "lyrryJ3PVpZ", "uri": "/contracts/lyrryJ3PVpZ#error-codes", "label": "Voluntary Data Sharing Agreement", "score": 35.1123311282, "published": true}, {"hash": "3YRlbISupdt", "uri": "/contracts/3YRlbISupdt#error-codes", "label": "Voluntary Data Sharing Agreement", "score": 34.9660493939, "published": true}], "snippet_links": [{"key": "an-introduction", "type": "clause", "offset": [15, 30]}, {"key": "subject-of", "type": "clause", "offset": [38, 48]}, {"key": "response-files", "type": "clause", "offset": [98, 112]}, {"key": "section-iv", "type": "definition", "offset": [202, 212]}, {"key": "complete-disposition", "type": "clause", "offset": [218, 238]}, {"key": "error-reporting", "type": "clause", "offset": [264, 279]}, {"key": "required-fields", "type": "clause", "offset": [309, 324]}, {"key": "input-file", "type": "clause", "offset": [332, 342]}, {"key": "covered-individual", "type": "definition", "offset": [383, 401]}, {"key": "date-of-birth", "type": "clause", "offset": [418, 431]}, {"key": "transaction-type", "type": "definition", "offset": [479, 495]}, {"key": "coverage-type", "type": "definition", "offset": [497, 510]}, {"key": "effective-date", "type": "definition", "offset": [530, 544]}, {"key": "termination-date", "type": "definition", "offset": [550, 566]}, {"key": "for-non", "type": "clause", "offset": [568, 575]}, {"key": "to-apply", "type": "clause", "offset": [623, 631]}, {"key": "the-response", "type": "clause", "offset": [691, 703]}, {"key": "drug-records", "type": "clause", "offset": [757, 769]}], "snippet": "\u200c Following is an introduction to the subject of Error Code Reporting in both the MSP and Non-MSP Response Files. A comprehensive listing of all error codes that a partner may encounter can be found in Section IV, The Complete Disposition and Edit Code List. Most error reporting can be avoided by completing required fields on the Input File. Required fields include the Surname of Covered Individual, First Initial, Date of Birth, Sex code, a DCN assigned by the VDSA partner, Transaction Type, Coverage Type, Individual\u2019s SSN, Effective Date, and Termination Date. For Non-MSP drug record processing, the BCRC will need to apply error checks and supply the results to the VDSA partner in the response file. The SP errors that will specifically apply for drug records are as follows: SP 12 Invalid Medicare ID (HICN or MBI) or SSN. At least one of the fields must contain alpha or numeric characters. Both fields cannot be blank or contain spaces.", "size": 8, "hash": "e6c92d40821db4e032744e1bfeef8e5b", "id": 1}, {"samples": [{"hash": "fwmX4ySk4LZ", "uri": "/contracts/fwmX4ySk4LZ#error-codes", "label": "Data Sharing Agreement", "score": 26.1704312115, "published": true}, {"hash": "g2tKyJ50WOX", "uri": "/contracts/g2tKyJ50WOX#error-codes", "label": "Data Sharing Agreement", "score": 26.1582162221, "published": true}, {"hash": "k0sqMLy6Tfv", "uri": "/contracts/k0sqMLy6Tfv#error-codes", "label": "Data Sharing Agreement", "score": 25.501026694, "published": true}], "snippet_links": [{"key": "input-file", "type": "clause", "offset": [38, 48]}, {"key": "information-on", "type": "clause", "offset": [253, 267]}], "snippet": "\u200c The edit checks applied to the SPAP input file will generate the following error codes, as necessary. This is a comprehensive listing of all the error codes that a partner may receive. The SPAP is expected to correct any errors, or update any missing information on its enrollees, and re-transmit the revised data on the following month\u2019s file. SP 12 Invalid Medicare ID (HICN or MBI) or SSN. At least one of the fields must contain alpha or numeric characters. Both fields cannot be blank or contain spaces.", "size": 4, "hash": "ed6a3e161ffbfd834499c2b0c2f076ac", "id": 2}, {"samples": [{"hash": "a4dKLsRMWLr", "uri": "/contracts/a4dKLsRMWLr#error-codes", "label": "Single User Software Tools License Agreement", "score": 21.0, "published": true}, {"hash": "8ttuoI8NV5S", "uri": "/contracts/8ttuoI8NV5S#error-codes", "label": "Single User Software Tools License Agreement", "score": 21.0, "published": true}, {"hash": "6ZabmNCoYII", "uri": "/contracts/6ZabmNCoYII#error-codes", "label": "Single User Software Tools License Agreement", "score": 21.0, "published": true}], "snippet_links": [{"key": "error-messages", "type": "clause", "offset": [4, 18]}, {"key": "the-problem", "type": "clause", "offset": [161, 172]}, {"key": "error-code", "type": "definition", "offset": [188, 198]}], "snippet": "The error messages generated by the compiler are intended to be complete without ad- ditional explanation. Since the compiler produces a detailed description of the problem rather than an error code, these error messages have not been reproduced in this manu- al.", "size": 3, "hash": "f3b8bcf0ac31b64ec3020bd22ada4200", "id": 3}, {"samples": [{"hash": "gjWrQkB19BD", "uri": "/contracts/gjWrQkB19BD#error-codes", "label": "Avaya Software Development Kit License Agreement", "score": 27.8790047289, "published": true}, {"hash": "j4mo000AGUG", "uri": "/contracts/j4mo000AGUG#error-codes", "label": "Avaya Software Development Kit License Agreement", "score": 24.8124572211, "published": true}], "snippet_links": [{"key": "error-code", "type": "definition", "offset": [0, 10]}, {"key": "error-message", "type": "clause", "offset": [11, 24]}], "snippet": "Error code Error message Description Response Syntax Return Value Parameters Description AGTGetErrorInfo Command Syntax Parameters", "size": 2, "hash": "02215362d456b74032ac555e543467e6", "id": 4}, {"samples": [{"hash": "41wrRBEmzHx", "uri": "/contracts/41wrRBEmzHx#error-codes", "label": "Voluntary Data Sharing Agreement", "score": 21.0, "published": true}], "snippet_links": [{"key": "an-introduction", "type": "clause", "offset": [13, 28]}, {"key": "subject-of", "type": "clause", "offset": [36, 46]}, {"key": "response-files", "type": "clause", "offset": [96, 110]}, {"key": "section-iv", "type": "definition", "offset": [200, 210]}, {"key": "complete-disposition", "type": "clause", "offset": [216, 236]}, {"key": "error-reporting", "type": "clause", "offset": [262, 277]}, {"key": "required-fields", "type": "clause", "offset": [307, 322]}, {"key": "input-file", "type": "clause", "offset": [330, 340]}, {"key": "covered-individual", "type": "definition", "offset": [381, 399]}, {"key": "date-of-birth", "type": "clause", "offset": [416, 429]}, {"key": "transaction-type", "type": "definition", "offset": [472, 488]}, {"key": "effective-date", "type": "definition", "offset": [523, 537]}, {"key": "termination-date", "type": "definition", "offset": [539, 555]}, {"key": "patient-relationship", "type": "clause", "offset": [557, 577]}, {"key": "employer-size", "type": "definition", "offset": [631, 644]}, {"key": "plan-number", "type": "definition", "offset": [659, 670]}, {"key": "policy-number", "type": "definition", "offset": [672, 685]}, {"key": "employee-coverage", "type": "clause", "offset": [687, 704]}, {"key": "employee-status", "type": "definition", "offset": [715, 730]}, {"key": "transaction-errors", "type": "clause", "offset": [819, 837]}, {"key": "disposition-codes", "type": "clause", "offset": [843, 860]}, {"key": "drug-coverage", "type": "clause", "offset": [887, 900]}, {"key": "type-a", "type": "clause", "offset": [956, 962]}, {"key": "the-combination", "type": "clause", "offset": [1015, 1030]}, {"key": "coverage-types", "type": "clause", "offset": [1031, 1045]}, {"key": "required-by", "type": "definition", "offset": [1113, 1124]}, {"key": "to-apply", "type": "clause", "offset": [1274, 1282]}, {"key": "the-response", "type": "clause", "offset": [1350, 1362]}, {"key": "drug-records", "type": "clause", "offset": [1416, 1428]}], "snippet": "Following is an introduction to the subject of Error Code Reporting in both the MSP and Non-MSP Response Files. A comprehensive listing of all error codes that a partner may encounter can be found in Section IV, The Complete Disposition and Edit Code List. Most error reporting can be avoided by completing required fields on the Input File. Required fields include the Surname of Covered Individual, First Initial, Date of Birth, Sex, a DCN assigned by the VDSA partner, Transaction Type, Coverage Type, individual\u2019s SSN, Effective Date, Termination Date, Patient Relationship, Subscribers\u2019 First and Last name, Subscriber\u2019s SSN, Employer Size, Group Health Plan Number, Policy Number, Employee Coverage Election, Employee Status, Employer TIN, and Insurer TIN. MSP processing will generate SP errors (MSP Maintenance Transaction errors) and disposition codes for records with duel MSP/Drug coverage. All of the existing CWF SP errors apply. For Coverage Type A, J, and K, the required input fields do not change. The combination Coverage Types that include Part A/B coverage also need to incorporate the fields required by CWF. These combination Coverage Types include V, W, X, Y, 4, 5, and 6. For Drug only, Subsidy, or Non-MSP drug record processing, the COBC will need to apply similar error checks and supply the results to the VDSA partner in the response file. The SP errors that will specifically apply for drug records are as follows:", "size": 2, "hash": "e4d2231105c51e905bf0352e8e1c2d88", "id": 5}, {"samples": [{"hash": "9PHTAoasDFb", "uri": "/contracts/9PHTAoasDFb#error-codes", "label": "Data Sharing Agreement", "score": 24.0357406464, "published": true}], "snippet_links": [{"key": "an-introduction", "type": "clause", "offset": [13, 28]}, {"key": "subject-of", "type": "clause", "offset": [36, 46]}, {"key": "response-files", "type": "clause", "offset": [96, 110]}, {"key": "section-iv", "type": "definition", "offset": [200, 210]}, {"key": "complete-disposition", "type": "clause", "offset": [216, 236]}, {"key": "all-d", "type": "clause", "offset": [257, 262]}, {"key": "references-to", "type": "definition", "offset": [315, 328]}, {"key": "error-reporting", "type": "clause", "offset": [349, 364]}, {"key": "required-fields", "type": "clause", "offset": [394, 409]}, {"key": "input-file", "type": "clause", "offset": [417, 427]}, {"key": "covered-individual", "type": "definition", "offset": [468, 486]}, {"key": "date-of-birth", "type": "clause", "offset": [503, 516]}, {"key": "transaction-type", "type": "definition", "offset": [563, 579]}, {"key": "coverage-type", "type": "definition", "offset": [581, 594]}, {"key": "effective-date", "type": "definition", "offset": [614, 628]}, {"key": "termination-date", "type": "definition", "offset": [634, 650]}, {"key": "for-non", "type": "clause", "offset": [652, 659]}, {"key": "to-apply", "type": "clause", "offset": [707, 715]}, {"key": "the-response", "type": "clause", "offset": [774, 786]}, {"key": "drug-records", "type": "clause", "offset": [840, 852]}], "snippet": "Following is an introduction to the subject of Error Code Reporting in both the MSP and Non-MSP Response Files. A comprehensive listing of all error codes that a partner may encounter can be found in Section IV, The Complete Disposition and Edit Code List. All D \u2013 Non-MSP Only Input filed submitters are to ignore references to MSP reporting. Most error reporting can be avoided by completing required fields on the Input File. Required fields include the Surname of Covered Individual, First Initial, Date of Birth, Sex code, a DCN assigned by the DSA partner, Transaction Type, Coverage Type, Individual\u2019s SSN, Effective Date, and Termination Date. For Non-MSP drug record processing, the COBC will need to apply error checks and supply the results to the DSA partner in the response file. The SP errors that will specifically apply for drug records are as follows:", "size": 2, "hash": "ee51652c4e757d8f477414cb061e27ac", "id": 6}, {"samples": [{"hash": "2dLuW8yrOD1", "uri": "/contracts/2dLuW8yrOD1#error-codes", "label": "License Agreement", "score": 19.0, "published": true}], "snippet_links": [{"key": "operating-system", "type": "clause", "offset": [53, 69]}, {"key": "successful-execution", "type": "definition", "offset": [73, 93]}], "snippet": "ACROCOMM feeds back the following error codes to the operating system: 0 Successful execution. 1 Instruction not executed. 2 Transmission cancelled. 3 Communications error.", "size": 1, "hash": "64cfb75832d8122e155455d9f671c4cb", "id": 7}, {"samples": [{"hash": "c945WjwZtW9", "uri": "/contracts/c945WjwZtW9#error-codes", "label": "Contract Agreement", "score": 25.4038329911, "published": true}], "snippet_links": [{"key": "number-of", "type": "clause", "offset": [245, 254]}, {"key": "contract-number", "type": "definition", "offset": [381, 396]}, {"key": "reference-source", "type": "definition", "offset": [404, 420]}], "snippet": "Reworkable error codes are: [R1] - Missed tree, [R2] - Live and/or dead limbs below pruning height, [R3] - Limbs not completely severed from stem, [R4] - Stub length or angled cut greater than 0.5 cm from branch collar, [R5] - More than allowed number of Internodal Branchlets, [R6] \u2013 Improper Prunable Tree selection. Taan Forest \u2013 2018 Spacing & Pruning Contract Page 29 of 37 \u25cf Contract Number Error! Reference source not found.DRAFT", "size": 1, "hash": "3dfa44eeca945c3d8f78e298f979966a", "id": 8}, {"samples": [{"hash": "5QwAdPVDlkq", "uri": "/contracts/5QwAdPVDlkq#error-codes", "label": "Operator's Manual", "score": 21.1006051443, "published": true}], "snippet_links": [{"key": "in-the-event-of-a", "type": "clause", "offset": [0, 17]}, {"key": "system-failure", "type": "definition", "offset": [26, 40]}, {"key": "digital-display", "type": "definition", "offset": [46, 61]}, {"key": "error-message", "type": "clause", "offset": [71, 84]}], "snippet": "In the event of a control system failure, the digital display shows an error message. The message codes are shown in the DISPLAY column below. A constant tone is heard when an er- ror code is displayed, and to silence this tone, press any button.", "size": 1, "hash": "ddbb60bef2345b4818abb7c476e4b6f2", "id": 9}, {"samples": [{"hash": "8W15VWctB9e", "uri": "/contracts/8W15VWctB9e#error-codes", "label": "Software License Agreement", "score": 35.4286645149, "published": true}], "snippet_links": [{"key": "software-support", "type": "clause", "offset": [17, 33]}, {"key": "code-number", "type": "definition", "offset": [52, 63]}, {"key": "support-staff-member", "type": "definition", "offset": [71, 91]}, {"key": "a-list", "type": "definition", "offset": [164, 170]}, {"key": "the-problem", "type": "clause", "offset": [525, 536]}, {"key": "the-installation", "type": "clause", "offset": [617, 633]}, {"key": "the-interface", "type": "clause", "offset": [909, 922]}, {"key": "data-link", "type": "definition", "offset": [982, 991]}, {"key": "communication-cables", "type": "clause", "offset": [1021, 1041]}, {"key": "error-description", "type": "clause", "offset": [1077, 1094]}, {"key": "electronic-technician", "type": "clause", "offset": [1181, 1202]}, {"key": "the-source", "type": "clause", "offset": [2047, 2057]}, {"key": "the-selected", "type": "clause", "offset": [2204, 2216]}, {"key": "operating-system", "type": "clause", "offset": [2270, 2286]}, {"key": "configuration-file", "type": "definition", "offset": [2308, 2326]}, {"key": "file-format", "type": "definition", "offset": [2698, 2709]}, {"key": "client-application", "type": "clause", "offset": [2853, 2871]}, {"key": "applies-to", "type": "clause", "offset": [2998, 3008]}, {"key": "to-establish", "type": "clause", "offset": [3164, 3176]}, {"key": "initialization-phase", "type": "clause", "offset": [3455, 3475]}, {"key": "relate-to", "type": "definition", "offset": [3623, 3632]}, {"key": "not-compatible", "type": "definition", "offset": [3710, 3724]}, {"key": "existing-data", "type": "definition", "offset": [3733, 3746]}, {"key": "not-responding", "type": "definition", "offset": [4148, 4162]}, {"key": "information-on", "type": "clause", "offset": [4292, 4306]}, {"key": "read-me", "type": "definition", "offset": [4366, 4373]}, {"key": "located-in", "type": "definition", "offset": [4379, 4389]}, {"key": "the-programs", "type": "clause", "offset": [4473, 4485]}], "snippet": "When calling for software support, report the error code number to the support staff member. This will aid in solving the communication problem. The chart below is a list of error codes and the possible solutions to those errors. --- No initialization file present. Install the Caterpillar Communication Adapter II software on the PC and reboot. --- Unable to read Cat Communication Adapter (RP1210) Initialization File. If the PC has Cat Comm Adapter II software installed, try rebooting the PC first. If this does not cure the problem, re-install the Cat Comm Adapter II software. Make sure you reboot the PC after the installation is complete. --- Unable to load CA2RP32.DLL If the PC has Cat Comm Adapter II software installed, try rebooting the PC first. If this does not cure the problem, re-install the Cat Comm Adapter II software. Make sure you reboot the PC after the installation is complete. 142* The interface hardware is not connected. Check the cables. Make sure the data link cable and serial or parallel communication cables are properly connected. Error Code Error Description Suggestion Verify the Cat Comm Adapter II \u201cPower\u201d light is on. Check that Caterpillar Electronic Technician is configured for the correct communications port. 202 A Required INI File Was Not Located. Un-install and then re-install the Cat Comm Adapter II software. Make sure you reboot the PC after the installation is complete. 204 A required INI file section was not found. Un-install and then re-install the Cat Comm Adapter II software. Make sure you reboot the PC after the installation is complete. 205 A necessary INI file key was not found. Un-install and re-install the Cat Comm Adapter II software. Make sure you reboot the PC after the installation is complete. 206 A INI file value was invalid. Un-install and then re-install the Cat Comm Adapter II software. Make sure you reboot the PC after the installation is complete. 230 Port not open Another program or device is currently using the comm port or the comm port's resources. Identify the source and remove or disable it. Or, use a parallel port instead of a serial port. Palm Pilot software commonly causes this error. 231 Invalid Comm Port The selected comm port is not set up properly in the PC\u2019s BIOS or operating system. 301 Cannot open the configuration file. Un-install and then re-install the Cat Comm Adapter II software. Make sure you reboot the PC after the installation is complete. 302 The session identifier was not found in the configuration file. Un-install and then re-install the Cat Comm Adapter II software. Make sure you reboot the PC after the installation is complete. 303 An error was found in the configuration file format. Un-install and then re-install the Cat Comm Adapter II software. Make sure you reboot the PC after the installation is complete. 308 A 16-bit client application is trying to use the Comm Adapter II, but the APISRV32.EXE file is missing or not in the default Windows directory. This only applies to Windows 98. Re-install the Comm Adapter II software. Make sure you reboot the PC after the installation is complete. 405 The PC had a problem while trying to establish the communication baud rate with the Comm Adapter II. Power cycle the Comm Adapter II and reboot the PC. If the error persists, lower the communication baud rate. 406 The PC tried to establish a connection to the Comm Adapter II, but ran into a problem during the communication initialization phase. This error code occurs during the communication initialization phase when the specific stage is not identified. Error codes 142, 405, 441, or 453 relate to specific stages in the initialization process. 441 The requested protocol is not compatible with an existing data link. Cycle the power on the Cat Comm Adapter II and ECM. If this does not correct the problem, reboot the PC, and try again. Do not launch the Comm Adapter II Toolkit while Cat ET is running. 443* The drivers software and the communiaction adapter Firmware are not compatible Install the appropriate Firmware onto the Communications Adapter II. 453* The Communicaion Adapter has been detected but is not responding The Serial.vdx file in your Windows/System folder may be corrupt. Reinstall the Serial vdx file provided with Windows. *For more information on Error Codes 142, 443, and 453, consult the Comm Adapter II Read Me file located in the Caterpillar Comm Adapter II Group Box (select Caterpillar Comm Adapter II from the Programs menu, then select Read Me from the submenu).", "size": 1, "hash": "e19c8b5d3cb9d50baab6946b26b8520e", "id": 10}], "next_curs": "ClQSTmoVc35sYXdpbnNpZGVyY29udHJhY3RzcjALEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhRlcnJvci1jb2RlcyMwMDAwMDAwYQyiAQJlbhgAIAA=", "clause": {"title": "Error Codes", "parents": [["methodological-description", "Methodological Description"], ["agreement", "AGREEMENT"], ["using-acrocomm", "Using Acrocomm"], ["acrocomm-command-line", "ACROCOMM: Command Line"], ["status-reporting", "STATUS REPORTING"]], "children": [["file-contents", "FILE CONTENTS"], ["file-naming-convention", "FILE NAMING CONVENTION"]], "size": 29, "id": "error-codes", "related": [["malicious-use-of-orphan-glue-records", "Malicious Use of Orphan Glue Records", "Malicious Use of Orphan Glue Records"], ["security-of-access-code", "Security of Access Code", "Security of Access Code"], ["malicious-code", "Malicious Code", "Malicious Code"], ["incorporation-of-software-code", "Incorporation of Software Code", "Incorporation of Software Code"], ["how-to-update-your-records", "How to Update Your Records", "How to Update Your Records"]], "related_snippets": [], "updated": "2025-07-07T16:38:45+00:00", "also_ask": [], "drafting_tip": "", "explanation": "The Error Codes clause defines the specific codes used to identify and categorize errors within a system or service. Typically, it outlines a standardized list of numeric or alphanumeric codes, each corresponding to a particular type of error, such as authentication failures, invalid input, or system outages. By establishing a clear framework for error identification, this clause ensures consistent communication between parties and facilitates efficient troubleshooting and resolution of issues."}, "json": true, "cursor": ""}}