Hello All,
I can clearly see all file systems are mounted correctly .
HFS 190 ACTIVE RDWR 03/06/2016 L=138
NAME=OMVS.MVS1.ZOS13.SIGYROOT 23.40.14 Q=138
PATH=/Service/usr/lpp/cobol
WhenI dont find any issue in filesystem mounted on this path, then what
else can be reason for this error while applying
BPXF140E RETURN CODE 00000081, REASON CODE 0594003D. A LINK FAILED FOR
LINK NAME /Service/usr/lpp/cobol/../../demo/oosample/Check.j
Any more clue.
On Sun, Mar 13, 2016 at 5:47 AM, Lizette Koehler <[email protected]>
wrote:
> Sorry if this has been discussed.
>
> Do a D OMVS,F on the system where the failure is occurring. If nothing
> pops out, open an SR with IBM
> Lizette
>
>
> -----Original Message-----
> >From: Mainframe Mainframe <[email protected]>
> >Sent: Mar 11, 2016 8:16 PM
> >To: [email protected]
> >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 00000081, REASON CODE 0594003D. A LINK FAILED FOR
> >LINK NAME /Service/usr/lpp/cobol/../../demo/oosample/Check.j
> >
> >Any more suggestion.
> >
> >On Thu, Mar 10, 2016 at 4:29 PM, Giliad Wilf <
> >[email protected]> wrote:
> >
> >> On Thu, 10 Mar 2016 12:47:58 +0530, Mainframe Mainframe <
> >> [email protected]> wrote:
> >>
> >> >Hello Group,
> >> > While installing Cobol 5.2, I am getting below issue.
> >> >
> >> >BPXF140E RETURN CODE 00000081, 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
> >> >checked all available solution but nothing working for me.
> >> >
> >> >Any clue.
> >> >
> >> >----------------------------------------------------------------------
> >> >For IBM-MAIN subscribe / signoff / archive access instructions,
> >> >send email to [email protected] with the message: INFO IBM-MAIN
> >>
> >> - In order to maintain two different versions of Enterprise Cobol
> >> simultaneously, there is a requirement that each version
> >> has to have its own SIGYROOT filesystem.
> >> - When there is only a single version of Enterprise Cobol, its SIGYROOT
> >> gets mounted at '/usr/lpp/cobol/'.
> >> - What do we do if we have two or more?
> >> - The answer is you define two different mountpoints on top of
> >> '/usr/lpp/cobol/' and mount each Cobol's SIGYROOT at its own
> >> unique mountpoint.
> >> - Each Cobol will look for the DDDEF for SIGYHFS, which ends with
> >> '.../bin/IBM/', back two directory levels, and will expect
> >> its own SIGYROOT to have been mounted there, and will expect to see
> >> directories 'demo', 'include', and 'lib' alongside
> >> directory 'bin'.
> >> - Lookup the internet for a description of a technical problem, using
> >> "igzcjava.x" and BPXF140E as search arguments,
> >> e.g. http://www-01.ibm.com/support/docview.wss?uid=swg21195928
> >>
> >> We were installing Enterprise Cobol V4R2 for z/OS alongside existing
> >> Enterprise Cobol V3R4 for z/OS, and what I did was this:
> >>
> >> unmount filesystem('....V3R4.SIGYROOT') immediate
> >> mkdir '/usr/lpp/cobol/EC34' mode(7,5,5)
> >> mkdir '/usr/lpp/cobol/EC42' mode(7,5,5)
> >> mount FILESYSTEM('....V3R4.SIGYROOT') MOUNTPOINT('/usr/lpp/cobol/EC34')
> >> TYPE(HFS) MODE(RDWR)
> >> mount FILESYSTEM('....V4R2.SIGYROOT') MOUNTPOINT('/usr/lpp/cobol/EC42')
> >> TYPE(HFS) MODE(RDWR)
> >>
> >> ----------------------------------------------------------------------
> >> For IBM-MAIN subscribe / signoff / archive access instructions,
> >> send email to [email protected] with the message: INFO IBM-MAIN
> >>
> >
> >----------------------------------------------------------------------
> >For IBM-MAIN subscribe / signoff / archive access instructions,
> >send email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
