MALAYSIA - Computer Glitch Temporarily Halts Trading

greenspun.com : LUSENET : Grassroots Information Coordination Center (GICC) : One Thread

[Fair Use: For Educational and Research Purposes Only]

STOCKS - KL SHARES END LOWER - JUNE 26, 2000

Story Filed: Monday, June 26, 2000 6:20 AM EST

KUALA LUMPUR, Jun 26, 2000 (AsiaPulse via COMTEX) -- Share prices on the Kuala Lumpur Stock Exchange ended lower across the board in a shorter trading session today.

The exchange resumed trading only in the afternoon after a computer glitch temporarily halted trading.

Interest was thin as investors' interest was interrupted by the KLSE's computer system failure, dealers said.

They added that concerns over the impending release of Central Limit Order Book (CLOB) shares on July 3 also affected sentiment.

At the close, the closely-watched Composite Index (CI) stayed slightly above the 800 support level when it settled at 803.87, down 8.38 points from 812.25 on last Friday. The KLCI had dipped below the 800-mark several times today.

Dealers said the KLCI was supported by late institutionAL buying on selected key-index linked counters.

The Emas Index dropped 1.99 points to 200.54 while the Second Board Index shed 1.99 points to 206.36.

The Finance Index fell 89.23 points to 6,528.97 and the Industrial Index eased 16.52 points to 1,415.11.

Decliners overwhelmed advancers 424 to 142 while 135 counters were unchanged, 287 counters were untraded.

Total volume traded declined to 65.772 million shares worth RM299.622 million against 93.729 million shares valued at RM476.564 million on Friday

http://library.northernlight.com/FA20000626810000190.html?cb=200&dx=2006&sc=0#doc

-- (Dee360Degree@aol.com), June 26, 2000

Answers

KLSE officials declined to disclose the
precise nature of the problem, the second
in less than a week. But KLSE sources told
Reuters that that glitch was caused by
malfunctioning computer disk, a problem
that caused last week's outage.

AltaVista Live

-- spider (spider0@usa.net), June 26, 2000.


Moderation questions? read the FAQ