Re: SSD tiering benefits

[k Zaf]

Thanks for your answer Lizette

We are using various tools like IBM RMF & ASG TMONZOS in z/OS running SMS &
HSM. We actually want to tier some very utilized DB2 v9.1 workload to SSD
and keep all the rest running in spinning VMAX 15000 rpm disks. I am very
interesting in forecasting any potential  CPU benefit beside of course the
better IO. How can we project this?




On 7 August 2013 12:55, Lizette Koehler  wrote:

> What tools do you have?  Do you have SAS SAS/MXG SAS/MICS, Omegamon
> (Tivoli), DISK Magic,  etc...
>
> What version of z/OS, DB2?
>
> What hardware is used?  EMC (VMAX, other), HDS, IBM?
>
> RMF which creates the Type 70  records, should contain some of the
> information you are looking for.  Do you have experience in Performance
> analysis?  If you do, what tools do you normally use?
>
> What will you be using for tiering?   Each hardware vendors have their own
> tiering solutions.
>
> I think DISK magic (fee product) by Intellimagic can do what if analysis.
>
> My understanding is that Tiering is used to move less active data to
> slower devices inside a storage array and put highly accessed data on
> faster devices in the array.  That tiering is used to smooth out the hot
> spots in the array itself.  Or move data from more expensive storage (SSD)
> to less expensive (SATA) devices within the array.
>
> So is your issue hot spots in the array and DB2 requires better
> performance (1 ms or less per transaction)?  Are you mixing SSD to SATA
> type devices and want to ensure high access data is on the fast  device?
>
> What is the problem you are trying to solve with SSD drives?
>
> Do you use DFHSM and DFSMS to manage your storage?  Do you have a mixed
> DFSMS pool with both Spinning and SSD disks?  Is the SMS pool a pure DB2
> table pool or share with non-VSAM?  Are your DB2 Tables currently on SSD or
> spinning disks?  Or on mixed devices? Do you use your Storage groups to
> direct your DB2 tables to SSD?
>
> Lizette
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of K
> Sent: Wednesday, August 07, 2013 1:28 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: SSD tiering benefits
>
> Dear Listers,
>
> We are thinking to implement storage tiering using some SSD volumes for
> some of our very active DB2 tablespaces. Is there any way to measure
> performance improvements for both CPU and IO utilization?  Do you have any
> experience on tiering with SSD in DB2 environment?
>
> Kind regards
> Kostas
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: zHPF

[Ron Hawkins]

Ed,

Actually the TCW has a shorter path length to process on the storage side, at 
least on HDS kit.

On the VSP we see an improvement in response time, tens of microseconds, and an 
increase in max throughput of a VSD (Virtual Storage Director - the MP that 
handles almost everything except data transfer). Noticeable for cache hit 
workloads, but not so much for cache miss.

Ron

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Ed Jaffe
> Sent: Tuesday, August 06, 2013 12:48 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [IBM-MAIN] zHPF
> 
> On 8/6/2013 12:35 PM, gsg wrote:
> > Would like to turn on zHPF.  Is there a way to benchmark this to see what
> we're getting out of it?  Would like to do this in test and then again in
> production.
> 
> The main advantage to zHPF is more (overlapped) I/Os per second, not faster
> per-I/O speed. Therefore, to observe a measurable difference, you will need
> to run one "hellacious" benchmark! :)
> 
> --
> Edward E Jaffe
> Phoenix Software International, Inc
> 831 Parkview Drive North
> El Segundo, CA 90245
> http://www.phoenixsoftware.com/
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: List all dataset in system by HLQ

[Lizette Koehler]

It will depend.  Are you looking for something in ISPF like option 3.4?
Do you want to read a DCOLLECT file that will contain all files on Dasd, 
Migrated?

Do you want to use ISMF?

Do you want to code a program like REXX or COBOL?

Many ways to do what you want.

You can also use the Catalog Search Interface (CSI)

I typically use DCOLLECT with SAS and MXG


Lizette


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Victor Hugo Ochoa Avila
Sent: Sunday, August 11, 2013 8:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: List all dataset in system by HLQ

Hello Group.
I want to know if it is possible to list all datasets on the system but I'm 
just interested to obtain the list by the HLQ.

That way I can get this?

Example.

sys1. *
parmlib. *


Thanks to all

ATTE

Victor

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

List all dataset in system by HLQ

[Victor Hugo Ochoa Avila]

Hello Group.
I want to know if it is possible to list all datasets on the system but I'm 
just interested to obtain the list by the HLQ.

That way I can get this?

Example.

sys1. *
parmlib. *


Thanks to all

ATTE

Victor

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Announcing PCRE for z/OS 8.33 V2

