Hi,
Is somebody know how to calculate the average dasd response time from WLM
Period's connect/disconnect/wait/iosq times ?
On my shop, we use SYSVIEW. In his option WLM, we can see the I/O metrics but I
don't understand how is calculated the average response time.
For the example, how is
On Tue, Nov 22, 2022 at 01:40:47PM +, Seymour J Metz wrote:
> My experience was that I had to read the fiche for things that should
> be in the PLM and I had to read the PLM for things that should have been
> in the macros or services manual.
I read many a fiche when writing UCLA/IPC.
I think that you are missing the fact that you can VERY easily add GRS ring via
a couple of really inexpensive FICON cards. You may already even have them
just sitting there unused on your processor. In any case, you can buy them
even on eBay now for next to nothing.
The GRS ring (not
On Fri, 25 Nov 2022 12:12:36 -0800, Leonard D Woren
wrote:
>
>I've long wondered why. And in the 1980s (I think), IBM actually had
>a disk for s370 which was FBA, but only supported by DOS/VS.
>
3310 and 3370. Also supported by VM/SP. (Certain models of 3370 could also
attach to System/38)
Joel C. Ewing wrote on 11/24/2022 9:38 PM:
[...]
If volumes are SMS, all datasets must be cataloged and the
associated catalogs must be accessed from any system that accesses
those datasets. If the systems are not in a relationship that
enables proper catalog sharing, access and possible
Paul Schuster wrote on 11/24/2022 11:13 PM:
TRKCALC knows everything.
Second best, I dug up this exec from the 1990s that should get it right:
/* Rexx */
Parse Arg kl dl .
"XPROC 2 KL DL DEBUG"
If dl = "" Then Do
Say "Usage: BLK3390 keylen datalen [DEBUG]"
Exit 2
End
c = 10
If kl = 0
Seymour J Metz wrote on 11/25/2022 6:23 AM:
You have 80 terabytes?
At least. You can get there pretty fast with 10 and 12 TB disks, in
pairs for backup purposes. But the pressure is on to switch to Linux
because I'm just about out of drive letters on Windows, and I already
have some disks
As someone who has delved deeply into this subject for different reasons, and
without "inside" knowledge, here's what I have learned or intuited:
1. Logical volumes are entirely self-contained (think of them as files),
allocated from the arrays with all required space needed to hold metadata,
On 11/23/2022 5:19 PM, Leonard D Woren wrote:
It's time to use this brainpower for better things than optimizing the
arrangement of angels on a pinhead. Just throw more hardware at it
and move on.
We have standardized on a mixture of Mod-27 and Mod-216 volumes for all
of our SMS-managed
On 11/25/2022 6:22 AM, Don Parrott wrote:
We created a DASD only SYSPLEX about 3(?) years ago on a z/14 primarily to facilitate
PDSE sharing between the PROD and DEVL lpars. I would have rather had a coupling
facility for a full sysplex, but we did not have one.There was a ton of work to
That's why off-site backup, outside of the range of regional disasters, are so
important. Data centers have been destroyed by earthquakes, industrial
accidents and weather in the past, and RAID offers no protection.
Hot backup and its cousins are no longer arcane topics.
--
Shmuel (Seymour
The MI is an object oriented language at a high level than Pascal P-code. I
don't know how it compares to JVM byte code. The key feature is that you can
only call a program object and that the objects are black box.
You might want to read up on capability based machines and browse the manuals
Would you consider that the applications were more like P-Code ( pseudo-code )
... not that much different in principle to JAVA today ?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
send to lists...@listserv.ua.edu, not the group.
On Fri, Nov 25, 2022 at 9:24 AM Don Parrott wrote:
>
> SET IBM-MAIN NODIGEST
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to
AFAIK the replacement for i still uses the same paradigm as the S/38; a program
requests compilation of MI code (with name changes since S/38) and the compiled
code is a black box object; you can invoke it but you can't change or even
inspect it. Whether it compiles to POWER code or to some
Thanks for the info Dana,
"For the record, there are no i-Server, or p-Servers any more. IBM Power
servers can run any combination of IBMi, AIX and Linux LPARS concurrently."
This reduces the IBM "mainframe" product line to just two; Z and Power Servers.
( or is it one in reality ? The
SET IBM-MAIN NODIGEST
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
On Thu, 24 Nov 2022 09:27:41 -0600, Paul Gorlinsky
wrote:
>
>It would also make good business sense that IBM would share as much tech as
>possible between the product lines of i-Server, p-Server and z-Server... in
>order to save costs.
>
For the record, there are no i-Server, or p-Servers
I had to explain to some people that RAID disks do not give 100%
protection. If you delete a file or corrupt a file, then the RAID will
*reliably* make the change to delete or corrupt all copies of the data.
We used z/VM and ran z/OS on top of it. We could share volumes read only
and so people
You have 80 terabytes?
One reason is IBM's refusal to accept and implement the SHARE requirement to
support FBA in MVS for both access methods and IPL. However, IBM did add new DD
parameters to allow the OS to do some of the calculations for the user.. Even
with that, however, there would
Gord,
We created a DASD only SYSPLEX about 3(?) years ago on a z/14 primarily to
facilitate PDSE sharing between the PROD and DEVL lpars. I would have rather
had a coupling facility for a full sysplex, but we did not have one.There
was a ton of work to setup the CTC pairs between the
SET IBM-MAIN NODIGEST
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
No, but the controller does. When the access method uses Locate and Define
Extent, the controller pulls full tracks into the cache.
There's also a a/OS authorized service for accessing SCSI DASD via FCP; I
believe that works by sector, but, again, the controller does things behind the
scenes
Best practice is to not share what you can't protect. MIM, GRS ring, etc., can
help, but sharing of PDSE or Unix files can lead to data corruption even with
serialization, and sharing between security domains might not only lead to
compromisng data but to legal issues, both civil and criminal.
I don't even trust myself; belt and suspender policies are highly useful in a
development environment. The key is to deploy safeguards that don't get
underfoot. Have you never had to revert a change?
Auditors serve a useful purpose. Get rid of the bad ones, not all.
--
Shmuel (Seymour J.)
Additionally, there's the generic class DASDVOL that may be applicable/helpful.
Used to be $DASDI. in FACILITY... I think?
- KB
--- Original Message ---
On Friday, November 25th, 2022 at 6:11 PM, Ituriel do Neto
<03427ec2837d-dmarc-requ...@listserv.ua.edu> wrote:
> Hi,
>
> In the
Hi,
In the past, i used to work for a tiny shop with the same distribution you
indicated.
Only three Lpars and no Sysplex, no GRS.
At that time, we choose to make all disks available to all Lpars, but there was
a segregation of Production, Development, and Sysprog volumes done by VOLSER.
I
27 matches
Mail list logo
