Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

On Fri, 20 Apr 2018 07:14:20 -0700, Gerhard Adam wrote: >Applications don't get old. They either do what they're supposed to do or >they don't. It has nothing to do with age. > Remember Y2K? -- gil -- For IBM-MAIN

Re: XCF Group HSFIXC ?

Rob, Graham thank you for the information  On ‎Friday‎, ‎April‎ ‎20‎, ‎2018‎ ‎05‎:‎16‎:‎58‎ ‎AM‎ ‎EDT, Rob Scott wrote: "HSF" is the prefix for new SDSFAUX elements in the  SDSF product. "ISF" is the legacy prefix for SDSF elements. The HSFIXC group

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

Here's a somewhat interesting document: https://www.irs.gov/pub/irs-pia/imf_pia.pdf. "IMF is a batch driven application that uses VSAM files." Date of Approval: February 28, 2017 PIA ID Number: 2140 A ... Date of Approval: February 28, 2017 PIA ID

Re: DFSMSdss dump fix after binary transfer

If still on the PC, transfer in binary again. (high odds of success). If only on the mainframe, and it was transferred with translation (ASCII->EBCDIC), then download to PC with translation (EBCDIC->ASCII), then back to the mainframe in Binary. (suspect you may have some drop out errors). On

Re: IRS Assembler Java Big Plus Jobs

Clark Morris wrote: Would a non-IBM C/C++ be suitable for TPF? Clark Morris z/TPF is an ELF-based environment. You can use a z/TPF-targeted variant of GCC or the Dignus tool chain for z/TPF. I don't believe there are too many (any?) TPF 4.1 shops still around, but at that time

Re: DFSMSdss dump fix after binary transfer

Potentially, it's still just a string of bits. So, you can examine it, possibly discern a pattern or patterns, and write custom code to reconstitute it. Having a valid ADRDSSU file with similar data for comparison might help. SMOP :) > -Original Message- > From: IBM Mainframe

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

I agree with both you and Gil. But, how many programmers in the 60s, 70s, even 80s were thinking about Y2K? Sure, the really good ones were, but what about the other 80%? and, Y2K came off without a hitch...(FSVO - "hitch") I love Fridays... BobL -Original Message- From:

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

I started in 1983 and it was thought about, but a few years in and everyone said the mainframe would be gone by 2000... That mainframe was gone by the mid 1990's. On Fri, Apr 20, 2018 at 3:49 PM, Lester, Bob wrote: > >Very good point! > > -Original Message- >

OAM and Object Tape Support with an MTL

We are using a DLM for our virtual tape library and have them defined as MTLs. OAM starts without object tape support, I would like to know if this is something we should look at adding, or does it not have any impact one way or another? Here is what OAM shows at startup. 22.16.22 S0169252

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

IMO, it was often an explicit decision based on the cost of the technology of the time. Also, apparently more often the correct decision given the subsequent and apparently successful mitigation. > -Original Message- > From: IBM Mainframe Discussion List

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

That looks more like when the TOD clock overflows. > On Apr 20, 2018, at 18:17, Lester, Bob wrote: > > I, OTOH, seem to remember 2049 as the (or our?) window. Not sure these days, > I'm busy in penguin land > > BobL

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

Y2k had nothing to do with age. It had to do with what applications did or didn't do. If they had been written with 4 digit years they could have been written in 1964 and had no date issues. It wasn't like a LA instruction suddenly showed signs of age. Sent from my iPhone > On Apr 20, 2018,

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

Now for those that didn't move to a 4 digit year to resolve Y2K but instead went to a window technique, how many of your current staff know what dates were used for the window so they can again fix the problem before it occurs. -Original Message- From: IBM Mainframe Discussion List

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

That was due to lack of foresight by the programmer not due to the age of the system. This email message and any accompanying materials may contain proprietary, privileged and confidential information of CIT Group Inc. or its subsidiaries or affiliates (collectively, “CIT”), and are intended

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

Very good point! -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gerhard Adam Sent: Friday, April 20, 2018 1:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

It seems your picking a fight that doesn't exist. The IRS, has not had a problem complying with the tax code, nor in processing returns. Software was clearly changed and capable of doing what was needed. COBOL was never intended to interface directly with networking software so it was no

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

Windows programmers are blown away when I tell them that I still run a program I wrote 45+ years ago. They ask if I have to re-compile it and I tell them no, it is the same load module created way back then. Their jaws drop. Chris Blaicher Technical Architect Mainframe Development P:

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

I seem to recall that 69 was a popular choice for the window breakpoint ... Chris Hoelscher Technology Architect, Database Infrastructure Services Technology Solution Services Humana Inc. 123 East Main Street Louisville, KY 40202 Humana.com (502) 476-2538 or 407-7266 -Original Message-

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

On Fri, 20 Apr 2018 07:14:20 -0700, Gerhard Adam wrote: >Applications don't get old. They either do what they're supposed to do or >they don't. >It has nothing to do with age. That's true if they don't need to be changed. But a program that has to be changed periodically does become harder

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

