obinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-302-7535 Office
> robin...@sce.com
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU
Sent: Friday, April 01, 2016 5:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: COBOL Rookie Problem
An update for anyone who cares. My motivation was to get a preview of how real
application programs might benefit from ABO. As an electric utility, we have
millions of customers and millions
Guys,
Add me to that result list too.
Thx for all the work Skip..
Regards,
Scott
On Friday, April 1, 2016, Sam Siegel wrote:
> Thanks for sending this out. We will be looking at ABO soon. I'll be very
> interested to see your ABO results.
>
> Sam
>
> On Fri, Apr 1, 2016 at
Thanks for sending this out. We will be looking at ABO soon. I'll be very
interested to see your ABO results.
Sam
On Fri, Apr 1, 2016 at 5:09 PM, Jesse 1 Robinson
wrote:
> An update for anyone who cares. My motivation was to get a preview of how
> real application
An update for anyone who cares. My motivation was to get a preview of how real
application programs might benefit from ABO. As an electric utility, we have
millions of customers and millions of account records. We don't do elaborate
calculations for most customers. Think what it might take to
Cant answer your question, but if you want to chew some CPU, heres a cobol
program that will compute prime numbers...Doesnt do any IO though.
000100 IDENTIFICATION DIVISION.
000200 PROGRAM-ID. PRIMECB2.
000300* EXAMPLE
On Fri, 1 Apr 2016, at 01:13, Bill Woodger wrote:
> X'0001F1' where the ? have the numeric as 0, gives you your 01100 in
> iterate, once it has been packed (prior to becoming binary) to use in the
> TIMES.
Why did it DISPLAY as 1 though?
--
Jeremy Nicoll - my opinions are my own.
On 01/04/2016 06:26 PM, Bill Woodger wrote:
Andrew, I don't think it would be difficult at all. Especially for ARCH 11,
there's some substantial differences in that example of what code would be
possible (with V5 or V6), so it will be interesting to see if the ABO takes
full advantage.
I'm
Yes, the compiler kindly (but not very politely) informed me of that necessity.
Thanks also to Sam for similar advice.
.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com
Bill, you're a genius. Made the change, now it works as expected. I forgot
about the structure of PARM when passed to the program. Now I get displays
+Iterate 1 times
+Reading record
+Reading record
Tried larger values also; all look good. Thanks!
.
.
.
J.O.Skip
.
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-302-7535 Office
> robin...@sce.com
>
> -----Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MA
Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Farley, Peter x23353
Sent: Thursday, March 31, 2016 4:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: COBOL Rookie Problem
Skip, I would need to see the invoking JCL and the COBOL definition
Skip, I would need to see the invoking JCL and the COBOL definition of
"iterate" in the LINKAGE SECTION to confirm my suspicion, but my first guess is
that you gave the program a PARM of 1100 to do 1100 iterations, and that is
what it did. Empty (even DUMMY) sequential files always open
13 matches
Mail list logo