The current CBT 183 has a fix for this. See SWAREQ22 (it was z/OS 2.2
where the breaking change was introduced.) It works on pre-2.2 as
well, so there's no need to hold on to the original SWAREQ.
In article <3385731727254339.wa.pbishop23dxc@listserv.ua.edu> you wrote:
> Bad form to reply to m
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.idad400/zfslds.htm
"Beginning in z/OS V2R1, you can specify extended addressability for a VSAM
linear data set (LDS) that is neither extended-format nor SMS-managed. This
allows the LDS to exceed the four-gigabyte size
ObUnclean Does Unix System Services implement its own spin locks or does it use
MVS services? Does any *ix have spin locks outside of the kernel?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
On Thu, 17 Oct 2019 at 08:54, Thomas David Rivers wrote:
> Does anyone happen to know the best way for a running task
> to give up running and let another task run?
> Sorta like "I'm done for the moment if something else would like to run".
This sounds so wrong right from the start. Or rather,
From a design perspective it would seem that your task is done and waiting for
more work? Generally I’d think you’d want to wait and have someone post that
work is ready or an stimer to wait for a period of time.
z/OS is unlike many operating systems where it will pre-empt running work and
s
Each Branch has an Environmental specialist. They'll help you and are familiar
with Auto-Cad for layouts and loading.
In a message dated 10/18/2019 4:56:15 AM Central Standard Time,
kees.verno...@klm.com writes:
Or: open the floor and check if the power cords are really connected to
different r
Timothy,
Well said, totally agree. I love z/PDT ..Its great for a small ISV shop
.Makes my life easier.
I have ran both zVM and z/OS since 1.13 on it.
Scott
On Wed, Oct 16, 2019 at 6:57 AM Jousma, David <
01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:
> -Original Message-
> From
You only get the CPU for a time slice, or until the next interrupt occurs,
which is very often. After each interrupt, the highest priority piece of work
is dispatched. If you are still at the top, you go next. If not, you wait
until you are at the top of the dispatch chain.
Chris Blaicher
Te
Question is about generating an interrupt on a console for a standalone restore.
I read this previous post:
https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/lX4ZGaoUH_s
So for a z13 would the interrupt needed be the one described in
zEnterprise System
Support Element Operations Guide
The procedure you are describing would present an
Interrupt Key external interruption, and that is not what Standalone DFDSS
is looking for. It is looking for an attention from what looks like a
channel-attached console
(which on days machines would be OSA-ICC), which you would do by hittin
z/OSMF can create an extract of the migration information (now called "upgrade"
instead
of "migration") from the z/OSMF workflow (either z/OS 2.2 to z/OS 2.4 or z/OS
2.3
to z/OS 2.4 - whichever one you import from GitHub or both). It's in HTML
format
and quite readable with links to the diffe
Jim is correct, all it takes is for one of the consoles that is attached to the
ICC, or which you have limited your DFDSS SA build to to press enter. I have
found that almost any key that generates "something" seems to work though, the
function keys, pageup etc. The ones that just move the cur
12 matches
Mail list logo
