Re: "The Computers Nobody Wanted"

Paul Gilmartin wrote: >For me, it was broken on the UA LISTSERV website and in >Mac Mail.app. The raw source shows: >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >... > > http://worrydream.com/refs/Strassmann%20-%20The%20Computers%20Nobody%20Wante

Re: "The Computers Nobody Wanted"

On Thu, 14 Apr 2022 17:16:56 -0400, Phil Smith III wrote: >? My link worked fine as sent, both at my end and in Gmail. Gil, your client >seems to be breaking QPed lines?! > For me, it was broken on the UA LISTSERV website and in Mac Mail.app. The raw source shows: Content-Type: text/plain;

Re: "The Computers Nobody Wanted"

? My link worked fine as sent, both at my end and in Gmail. Gil, your client seems to be breaking QPed lines?! Anyway, yours works too! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: "The Computers Nobody Wanted"

On Thu, 14 Apr 2022 16:59:46 -0400, Phil Smith III wrote: >http://worrydream.com/refs/Strassmann%20-%20The%20Computers%20Nobody%20Wante >d.pdf > ITYM . -- gil

"The Computers Nobody Wanted"

http://worrydream.com/refs/Strassmann%20-%20The%20Computers%20Nobody%20Wante d.pdf This is sort of interesting, starting at bottom of PDF page 10, "The IBM 360 Promises". A different view on the 360 from the one we grew up with; reality is presumably somewhere in the middle. (And how did I

Re: dequeue program

On Thu, 14 Apr 2022 16:30:49 +, Steely.Mark wrote: >There was a program that when executed would prevent the ENQ on a dataset. >This was used for jobs which would FTP a file and then use that file in steps >after the FTP. > >This was the JCL used: > >//JS010 EXEC PGM=FTPDEQ, >//

Re: dequeue program

IYM that the program dynamically allocated the dataset with a disposition of SHR. It is possible to prevent the ENQ for a started task with an entry in the program properties table (PPT), but that is not done by the program. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3

dequeue program

There was a program that when executed would prevent the ENQ on a dataset. This was used for jobs which would FTP a file and then use that file in steps after the FTP. This was the JCL used: //JS010 EXEC PGM=FTPDEQ, //PARM='data.set.name.here' //SYSUDUMP DD SYSOUT=* This would be

Re: Reliable source for OCO?

The best way to address potentially transient URLs in wiki may be to quote the relevant text as part of the citation. If I could find a reliable online secondary source, that would be better due to wiki's prejudice against primary sources. Back when they were still available, I used to read

Re: Reliable source for OCO?

That might be reasonable in a different context, but wiki has rules about verifiability. Worse, they consider secondary sources more reliable than primary sources, which to anybody with exposure to Academia seems insane. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3

Re: Reliable source for OCO?

Seymour, He is asking you to prove a negative. Call him on it. Tony Thigpen Seymour J Metz wrote on 4/14/22 07:37: I'm editing the wikipedia [[Operating system]] article, and another editor has challenged the sentence "The logic manuals for their contemporary descendants, z/VM, z/VSE and

Re: Reliable source for OCO?

On Thu, 14 Apr 2022 at 07:37, Seymour J Metz wrote: > I'm editing the wikipedia [[Operating system]] article, and another editor > has challenged the sentence "The logic manuals for their contemporary > descendants, z/VM, z/VSE and z/VM, are not available to the general public." > What are the

Re: System Proclibs, Member management

I recently had to do a similar research function like this one, I found you have to use whatever data you can glean from your batch scheduler (at a minimum), and even then you can miss PROC's used by STC's started at IPL rather than by a scheduler as well as "on demand" jobs requested outside

Re: System Proclibs, Member management

Prolly wandering somewhat off topic... Lionel sez; "but if you do it under an official change control process at least you've documented what you're doing and received official approval for doing it." At a former shop that was the only way application proclibs and jcl members were added

Re: System Proclibs, Member management

There is always the approach of making a copy and then deleting - or just renaming suspect members and waiting for the fallout. This can be dangerous but if you do it under an official change control process at least you've documented what you're doing and received official approval for doing

Re: System Proclibs, Member management

My humble opinion: NO. No way. I have seen discussion about tracking library access, hopefully at member level. So what? Let's imagine member ABC has not been touched for 5 months. Can you delete it? No, you are not sure about half-year or once-a-year processes. Of course, detailed report of

Re: View ASCII Command inUSS

On Thu, 14 Apr 2022 12:59:35 +, Seymour J Metz wrote: >Yes and no. Special files are kernel facilities. The shell recognizes "|" as a >pipe request, creates the special file and file descriptors. The communication >between the processes does not involve the shell. > I wonder whether:

Re: z16 documentation discrepancy

Yes, CFCC is another case for discrepancies in documentation. I just pointed few of them, it wasn't complete list. And to be clear - I complaining about documentation, not limitations. I'm perfectly OK with statements like: "CF LPAR can be up to 16TB, but current CFCC will not use more than

Re: View ASCII Command inUSS

Yes and no. Special files are kernel facilities. The shell recognizes "|" as a pipe request, creates the special file and file descriptors. The communication between the processes does not involve the shell. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3

Reliable source for OCO?

I'm editing the wikipedia [[Operating system]] article, and another editor has challenged the sentence "The logic manuals for their contemporary descendants, z/VM, z/VSE and z/VM, are not available to the general public." What are the relevant URLs for IBM's policy? Thanks. -- Shmuel