Well, you might think its fine, but the system does not:
TEC1:$ bpxmtext 0594003D
BPXFVLKP 12/05/14
JRDirNotFound: A directory in the pathname was not found
Action: One of the directories specified was not found. Verify that the name
specified is spelled correctly.
_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Engineering
[email protected]
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H
p 616.653.8429
f 616.653.2717
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Mainframe Mainframe
Sent: Friday, March 11, 2016 10:17 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
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail in error, please do not read, copy or disseminate it in any
manner. If you are not the intended recipient, any disclosure, copying,
distribution or use of the contents of this information is prohibited. Please
reply to the message immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer system. Your
assistance in correcting this error is appreciated.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
