Delivery Manager, but no indication whether this
> was a reference to the same CAS Charlie. IBM could easily have had
> multiple employees over the years with the same first-last name.
re:
http://manana.garlic.com/~lynn/2016d.html#96 Multithreaded output to stderr and
stdout
http://manana.garl
On 07/02/2016 08:25 PM, Paul Gilmartin wrote:
> On Sat, 2 Jul 2016 17:33:46 -0700, Anne & Lynn Wheeler wrote:
>
>> mike.lamart...@mcleansoft.com (Mike La Martina) writes:
>>> After reading the story of Compare and Swap for, lo, all these many years, I
>>> am sorry but I must ask.
>>>
>>> Charlie wh
On Sat, 2 Jul 2016 17:33:46 -0700, Anne & Lynn Wheeler wrote:
>mike.lamart...@mcleansoft.com (Mike La Martina) writes:
>> After reading the story of Compare and Swap for, lo, all these many years, I
>> am sorry but I must ask.
>>
>> Charlie who?
>
>aka Charlie's initials are CAS ... part of the ef
mike.lamart...@mcleansoft.com (Mike La Martina) writes:
> After reading the story of Compare and Swap for, lo, all these many years, I
> am sorry but I must ask.
>
> Charlie who?
aka Charlie's initials are CAS ... part of the effort was to choose
mnemonic (compare-and-swap) that were Charlie's ini
MAIN@LISTSERV.UA.EDU
Subject: Re: Multithreaded output to stderr and stdout
000433f07816-dmarc-requ...@listserv.ua.edu (Paul Gilmartin) writes:
> I'm trying to envision how to use WAIT/POST to do that since no more
> than one task can be WAITing on a given ECB. I vaguely rec
000433f07816-dmarc-requ...@listserv.ua.edu (Paul Gilmartin) writes:
> I'm trying to envision how to use WAIT/POST to do that since no
> more than one task can be WAITing on a given ECB. I vaguely recall
> long ago writing code that used a variant of a CS example in PoOps
> to manage a queue of
In article <5452732228714303.wa.paulgboulderaim@listserv.ua.edu> you wrote:
> On Fri, 1 Jul 2016 21:38:14 -0400, Don Poitras wrote:
> >
> >I wrote the support in SAS/C for handling multiple tasks writing to the same
> >sysout DD. I used WAIT/POST rather than ENQ/DEQ.
> >
> >https://support.sas.
On Fri, 1 Jul 2016 21:38:14 -0400, Don Poitras wrote:
>
>I wrote the support in SAS/C for handling multiple tasks writing to the same
>sysout DD. I used WAIT/POST rather than ENQ/DEQ.
>
>https://support.sas.com/documentation/onlinedoc/sasc/doc750/html/clug/zntimeop.htm#zid-1494
>
I'm trying to envi
In article <4827659745512199.wa.woodagozemail.com...@listserv.ua.edu> you wrote:
> On Wed, 29 Jun 2016 13:00:10 -0500, John McKown
> wrote:
> . . .
> >Now, with JES2 (or UNIX output), what happens? Well, it's more like a data
> >base. You still have two DCBs, but the actual write sends the data
On Wed, 29 Jun 2016 13:00:10 -0500, John McKown
wrote:
. . .
>Now, with JES2 (or UNIX output), what happens? Well, it's more like a data
>base. You still have two DCBs, but the actual write sends the data to JES2
>and tells it to place it in the SPOOL file. So JES2 is accepting and
>interleaving
On Fri, 1 Jul 2016 20:36:38 +0200, Michael Knigge wrote:
>Yes, DISP=(NEW,CATLG,DELETE)
> [much snippage]
>
I've noticed, mostly on non-z/OS systems:
o (documented) For "cat -u", the "-u" is always in effect; provided for
compatibility but otherwise ignored.
o (not well documented) stderr t
Yes, DISP=(NEW,CATLG,DELETE)
Bye,
Michael
Am 01.07.2016 um 14:14 schrieb Kurt Quackenbush:
At our site there is no difference if I use DSN= or SYSOUT=* in my
JCL for STDOUT and STDERR. Output from all threads is written to the
file.
At the customer site if DSN=xxx is used, only output
At our site there is no difference if I use DSN= or SYSOUT=* in my
JCL for STDOUT and STDERR. Output from all threads is written to the file.
At the customer site if DSN=xxx is used, only output from the main
thread is written to the file. If SYSOUT=* is used the customer can see
all output i
Yes
At our site there is no difference if I use DSN= or SYSOUT=* in my
JCL for STDOUT and STDERR. Output from all threads is written to the file.
At tzhe customer site if DSN=xxx is used, only output from the main
thread is written to the file. If SYSOUT=* is used the customer can s
Tony,
I've tried to reproduce it locally on our z/OS System. I've allocated a
Data Set in RECFM=VB (and large block size) and a second test with
an allocated RECFM=V data set. No differecne at our z/OS system. It
works like a charm in both cases...
Bye,
Michael
Am 29.06.2016 um 21:
sking more questions here, but I suspect that going down those
roads may lead you to better answers.
HTH
Peter
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Michael Knigge
Sent: Wednesday, June 29, 2016 1:30 PM
To: IBM-MAIN@LIS
On Wed, 29 Jun 2016 16:07:05 -0500, Kirk Wolf wrote:
>When using two Unix threads in the same z/OS Unix process, operations to
>sdout/stderr are serialized.
>
>Are you certain that these are two threads in the same process rather than
>threads in different processes (which would be at least separa
ssage-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Kirk Wolf
Sent: Wednesday, June 29, 2016 5:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Multithreaded output to stderr and stdout
When using two Unix threads in the same z/OS Unix process, operations to
Agreed. I just reread the OP and it's not clear if he's tried DSN= . I
originally assumed he had.
Sent from my iPhone
> On Jun 29, 2016, at 17:13, Clark Morris wrote:
>
> [Default] On 29 Jun 2016 12:37:05 -0700, in bit.listserv.ibm-main
> t...@harminc.net (Tony Harminc) wrote:
>
>>> On 29
[Default] On 29 Jun 2016 12:37:05 -0700, in bit.listserv.ibm-main
t...@harminc.net (Tony Harminc) wrote:
>On 29 June 2016 at 14:00, John McKown wrote:
>
>> I may be blowing smoke here, if so I'm sure someone will point it out :-}.
>
>I think you're on the right (write...?) track.
>
>[...]
>> A D
When using two Unix threads in the same z/OS Unix process, operations to
sdout/stderr are serialized.
Are you certain that these are two threads in the same process rather than
threads in different processes (which would be at least separate LE
enclaves, and perhaps different address spaces) ?
Ki
On 29 June 2016 at 14:00, John McKown wrote:
> I may be blowing smoke here, if so I'm sure someone will point it out :-}.
I think you're on the right (write...?) track.
[...]
> A DD pointing to a sequential data set is _not_ designed to be
> written to by two different DCBs concurrently. What
Wednesday, June 29, 2016 1:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Multithreaded output to stderr and stdout
All,
I have a multithreaded Java application that writes to stdout (and
stderr) thru a native C library using fputc and fwrite. Now, at our site
everything is all right with output to
On Wed, Jun 29, 2016 at 12:29 PM, Michael Knigge
wrote:
> All,
>
> I have a multithreaded Java application that writes to stdout (and stderr)
> thru a native C library using fputc and fwrite. Now, at our site everything
> is all right with output to stderr and stdout from multiple threads.
>
> At
Possibly fundamental difference between JES (simulating unit record) and DASD
(probably blocked).
Sent from my iPhone
> On Jun 29, 2016, at 13:30, Michael Knigge wrote:
>
> All,
>
>
> I have a multithreaded Java application that writes to stdout (and stderr)
> thru a native C library usin
All,
I have a multithreaded Java application that writes to stdout (and
stderr) thru a native C library using fputc and fwrite. Now, at our site
everything is all right with output to stderr and stdout from multiple
threads.
At a customer site only output from the main thread is written to
26 matches
Mail list logo
