Re: Cobol Install FS issue

2016-03-20 Thread venkat kulkarni
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 >

Re: Cobol Install FS issue

2016-03-14 Thread Andrew Rowley
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

Re: Cobol Install FS issue

2016-03-14 Thread venkat kulkarni
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

Re: Cobol Install FS issue

2016-03-14 Thread venkat kulkarni
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

Re: Cobol Install FS issue

2016-03-14 Thread Doug Henry
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

Re: Cobol Install FS issue

2016-03-14 Thread Staller, Allan
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

Re: Cobol Install FS issue

2016-03-14 Thread Jousma, David
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

Re: Cobol Install FS issue

2016-03-13 Thread venkat kulkarni
; > >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

Re: Cobol Install FS issue

2016-03-12 Thread Lizette Koehler
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

Re: Cobol Install FS issue

2016-03-11 Thread Mainframe Mainframe
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

Re: Cobol Install FS issue

2016-03-10 Thread Giliad Wilf
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

Cobol Install FS issue

2016-03-09 Thread Mainframe Mainframe
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