{"type": "object", "properties": {"RUN_DATETIME": {"type": "string", "examples": ["2026/01/20 00:05:00"], "format": "date-time", "description": "Date processing of the run begins. Generated from the solution file CASEID."}, "RUN_NO": {"type": "integer", "maximum": 32767, "minimum": -32768, "description": "Unique run id. Generated from the solution file CASEID."}, "CASESETID": {"type": "integer", "maximum": 32767, "minimum": -32768, "description": "Unique id to link a set of cases run from the same inputs"}, "LASTCHANGED": {"type": "string", "examples": ["2026/01/20 00:05:00"], "format": "date-time", "description": "Date the solution was loaded"}, "RUNTYPEID": {"type": "integer", "maximum": 127, "minimum": -128, "description": "Unique id for type of run, being either"}}, "required": ["RUN_DATETIME", "RUN_NO"], "description": "MTPASA_CASE_SET is obsolete from 2005 End of Year Release. The RUNTYPE added to the primary key of the detail tables for MTPASA allows for the different types of runs for each case.\nMTPASA_CASE_SET allows a MT PASA scenario to be linked across runs.\nSource\n\nUpdate weekly."}