Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Martin Packer
Right. My (now long gone, I fear) VIOTOES presentation majored on (the then new) DFSMS implementation. In particular ACS Routines and VIOMAXSIZE. But I still thought you had to have some VIO devices defined. Cheers, Martin Sent from my iPad > On 19 May 2016, at 22:53, Gibney, David Allen wrot

Re: What was a 3314?

2016-05-19 Thread Tom Brennan
Not if the jobs run fine. To change the subject beyond VIO: In my experience, arbitrary limits on mainframe resources do nothing more than result in job reruns. Jobs killed because of time/space/spool/etc might need double the CPU because of the rerun after the limits are increased. What a w

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Tony Harminc
On 19 May 2016 at 16:56, Martin Packer wrote: > The whole disk is NOT in your virtual storage; The track window IS (IIRC). Well I wasn't thinking *your* (the caller's) virtual storage; obviously it can't all be there. I was thinking there would be a VSM mapping of the whole device in *some* virtu

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Ward, Mike S
Wasn't the MM the bon number? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Gould Sent: Wednesday, May 18, 2016 11:20 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: What was a 3314? (was: Whither VIO) > On May 18, 2016, at 7:50

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Gibney, David Allen
Very, Very early in implementing SMS (the minimal implementation) is managing VIO. Since we've been SMS for a long time, there aren't even any devices in our EDT(s) for VIO > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Norma

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Norman.Hollander
Maybe a bunch of JCL with UNIT=VIO is a cause to make you fuss? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ted MacNEIL Sent: Thursday, May 19, 2016 1:18 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: What was a 3314? (was: Whither V

Re: What was a 3314?

2016-05-19 Thread Anne & Lynn Wheeler
norman.hollan...@desertwiz.biz (Norman.Hollander) writes: > Track size. We actually used to use a 2305 "drum" definition for VIO. > But if you genned 1 dummy address, you had to gen all 8. Made for a > larger IO-gen. So we would go for the next best tracksize of the > 2314. So- how many 4K pages

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Martin Packer
ESCTVIO (Expanded Storage Criterion Age for VIO) was supposed to control it. Current Migration Age was compared to the Criterion Age. (I think Criterion Age SINGULAR for VIO. Someone correct me if I'm wrong, please.) Cheers, Martin Sent from my iPad > On 19 May 2016, at 22:05, Longabaugh, Rob

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Longabaugh, Robert E
Small track sizes were considered more efficient for VIO because of the number of page slots that had to be used in order to satisfy the allocation. Also VIO would get all 16 extents at once, so saying TRK(1,1) was not better than saying TRK(16). When a job did the VIO allocation, it got the p

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Martin Packer
The whole disk is NOT in your virtual storage; The track window IS (IIRC). Cheers, Martin Sent from my iPad > On 19 May 2016, at 21:45, Tony Harminc wrote: > >> On 19 May 2016 at 01:44, Martin Packer wrote: >> It's sort of come back to me: >> >> A small track size limits the virtual storage w

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Tony Harminc
On 19 May 2016 at 01:44, Martin Packer wrote: > It's sort of come back to me: > > A small track size limits the virtual storage window (probably usually > below the line in 1989 when I looked at this). Or it might've been > cylinder. But I think it was track. > > I'm wondering if anyone else remem

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Ted MacNEIL
Memory is abundant‎ in most shops and cheap overall. So, why all fuss about VIO? Make s decision, implement it, forget it. -teD   Original Message   From: Norman.Hollander Sent: Thursday, May 19, 2016 12:19 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: What was

Re: Mirror/back up your Development DASD

2016-05-19 Thread Ted MacNEIL
You may, if the source changed after the last backup. -teD   Original Message   From: van der Grijn, Bart (B) Sent: Thursday, May 19, 2016 11:24 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: Mirror/back up your Development DASD Andy, we mirror our production to

Re: [EXTERNAL] Re: Two RFE's to please vote for

2016-05-19 Thread Dyck, Lionel B. (TRA)
You can add your comments to the comments section on both RFEs - I think that would be terrific. Thank you -- Lionel B. Dyck (Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200) (005OP6.

Re: Two RFE's to please vote for

2016-05-19 Thread Paul Gilmartin
On Thu, 19 May 2016 13:57:41 -0500, Dyck, Lionel B. (TRA) wrote: >I would like to encourage everyone on these listservs to check out these two >RFE's and please vote for them - let's "nudge" IBM into doing them: > I have voted for both of these. I think. How does one indicate strength of inter

Two RFE's to please vote for

2016-05-19 Thread Dyck, Lionel B. (TRA)
I would like to encourage everyone on these listservs to check out these two RFE's and please vote for them - let's "nudge" IBM into doing them: TSO Pipes http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=47699 also for StreamIO http://www.ibm.com/developerworks/rfe/execute?

Re: Interesting (?) 64-bit assembler surprise

2016-05-19 Thread Phil Smith III
Ah.thanks, Rob and Greg! SYSSTATE is it then. Kinda figured it couldn't be this broken-ish. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-M

Re: Interesting (?) 64-bit assembler surprise

2016-05-19 Thread Greg Dyck
On 5/19/2016 9:54 AM, Phil Smith III wrote: ... The surprise here was that since R14 had something in the top half of the grande register, Bad Things resulted (S0C4) on the line with comment "ADDR SYST LINKAGE TABLE". This seemed.unintuitive. Are we the only ones who were (or have been) surprised

Re: Interesting (?) 64-bit assembler surprise

2016-05-19 Thread Rob Scott
Did you issue a SYSSTATE to inform the assembler which AMODE you are in before the STORAGE macro? Sent from my iPhone > On 19 May 2016, at 17:55, Phil Smith III wrote: > > Doing a STORAGE OBTAIN in 64-bit mode: > > > > STORAGE OBTAIN,LENGTH=WORKLEN > > + CNOP 0,4 > > +

Interesting (?) 64-bit assembler surprise

2016-05-19 Thread Phil Smith III
Doing a STORAGE OBTAIN in 64-bit mode: STORAGE OBTAIN,LENGTH=WORKLEN + CNOP 0,4 + B IHB0012B .BRANCH AROUND DATA +IHB0012L DC A(WORKLEN) .STORAGE LENGTH +IHB0012F DC BL1'' + DC AL1(9*16)

Re: Mirror/back up your Development DASD

2016-05-19 Thread Jesse 1 Robinson
We began mirroring production around 2000. It was several years before we able to sell the idea of mirroring development too. The argument went something like this: -- In our business (utility), program changes are constantly required by the State (PUC) -- We cannot luxuriate in a lengthy perio

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Paul Gilmartin
On Thu, 19 May 2016 13:40:48 +, Roach, Dennis wrote: >Since almost all "3390" DASD resides on FBA arrayed disks, the software exists >and is running in the control units to convert ECKD to FBA requests. > Kinda proprietary, though, whether from IBM or competitors, and hard to make a business

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Norman.Hollander
Track size. We actually used to use a 2305 "drum" definition for VIO. But if you genned 1 dummy address, you had to gen all 8. Made for a larger IO-gen. So we would go for the next best tracksize of the 2314. So- how many 4K pages fit into a track without wasting too much of it? Plus the 23

Re: Mirror/back up your Development DASD

2016-05-19 Thread van der Grijn, Bart (B)
Andy, we mirror our production to a recovery site using Global Mirror. We do back up the NonProd data and send it offsite. The thought is that we do want to be able to recover the other lifecycles at some point but don't have the RTO/RPO requirements that drive a mirror solution. Bart -Or

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread R.S.
W dniu 2016-05-19 o 15:40, Roach, Dennis pisze: Since almost all "3390" DASD resides on FBA arrayed disks, the software exists and is running in the control units to convert ECKD to FBA requests. Not so easy. USB stick use USB "CCW", so without hardware changes on mainframe side there would be

Re: Mirror/back up your Development DASD

2016-05-19 Thread John McKown
On Thu, May 19, 2016 at 9:31 AM, Vernooij, CP (ITOPT1) - KLM < kees.verno...@klm.com> wrote: > Backup Dasd via your laptop to an USB stick? Your company differs a lot > from mine. > ​Well, it is one way to make the mainframe security administrator have a heart attack. Or hire a "wetworks" team to

Re: Mirror/back up your Development DASD

2016-05-19 Thread Vernooij, CP (ITOPT1) - KLM
Backup Dasd via your laptop to an USB stick? Your company differs a lot from mine. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jack J. Woehr Sent: 19 May, 2016 16:14 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Mirror/back up

Re: Mirror/back up your Development DASD

2016-05-19 Thread Ambros, Thomas
Mirroring development because we don't want to toss out a week or so worth of work, also allows our guys to fix apps fast (OK, not fast but you get the idea) if it comes to that. It doesn't cost that much more to do it in our environment so it's worth the investment. Thomas Ambros zEnterprise

Re: Mirror/back up your Development DASD

2016-05-19 Thread Bigendian Smalls
In general .. Mirroring is a recovery technology for infrastructure - should you lose hardware / geographic incident, etc. - If you have any data corruption (intentional or otherwise) - Mirroring just makes it worse.. If you’re serious about having a development environment (Most shops are -

Re: Mirror/back up your Development DASD

2016-05-19 Thread Jack J. Woehr
White, Andy wrote: Currently, we mirror all production but don't mirror the development DASD we back most via VTS but I am pushing or trying that we back up all DASD. At this point in the Moore curve, can't you just stick a USB in your laptop and write a script to back it up? -- Jack J. Woe

Mirror/back up your Development DASD

2016-05-19 Thread White, Andy
Hi people - For companies that mirror their mainframe DASD via XRC, SRDF, how many of them back up the development DASD? Currently, we mirror all production but don't mirror the development DASD we back most via VTS but I am pushing or trying that we back up all DASD. My thoughts about this are

Re: GDG retention

2016-05-19 Thread Vernooij, CP (ITOPT1) - KLM
CA-1 can keep the tape longer, but cannot prevent it from rolling off the GDG. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Brian Fraser Sent: 19 May, 2016 15:49 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: GDG retention Depends

Re: GDG retention

2016-05-19 Thread Brian Fraser
Depends in the tape management system as well. CA-1 can be set and override retention On 19 May 2016 20:58, "Lizette Koehler" wrote: > You need to see if the JCL that creates the JCL have things like > > RETPD= > EXPDT= > > For GDGs, you also need to list the BASE GDG and see if it has NOSCRATCH

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Roach, Dennis
Since almost all "3390" DASD resides on FBA arrayed disks, the software exists and is running in the control units to convert ECKD to FBA requests. Dennis Roach, CISSP, PMP IAM Access Administration - Consumer - Senior Analyst 2929 Allen Parkway, America Building, 3rd Floor, Houston, TX 77019 Wo

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread Clark Morris
[Default] On 18 May 2016 19:31:34 -0700, in bit.listserv.ibm-main ste...@copper.net (Steve Thompson) wrote: >> snip >Makes one very glad to have things like thumb drives that we have >today. Now if I could just get one big enough to IPL z/OS... Would 128 gigabytes be enough. I think I have seen

Re: LOGR Format Level

2016-05-19 Thread Dazzo, Matt
Thanks Mark -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Zelden Sent: Wednesday, May 18, 2016 5:49 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: LOGR Format Level On Wed, 18 May 2016 14:04:59 -0400, Dazzo, Matt wrote: >>Start

Re: Privileged Users (was: EXTERNAL: Re: [EXTERNAL] Re: smp/e sha-2 support?)

2016-05-19 Thread Joel C. Ewing
On 05/18/2016 05:16 AM, Elardus Engelbrecht wrote: > Robert S. Hansel (RSH) wrote: > >> OPERATIONS users actually can grant privileges because they can create >> dataset profiles for any group. And if they own a profile they create, they >> can permit access to it. > RACF by default will allow th

Re: What was a 3314? (was: Whither VIO)

2016-05-19 Thread John McKown
On Wed, May 18, 2016 at 7:33 PM, Edward Gould wrote: > Chales, > > 2321 was a data cell (magnetic strip) hardly could be called DASD) > ​Technically, it was because you could get to a particular "block" of data "directly" (DASD == Direct Access Storage Device) as opposed to a "serial" device lik

Re: GDG retention

2016-05-19 Thread Lizette Koehler
You need to see if the JCL that creates the JCL have things like RETPD= EXPDT= For GDGs, you also need to list the BASE GDG and see if it has NOSCRATCH OR NOEMPTY or SCRATCH or EMPTY Normally a GDG is created with EXPDT=99000 which is Catalog control. Then when the +1 generation is created, i

Re: Product name by module

2016-05-19 Thread Peter Relson
I would have added, just in case the excellent advice previously given didn't pan out: You might well get a clue simply from the name of the load module, as "module prefixes" are pretty carefully managed by most. The prefix might not tell you all you want to know but will at least usually get y

Re: Logrec Analysis

2016-05-19 Thread Tom Conley
On 5/19/2016 4:06 AM, Jake Anderson wrote: Hi, One of our sandbox system took an outage, During the Outage period I found the below messages in Logrec. ABEND S077 PSW 070C1000 84 ABEND S077 PSW 070C1000 84 ABEND S077 PSW 070C1000 84 ABEND S077 PSW 070C1000 84 ABEND S077 PSW 070C1000 84 ABE

Re: GDG retention

2016-05-19 Thread Vernooij, CP (ITOPT1) - KLM
What is the 'no days' parameter? Yes, retention periods in days are an attribute of the managementclass and your storage administrators can tell you how this is implemented at your site. Be aware that both SMS retention and GDG limit work, so if you want only the SMS retention to be effective, y

Re: GDG retention

2016-05-19 Thread Nathan Astle
Hi, Since these GDG were defined with No days Parmeter, So i assume this can be deleted can be anytime. Is there a way to determine the retentions of this GDG ? I hope My storage administrators can answer ? Any suggestions ? On Thu, May 19, 2016 at 3:08 PM, Vernooij, CP (ITOPT1) - KLM < kees.ver

Re: GDG retention

2016-05-19 Thread Vernooij, CP (ITOPT1) - KLM
No, 14 versions/members. When G0015v00 is created, G0001V00 is deleted. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Nathan Astle Sent: 19 May, 2016 11:33 To: IBM-MAIN@LISTSERV.UA.EDU Subject: GDG retention Hello, We have s

GDG retention

2016-05-19 Thread Nathan Astle
Hello, We have some GDG getting created during the SMF processing. Is there a way to determine its retention ? I see the value for GDG as LIM 14. Does that mean the retention would be 14 days ? Nathan -- For IBM-MAIN subscribe

Re: Logrec Analysis

2016-05-19 Thread Lucas Rosalen
Complete description of S077 can be found here: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieah700/m014885.htm Regards, --- *Lucas Rosalen* Em

Re: Logrec Analysis

2016-05-19 Thread Edward Finnell
Yep. CNZ definitely console. R15 where is return code. In a message dated 5/19/2016 4:02:23 A.M. Central Daylight Time, rreyno...@cix.co.uk writes: I am rusty, but I think I saw this from a product trying to allocate a console. --

Re: Logrec Analysis

2016-05-19 Thread Rupert Reynolds
I am rusty, but I think I saw this from a product trying to allocate a console. On 19 May 2016 9:06 a.m., "Jake Anderson" wrote: > Hi, > > One of our sandbox system took an outage, During the Outage period I found > the below messages in Logrec. > > ABEND S077 PSW 070C1000 84 > ABEND S077 PSW 0

Re: Logrec Analysis

2016-05-19 Thread Elardus Engelbrecht
Jake Anderson wrote: >One of our sandbox system took an outage, During the Outage period I found the >below messages in Logrec. >ABEND S077 PSW 070C1000 84 >MODULE CNZINLPA >PSW 070C1000 >the failing CSECT is CNZM1RM Please post the SYSLOG messages during that abend. What is the Register 15

Logrec Analysis

2016-05-19 Thread Jake Anderson
Hi, One of our sandbox system took an outage, During the Outage period I found the below messages in Logrec. ABEND S077 PSW 070C1000 84 ABEND S077 PSW 070C1000 84 ABEND S077 PSW 070C1000 84 ABEND S077 PSW 070C1000 84 ABEND S077 PSW 070C1000 84 ABEND S077 PSW 070C1000 84 ABEND S077 PSW 070C

Re: Old OS/390 1.3 loading in z890

2016-05-19 Thread Brian Westerman
You cannot have any "specialty" engines active when you IPL an OS that doesn't support them. You will need to disable them via the HMC before the IPL. There is another setting that sets the arch level, but I don't think that is your (current) problem. When the 890 first came out, we had some