Re: Implicit VVDS creation

2014-02-08 Thread Ted MacNEIL
‎As for location, in a distant galaxy long ago, SLED DASD liked VTOC and  VVDS (did that exist then?) located in the middle of  the volume to  minimize head movement. (Nod if you agree.) That pra It stopped nattering long before RAID came out. 3380-K was when IBM stopped recommending it. Sent from

Re: SYSB-II

2014-02-08 Thread John McKown
Two reasons we don't get DB2. 1. It costs money. 2. I.T. management despises z/OS. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Implicit VVDS creation

2014-02-08 Thread Skip Robinson
Aside from the how of creating your own VVDS, I'm concerned about the why. OK, if an existing VVDS fills up, that's a why. Otherwise, you might consider creating your own VVDS at the outset if the default size or location is likely not appropriate for the volume. For example, a huge volume like

Re: SYSB-II

2014-02-08 Thread Dale R. Smith
On Fri, 7 Feb 2014 07:17:54 -0600, John McKown wrote: >The "problem" with data access here is that _all_ our data is stored in >VSAM KSDS data sets. As opposed to, say, Windows where it is on MS-SQL >Server and Oracle databases. So every time the users want a data extract, >they must request tha

Re: Sysplex Common Time Source

2014-02-08 Thread Dale R. Smith
On Sat, 8 Feb 2014 20:27:09 +0800, Timothy Sipples wrote: >Shane opines: >>Bloody typical. > >I posit that my reply was detailed, helpful, truthful, and complete. I'll >leave it at that. > > >T

Re: Automating SAD

2014-02-08 Thread Ed Jaffe
On 2/8/2014 6:31 AM, Jake anderson wrote: Could someone throw light on the best practices or some efficient process followed at your shops. My advice is to use multiple DASD data sets to get as much parallel I/O as possible. Also, human interaction is responsible for tremendous delays. Elimin

Re: Automating SAD

2014-02-08 Thread Lizette Koehler
Jake, What verion(s) of z/OS are you working with? It would help to know what level you are asking about Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Jake anderson > Sent: Saturday, February 08, 2014 7:31 AM > To: I

Automating SAD

2014-02-08 Thread Jake anderson
Hello Group, We have been taking a z/OS SAD to a dasd in our shop and it is also little time consuming since the LPAR in a wait state has to wait for re-ipl until the SAD process completes. I have been reading through : http://pic.dhe.ibm.com/infocenter/zos/v1r13/index.jsp?topic=%2Fcom.ibm.zos.r1

Re: Sysplex Common Time Source

2014-02-08 Thread Timothy Sipples
Shane opines: >Bloody typical. I posit that my reply was detailed, helpful, truthful, and complete. I'll leave it at that. Timothy Sipples GMU VCT Architect Executive (Based in Singapore) E-Ma

Re: VSAM Data Access (and SYSB-II)

2014-02-08 Thread Timothy Sipples
John McKown writes: >But it does not refute the "z/OS is hard to get data out of" >thoughts because it induces the "see, if data access on z/OS >were easy, we'd have access to _current_ data and not need to >be doing all this data duplication into an easy to access >system like MS SQL Server". As

Re: ARM contention

2014-02-08 Thread Lizette Koehler
Have you reviewed SYSLOG or the HMC? Have you looked at LOGREC? Did you do an SVC dump (any will do)? Without knowing the chain of events, it is hard to understand what occurred. If you still have the syslog from then, or the Logrec, or any SVC DUMP, you can try to piece together the events tha

ARM contention

2014-02-08 Thread mf db
Hello Experts, In of my Sandbox system, we had a situation where ARM held the TCPIP address space. Due to which OSA got deactivated and I had to recycle. Is there a way to prevent this situation in future. Apology, I couldn't capture the error message. Peter ---