From Newsgroup: comp.os.vms

Hi Arne
I am impressed... :_) where did you read/see this ??

On 2025-12-18, Arne Vajh|+j <arne@vajhoej.dk> wrote:

On 11/11/2025 10:50 AM, Arne Vajh|+j wrote:

On 11/3/2025 8:31 AM, Simon Clubley wrote:

What are they moving to, and how are they satisfying the extremely high
constraints both on software and hardware availability, failure
detection,
and recovery that z/OS and its underlying hardware provides ?

z/OS has a unique set of capabilities when it comes to the absolutely
critical this _MUST_ continue working or the country/company dies area.

Note that even though z/OS and mainframes generally have a
good track recording regarding availability, then it is not
a magic solution - they can also have problems.

Banks having mainframe problems are rare but far from
unheard of.

And speaking of.

A lot of banking services were down Monday in Denmark.

Because a bank mainframe was down for 5 hours.

Both the company and the country survived. :-)

As often is the case the root cause was simple and
stupid. A capacity management application took away
the resources needed to process transactions.

Arne

--
kind regards/mvh

Niels S. Eliasen

Eliasen Consult
Oregaardsvaengevej 1
DK-4720 Pr|ast|+
Tel/Cell: +45 21779590
mailto:niels@eliasen.co
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.os.vms

On 12/19/2025 6:16 AM, Niels S. Eliasen wrote:

On 2025-12-18, Arne Vajh|+j <arne@vajhoej.dk> wrote:

On 11/11/2025 10:50 AM, Arne Vajh|+j wrote:

On 11/3/2025 8:31 AM, Simon Clubley wrote:

What are they moving to, and how are they satisfying the extremely high >>>> constraints both on software and hardware availability, failure
detection,
and recovery that z/OS and its underlying hardware provides ?

z/OS has a unique set of capabilities when it comes to the absolutely
critical this _MUST_ continue working or the country/company dies area. >>>

Note that even though z/OS and mainframes generally have a
good track recording regarding availability, then it is not
a magic solution - they can also have problems.

Banks having mainframe problems are rare but far from
unheard of.

And speaking of.

A lot of banking services were down Monday in Denmark.

Because a bank mainframe was down for 5 hours.

Both the company and the country survived. :-)

As often is the case the root cause was simple and
stupid. A capacity management application took away
the resources needed to process transactions.

I am impressed... :_) where did you read/see this ??

I saw the story on LinkedIn.

But the company has been very honest about it.

https://www.jndata.dk/driftsforstyrrelser/

<quote>
JN Data har natten igennem arbejdet p|N at finde kerne|Nrsagen til driftsudfaldet p|N vores Mainframe. De f|+rste unders|+gelser tyder p|N, at
en forkert kommando i JN Datas kapacitetsstyringsv|arkt|+j var
kerne|Nrsagen til driftsudfaldet. Den forkerte kommando bet|+d, at der
blev tildelt for lidt kapacitet til at afvikle kundernes transaktioner.
Som konsekvens deraf blev services som kreditkort samt net- og mobilbank utilg|angelige for JN Datas kunder Jyske Bank, Bankdata, BEC og Nykredit.
Vi arbejder nu videre med den bagvedliggende |Nrsag til dette for at
sikre, at en lignende fejl ikke kan opst|N fremadrettet.
</quote>

And for those that does not read Danish:

<quote>
JN Data has been working through the night to find the root cause of
the outage on our Mainframe. Initial investigations indicate that an
incorrect command in JN Data's capacity management tool was the root
cause of the outage. The incorrect command meant that too little
capacity was allocated to process customers' transactions. As a result, services such as credit cards and online and mobile banking became
unavailable for JN Data's customers Jyske Bank, Bankdata, BEC and
Nykredit. We are now working on the underlying cause of this to ensure
that a similar error cannot occur in the future.
</quote>

I think it has been in CW as well.

Arne

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.os.vms

On 12/19/2025 8:07 AM, Arne Vajh|+j wrote:

And for those that does not read Danish:

<quote>
JN Data has been working through the night to find the root cause of
the outage on our Mainframe. Initial investigations indicate that an incorrect command in JN Data's capacity management tool was the root
cause of the outage. The incorrect command meant that too little
capacity was allocated to process customers' transactions. As a result, services such as credit cards and online and mobile banking became unavailable for JN Data's customers Jyske Bank, Bankdata, BEC and
Nykredit. We are now working on the underlying cause of this to ensure
that a similar error cannot occur in the future.
</quote>

Which is not very technical, but if I translate to VMS in
a "creative" way:

<humor>

mod produser /cpu=00:00:01 /wsmax=10 /wsext=20 /pgflq=100

nice - look at all that free CPU and memory

hmm - why are all the phones rinning?
</humor>

:-)

Arne


--- Synchronet 3.21a-Linux NewsLink 1.2