at level of CPU burn for
>planning for capacity for migrating to 6.2.
>
>Regards
>Steve Thomoson
>
>--- frank.swarbr...@outlook.com wrote:
>
>From: Frank Swarbrick
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: [IBM-MAIN] What crashing COBOL systems rev
From: IBM Mainframe Discussion List On Behalf
> Of ste...@copper.net
> Sent: Wednesday, May 20, 2020 5:08 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [External] Re: What crashing COBOL systems reveal about
> applications maintenance -- GCN
>
> We setup for OPT(1) because IBM
ginal Message-
From: IBM Mainframe Discussion List On Behalf Of
ste...@copper.net
Sent: Wednesday, May 20, 2020 5:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: What crashing COBOL systems reveal about applications
maintenance -- GCN
We setup for OPT(1) because IBM said that was the
vel of CPU burn for planning
for capacity for migrating to 6.2.
Regards
Steve Thompson
--- frank.swarbr...@outlook.com wrote:
From: Frank Swarbrick
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] What crashing COBOL systems reveal about applications
maintenance -- GCN
D
COBOL systems reveal about applications maintenance
-- GCN
>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 signif=
>icant reduction in MSUs? Assuming they are running on z14s minimally
>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 signif=
>icant reduction in MSUs? Assuming they are running on z14s minimally?
I sure hope no one is using OPT(1) with 3rd generation COBOL! IBM exp
Hi Wayne!
If you'd like to recompile that C code too - just drop us a note!
Newer versions of Systems/C have better optimization too!
- Dave Rivers -
Wayne Bickerdike wrote:
We're going through the COBOL 6 compile exercise, on a Z13. The only
hiccups have been source control and the odd
ented and brought up to snuff.
> >>>
> >>>
> >>> --
> >>> Shmuel (Seymour J.) Metz
> >>> http://mason.gmu.edu/~smetz3
> >>>
> >>>
What crashing COBOL systems reveal about applications maintenance --
GCN
https://secure-web.cisco.com/1Ck2hssvPisqB8qyqrPsKlWMSh6SVj36qT95iEGNsvW41QGGjEH5TGYkmfjBEBCwAqsZp1UH2qlJxAPV-nlun5Dg56JO8lyf2QqkfAQDmic0ch6e5uj8J9A-Q3B3We8shuckCRr_XeQmGMDhXgd8TQyRlLdX
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
ktre...@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/1Ck2hssvPisqB8qyqrPsKlWMSh6SVj36qT95iEGNsvW41QGGjEH5TGYkmfjBEBCwAqsZp
U] 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.cisc
https://gcn.com/articles/2020/05/12/keeping-mainframes-up-to-date.aspx?m=1
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
13 matches
Mail list logo
