Gang …
I’m sure there are a few of you out there running your z/VSE on DS6800 storage. As you are probably aware, these are going off IBM’s maintenance schedule at the end of September. With z/VSE, other than buying a fairly expensive DS8xxx series device, there seems to be only the Storwize as a reasonable solution. Unfortunately, the entry point for this is not cheap if you don’t already have a SAN fabric in place. The other alternative I can think of is to have IBM maintain the DS6800 off schedule (RPQ) or go to a third party service provider. Our past experience with third party providers has not been the best. Anyway, I was wondering if there’s anything out there I should be considering. TIA for your thoughts.
Kevin P Corkery
Independent Consultant
Voorhees, New Jersey
_______________________________________________
VSE-L mailing list
VS...@lists.lehigh.edu
https://lists.lehigh.edu/mailman/listinfo/vse-l
Kevin,
I’ve been looking at this for a while, now. I have a quote for a Storwize V5000, including two SAN switches, for under $50k. Less than ¼ of the DS8870 that was originally proposed. Although I would prefer the DS8870 for ease of installation/migration.
Unfortunately, it would require an ECKD to FBA conversion. My new management doesn’t seem to understand what they requires in terms of time or risk… I doubt any decisions will be made by September 30, though, so we’re sticking with our current 3rd party main provider. They say they can continue to support the DS680 without any problems.
Dave
Dave Stuart
Principal Information Systems Support Analyst
Information Technology Services
County of Ventura, CA
I’m thinking that the leverage on all of this needs to be the RPQ from IBM to continue to maintain the DS6800. I’ll bet over 3 years it would cover a lot of the cost of the replacement system.
A few year ago I was working with someone that had a MP3K and wanted to attach a Shark they had acquired as excess from a related company. Since they only had 1/3 of the internal disks populated, we instead populated the other internal drives really cheap, and it had minimal impact on their maintenance fees for the MP3K. It was completely paid for by less than 3 months maintenance for the Shark, which was ultimately sold for scrap. Also, the internal SSA drive on the MP3K run like lightning, only downside is that they use processor storage as cache.
From: VSE-L [mailto:vse-l-bounces+kcorkery=live...@lists.lehigh.edu] On Behalf Of Mike Moore
Sent: Tuesday, April 07, 2015 1:09 PM
To: VSE Discussion List
Subject: RE: DS6800, Options post-September?
We got into a DS8870 for $113k with 5 years of maintenance. We were paying $110k per year maintenance on our SHARK.
Mike Moore
IT Manager
Alabama Judicial Datacenter
300 Dexter Avenue
Montgomery, Alabama 36104
“This is the final test of a gentleman: his respect for those who can be of no possible service to him.” – William Lyon Phelps
From: VSE-L [mailto:vse-l-bounces+mike.moore=alacou...@lists.lehigh.edu] On Behalf Of Duerbusch, Tom
Sent: Tuesday, April 07, 2015 12:04 PM
To: VSE Discussion List
Subject: Re: DS6800, Options post-September?
The price we got for a DS8870 was about $25K more over 3 years than our DS6800 when IBM maintenance was factored in.
Tom Duerbusch
THD Consulting
Dave …
We’re getting a much higher quote then that with the V3700. It’s the switches that really run up the price. As for FBA, that’s not a problem for us. When we converted from FBA to ECKD (9336-to-RAMAC2) we adopted a neutral policy in all our systems. This was made pretty easy by the fact that 99% of all files on out system as VSAM; real VSAM, not managed-SAM. We changes all the IDCAMS definitions to allocate datasets based on RECORDS as opposed to BLOCKS or CYLINDERS/TRACKS. Going back the other way is only just moving the files from one device to another, all the JCL would continue to work as is.
… Kevin
From: VSE-L [mailto:vse-l-bounces+kcorkery=live...@lists.lehigh.edu] On Behalf Of Stuart, David
Sent: Tuesday, April 07, 2015 1:11 PM
To: VSE Discussion List
Subject: RE: DS6800, Options post-September?
Kevin,
Kevin,
A lot of our data is VSAM, too. We have a mix of VSAM and managed-SAM. Most are allocated by records, even the managed-SAM, but I have some that are allocated by cylinders (my predecessor’s legacy). And I have several volumes of DA files, blocked at 6184 bytes. Those will take some work…
Dave
We moved from the DS6800 to an HP P9500 about 3 years ago. Working great so far…
____________________________________
Andy Engels
IS Team Leader – Technology Infrastructure
IMRF
Oak Brook, IL
630-368-5346
From: VSE-L [mailto:vse-l-bounces+aengels=imrf...@lists.lehigh.edu]
On Behalf Of Kevin Corkery
Sent: Tuesday, April 07, 2015 11:32 AM
To: Newsgroup, VSE
Subject: DS6800, Options post-September?
Gang …
------- DISCLAIMER -----------------------------------------------------------------------------------------------------------------------
This message and any attachments are confidential to the ordinary user of the e-mail address to which it was addressed and may also be privileged. If you are not one of the addressees you may not copy, forward, disclose or use any part of the message or its attachments. If you have received this message in error, please notify the sender immediately by return e-mail and delete it from your system. The sender does not accept liability for any errors or omissions in the context of this message that arise as a result of Internet transmission. Sender accepts no liability for any damages caused by any virus transmitted by this email. Any opinions contained in this message are those of the author and are not given or endorsed by the Rock River Water Reclamation District (RRWRD) unless otherwise clearly indicated in this message and the authority of the author to so bind the RRWRD referred to is duly verified.
------- DISCLAIMER --------------------------------------------------------------------------------------------------------------------------
Greetings,
I am getting this message in one of my CICS startups trying to enable MacKinney to CICS) to work.
The doc tells me to add the // OPTION SYSPARM='TCPIP ID' (00 in this case.)
That did not help. Where should I look?
Thanks
F2 0124 BSD100I IPNRBSDC 01.05 F 09/15/14 15.47 01756000 007C
F2 0124 DFHSO0117 DBDCCICS
Unable to determine the TCP/IP host name. Language Environment return
code X'00000079', reason code X'000000FF'. TCP/IP services are
unavailable.
F2 0123 EZA200I EZATRUE has successfully been started.
Suleiman Shahin
We have had ours on 3rd party for a couple of years. So far so good. All IBM did was swap parts. As long as the parts are available anybody can do that.
Dennis McLoud
Systronics
From: VSE-L [mailto:vse-l-bounces+dmcloud=systroni...@lists.lehigh.edu] On Behalf Of Kevin Corkery
Sent: Tuesday, April 07, 2015 11:32
To: Newsgroup, VSE
Subject: DS6800, Options post-September?
Gang …
Suleiman,
You need a Define Name statement in your IPINIT00.L member for that IP address.
For one of my Systems, I have the following:
DEFINE NAME,NAME=TCPENTERPRS,IPADDR=157.145.4.151
The Define Name statement can also be entered from the Console, via a MSG xx,DATA=DEFINE NAME…
Dave
Dave Stuart
Principal Information Systems Support Analyst
Information Technology Services
County of Ventura, CA
Yep. If we went 3rd party we’d likely purchase a bunch of drives and maybe an extra 1750-522 for spare parts.
From: VSE-L [mailto:vse-l-bounces+kcorkery=live...@lists.lehigh.edu] On Behalf Of Dennis McLoud
Sent: Tuesday, April 07, 2015 2:33 PM
To: 'VSE Discussion List'
Subject: RE: DS6800, Options post-September?
We have had ours on 3rd party for a couple of years. So far so good. All IBM did was swap parts. As long as the parts are available anybody can do that.
I think my maintenance provider is doing that behind the scenes.
Dave
I guess you’re right about that. In any case, I would like to “fill out” the existing unit. Adding another rank I could define them as SCSI and use the direct connect feature to migrate to an FBA environment on the existing box. This would set-up any move at a later date since I don’t see an ECKD capable box anywhere in our future.
Interesting idea, Kevin. I like it. If you have z/VM, you could start doing something like that, too.
Unfortunately, I don’t see anything like that happening here.
Suleiman,
I had the same problem with a CICS/TS region that had been running absolutely clean. All of a sudden, I needed the Define Name.
Dave
What MacKinney software?
Frank M. Ramaekers Jr.
From: VSE-L [mailto:vse-l-bounces+framaekers=ailif...@lists.lehigh.edu] On Behalf Of Suleiman Shahin
Sent: Tuesday, April 07, 2015 1:23 PM
To: VSEL VSEL
Subject: DFHSO0117
Greetings,
Mackinney’s “Batch to CICS”?
Frank M. Ramaekers Jr.
From: VSE-L [mailto:vse-l-bounces+framaekers=ailif...@lists.lehigh.edu] On Behalf Of Suleiman Shahin
Sent: Tuesday, April 07, 2015 1:23 PM
To: VSEL VSEL
Subject: DFHSO0117
Greetings,
Under z/VSE 5.2 there are some fixes that need to be applied to CSI TCP/IP in order for this to work. Tried to find them but couldn’t but I’ll poke around a little more. I used the CICS external call interface instead but I did ultimately test the TCP/IP capability after the patches and it worked. OK, try ZP15F538 from the CSI web-site (this was more than 6 months ago so check for pre-reqs and superceeds).
One thing we ran into was the limited cache. I think we had around 9.?? TB of disk. Once we started really cranking images into the 6800, the 4GB of cache became a problem. I had a batch job on VSE that ran 17 hours suddenly. Because 1 GB of cache was used for management. The imaging system glommed on to a ton more.
The new SAN has 32GB and that 17 hour job shrunk to 22 minutes. Doesn’t use much data base or CPU. Sequential file to sequential file. Pretty simple.
We’re also running 57 TB of shared disk now. The Z is only using 2.1 TB of that………..
____________________________________
Andy Engels
IS Team Leader – Technology Infrastructure
IMRF
Oak Brook, IL
630-368-5346
If you have 1.5G you have to go to CSI, but try ZP15G104, ZP15G105, ZP15G106 or supersedes.
The latest zaps also include an enhancement to socket close performance. I am not sure that CSI documented how to make socket close happen immediately after applying the zap, but I think it is by using CLST=0 - ask CSI to confirm that if you are interested. My notes say that came with ZP15F108 or whatever the 1.5G equivalent is. All socket close requests in CICS must be synchronous as that is the only option available to it. If a socket close request is slow to complete, it will block the SO subtask and slow down all CICS socket I/O requests causing task waits and response times to be longer than normal.
BTW the return code X'79' is the TCP/IP errno value. In this case it is EINVAL, which is not very helpful as it says that TCP/IP was not happy with one of the parameters passed by CICS, and only the trace would help to show what CICS was trying to do at that time. Knowing what the real cause is helps a lot.
Mike
Used to be called:
CICS/CEMT from Batch
With MacKinney Batch to CICS (MBC) you can quickly send commands from your batch jobs to your CICS regions to coordinate file access, dynamically enable or disable programs and transactions, kick off transactions, send terminal messages and more.
Paul L’Heureux
Department of Corrections | Central Office | BIT
1920 Technology Parkway
Mechanicsburg, PA 17050