Hello All,
Problem has been resolved. I think somebody messed up SIGYHFS
which was causing issue and its been corrected now. Thanks all for help.
On Tue, Mar 15, 2016 at 4:25 AM, Andrew Rowley wrote:
> In your initial question you showed path
>
In your initial question you showed path
/Service/usr/lpp/cobol/../../demo/oosample/Check.j
".." refers to the parent directory, so doesn't this resolve to
/Service/usr/demo/oosample/Check.j
//
Andrew Rowley
On 15/03/2016 2:41, venkat kulkarni wrote:
Here also its same
Here also its same /usr/lpp/cobol/demo/oosample/Check.java. This file
should be created during applying process of this FMID.
On Mon, Mar 14, 2016 at 8:02 PM, Doug Henry wrote:
> On my system I can see this file name is
> /usr/lpp/cobol/demo/oosample/Check.java. Unless
No, its mounted under R/W .
On Mon, Mar 14, 2016 at 7:26 PM, Staller, Allan wrote:
> Check file permissions. Is the zFS file read only?
>
>
> I can clearly see all file systems are mounted correctly .
>
> HFS 190 ACTIVE
On my system I can see this file name is
/usr/lpp/cobol/demo/oosample/Check.java. Unless you truncated your display
yours end with j instead of java.
Doug
On Mon, 14 Mar 2016 10:52:52 +0530, venkat kulkarni
wrote:
>Hello All,
> I can clearly see all
Check file permissions. Is the zFS file read only?
I can clearly see all file systems are mounted correctly .
HFS 190 ACTIVE RDWR 03/06/2016 L=138
NAME=OMVS.MVS1.ZOS13.SIGYROOT23.40.14Q=138
PATH=/Service/usr/lpp/cobol
List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Mainframe Mainframe
Sent: Friday, March 11, 2016 10:17 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cobol Install FS issue
Thanks for reply. I am installing Cobol in new file system, I don't find any
issues with this directory structure. I tried
;
> >Sent: Mar 11, 2016 8:16 PM
> >To: IBM-MAIN@LISTSERV.UA.EDU
> >Subject: Re: Cobol Install FS issue
> >
> >Thanks for reply. I am installing Cobol in new file system, I don't find
> >any issues with this directory structure. I tried all but not able to come
DU
>Subject: Re: Cobol Install FS issue
>
>Thanks for reply. I am installing Cobol in new file system, I don't find
>any issues with this directory structure. I tried all but not able to come
>out with this issue.
>
>
>BPXF140E RETURN CODE 0081, REASON CODE 0594003D. A
Thanks for reply. I am installing Cobol in new file system, I don't find
any issues with this directory structure. I tried all but not able to come
out with this issue.
BPXF140E RETURN CODE 0081, REASON CODE 0594003D. A LINK FAILED FOR
LINK NAME
On Thu, 10 Mar 2016 12:47:58 +0530, Mainframe Mainframe
wrote:
>Hello Group,
> While installing Cobol 5.2, I am getting below issue.
>
>BPXF140E RETURN CODE 0081, REASON CODE 0594003D. A LINK FAILED FOR
>LINK NAME
Thanks alot for help and answering the query .
On Thu, Mar 3, 2016 at 11:22 AM, Timothy Sipples wrote:
> Clark Morris wrote:
> >Check your licensing requirements. Normally there is only a short
> >period when you can run 2 versions without having to pay for both.
>
> It's
Hello Group,
While installing Cobol 5.2, I am getting below issue.
BPXF140E RETURN CODE 0081, REASON CODE 0594003D. A LINK FAILED FOR
LINK NAME /Service/usr/lpp/cobol/../../demo/oosample/Check.j
I did check for all directory path and I don't find any issues with this. I
Clark Morris wrote:
>Check your licensing requirements. Normally there is only a short
>period when you can run 2 versions without having to pay for both.
It's normally 12 months for IBM Monthly License Charge products. However,
if you have IBM Country Multiplex Pricing there is no time limit,
')
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
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,
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 wrote:
> On 2/03/2016 2:02 PM, Mainframe Mainframe wrote:
>
>> Hello Group,
>> We have COBOL V4.2 in our system
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
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
Any suggestion please.
19 matches
Mail list logo