On 2017-12-19, at 20:51:23, Jon Perryman wrote:
>> I wrote: TSO has the alloc command which can easily be > used in clists. It
>> exists because of MVS UNIX.
> MVS UNIX has nothing to do with TSO ALLOC. When I moved the C FOPEN text, I
> forgot to delete the MVS UNIX senstence. It's FOPEN
> I wrote: TSO has the alloc command which can easily be > used in clists. It
> exists because of MVS UNIX.
MVS UNIX has nothing to do with TSO ALLOC. When I moved the C FOPEN text, I
forgot to delete the MVS UNIX senstence. It's FOPEN dynamic alloc only exists
because of MVS Unix and is
A spin type lock is necessary if the code is running disabled. It also means
that the lock must never be obtained by enabled code. and as previously state,
recovery is mandatory.
Disabled code is not for the faint of heart. It's very easy to shoot the whole
system in disabled code,
On 12/19/2017 1:16 PM, Charles Mills wrote:
Isn't there some issue with using SUSPEND or RESUME if the caller of the code
in question might hold locks and you have no control over that (such as in a
system exit)?
Haha! Yes, and that applies to WAIT and PAUSE as well. The secret is to
Isn't there some issue with using SUSPEND or RESUME if the caller of the code
in question might hold locks and you have no control over that (such as in a
system exit)?
Charles
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of
Why not, e.g., ARR?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List on behalf
of Charles Mills
Sent: Tuesday, December 19, 2017 3:57 PM
To:
FRR's are mandatory! Even on a multiprocessor.
Charles
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of Gary Weinhold
Sent: Tuesday, December 19, 2017 3:10 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: LT Instruction After
If this code ever ran on a uniprocessor, it's could bring it to its
knees if the lock field is left locked because cleanup code never ran
after an abend or a random error overlaid the lock field.
Regards, Gary
On 2017-12-19 10:30 AM, Ed Jaffe wrote:
On 12/18/2017 6:02 PM, Tony Harminc
On 12/18/2017 6:02 PM, Tony Harminc wrote:
I wouldn't want to have to argue the case for having an enabled
application program do spin loops. But we don't know the context this
code was found in; maybe it's part of an OS or a standalone program.
In my entire IT career, most of which has been