Re: IBM-MAIN Digest - 1 Nov 2022 to 2 Nov 2022 (#2022-302)

2022-11-03 Thread Reg Harbeck
/* ¬ */

- Reg Harbeck, M.A.
+1.403.605.7986

> On Nov 3, 2022, at 17:23, Reg Harbeck  wrote:
> 
> #!
> 
> - Reg Harbeck, M.A.
> +1.403.605.7986
> 
>> On Nov 3, 2022, at 15:17, zMan  wrote:
>> 
>> !
>> 
>> Srsly, what do you mean?
>> 
>>>> On Thu, Nov 3, 2022 at 4:33 PM Willie Favero  wrote:
>>> 
>>> ?
>>> 
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>> 
>> 
>> 
>> -- 
>> zMan -- "I've got a mainframe and I'm not afraid to use it"
>> 
>> --
>> 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


Re: IBM-MAIN Digest - 1 Nov 2022 to 2 Nov 2022 (#2022-302)

2022-11-03 Thread Reg Harbeck
#!

- Reg Harbeck, M.A.
+1.403.605.7986

> On Nov 3, 2022, at 15:17, zMan  wrote:
> 
> !
> 
> Srsly, what do you mean?
> 
>> On Thu, Nov 3, 2022 at 4:33 PM Willie Favero  wrote:
>> 
>> ?
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
> 
> 
> -- 
> zMan -- "I've got a mainframe and I'm not afraid to use it"
> 
> --
> 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


Re: Is there a word for that?

2020-09-20 Thread Reg Harbeck
“Dynamically persistent”?

- Reg Harbeck
+1.403.605.7986
Upcoming IBM Systems Magazine webinar, Wed, October 21, 2020 2:00 PM CDT: “If 
It Ain’t Broke, Why Recompile COBOL?” | More info.

> On Sep 20, 2020, at 20:18, Gibney, Dave  wrote:
> 
> I suppose dynamic would work. Today, many more of the parmlib members 
> referenced by IEASYSxx can also be activated on the fly with seT. What I'd 
> like would be a nice table or list showing which ones can be seT. A similar 
> list for JES would be nice, but probably shorter to list those that can't be 
> so changed.
> 
>> -Original Message-
>> From: IBM Mainframe Discussion List  On
>> Behalf Of Jesse 1 Robinson
>> Sent: Sunday, September 20, 2020 12:01 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Is there a word for that?
>> 
>> This is a question about categorizing JES2 commands. At one time, when we
>> were still buckling our knickerbockers above the knee, many/most JES2
>> configuration definitions could be modified only by some kind of restart
>> ranging from hot start to warm start to cold start. Some years ago JES2
>> developers got very busy and created command support for all kinds of
>> parameters that previously required some kind of disruption.
>> 
>> The result is that now most JES2 configuration parameters can be modified
>> via $T. In fact, most changes are generally *ignored* during JES2 restarts
>> other than cold start. So here's my question: is there a generally accepted
>> term for 'changeable by command'? It would facilitate communication
>> regarding all kinds of changes. This weekend we scheduled a JES2 change
>> involving layers of administrative rigmarole that was 'implemented' by 
>> editing
>> the JES2 init deck. We eventually issued a $T command after noticing that the
>> desired change did not take effect at IPL. I've heard 'volatile' suggested 
>> for
>> 'changeable by command', but I don't find documentation to support that.
>> Any ideas?
>> 
>> .
>> .
>> J.O.Skip Robinson
>> Southern California Edison Company
>> Electric Dragon Team Paddler
>> SHARE MVS Program Co-Manager
>> 323-715-0595 Mobile
>> 626-543-6132 Office <= NEW
>> robin...@sce.com<mailto:robin...@sce.com>
>> 
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Some COBOL Links

2020-04-08 Thread Reg Harbeck
While I still think the governor of New Jersey probably should be looking at
a capacity increase before tempting Brook's Law by adding programmers to a
project that is already behind the eight ball, since we all have the
opportunity to defend COBOL to people who are temporarily listening, here
are some links that may be of use:

 

https://www.planetmainframe.com/2019/08/cobol-still-the-best-for-new-high-vo
lume-applications-after-all-these-years/ 

 

https://ibmsystemsmag.com/IBM-Z/05/2019/cobol-turns-60 

 

https://ibmsystemsmag.com/Trends/09/2019/captain-cobol-tom-ross 

 

https://ibmsystemsmag.com/Trends/11/2019/michelle-yeager-hayley-owens-cobol

 

https://ibmsystemsmag.com/Trends/10/2019/ray-mullins

 

https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/destination
-z1/2019/12/23/genealogy-of-cobol-and-hlasm

 

Reg Harbeck

403-605-7986

 


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Wanted Civil programmers in New Jersey urgently

2020-04-05 Thread Reg Harbeck
Hopefully it is a capacity issue and not programming, given Brooks’ law...

- Reg Harbeck
+1.403.605.7986

> On Apr 5, 2020, at 12:15, Martin Packer  wrote:
> 
> I came to the opposite conclusion: I couldn't see why coding was required 
> unless new function was DESPERATELY needed. The word in bold because that 
> seems very risky - going around changing function at a time like this.
> 
> And, because my lens is more-or-less performance, I thought making the 
> application scale was the urgent and safer thing. Yes, I realise 
> application changes can be necessary to make something scale but then 
> we're back to desperation. :-(
> 
> Cheers, Martin
> 
> Martin Packer
> 
> zChampion, Systems Investigator & Performance Troubleshooter, IBM
> 
> +44-7802-245-584
> 
> email: martin_pac...@uk.ibm.com
> 
> Twitter / Facebook IDs: MartinPacker
> 
> Blog: 
> https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker
> 
> Podcast Series (With Marna Walle): https://developer.ibm.com/tv/mpt/or 
> 
> https://itunes.apple.com/gb/podcast/mainframe-performance-topics/id1127943573?mt=2
> 
> 
> Youtube channel: https://www.youtube.com/channel/UCu_65HaYgksbF6Q8SQ4oOvA
> 
> 
> 
> From:   Laurence Chiu 
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date:   05/04/2020 20:06
> Subject:[EXTERNAL] Wanted Civil programmers in New Jersey urgently
> Sent by:IBM Mainframe Discussion List 
> 
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: IBM Destination z - Of Elephants and Mainframes

2019-08-06 Thread Reg Harbeck
Good news: the article has been updated based on input from Gabe and IBM-MAIN. 
See http://destinationz.org/Mainframe-Solution/Trends/elephants-and-mainframes 
for the revised version.

Thanks, all!

Reg Harbeck
+1.403.605.7986

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Reg 
Harbeck
Sent: August 1, 2019 14:40
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IBM Destination z - Of Elephants and Mainframes

Thank you, Gabe. I'm honoured that you read my writing so closely, and I take 
your correction seriously. I'll be more careful how I phrase such things in 
future articles.

FWIW, I am aware that Fortran and other pre-COBOL languages already existed, so 
perhaps I should have said "much of this stuff" instead.

(And to those who have made other suggestions on IBM-MAIN that I should have 
caught, but missed, in the past, my apologies: still getting into good habits 
of keeping up with this important part of the mainframe ecosystem.)

Reg Harbeck
+1.403.605.7986

P.S. Looking forward to seeing many of you in Pittsburgh next week.

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Gabe Goldberg
Sent: August 1, 2019 13:45
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IBM Destination z - Of Elephants and Mainframes

Think back… think way back, possibly to before you were born. Think of the 
reasons why SHARE was founded in 1955, and the main activities of SHARE. Once 
upon a time, when electronic computing technology was still being figured out, 
each new machine was so different from its predecessors that it was necessary 
to rewrite a whole new set of utilities and drivers and applications for it. 
Even Assembly language wasn’t available until 1957 (and the first COBOL 
compiler didn’t come out until 1960) so most of this stuff had to be manually 
entered in machine language.

http://destinationz.org/Mainframe-Solution/Trends/elephants-and-mainframes

Um, no. ACM SIGPLAN History of Programming Languages Conference 1978 article on 
FORTRAN says:

Page 166 1.3 Programming Systems in 1954

Most "automatic programming" systems  were either assembly programs, or 
subroutine-fixing programs, or, most popularly, interpretive systems to provide 
floating point and indexing operations.

---

That's far beyond machine language three years before article claims anything 
more advanced than that was used.

--
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


Re: IBM Destination z - Of Elephants and Mainframes

2019-08-01 Thread Reg Harbeck
Thank you, Gabe. I'm honoured that you read my writing so closely, and I take 
your correction seriously. I'll be more careful how I phrase such things in 
future articles.

FWIW, I am aware that Fortran and other pre-COBOL languages already existed, so 
perhaps I should have said "much of this stuff" instead.

(And to those who have made other suggestions on IBM-MAIN that I should have 
caught, but missed, in the past, my apologies: still getting into good habits 
of keeping up with this important part of the mainframe ecosystem.)

Reg Harbeck
+1.403.605.7986

P.S. Looking forward to seeing many of you in Pittsburgh next week.

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Gabe Goldberg
Sent: August 1, 2019 13:45
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IBM Destination z - Of Elephants and Mainframes

Think back… think way back, possibly to before you were born. Think of the 
reasons why SHARE was founded in 1955, and the main activities of SHARE. Once 
upon a time, when electronic computing technology was still being figured out, 
each new machine was so different from its predecessors that it was necessary 
to rewrite a whole new set of utilities and drivers and applications for it. 
Even Assembly language wasn’t available until 1957 (and the first COBOL 
compiler didn’t come out until 1960) so most of this stuff had to be manually 
entered in machine language.

http://destinationz.org/Mainframe-Solution/Trends/elephants-and-mainframes

Um, no. ACM SIGPLAN History of Programming Languages Conference 1978 article on 
FORTRAN says:

Page 166 1.3 Programming Systems in 1954

Most "automatic programming" systems  were either assembly programs, or 
subroutine-fixing programs, or, most popularly, interpretive systems to provide 
floating point and indexing operations.

---

That's far beyond machine language three years before article claims anything 
more advanced than that was used.

--
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