I have z14 on the brain. I meant z12s.
On 5/13/20 9:10 PM, Clark Morris wrote:
[Default] On 13 May 2020 16:56:58 -0700, in bit.listserv.ibm-main
ste...@copper.net (Steve Thompson) wrote:
Suppose that they took a group of programmers and got the production online
programs to all compile with COBOL 6.2 and OPT(1). Would they see a significant
reduction in MSUs? Assuming they are running on z14s minimally?
Is it likely in most environments that both the primary and fallback
computers (disaster recovery) are z14 or more recent?
Clark Morris
And from that, would they actually be able to do more transactions per hour?
Sent from my iPhone — small keyboarf, fat fungrs, stupd spell manglr. Expct
mistaks
On May 13, 2020, at 7:45 PM, Seymour J Metz <sme...@gmu.edu> wrote:
?Conspicuously missing from the coverage is any evidence of delays or outages
attributable to COBOL code running on mainframes. So far the stories I've seen
turn out to relate to web servers or manual processing, not to the back end.
Yeah, there could be issues with, e.g., CICS transactions written in COBOL, but
none of the stories provide any reason to believe that to be the case.
More disturbing is the assumption that if they train hordes of COBOL
programmers and bring all of the applications written in COBOL up to date,
their troubles will be over. The elephant in the room is all of the code in
other languages that has also been allowed to languish. It *all* needs to be
documented and brought up to snuff.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Mark Regan [marktre...@gmail.com]
Sent: Wednesday, May 13, 2020 12:21 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: What crashing COBOL systems reveal about applications maintenance --
GCN
https://secure-web.cisco.com/1Ck2hssvPisqB8qyqrPsKlWMSh6SVj36qT95iEGNsvW41QGGjEH5TGYkmfjBEBCwAqsZp1UH2qlJxAPV-nlun5Dg56JO8lyf2QqkfAQDmic0ch6e5uj8J9A-Q3B3We8shuckCRr_XeQmGMDhXgd8TQyRlLdXH9bKy-iCiUCWHj2Kqen8MgwZNhQmpmPDXCZynS12e9_NREBCyJ-ImKut7vZYA4mccK38-ps5r3DJciC05kNl8kmdPhUg60gd1zZz7JURnW9weaJQKKDRSp57OBFh-n49E04rQSKCcaRjfOb7cGMU1n6iqgjTNOpmxmuPIjDr4aGw9aUMm9k3V6bRy75OJLSewcdQoYLb3wcGP1Iff-nYxUbFk8wp8l3lc_AhRdjTQ-059TNEsAQTLJUnMUEkSHuyT9PtOAgQrQdm_g-sdoO8Y415VmGflAy_9xBgfqdVJiOoYQb3UbkX7P6tc_A/https%3A%2F%2Fgcn.com%2Farticles%2F2020%2F05%2F12%2Fkeeping-mainframes-up-to-date.aspx%3Fm%3D1
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
