I think the op question was about the file system name during the COBOL
installation. Do you need to setup a new path, use an existing path or how
does COBOL 5.2 know to use the COBOL 5.2 path vs. the other path? Or is the
file system not needed during comp/lked?
MOUNT FILESYSTEM('#dsn')
MOUNTPOINT('/usr/lpp/IBM/cobol/igyv5r2')
MODE(RDRW) /* can be MODE(READ) */
TYPE(ZFS)
Or I misunderstood the op question.
Lizette
-----Original Message-----
>From: Bill Woodger <bill.wood...@gmail.com>
>Sent: Mar 2, 2016 2:21 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: COBOL Install
>
>The JCL for the compiles are substantially different, so your customer will
>have to select the correct option from a panel you provide (presumably).
>
>There is no direct impediment to running two different COBOL compilers
>concurrently. You'll probably have one just sitting entirely in a STEPLIB, and
>the other (the more common) installed for more widespread use.
>
>With the release of V6.1 I'm sure that's been considered as an alternative to
>V5.2...
>
>
>On Wednesday, 2 March 2016 06:08:20 UTC, Mainframe Mainframe wrote:
>> Thanks for reply. You Mean, customer will be able to use both version of
>> cobol. v4.2 and v5.2
>>
>> On Wed, Mar 2, 2016 at 11:35 AM, David Crayford <dcrayf...@gmail.com> wrote:
>>
>> > On 2/03/2016 2:02 PM, Mainframe Mainframe wrote:
>> >
>> >> Hello Group,
>> >> We have COBOL V4.2 in our system and recently we
>> >> installed v5.2 as well. Now my customers want to use both of these
>> >> version.
>> >> Is it possible or as we installed v5.2 on same file system, they can use
>> >> only v5.2 not the v4.2
>> >>
>> >
>> > Of course. Just setup JCL that STEPLIB the compiler libraries. LE should
>> > have no problems at runtime.
>> >
>> > Any suggestion please.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
