Hello Glenn,
I agree with Kevin and Tony.
If the vendor of the new product needs JCL turned into scripts, the vendor should have the process defined.
In the meetings, this is where your Tech consultant, wears the Black Hat, and tells the vendor that right in front of management.
Played the bad guy to vendors, it works.
Edward M. Martin
Aultman Health Foundation
HealthQuest
330-363-9666
Internal EXT 39666
-----Original Message-----
From: VSE-L [mailto:
vse-l-bounces+edward.martin=
aultm...@lists.lehigh.edu] On Behalf Of Kevin Corkery
Sent: Tuesday, July 26, 2016 9:14 AM
To: 'VSE Discussion List'
Subject: RE: JCL Conversion
Just my $0.02 on Tony's response. I would think that if a vendor was proposing moving something from z/VSE to a Windows environment and providing an infrastructural items that Tony enumerates, a solution for handling JCL would need to be in their wheelhouse. If, by your question, it is not, then RRRRRuuunnnnnnnnnnnnn!!!!!!!
-----Original Message-----
From: VSE-L [mailto:
vse-l-bounces+kcorkery=
live...@lists.lehigh.edu] On Behalf Of Tony Thigpen
Sent: Tuesday, July 26, 2016 9:04 AM
To: VSE Discussion List
Subject: Re: JCL Conversion
I am sure there are some out there that would say "yes, we can do that for $xxx", but the nature of the beast is that they are just too different.
The JCL is just a small part of any move to Windows. The executiables, the utility programs (sort, idcams, ditto, etc.), vsam files, and the way print is handled is the big items. The JCL is just a support structure.
Based on your question, I don't think you have that much experience with VSE, and maybe not z/OS. So, I guess someone asked you "can you do this?" If so, tell them 'No'. You don't want to be the one that costs a company millions leaving them with a sub-standard system that may "work", but will not get the job done. We have seen that many times.
Most of the time the dollars are wasted and the conversion scraped. Many times, the company goes under because of the money-pit they end up with.
Tony Thigpen
Glenn Schneck wrote on 07/25/2016 01:38 PM:
> Hello all! I am looking for any information on converting existing
> JCL to Windows scripts. Anyone have any information?
>
> Thanks!
>
> Glenn
>
>
> _______________________________________________
> VSE-L mailing list
>
VS...@lists.lehigh.edu
>
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2flists
> .
lehigh.edu%2fmailman%2flistinfo%2fvse-l&data=01%7c01%7cEdward.Martin%
>
40aultman.com%7c04ecd17fef5a4eca104508d3b556a792%7cb91830d1006447288b5
> 657e8943c3565%7c0&sdata=43z7dv3bTDkpnxLIgppOZge6Gq4GR%2fWneY8b3YOBVbc%
> 3d
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2flists.lehigh.edu%2fmailman%2flistinfo%2fvse-l&data=01%7c01%7cEdward.Martin%40aultman.com%7c04ecd17fef5a4eca104508d3b556a792%7cb91830d1006447288b5657e8943c3565%7c0&sdata=43z7dv3bTDkpnxLIgppOZge6Gq4GR%2fWneY8b3YOBVbc%3d
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2flists.lehigh.edu%2fmailman%2flistinfo%2fvse-l&data=01%7c01%7cEdward.Martin%40aultman.com%7c04ecd17fef5a4eca104508d3b556a792%7cb91830d1006447288b5657e8943c3565%7c0&sdata=43z7dv3bTDkpnxLIgppOZge6Gq4GR%2fWneY8b3YOBVbc%3d
CONFIDENTIALITY NOTICE: This e-mail (including the information it contains and attachments) is a business communication intended for the authorized use by the person who requested it, or for the authorized use by the intended recipient to perform an employment duty or business function. This e-mail may contain confidential, privileged, or proprietary information, including (but not limited to) Protected Health Information covered by the Health Insurance Portability and Accountability Act (HIPAA). It also may be protected by the Electronic Communications Act. If you received this e-mail by mistake, either directly or inadvertently as a recipient on a copied or forwarded e-mail, promptly notify us by return e-mail. Destroy this e-mail, the information, and attachments you received by mistake. You must not print, use, forward, or disclose to any third party by electronic, written or oral means any information you received by mistake. We do not waive any privilege. We may take le
gal steps or other appropriate action, as needed, to protect the confidentiality and privilege of any information inadvertently disclosed.