At one job I was on the standards committee and ended up writing quite a few
COBOL/JOB/JCL standards.
One of the first was that no COBOL (no other languages were permitted) could
not have any WTORS. Some programmers objected to it and we got in a nice
discussion about operators priorities and I
On 6/4/2016 2:31 PM, Greg Dyck wrote:
On 6/4/2016 6:34 AM, Ed Jaffe wrote:
So, the local lock is obtained in only a subset of Pause/Release
scenarios?
Ed,
The local lock is *never* obtained for single PET Pause/Release
processing.
That's great to know! That makes Pause/Release/Transfer extr
On 6/4/2016 6:34 AM, Ed Jaffe wrote:
So, the local lock is obtained in only a subset of Pause/Release scenarios?
Ed,
The local lock is *never* obtained for single PET Pause/Release
processing.
For multiple PET Pause/Release it is obtained to serialize creation of
an address space related CP
>> Did you allow them to stack up on the console? or did you K E,? them? and if
>> so how did you keep track of which reply numbers were >>outstanding hidden
>> off the console?
>
>The op k e,1’d them. They did a d r,l to get the message number. I wasn’t
>watching the console that closely but th
This is a simplification of to focus on the main points. During a part of the
day we run a procedure that was developed offshore. This procedure provides
certain secure services and when a violation is detected it must write a data
record for later analysis. This requirement was discovered later
On 6/4/2016 5:55 AM, Peter Relson wrote:
It is still thought that, for many cases, pause/release is more efficient
than wait/post (not just more effective), primarily due to the reduction
in local lock usage which can be a significant difference-maker in
application performance.
So, the local l
>...led to believe...
>...sentence is especially misleading. It suggests the primary use ...
As I read the wording that was quoted:
I do not see a comparison of the pause/release group of services to the
wait/post services.
I do not see a "suggestion". I see a valid example. An "example" is not
