Barbara,
Are you sure you had all of your Service filesystems mounted correctly? The
error indicates the possibility that maybe not? On my systems IZUUSRD is
mounted off /var/zosmf and is NOT updated by SMPE as it is the ZOSMF
operational data container. My V2.3 SMPE shows DDDEF SIZUFSD with a path of
'/SERVICE/usr/lpp/zosmf/IBM/' and when I mount my Service filesystems, and
navigate there, I see;
/SERVICE/usr/lpp/zosmf/IBM
TEC1:$ df -vk .
Mounted on Filesystem Avail/Total Files Status
/SERVICE (OMVSU.SERVICE.ROOT) 444779/3556800 4294929811 Available
ZFS, Read/Write, Device:648776, ACLS=Y
File System Owner : TEC1 Automove=U Client=N
Filetag : T=off codeset=0
Aggregate Name : OMVSU.SERVICE.ROOT
TEC1:$
TEC1:$ bpxmtext 0549010C
BPXFSLNK 10/03/16
JRLnkAcrossFilesets: The service tried to link across file systems
Action: Reissue the request, specifying a new pathname that is within the same
file system as the existing pathname.
TEC1:$
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Barbara Nitz
Sent: Monday, September 10, 2018 4:42 AM
To: [email protected]
Subject: Failing to install zOSMF ptfs
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
What a good thing we are not using z/OSMF. Last Friday I downloaded a refresh
for z/OS 2.3 from ShopZ. Everything went fine *except* ptfs UI55431, UI55737,
UI56534, UI57065 and UI57212. They fail to go in.
I install maintenance into /SERVICE, so the root is mounted under /SERVICE.
SBBLZFS is mounted under /SERVICE/usr/lpp/liberty_zos, SIZUUSRD is mounted
under /SERVICE/usr/lpp/zosmf/IBM, just like the DDDefs from serverpac specified.
I get these errors:
BPXF151I BPXCOPY WAS INVOKED FOR HEAD ID 000009.
BPXF150I MVS DATA SET WITH DDNAME SYSUT1 SUCCESSFULLY COPIED INTO TEXT HFS FILE
/SERVICE/usr/lpp/zosmf/IBM/IZUGUTSC.
BPXF140E RETURN CODE 00000090, REASON CODE 0549010C. A LINK FAILED FOR LINK
NAME /SERVICE/usr/lpp/zosmf/IBM/../samples/IZUSEC.xml.
BPXF151I BPXCOPY WAS INVOKED FOR HEAD ID 000010.
BPXF150I MVS DATA SET WITH DDNAME SYSUT1 SUCCESSFULLY COPIED INTO BINARY HFS
FILE /SERVICE/usr/lpp/zosmf/IBM/IZUSPEAR.
-------------------------------------------------------------------------------
SHELL SCRIPT IZUSPUNE OUTPUT FOR HFS IZUSPEAR SEQ NUM 000011
/SERVICE/usr/lpp/zosmf/IBM/IZUSPUNE: /SERVICE/usr/lpp/zosmf/IBM/IZUSPUNE: not
found
BPXF151I BPXCOPY WAS INVOKED FOR HEAD ID 000012.
BPXF150I MVS DATA SET WITH DDNAME SYSUT1 SUCCESSFULLY COPIED INTO BINARY HFS
FILE /SERVICE/usr/lpp/zosmf/IBM/IZUDMUI.
-------------------------------------------------------------------------------
SHELL SCRIPT IZUDUPUI OUTPUT FOR HFS IZUDMUI SEQ NUM 000013
/SERVICE/usr/lpp/zosmf/IBM/IZUDUPUI: /SERVICE/usr/lpp/zosmf/IBM/IZUDUPUI: not
found
BPXF151I BPXCOPY WAS INVOKED FOR HEAD ID 000014.
BPXF150I MVS DATA SET WITH DDNAME SYSUT1 SUCCESSFULLY COPIED INTO BINARY HFS
FILE /SERVICE/usr/lpp/zosmf/IBM/IZUGNAEW.
BPXF140E RETURN CODE 00000090, REASON CODE 0549010C. A LINK FAILED FOR LINK
NAME /SERVICE/usr/lpp/zosmf/IBM/../lib/izur
estjobs.jar.
BPXF151I BPXCOPY WAS INVOKED FOR HEAD ID 000015.
BPXF150I MVS DATA SET WITH DDNAME SYSUT1 SUCCESSFULLY COPIED INTO BINARY HFS
FILE /SERVICE/usr/lpp/zosmf/IBM/IZUCAHLP.
-------------------------------------------------------------------------------
SHELL SCRIPT IZUCATAR OUTPUT FOR HFS IZUCAHLP SEQ NUM 000016
/SERVICE/usr/lpp/zosmf/IBM/IZUCATAR: /SERVICE/usr/lpp/zosmf/IBM/IZUCATAR: not
found
I am unable to determine why the link fails. What did I do wrong?
Regards, Barbara
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN **CAUTION EXTERNAL
EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
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
