Re: I would love to know what went wrong at NAB

2010-12-01 Thread Shmuel Metz (Seymour J.)
In , on 11/30/2010 at 09:57 PM, Mike Schwab said: >Here is an idea to bounce around. z/OS Unix System Services does a >lot of work converting ASCII to EBCDIC and back. z/Linux works all >in ASCII. I doubt it. >Could we do some sort of Unicode translation? We already do. >Have GPR2 point

Re: I would love to know what went wrong at NAB

2010-12-01 Thread Chris Craddock
On Wed, Dec 1, 2010 at 2:11 AM, Ron Hawkins wrote: > If I remember rightly it was a bug in IMS 2.2 or 2.3. If I remember > correctly NAB (where I worked at the time) had found the bug in stress and > regression testing (TPNS for those that remember it) and were waiting for > the fix that hit Westp

Re: I would love to know what went wrong at NAB

2010-12-01 Thread Tony Harminc
On 30 November 2010 22:57, Mike Schwab wrote: > Here is an idea to bounce around.  z/OS Unix System Services does a > lot of work converting ASCII to EBCDIC and back. I'm puzzled by this. What is all this conversion work that takes to much time and effort? To the extent that character coding is

Re: I would love to know what went wrong at NAB

2010-12-01 Thread Steve Comstock
On 11/30/2010 10:34 PM, Jim Phoenix wrote: Mike Schwab wrote: On Tue, Nov 30, 2010 at 7:01 PM, Wayne Bickerdike wrote: My same source related the tale of a person in same bank who received an EBCDIC file, opened it in Windows and saved it back as ASCII. The file was duly transferred for proce

Re: I would love to know what went wrong at NAB

2010-12-01 Thread Ron Hawkins
m: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of > Stephen Mednick > Sent: Wednesday, December 01, 2010 12:19 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: [IBM-MAIN] I would love to know what went wrong at NAB > > Nostalgia, don't you just love it. > &

Re: I would love to know what went wrong at NAB

2010-12-01 Thread Stephen Mednick
Sent: Wednesday, 1 December 2010 7:12 PM To: IBM-MAIN@bama.ua.edu Subject: Re: I would love to know what went wrong at NAB Chris, If I remember rightly it was a bug in IMS 2.2 or 2.3. If I remember correctly NAB (where I worked at the time) had found the bug in stress and regression testing (TPN

Re: I would love to know what went wrong at NAB

2010-12-01 Thread Ron Hawkins
2010 5:01 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: [IBM-MAIN] I would love to know what went wrong at NAB > > Some information from a close source... > > It was a plain old S0C7 during their batch process. > > All Aussie banks use Cemtex ABA format which has been around for year

Re: I would love to know what went wrong at NAB

2010-12-01 Thread Ron Hawkins
> -Original Message- > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of > Chris Craddock > Sent: Tuesday, November 30, 2010 8:56 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: [IBM-MAIN] I would love to know what went wrong at NAB > > On Tue, Nov 30,

Re: I would love to know what went wrong at NAB

2010-11-30 Thread Bruce Hewson
A comment here:- http://www.theaustralian.com.au/australian-it/human-error-triggered-nab- software-corruption/story-e6frgakx-1225962953523 "The "file" was actually software code containing instructions on how systems should operate in the batch processing cycle." would lead me to think someone

Re: I would love to know what went wrong at NAB

2010-11-30 Thread Jim Phoenix
Mike Schwab wrote: On Tue, Nov 30, 2010 at 7:01 PM, Wayne Bickerdike wrote: My same source related the tale of a person in same bank who received an EBCDIC file, opened it in Windows and saved it back as ASCII. The file was duly transferred for processing on the mainframe. Most of the packe

Re: I would love to know what went wrong at NAB

2010-11-30 Thread Chris Craddock
On Tue, Nov 30, 2010 at 10:39 PM, Chase, John wrote: > > -Original Message- > > From: IBM Mainframe Discussion List On Behalf Of Shane > > > > As if. > > Can't you just imagine a major Aussie Bank doing that. You were at > Bank > > of NSW when they had the IMS fiasco Steve - how much info

Re: I would love to know what went wrong at NAB

2010-11-30 Thread Chase, John
> -Original Message- > From: IBM Mainframe Discussion List On Behalf Of Shane > > As if. > Can't you just imagine a major Aussie Bank doing that. You were at Bank > of NSW when they had the IMS fiasco Steve - how much info on that got > out ? (via Bank press releases I mean :-) Yeh I

Re: I would love to know what went wrong at NAB

2010-11-30 Thread Mike Schwab
On Tue, Nov 30, 2010 at 7:01 PM, Wayne Bickerdike wrote: > My same source related the tale of a person in same bank who received > an EBCDIC file, opened it in Windows and saved it back as ASCII. The > file was duly transferred for processing on the mainframe. Most of the > packed data was garbag

Re: I would love to know what went wrong at NAB

2010-11-30 Thread Sam Siegel
On Tue, Nov 30, 2010 at 5:01 PM, Wayne Bickerdike wrote: > Some information from a close source... > > It was a plain old S0C7 during their batch process. > > All Aussie banks use Cemtex ABA format which has been around for years > as a transfer format between organisations. You would think that

Re: I would love to know what went wrong at NAB

2010-11-30 Thread Wayne Bickerdike
Some information from a close source... It was a plain old S0C7 during their batch process. All Aussie banks use Cemtex ABA format which has been around for years as a transfer format between organisations. You would think that there is a validate step before running the transactions against thei

Re: I would love to know what went wrong at NAB

2010-11-30 Thread Shane
As if. Can't you just imagine a major Aussie Bank doing that. You were at Bank of NSW when they had the IMS fiasco Steve - how much info on that got out ? (via Bank press releases I mean :-) Shane ... On Tue, 30 Nov 2010 18:52:08 +1100 Stephen Mednick wrote: > One wonders if a detailed explanati

Re: I would love to know what went wrong at NAB

2010-11-30 Thread Ted MacNEIL
>I'd bet that the upgrade was to the application system, not the mainframe, and >something was wrong in a new application program that corrupted the file. I wouldn't take the opposite of that bet! >I'm wondering why it took 5 days to recover. Since, upon reading the article, I see that INFOSYS

Re: I would love to know what went wrong at NAB

2010-11-30 Thread Shmuel Metz (Seymour J.)
In , on 11/30/2010 at 12:54 AM, Sheldon Davis said: >I would love to know how a corrupt system file in a parrallel sysplex >can affect a payroll system Why? That's not what the article claims. "a corrupted file on an IBM mainframe system" is quite different from "a corrupt system file". >Fro

Re: I would love to know what went wrong at NAB

2010-11-30 Thread Kelman, Tom
as City -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Stephen Mednick Sent: Tuesday, November 30, 2010 1:52 AM To: IBM-MAIN@bama.ua.edu Subject: Re: I would love to know what went wrong at NAB One wonders if a detailed explanation of wh

Re: I would love to know what went wrong at NAB

2010-11-30 Thread Steve Comstock
love to know what went wrong at NAB I would love to know how a corrupt system file in a parrallel sysplex can affect a payroll system http://www.channelregister.co.uk/2010/11/29/nab_mainframe_cockup/ -- Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-393

Re: I would love to know what went wrong at NAB

2010-11-30 Thread Andrew Rowley
On 30/11/2010 6:12 PM, Mike Schwab wrote: That was not payroll. That was a bank. They screwed up all transactions for a week after a conversion and fallback. I would be really curious as to how the database was functioning without crashing while processing all those bad transactions. Almost

Re: I would love to know what went wrong at NAB

2010-11-29 Thread Stephen Mednick
- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Sheldon Davis Sent: Tuesday, 30 November 2010 5:54 PM To: IBM-MAIN@bama.ua.edu Subject: I would love to know what went wrong at NAB I would love to know how a corrupt system file in a parrallel sysplex can affect a

Re: I would love to know what went wrong at NAB

2010-11-29 Thread Mike Schwab
On Tue, Nov 30, 2010 at 12:54 AM, Sheldon Davis wrote: > I would love to know how a corrupt system file in a parrallel sysplex can > affect > a payroll system > > http://www.channelregister.co.uk/2010/11/29/nab_mainframe_cockup/ That was not payroll. That was a bank. They screwed up all transa

I would love to know what went wrong at NAB

2010-11-29 Thread Sheldon Davis
I would love to know how a corrupt system file in a parrallel sysplex can affect a payroll system http://www.channelregister.co.uk/2010/11/29/nab_mainframe_cockup/ -- For IBM-MAIN subscribe / signoff / archive access instructio