In 1250849277558111.wa.haroldberglasyahoo...@bama.ua.edu, on
03/03/2012
at 07:25 AM, Myname Is haroldberg...@yahoo.ca said:
pardon the language, sir, but did u know that the jcl keyword
UNIT=[/]n would create an internal text specification
Yes. I also know that the Internalt Text Buffer
pardon the language, sir, but did u know that the jcl keyword UNIT=[/]n
would create an internal text specification
that would require internal testing of either 3 4 OR now 5 characther length,
this would be simliar to the-svc 99- checking of the length field as well,
since u can't see
In 2280839336598964.wa.haroldberglasyahoo...@bama.ua.edu, on
02/29/2012
at 11:26 AM, Myname Is haroldberg...@yahoo.ca said:
and 3 bytes would upset the world of ZOS, (JCL,
JCL? NFW.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see
check the iocp manual - it's the CSS-ID (the logical channel subsystem id).
http://www-01.ibm.com/support/docview.wss?uid=isg2de3388ad7e19bffc85257768003f170eaid=1
page 68 and of course page 303, which says the 2817 has max of 3 for css-id,
and a max of 2 for subchanel set id.
p.s. i loved
Myname Is haroldberg...@yahoo.ca wrote in message
news:2280839336598964.wa.haroldberglasyahoo...@bama.ua.edu...
check the iocp manual - it's the CSS-ID (the logical channel
subsystem id).
http://www-01.ibm.com/support/docview.wss?uid=isg2de3388ad7e19bffc852577
68003f170eaid=1
page 68 and
, such as from
a CRC polynomial. So the path through the pages will be different,
and so different approximately LRU pages will be selected.
Never having tried this, those are the ones I think up.
re:
http://www.garlic.com/~lynn/2012b.html#98 5 Byte Device Addresses?
http://www.garlic.com/~lynn
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Anne Lynn Wheeler
Sent: Thursday, February 23, 2012 8:53 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: 5 Byte Device Addresses?
As I previously mentioned, something similar happens with a large DBMS
Addresses?
http://www.garlic.com/~lynn/2012b.html#100 5 Byte Device Addresses?
http://www.garlic.com/~lynn/2012c.html#16 5 Byte Device Addresses?
http://www.garlic.com/~lynn/2012c.html#17 5 Byte Device Addresses?
misc. past posts mentioning page replacement virtual memory management
http
://www.garlic.com/~lynn/2012b.html#98 5 Byte Device Addresses?
http://www.garlic.com/~lynn/2012b.html#100 5 Byte Device Addresses?
http://www.garlic.com/~lynn/2012c.html#16 5 Byte Device Addresses?
http://www.garlic.com/~lynn/2012c.html#17 5 Byte Device Addresses?
http://www.garlic.com/~lynn/2012c.html#27 5
re:
http://www.garlic.com/~lynn/2012b.html#98 5 Byte Device Addresses?
http://www.garlic.com/~lynn/2012b.html#100 5 Byte Device Addresses?
http://www.garlic.com/~lynn/2012c.html#16 5 Byte Device Addresses?
http://www.garlic.com/~lynn/2012c.html#17 5 Byte Device Addresses?
http://www.garlic.com
glen herrmannsfeldt g...@ugcs.caltech.edu writes:
It would seem less likely that they would use the exact same
replacement algorithm, but could eventually lock, anyway.
re:
http://www.garlic.com/~lynn/2012b.html#98 5 Byte Device Addresses?
http://www.garlic.com/~lynn/2012b.html#100 5 Byte
In af2ee1ca5139d947b1ccdbf226607e8e02b9d...@tad03.tad.org, on
02/19/2012
at 07:36 PM, Fred Hoffman fhoff...@tad.org said:
I thought os/vs1 was MFT with virtual storage.
That doesn't conflict with what anybody wrote in this thread, although
it is an oversimplification.
--
Shmuel
I thought os/vs1 was MFT with virtual storage.
Fred
From: IBM Mainframe Discussion List on behalf of Shmuel Metz (Seymour J.)
Sent: Fri 2/17/2012 12:51 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: 5 Byte Device Addresses?
In p06240802cb635acf006e@[192.168.1.11
glen herrmannsfeldt g...@ugcs.caltech.edu writes:
That is, as I understand it, pretty close to how it started out.
Among others, though OS/VS1 has special features for running
under VM that OS/VS2 never got. It has the ability to switch
to a different task while VM is paging a task. That
In
CAPD5F5oS=2wrluhxwtpjbcjbx8v0m9-nymvcfyjpbzket9u...@mail.gmail.com,
on 02/16/2012
at 11:45 AM, John Gilmore johnwgilmore0...@gmail.com said:
The original System/360 scheme was simple and in its way elegant.
01F---decodable unambiguously into (multiplexor) channel 0, control
unit 1, and that
In
77142d37c0c3c34da0d7b1da7d7ca346c...@nwt-s-mbx1.rocketsoftware.com,
on 02/16/2012
at 08:55 PM, Bill Fairchild bfairch...@rocketsoftware.com said:
Seymour is right that we have had subchannel numbers since 1983
instead of device addresses, but we have also had device numbers
since 1983.
In p06240802cb635acf006e@[192.168.1.11], on 02/16/2012
at 08:23 PM, Robert A. Rosenberg hal9...@panix.com said:
No Bill is right.
No.
OS/VS2 Release 2 WAS MVS
But MVS wasn't OS/VS2 Release 2.
like OS/VS2 Release 1 was SVS.
The difference is that SVS was *only* release 1; MVS was *not*
W dniu 2012-02-16 01:55, Dan pisze:
Thanks Radoslaw Bob.
I figured there must be some explanation for the additional byte other than
some new extended device ranges.
This is still a DOC problem as the manual simply states these are device
addresses.
Radoslaw, are you saying there is a way of
Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Dan
Sent: Wednesday, February 15, 2012 6:56 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: 5 Byte Device Addresses?
This is still a DOC problem as the manual simply states these are device
addresses
W dniu 2012-02-16 15:14, Bill Fairchild pisze:
They haven't been device addresses since 1983 with the advent of MVS/XA, in spite of the fact
that people who had been calling them device addresses since 1964, for the most part, still call them device
addresses. They have been device numbers
Predictably--I am the pedant who insists on distinguishing KB and
KiB--Bill Fairchild's point seems to me to be important. Quaint,
long familiar terminology should be avoided where it is misleading.
The original System/360 scheme was simple and in its way elegant.
01F---decodable unambiguously
johnwgilmore0...@gmail.com (John Gilmore) writes:
The original System/360 scheme was simple and in its way elegant.
01F---decodable unambiguously into (multiplexor) channel 0, control
unit 1, and that control unit's device F or 15---was, for example, the
usual device address of the card punch
In
77142d37c0c3c34da0d7b1da7d7ca346c...@nwt-s-mbx1.rocketsoftware.com,
on 02/16/2012
at 02:14 PM, Bill Fairchild bfairch...@rocketsoftware.com said:
They haven't been device addresses since 1983 with the advent of
MVS/XA, in spite of the fact that people who had been calling them
device
In 4f3d172f.9030...@bremultibank.com.pl, on 02/16/2012
at 03:48 PM, R.S. r.skoru...@bremultibank.com.pl said:
Yes, in z/OS (OS/390,...) there are device numbers, not adresses.
No.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see
In 0156585592475057.wa.mvsjes2sympatico...@bama.ua.edu, on
02/14/2012
at 07:06 AM, Dan D mvs-j...@sympatico.ca said:
Subject: 5 Byte Device Addresses?
ITYM 5-digit device addresses[1], unless you're talking about 4-bit
bytes. IAC, the subchannel-set identifier (SSID) is not formally part
Fairchild
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Shmuel Metz (Seymour J.)
Sent: Thursday, February 16, 2012 12:13 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: 5 Byte Device Addresses?
In
77142d37c0c3c34da0d7b1da7d7ca346c...@nwt-s-mbx1
At 13:12 -0500 on 02/16/2012, Shmuel Metz (Seymour J.) wrote about
Re: 5 Byte Device Addresses?:
In
77142d37c0c3c34da0d7b1da7d7ca346c...@nwt-s-mbx1.rocketsoftware.com,
on 02/16/2012
at 02:14 PM, Bill Fairchild bfairch...@rocketsoftware.com said:
But that's ok, since I still call z/OS
hal9...@panix.com (Robert A. Rosenberg) writes:
No Bill is right. OS/VS2 Release 2 WAS MVS like OS/VS2 Release 1 was
SVS. SVS was OS/360 MVT with Virtual Addresses (SVS was a single 16MB
Address Space with which was divided into smaller areas for the
programs to use, just like MVT). MVS made
To stay young requires unceasing cultivation of the ability to unlearn old
falsehoods
(Robert A Heinlein)
Some-how seemed appropriate. Must be time I went back and re-read some of his
work.
Shane ...
--
For IBM-MAIN
Thanks Radoslaw Bob.
I figured there must be some explanation for the additional byte other than
some new extended device ranges.
This is still a DOC problem as the manual simply states these are device
addresses.
Radoslaw, are you saying there is a way of creating an IPLable device with a
I'm wondering when 5 byte UCBs came into service and where this data comes from.
UCBCHAN in a z/OS 1.12 and 13 system's MODGEN still shows as 2 bytes.
How do you get 5 hex characters represented out of 2 bytes?
D IPLINFO
IEE254I 18.36.23 IPLINFO DISPLAY
SYSTEM IPLED AT 17.34.39 ON 01/10/2012
W dniu 2012-02-14 14:06, Dan D pisze:
I'm wondering when 5 byte UCBs came into service and where this data comes from.
UCBCHAN in a z/OS 1.12 and 13 system's MODGEN still shows as 2 bytes.
How do you get 5 hex characters represented out of 2 bytes?
D IPLINFO
IEE254I 18.36.23 IPLINFO DISPLAY
: 5 Byte Device Addresses?
W dniu 2012-02-14 14:06, Dan D pisze:
I'm wondering when 5 byte UCBs came into service and where this data comes
from.
UCBCHAN in a z/OS 1.12 and 13 system's MODGEN still shows as 2 bytes.
How do you get 5 hex characters represented out of 2 bytes?
D IPLINFO
33 matches
Mail list logo
