If you convert to the new Country Multiplex Pricing, you only pay for
1 version of Cobol despite having multiple versions available for
compiling.

 
http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&supplier=897&letternum=ENUS215-230

On Tue, Aug 30, 2016 at 11:45 AM, Lizette Koehler
<stars...@mindspring.com> wrote:
> So if EOS is announced - the most that means is no new fixes for that version 
> of
> the Compiler.  I do not think the compiler shuts itself down.  You can still 
> use
> it.
>
> Note:  I think IBM has altered the pricing on V3/V4 Enterprise Cobol Compiler 
> to
> be the same as V5 Enterprise Cobol compiler.  I am not sure if there was a 
> cost
> increase from V5 to V6 Enterprise Cobol Compiler.  So if cost is a factor, I
> think that has already been handled by IBM.
>
> Depending on what your requirements are, here are some things to look at for 
> an
> upgrade
> 1)  Do you have a source management tool that needs to be altered for the new
> compiler? (Change Man, Endevor, CA Telon, etc...)
>         a) New work would use the new compiler
>         b) old work may use the older compiler
> 2)  What are the new Reserve words in the Compiler and are any current 
> programs
> using them?
> 3)  What COBOL options are in place today, and how does the new compiler alter
> that environment
>         a) In a previous release PMAP is LIST on the compiler options
> 3)  Are the benefits of the new Compiler worth the effort to upgrade? (Most 
> have
> indicated yes)
> 4)  Do you have very complex Programs that need TLC to upgrade?  These could 
> be
> including, CICS, IMS, MQ, DB2 type of programs
> 5)  How long does your company require for a checkout for the new compiler?
>         a) Some shops have mandatory recompile Everything under the new 
> compiler
>         b) Some shops have compile the worst case programs as a test case of 
> the
> new compiler
>         c) Some shops have performance requirements for a new compiler.  
> Program
> must run the same way or better.  Not worse
> 6)  Will you need to run only new work through the V5/V6 Enterprise Cobol
> compiler while old work gets the current compiler?
>         a)  This may be needed as the older programs have to be evaluated and
> that takes time.
> 7)  How long will this process take.  As other have pointed out - the BIG 
> CLOCK
> Starts the minute you being this process.  Work with your IBM Representative 
> on
> actual requirements.
> 8)  Older programs running do not necessarily need to be recompiled.  That is
> why the new Parmlib member was created.  To allow everything to run as is.
>         a) When a program gets a fix - then the company should look are the
> recompile with the new compiler.
>
> There may be other considerations.
>
> To upgrade the compiler is easy.  Running parallel processes to ensure
> everything is working the same or better is what takes time.  And what
> application group is not busy and has the time to do the checkouts?  Answer -
> very few.
>
> And because the LOAD lib for the compile MUST be a PDS/E, that has had a new
> level to a simple roll out.
>
> I hope this helps
>
> Lizette
>
>
>
>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
>> Behalf Of Lopez, Sharon
>> Sent: Tuesday, August 30, 2016 7:12 AM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: Cobol V5/V6
>>
>> My concern is that IBM will announce EOS for Enterprise Cobol 4.2 and we will
>> not be ready.
>>
>>
>>
>> > -----Original Message-----
>> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
>> > On Behalf Of Lizette Koehler
>> > Sent: Tuesday, August 30, 2016 6:29 AM
>> > To: IBM-MAIN@LISTSERV.UA.EDU
>> > Subject: Re: Cobol V5/V6
>> >
>> > We are not planning to upgrade to Cobol V5/6 until after z/OS V2.2 is
>> > installed because that is the only level where IEFOPZxx is available.
>> >
>> > Once that is available we will use the concatenation function in this
>> > parm to use a PDSE dataset prior to a PDS dataset in our Production batch.
>> >
>> > z/OS 2.2 was announced Aug 2015. It requires a Z10 or newer processor.
>> > Here is the announcement letter.
>> >
>> > http://www-01.ibm.com/common/ssi/cgi-
>> > bin/ssialias?subtype=ca&infotype=an&appname
>> > =iSource&supplier=897&letternum=ENUS215-267#availx
>> >
>> > or tinyurl
>> >
>> > http://preview.tinyurl.com/p64hluq
>> >
>> > Lizette
>> >
>> >
>> > > -----Original Message-----
>> > > From: IBM Mainframe Discussion List
>> > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lopez, Sharon
>> > > Sent: Tuesday, August 30, 2016 6:20 AM
>> > > To: IBM-MAIN@LISTSERV.UA.EDU
>> > > Subject: Cobol V5/V6
>> > >
>> > > Have a lot of shops migrated to COBOL V5/V6?  Does anyone have a
>> > > project plan they would like to share with me?  Is the IEFOPZxx
>> > > member only available in z/OS 2.2?
>> > >
>> > > Thanks to everyone in advance.
>> > >
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Reply via email to