Balancing Zone Name duplicationįixed a bug where ENOM would allow a balance name to be duplicated when editing. Fixes Sort Order for Messagesįixed a bug where ENOM was not correctly sorting messages by creation time with the Only Latest option selected. ENOM: 7.09.0 New Features Support for DVGW package 17 format messagesĮNOM now supports DVGW specification messages: ALOCAT 5.10 (TDDA,TDPA,TPA and TDA), CHACAP 4.6 (CHACAP and CHACAPR), IMBNOT 5.7, NOMINT 4.6 (CDT) and NOMRES 4.7 (HCN and HDT) NCG Control Energy custom REQEST and REQRESĪdded support for Netconnect’s implementation of REQEST and REQRES (BDR and SDR) as used only for the control energy process. Generating outgoing messages could be slow for SQL Server databases. Performance issue for outgoing messagesįixed a performance issue in the ENOM service. An error could occur for certain SQL Server language settings. Language settings error for SQL Server database upgradesįixed a bug upgrading SQL Server databases from ENOM v7.06 or earlier.
#Coderunner column 80 windows#
Regional settings error on Balancing screenįixed a bug where an error message could be displayed on the Balancing screen for certain Windows regional settings. This fix allows 16G to be interpreted correctly as “Confirmed” in messages of this format from the NetConnect recipient.
#Coderunner column 80 code#
NCGVHP are changing their use of this status code in NOMRES messages from version 4.7 to bring it inline with its use elswhere. ENOM: 7.09.3 Fixes Decode a status of 16G correctly in messages from NetConnectįor historical reasons 16G was being decoded differently in messages received from the recipient in ENOM configured with the Edigas code NCGVHP to its use by other players. ENOM: 7.10.0 New Features Support DVGW format ALOCAT 5.11 (TDDA,TDPA,TPA and TDA)ĮNOM now supports the latest version of the ALOCAT message from the DVGW standard as released in message package 18. For SQL Server, ENOM no longer requires the SQL Server Native Client.
#Coderunner column 80 software#
For Oracle, ENOM no longer requires Oracle client software to be installed.
Legacy data access components have been removed from both the ENOM Client and Service. ENOM: 7.13.2 New Features Support for v5.1 messaging with TAPĮNOM now supports sending v5.1 NOMINT messages and receiving v5.1 ACCSIT messages in the formats specified by Trans Adriatic Pipeline (TAP). Fixes Error stopping the ENOM Serviceįixed a bug that occasionally prevented the ENOM Service from being stopped. ENOM: 7.15.0 New Features Automatic acknowledgement of messages from Trading Hub Europe (THE)ĮNOM now responds to any message from THE with a CONTRL message (excluding CONTRL messages received from THE). The ENOM application files and installers are now digitally signed. TRANOT messages from THE will be responded to with CONTRL messages (if these are not disabled - see above). TRANOT messages can be imported into ENOM. Importing TRANOT (Transfer Notice) messages This is useful if CONTRL messages are already being sent by another system.
It is possible to disable responding to messages from THE with CONTRL messages. ENOM: 7.17.0 Support MARSIT messages as used by EnerginetĮNOM now decodes MARSIT (Market Situation) messages of types 95G (TSO’s Daily Provisional Allocation Report), 96G (TSO’s Daily Definitive Allocation Report), 16G (TSO’s Daily Reconciliation Report) and 14G (TSO’s Daily Imbalance Notification Report) as used by Energinet ENOM: 7.16.0 Configurable acknowledgement of messages from Trading Hub Europe (THE) Fixes Support for UTC offsets in ENOM input XMLĮNOM now correctly uses the UTC offset in the created_dts attribute of ENOM XML if it is present. ENOM: 7.18.0 New Features Support PSV NOMINTĮNOM now encodes version 5.1 NOMINTs as required by Snam to nominate Punto di Scambio Virtuale (Virtual Trading Point - PSV).
0 kommentar(er)