I, OTOH, seem to remember 2049 as the (or our?) window. Not sure these days, I'm busy in penguin land BobL -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Chris Hoelscher Sent: Friday, April 20, 2018 2:37 PM To:

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

On Fri, 20 Apr 2018 19:25:54 +, Lester, Bob wrote: > >I agree with both you and Gil. But, how many programmers in the 60s, 70s, >even 80s were thinking about Y2K? Sure, the really good ones were, but what >about the other 80%? > >and, Y2K came off without a hitch...(FSVO - "hitch")

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

It was discussed, but the general feeling was that those systems would have been rewritten or replaced long before it became an issue. No one expected applications to be running 30-40 years after they were first implemented. Sent from my iPhone > On Apr 20, 2018, at 12:25 PM, Lester, Bob

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

In 1974, we considered it, but the cost of a byte of disk storage was enough to push the storage of each date's century toward the '90s. We fully expected the remediation would be needed but storage would be more affordable by then, which panned out. What everybody got wrong was expecting the

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

IBM designed EBCDIC to work with existing card punch equipment and 7 track tapes. ASCII had not been finalized. They included a mode switch into S360 but didn't implement it in software. On Fri, Apr 20, 2018 at 5:26 PM, Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On

Re: XCF Group HSFIXC ?

Thanks (and thanks to Patrick Falcone for the same information). I suspect that both because it’s new and because it doesn’t have a huge amount of traffic it wouldn’t bubble up in our code. Generally we see IXCLOnnn, DXRm, and DFHIR000 groups bubble up. This is probably one of those

Re: OAM and Object Tape Support with an MTL

So, are you using Optical Tape processing or not. If not, then your start up is okay. If you are, then there are configurations you need to do to use DLm with OAM. Some products like Content Manager on Demand (Report repository product) require OAM to manage the reports. Other than that, OAM

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

> On Apr 20, 2018, at 2:13 PM, Paul Gilmartin > <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > On Fri, 20 Apr 2018 07:14:20 -0700, Gerhard Adam wrote: > >> Applications don't get old. They either do what they're supposed to do or >> they don't. It has nothing to do with age. >>

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

> On Apr 20, 2018, at 3:26 PM, David L. Craig wrote: > > In 1974, we considered it, but the cost of a byte of disk storage was > enough to push the storage of each date's century toward the '90s. We > fully expected the remediation would be needed but storage would be more >

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

> On Apr 20, 2018, at 3:03 PM, Christopher Y. Blaicher > wrote: > > Windows programmers are blown away when I tell them that I still run a > program I wrote 45+ years ago. They ask if I have to re-compile it and I > tell them no, it is the same load module created way

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

Sorry, but I see this as the extension of the nonsense LILCO pulled during a hurricane or a nor'easter (I can't recall which) where they blamed the lousy pole maintenance on the MF system's they were running. It was a bunch of nonsense. This is too. Doug Fuerst d...@bkassociates.net --

Re: IRS Assembler Java Big Plus Jobs

Clark Morris wrote: >Does TPF support Ziip/Zaap processors? Does PL1 support TPF? >Would metal C or a non-IBM C/C++ be suitable for TPF? I see Dana Mitchell already replied about ALCS. In short, anything you can do on/with z/OS you should be able to do on/with ALCS. That includes whatever

Re: XCF Group HSFIXC ?

"HSF" is the prefix for new SDSFAUX elements in the SDSF product. "ISF" is the legacy prefix for SDSF elements. The HSFIXC group provides sysplex-wide services on behalf of the SDSFAUX started task. Rob Scott -Original Message- From: IBM Mainframe Discussion List

Re: SYSPLEX Hung

This looks like a problem we had some time ago, although it was part of a much more complex outage. The problem was a power failure (Murphy during actions on the power infra) in one site of the 2 site 9-LPAR sysplex. Several things like automatic recovery action (sysplex partitioning etc) were

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

I have a theory that no news article yet written on IT is accurate (and maybe we could drop the "on IT"). Regardless, this one seems to entirely miss the point that *new* hardware had a problem, not the *old* software. Not to mention that while being unable to accept payments and returns is bad

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

Why do people seem to ignore the fact that UNIX and the C Programming Language were being developed in 1969 and being used in the early '70s (thanks Bell Labs!)? I don't see the mad rush to do away with *nix-based systems or applications written in C because they're "old". Just because an

Re: [EXTERNAL] Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

FUD - pure and simple - used to convince IT management and decision makers that they are on the wrong side of the equation. Truth, facts, etc. don't fit that narrative. -- Lionel B. Dyck (Contractor) < Mainframe Systems

Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to New Hardware (nextgov.com)

Applications don't get old. They either do what they're supposed to do or they don't. It has nothing to do with age. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Smith, Nathan (ATLANTA, GA) Sent: Friday, April 20, 2018 6:13 AM

DFSMSdss dump fix after binary transfer

Hello all, this one is for the old-timers on the list (I guess :). A colleague has made a logical data set DUMP of important data and downloaded to his PC in binary (by mistake, without additional steps). As expected, after uploading from PC to z/OS, the format is broken, and ADRDSSU doesn't