[Ze'ev Atlas]

PCRE for z/OS 8.33 V2 is nnow available on my website www.zaconsultants.net.

New in this version:
Full support for the Posix compatibility module
GETMAIN and FREEMAIN as front ends for malloc and free
pcregrep version that recognizes PDS and PDSE as such and treat them as 
directories and full support for HFS and ZFS


With all the limitations of PCREGREP, I could still say SRCHFOR is dead, long 
live PCREGREP.

ZA

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: The z/OS V2.1 Migration PDF available

[Don Williams]

All double column formatted PDFs drive me crazy.  If I set the view to entire 
page, then the fonts too small. If I set the font large enough to see, then I 
have to yo-yo the pages up and down to read the columns.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Bonno, Tuco
> Sent: Friday, August 09, 2013 6:13 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: The z/OS V2.1 Migration PDF available
> 
> most emphatic "ditto" to what Louis Losee said, with this addendum:  " ...
> and doing so is driving me nuts "
> /s/ tuco bonno;
> Graduate, College of Conflict Management;
> University of SouthEast Asia;
> "I partied on the Ho Chi Minh Trail - tiến lên !! "
> 
> 
> 
> 
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Louis Losee
> Sent: Thursday, 08 August, 2013 10:36 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: The z/OS V2.1 Migration PDF available
> 
> The migration specific format is nice, however, for online reading the dual
> columns cause the reader to constanly page up and down to read each page.
> 
> 
> On Aug 8, 2013, at 4:51 PM, Marna WALLE  wrote:
> 
> > Hi All,
> > Since you mentioned the z/OS V2,1 Migration book being available, I
> thought I would bring to your attention something.  It's different.
> >
> > We've tried a new format for the book, which I'm hoping will make it easier
> to read.  We've divided up the chapters into which migration path you are on
> (R12-> V2.1,  or  R13-> V2.1).  You read only the chapters that apply to you.
> >
> > Here's the layout:
> > Chapter 1:  Introduction   for all users
> > Chapter 2:  General migration actionsfor all users
> > Chapter 3:  Migration from z/OS R13 for R13 -> V2.1 users
> > Chapter 4:  Migration from z/OS R12 for R12 -> V2.1 users
> >
> > R13->V2R1 :  Read Chapters 1, 2, and 3.  Skip Chapter 4.
> > R12 -> V2R1:  Read Chapter 1,2, and 4.  Skip chapter 3.
> >
> > Any feedback on this format is welcome!
> > -Marna WALLE
> > z/OS System Installation
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions, send
> > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Multiple timezones?

[Paul Gilmartin]

On Sun, 11 Aug 2013 17:41:04 +0800, Timothy Sipples wrote:

>I can think of a couple more possibilities:
>
>1. A job scheduler such as IBM Operations Manager for z/VM (IBM program
>number 5697-J10), CA VM:Schedule, etc. might handle this requested use case
>directly.
>
>2. A job scheduler -- on z/OS notably -- could start a job via RSCS or FTPS
>in z/VM. (This is a variation on the Linux idea.)
> 
Of these, how many can handle more timezones than "GMT" and "LOCAL"?
(After all, the topic is "Multiple timezones" and the OP's requirement is
clear.)

>These two possibilities depend somewhat on how smart the scheduler is about
>periodic shifts in local time, e.g. daylight savings time. Many job
>schedulers are pretty smart. I'm generally in favor of scheduling jobs in
>one logical place if possible and absent a compelling reason otherwise.
>
>Note that the local time changes rather often in the world, hence the
>previous paragraph and its "once and once well" view. Operating system
>release X.Y.Z may not have a current understanding of the correct local
>time in a particular geography if enough time passes.
> 
Indeed, the data base must be updated in a timely, hopefully
nondisruptive fashion.  For a Horrid Example, Independent Samoa
advanced its clocks by 24 hours on December 1, 2012.  So:

512 $ TZ=UTC0 date
Sun Aug 11 15:13:36 UTC 2013

513 $ ssh 192.168.0.5 "uname; TZ=Pacific/Apia date"
Linux
Mon Aug 12 04:13:43 WST 2013

Ubuntu Linux had it right, even in anticipation of the change
(admittedly, the system has been restarted since the change,
so I can't vouch for "nondisruptive"), but:

514 $ uname; TZ=Pacific/Apia date
Darwin
Sun Aug 11 04:14:16 WST 2013

OS X (above; admittedly an out-of-support release), Solaris,
and various other Linuxen still haven't got it right 16 months
after the fact.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Linkage Editing VSE Phase in z/OS

[Shmuel Metz (Seymour J.)]

In
,
on 08/09/2013
   at 04:13 PM, Roberto Halais  said:

>We are doing a VSE to z/OS conversion and had to do the following
>since we have no source.

Ouch!

>We put the phase in a z/os pds member (lrecl 80) 

How? If you used FTP, was it in binary mode?

>IEW2359E 240B SECTION FA010 CONTAINS AN RLD WITH AN INVALID ADCON
>LOCATION.
> CLASS = B_TEXT, ELEMENT OFFSET = FFAFFF88

Does VSE support negative offsets?
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FEW VLF RETRIEVES

[Peter Relson]

The general approach for VLF is that a module is eligible for caching only 
after being fetched 10 times.

The functionality of caching is asynchronous. It will be kicked off, via 
POST, after the 10th fetch. It is possible that your test program made it 
through its LOADs before the VLF processing got around to caching the 
module.

Peter Relson
z/OS Core Technology Design

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: z/TPF question

[Timothy Sipples]

ALCS -- a close cousin to z/TPF that runs on z/OS -- could use zIIPs
indirectly. As one example, if you've got an IPSEC connection to/from ALCS
then IPSEC can exploit zIIPs.

My understanding is that z/TPF benefits rather more substantially than most
software products from another specialty engine: SAPs (System Assist
Processors).


Timothy Sipples
GMU VCT Architect Executive (Based in Singapore)
E-Mail: sipp...@sg.ibm.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Multiple timezones?

[Timothy Sipples]

I can think of a couple more possibilities:

1. A job scheduler such as IBM Operations Manager for z/VM (IBM program
number 5697-J10), CA VM:Schedule, etc. might handle this requested use case
directly.

2. A job scheduler -- on z/OS notably -- could start a job via RSCS or FTPS
in z/VM. (This is a variation on the Linux idea.)

These two possibilities depend somewhat on how smart the scheduler is about
periodic shifts in local time, e.g. daylight savings time. Many job
schedulers are pretty smart. I'm generally in favor of scheduling jobs in
one logical place if possible and absent a compelling reason otherwise.

Note that the local time changes rather often in the world, hence the
previous paragraph and its "once and once well" view. Operating system
release X.Y.Z may not have a current understanding of the correct local
time in a particular geography if enough time passes.


Timothy Sipples
GMU VCT Architect Executive (Based in Singapore)
E-Mail: sipp...@sg.ibm.com
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: The z/OS V2.1 Migration PDF available

[Timothy Sipples]

That's not my suggestion. My suggestion is simply to list (and to link to)
all the previous migration documents within the current migration document.
Save the reader a step (or two) in hunting them down.

I don't know if the current migration document already does that but, if
not, it should. It'd be a very short chapter that looks something like
this:


Chapter X: Upgrade to z/OS 2.1 from Operating System Releases Prior to z/OS
1.12

IBM does not support sharing z/OS 2.1 datasets and other operating system
elements with operating system releases prior to z/OS 1.12. Also, IBM may
no longer support your older operating system release. Customers migrating
from operating system releases prior to z/OS 1.12 must prepare and execute
a special migration plan to move to z/OS 2.1. To understand the migration
considerations applicable to upgrades to past releases, please review the
historical migration guides relevant to your circumstances. Here is a list
of historical operating system migration guides:

(Insert list/links here.)

You may wish to engage a specialist services organization or IBM to assist
in preparing and executing your special migration plan. Special migration
plans are broadly split into two types: stepwise migrations and single step
migrations. Stepwise migrations adhere to IBM's previously and currently
supported operating system coexistence combinations. For example, if you
are upgrading to z/OS 2.1 from z/OS 1.10, then a stepwise migration would
involve an initial upgrade from z/OS 1.10 to 1.12 followed by a second
upgrade from 1.12 to 1.21, in sequence. Single step migrations involve
skipping intermediate releases, migrating directly to z/OS 2.1 without
sharing datasets and other operating system elements between the old
release and z/OS 2.1. For perspective, most of the IT industry's operating
systems do not support release coexistence, so a single step migration is
broadly similar in nature to release upgrades among other operating
systems. Customers vary in how they weigh risk and cost factors as they
consider migration strategies, but generally costs tend to increase as the
number of migration steps increases.

To reiterate, IBM may no longer support your older operating system
release. Moreover, IBM never supported sharing datasets and other elements
between operating system releases unless IBM specifically published
coexistence guidance indicating otherwise. You and your services partner
(if applicable) should carefully understand, assess, and manage the risks
involved when preparing and executing your special migration plan.


That'd work!


Timothy Sipples
GMU VCT Architect Executive (Based in Singapore)
E-Mail: sipp...@sg.ibm.com
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

AUTO: Frank Krueger is in vacation. (returning 09/03/2013)

[Frank Krueger]

I am out of the office until 09/03/2013.

I am on leave travelling through Europe. No mail access.
In urgent cases leave message on mobile phone
or contact my manager Bernd Mueller or my team leader Peter Kimmel


Note: This is an automated response to your message  "IBM-MAIN Digest - 9
Aug 2013 to 10 Aug 2013 (#2013-222)" sent on 11/08/2013 6:00:01.

This is the only notification you will receive while this person is away.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN