Re: Problem mounting file system

[Seymour J Metz]

Just because he wears glasses doesn't mean he's blind.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List  on behalf of 
David Spiegel 
Sent: Sunday, July 21, 2019 5:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Problem mounting file system

פּוֹקֵֽחַ עִוְרִים

On 2019-07-21 04:34, Gadi Ben-Avi wrote:
> I was my mistake.
> The file name was SYSV.OMVS.PTFS.ZFS.
> I need new glasses
> Gadi
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Mike Shorkend
> Sent: Sunday, July 21, 2019 11:29 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Problem mounting file system
>
> Gadi
> Does SYSV.OMVS.PTFS exist? Can you post the LISTCAT output against it  if it 
> does?
>
> On Sun, 21 Jul 2019 at 08:43, Gadi Ben-Avi  wrote:
>
>> Hi,
>> I am having trouble mounting a file system.
>> I issue the command
>>MOUNT FILESYSTEM('SYSV.OMVS.PTFS') MOUNTPOINT('/u/ptfs') TYPE(ZFS)
>> MODE(RDWR)
>> And get
>> BPXF135E RETURN CODE 0081, REASON CODE EF096055.  THE MOUNT FAILED
>> FOR FILE SYSTEM SYSV.OMVS.PTFS.
>>
>> Accordint to BPXMTEXT, the meaning of EF096055 is:
>> zFS Thu Mar 14 14:29:55 EDT 2019
>> Description: Error with issuing a LOCATE call on an HFS-compat aggregate.
>>
>> Action: Ensure that the zFS file system named on the MOUNT command has
>> the same name as the VSAM Linear Data Set (and the HFS compatibility
>> mode
>> aggregate) that contains the file system.
>>
>> SYSV.OMVS.PTFS exists
>> /u/ptfs exists, is a directory and is empty.
>>
>> What is the problem?
>> We are running z/OS v2.3.
>>
>> Gadi
>>
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions, send
>> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>
>
> --
> Mike Shorkend
> m...@shorkend.com
> https://eur03.safelinks.protection.outlook.com/?url=www.shorkend.com&data=02%7C01%7C%7C52faaebb4df54dc5559908d70db64c61%7C84df9e7fe9f640afb435%7C1%7C0%7C636992948972587862&sdata=aIEq7wkpjil5vsnTj%2BYDCchxq2wwb%2B4GmXciCJd1G68%3D&reserved=0
> Tel: +972524208743
> Fax: +97239772196
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Problem mounting file system

[David Spiegel]

פּוֹקֵֽחַ עִוְרִים

On 2019-07-21 04:34, Gadi Ben-Avi wrote:
> I was my mistake.
> The file name was SYSV.OMVS.PTFS.ZFS.
> I need new glasses
> Gadi
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Mike Shorkend
> Sent: Sunday, July 21, 2019 11:29 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Problem mounting file system
>
> Gadi
> Does SYSV.OMVS.PTFS exist? Can you post the LISTCAT output against it  if it 
> does?
>
> On Sun, 21 Jul 2019 at 08:43, Gadi Ben-Avi  wrote:
>
>> Hi,
>> I am having trouble mounting a file system.
>> I issue the command
>>MOUNT FILESYSTEM('SYSV.OMVS.PTFS') MOUNTPOINT('/u/ptfs') TYPE(ZFS)
>> MODE(RDWR)
>> And get
>> BPXF135E RETURN CODE 0081, REASON CODE EF096055.  THE MOUNT FAILED
>> FOR FILE SYSTEM SYSV.OMVS.PTFS.
>>
>> Accordint to BPXMTEXT, the meaning of EF096055 is:
>> zFS Thu Mar 14 14:29:55 EDT 2019
>> Description: Error with issuing a LOCATE call on an HFS-compat aggregate.
>>
>> Action: Ensure that the zFS file system named on the MOUNT command has
>> the same name as the VSAM Linear Data Set (and the HFS compatibility
>> mode
>> aggregate) that contains the file system.
>>
>> SYSV.OMVS.PTFS exists
>> /u/ptfs exists, is a directory and is empty.
>>
>> What is the problem?
>> We are running z/OS v2.3.
>>
>> Gadi
>>
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions, send
>> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>
>
> --
> Mike Shorkend
> m...@shorkend.com
> https://eur03.safelinks.protection.outlook.com/?url=www.shorkend.com&data=02%7C01%7C%7C52faaebb4df54dc5559908d70db64c61%7C84df9e7fe9f640afb435%7C1%7C0%7C636992948972587862&sdata=aIEq7wkpjil5vsnTj%2BYDCchxq2wwb%2B4GmXciCJd1G68%3D&reserved=0
> Tel: +972524208743
> Fax: +97239772196
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Problem mounting file system

[Gadi Ben-Avi]

I was my mistake.
The file name was SYSV.OMVS.PTFS.ZFS.
I need new glasses
Gadi

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Mike Shorkend
Sent: Sunday, July 21, 2019 11:29 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Problem mounting file system

Gadi
Does SYSV.OMVS.PTFS exist? Can you post the LISTCAT output against it  if it 
does?

On Sun, 21 Jul 2019 at 08:43, Gadi Ben-Avi  wrote:

> Hi,
> I am having trouble mounting a file system.
> I issue the command
>   MOUNT FILESYSTEM('SYSV.OMVS.PTFS') MOUNTPOINT('/u/ptfs') TYPE(ZFS)
> MODE(RDWR)
> And get
> BPXF135E RETURN CODE 0081, REASON CODE EF096055.  THE MOUNT FAILED 
> FOR FILE SYSTEM SYSV.OMVS.PTFS.
>
> Accordint to BPXMTEXT, the meaning of EF096055 is:
> zFS Thu Mar 14 14:29:55 EDT 2019
> Description: Error with issuing a LOCATE call on an HFS-compat aggregate.
>
> Action: Ensure that the zFS file system named on the MOUNT command has 
> the same name as the VSAM Linear Data Set (and the HFS compatibility 
> mode
> aggregate) that contains the file system.
>
> SYSV.OMVS.PTFS exists
> /u/ptfs exists, is a directory and is empty.
>
> What is the problem?
> We are running z/OS v2.3.
>
> Gadi
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


--
Mike Shorkend
m...@shorkend.com
www.shorkend.com
Tel: +972524208743
Fax: +97239772196

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Problem mounting file system

[Mike Shorkend]

Gadi
Does SYSV.OMVS.PTFS exist? Can you post the LISTCAT output against it  if
it does?

On Sun, 21 Jul 2019 at 08:43, Gadi Ben-Avi  wrote:

> Hi,
> I am having trouble mounting a file system.
> I issue the command
>   MOUNT FILESYSTEM('SYSV.OMVS.PTFS') MOUNTPOINT('/u/ptfs') TYPE(ZFS)
> MODE(RDWR)
> And get
> BPXF135E RETURN CODE 0081, REASON CODE EF096055.  THE MOUNT FAILED FOR
> FILE SYSTEM SYSV.OMVS.PTFS.
>
> Accordint to BPXMTEXT, the meaning of EF096055 is:
> zFS Thu Mar 14 14:29:55 EDT 2019
> Description: Error with issuing a LOCATE call on an HFS-compat aggregate.
>
> Action: Ensure that the zFS file system named on the MOUNT command has the
> same name as the VSAM Linear Data Set (and the HFS compatibility mode
> aggregate) that contains the file system.
>
> SYSV.OMVS.PTFS exists
> /u/ptfs exists, is a directory and is empty.
>
> What is the problem?
> We are running z/OS v2.3.
>
> Gadi
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
Mike Shorkend
m...@shorkend.com
www.shorkend.com
Tel: +972524208743
Fax: +97239772196

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Problem mounting file system

[Gadi Ben-Avi]

Hi,
I am having trouble mounting a file system.
I issue the command
  MOUNT FILESYSTEM('SYSV.OMVS.PTFS') MOUNTPOINT('/u/ptfs') TYPE(ZFS) MODE(RDWR)
And get
BPXF135E RETURN CODE 0081, REASON CODE EF096055.  THE MOUNT FAILED FOR FILE 
SYSTEM SYSV.OMVS.PTFS.

Accordint to BPXMTEXT, the meaning of EF096055 is:
zFS Thu Mar 14 14:29:55 EDT 2019
Description: Error with issuing a LOCATE call on an HFS-compat aggregate.

Action: Ensure that the zFS file system named on the MOUNT command has the
same name as the VSAM Linear Data Set (and the HFS compatibility mode
aggregate) that contains the file system.

SYSV.OMVS.PTFS exists
/u/ptfs exists, is a directory and is empty.

What is the problem?
We are running z/OS v2.3.

Gadi

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Problem Mounting File system

[John McKown]

On Wed, Sep 6, 2017 at 9:59 AM, גדי בן אבי  wrote:

> The problem was that the ZFS address space had no user assigned to it.
> Once I fixed that, which required an IPL, everything worked fine.
>
> Gadi
>
>
​IPL'ing is definitely the best way to go. But there is a way to restart
the ZFS address space with an IPL.
ref:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ioea700/stopzfs.htm



zFS can be stopped using the MODIFY OMVS,STOPPFS=ZFS operator command.
Automatic ownership movement can occur for both the z/OS UNIX owner and the
zFS owner. See z/OS UNIX System Services Planning

for
information about the various automove settings for z/OS UNIX file system
ownership. zFS aggregate ownership will move unless the file system is
unmounted by z/OS UNIX. zFS file systems that become unmounted will need to
be mounted again after zFS is restarted.
When zFS is stopped, you receive the following message (after replying Y to
message BPXI078D):

nn BPXF032D FILESYSTYPE ZFS TERMINATED. REPLY ’R’ WHEN READY TO
RESTART. REPLY ’I’ TO IGNORE.

When an LPAR is shut down without the orderly shutdown of zFS, it is likely
that recovery actions (automatic recovery on the next mount; if the mount
fails, it might be necessary to manually run salvager) will be necessary to
bring zFS aggregates back to a consistent state. In addition, some file
activity can be lost.
To restart zFS, reply *r* to message nn. (For example, *r 1,r*). If you
want zFS to remain stopped, you can reply *i* to remove the prompt. In this
case, zFS can be redefined at a later time using the SETOMVS
RESET=(xx)operator command. However, this can result in zFS file systems
becoming NOT ACTIVE. An unmount and remount is required to activate a file
system that is NOT ACTIVE. If you plan to restart zFS, you should reply r
to the message.
Note: Stopping zFS can have shared file system (sysplex) implications.
See Using
zFS in a shared file system environment

for
information about shared file systems.

​


-- 
UNIX was not designed to stop you from doing stupid things, because that
would also stop you from doing clever things. -- Doug Gwyn

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Problem Mounting File system

[גדי בן אבי]

The problem was that the ZFS address space had no user assigned to it.
Once I fixed that, which required an IPL, everything worked fine.

Gadi

From: IBM Mainframe Discussion List  on behalf of 
Lizette Koehler 
Sent: Wednesday, September 6, 2017 17:09
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Problem Mounting File system

What was your solution?

Second, on z/OS Is a tool called bpxmtext  use it on the reason code to
determine a possible issue/solution

In this case

Bpxmtext EF096055
Description: Error with issuing a LOCATE call on an HFS-compat aggregate.

Action: Ensure that the zFS file system named on the MOUNT command has the
same name as the VSAM Linear Data Set (and the HFS compatibility mode
aggregate) that contains the file system.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of ??? ?? ???
> Sent: Tuesday, September 05, 2017 10:16 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Problem Mounting File system
>
> Thanks
> I found the problem.
>
> Gadi
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Sankaranarayanan, Vignesh
> Sent: Wednesday, September 6, 2017 8:13 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Problem Mounting File system
>
> The user ID ZFS doesn't have access to the CICS zFS file, which is protected
> by CICS.*
>
> - Vignesh
> Mainframe Infrastructure
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of ??? ?? ???
> Sent: 06 September 2017 10:27
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Problem Mounting File system
>
> Hi,
>
> We are in the process of building a new system running z/OS v2.2
>
> When I try to mount a file system, I get:
> MOUNT FILESYSTEM('CICS.V54.ZFS') MOUNTPOINT('/usr/lpp/cicsts/cicsts54')
> TYPE(ZFS) MODE(RDWR) BPXF135E RETURN CODE 0079, REASON CODE EF096055.
> THE MOUNT FAILED FOR FILE SYSTEM CICS.V54.ZFS.
>
> In the system log, I see
> ICH408I JOB(ZFS ) STEP(ZFS ) 467
>   CICS.V54.ZFS CL(DATASET ) VOL(G22UC1)
>   INSUFFICIENT ACCESS AUTHORITY
>   FROM CICS.* (G)
>   ACCESS INTENT(READ   )  ACCESS ALLOWED(NONE   )
> BPXF274I FILE SYSTEM CICS.V54.ZFS 468
> FAILED TO MOUNT.
> RETURN CODE = 0079, REASON CODE = EF096055
>
> It looks like there is no user associated with ZFS.
> I do have a profile in the STARTED class for ZFS.*
>
> What can be causing this?
>
> Gadi

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
לתשומת ליבך, בהתאם לנהלי חברת מלם מערכות בע"מ ו/או כל חברת בת ו/או חברה קשורה 
שלה (להלן : "החברה") וזכויות החתימה בהן, כל הצעה, התחייבות או מצג מטעם החברה, 
מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או 
שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף 
להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין 
להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance 
with Malam and/or its subsidiaries (hereinafter : "Malam") regulations and 
signatory rights, no offer, agreement, concession or representation is binding 
on the Malam, unless accompanied by a duly signed separate document (or a 
scanned version thereof), affixed with the Malam seal.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Problem Mounting File system

[Lizette Koehler]

What was your solution?

Second, on z/OS Is a tool called bpxmtext  use it on the reason code to
determine a possible issue/solution

In this case

Bpxmtext EF096055
Description: Error with issuing a LOCATE call on an HFS-compat aggregate.

Action: Ensure that the zFS file system named on the MOUNT command has the
same name as the VSAM Linear Data Set (and the HFS compatibility mode
aggregate) that contains the file system.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of ??? ?? ???
> Sent: Tuesday, September 05, 2017 10:16 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Problem Mounting File system
> 
> Thanks
> I found the problem.
> 
> Gadi
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Sankaranarayanan, Vignesh
> Sent: Wednesday, September 6, 2017 8:13 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Problem Mounting File system
> 
> The user ID ZFS doesn't have access to the CICS zFS file, which is protected
> by CICS.*
> 
> - Vignesh
> Mainframe Infrastructure
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of ??? ?? ???
> Sent: 06 September 2017 10:27
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Problem Mounting File system
> 
> Hi,
> 
> We are in the process of building a new system running z/OS v2.2
> 
> When I try to mount a file system, I get:
> MOUNT FILESYSTEM('CICS.V54.ZFS') MOUNTPOINT('/usr/lpp/cicsts/cicsts54')
> TYPE(ZFS) MODE(RDWR) BPXF135E RETURN CODE 0079, REASON CODE EF096055.
> THE MOUNT FAILED FOR FILE SYSTEM CICS.V54.ZFS.
> 
> In the system log, I see
> ICH408I JOB(ZFS ) STEP(ZFS ) 467
>   CICS.V54.ZFS CL(DATASET ) VOL(G22UC1)
>   INSUFFICIENT ACCESS AUTHORITY
>   FROM CICS.* (G)
>   ACCESS INTENT(READ   )  ACCESS ALLOWED(NONE   )
> BPXF274I FILE SYSTEM CICS.V54.ZFS 468
> FAILED TO MOUNT.
> RETURN CODE = 0079, REASON CODE = EF096055
> 
> It looks like there is no user associated with ZFS.
> I do have a profile in the STARTED class for ZFS.*
> 
> What can be causing this?
> 
> Gadi

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Problem Mounting File system

[גדי בן אבי]

Thanks
I found the problem.

Gadi

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Sankaranarayanan, Vignesh
Sent: Wednesday, September 6, 2017 8:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Problem Mounting File system

The user ID ZFS doesn't have access to the CICS zFS file, which is protected by 
CICS.*

– Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of ??? ?? ???
Sent: 06 September 2017 10:27
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Problem Mounting File system

Hi,

We are in the process of building a new system running z/OS v2.2

When I try to mount a file system, I get:
MOUNT FILESYSTEM('CICS.V54.ZFS') MOUNTPOINT('/usr/lpp/cicsts/cicsts54') 
TYPE(ZFS) MODE(RDWR) BPXF135E RETURN CODE 0079, REASON CODE EF096055.  THE 
MOUNT FAILED FOR FILE SYSTEM CICS.V54.ZFS.

In the system log, I see
ICH408I JOB(ZFS ) STEP(ZFS ) 467
  CICS.V54.ZFS CL(DATASET ) VOL(G22UC1)
  INSUFFICIENT ACCESS AUTHORITY
  FROM CICS.* (G)
  ACCESS INTENT(READ   )  ACCESS ALLOWED(NONE   )
BPXF274I FILE SYSTEM CICS.V54.ZFS 468
FAILED TO MOUNT.
RETURN CODE = 0079, REASON CODE = EF096055

It looks like there is no user associated with ZFS.
I do have a profile in the STARTED class for ZFS.*

What can be causing this?

Gadi

לתשומת ליבך, בהתאם לנהלי חברת מלם מערכות בע"מ ו/או כל חברת בת ו/או חברה קשורה 
שלה (להלן : "החברה") וזכויות החתימה בהן, כל הצעה, התחייבות או מצג מטעם החברה, 
מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או 
שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף 
להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין 
להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance 
with Malam and/or its subsidiaries (hereinafter : "Malam") regulations and 
signatory rights, no offer, agreement, concession or representation is binding 
on the Malam, unless accompanied by a duly signed separate document (or a 
scanned version thereof), affixed with the Malam seal.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

MARKSANDSPENCER.COM

 Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
London
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670

www.marksandspencer.com

Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know 
and then delete it from your system; you should not copy, disclose, or 
distribute its contents to anyone nor act in reliance on this e-mail, as this 
is prohibited and may be unlawful.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
לתשומת ליבך, בהתאם לנהלי חברת מלם מערכות בע"מ ו/או כל חברת בת ו/או חברה קשורה 
שלה (להלן : "החברה") וזכויות החתימה בהן, כל הצעה, התחייבות או מצג מטעם החברה, 
מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או 
שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף 
להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין 
להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance 
with Malam and/or its subsidiaries (hereinafter : "Malam") regulations and 
signatory rights, no offer, agreement, concession or representation is binding 
on the Malam, unless accompanied by a duly signed separate document (or a 
scanned version thereof), affixed with the Malam seal.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Problem Mounting File system

[Sankaranarayanan, Vignesh]

The user ID ZFS doesn't have access to the CICS zFS file, which is protected by 
CICS.*

– Vignesh
Mainframe Infrastructure

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of ??? ?? ???
Sent: 06 September 2017 10:27
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Problem Mounting File system

Hi,

We are in the process of building a new system running z/OS v2.2

When I try to mount a file system, I get:
MOUNT FILESYSTEM('CICS.V54.ZFS') MOUNTPOINT('/usr/lpp/cicsts/cicsts54') 
TYPE(ZFS) MODE(RDWR) BPXF135E RETURN CODE 0079, REASON CODE EF096055.  THE 
MOUNT FAILED FOR FILE SYSTEM CICS.V54.ZFS.

In the system log, I see
ICH408I JOB(ZFS ) STEP(ZFS ) 467
  CICS.V54.ZFS CL(DATASET ) VOL(G22UC1)
  INSUFFICIENT ACCESS AUTHORITY
  FROM CICS.* (G)
  ACCESS INTENT(READ   )  ACCESS ALLOWED(NONE   )
BPXF274I FILE SYSTEM CICS.V54.ZFS 468
FAILED TO MOUNT.
RETURN CODE = 0079, REASON CODE = EF096055

It looks like there is no user associated with ZFS.
I do have a profile in the STARTED class for ZFS.*

What can be causing this?

Gadi

לתשומת ליבך, בהתאם לנהלי חברת מלם מערכות בע"מ ו/או כל חברת בת ו/או חברה קשורה 
שלה (להלן : "החברה") וזכויות החתימה בהן, כל הצעה, התחייבות או מצג מטעם החברה, 
מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או 
שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף 
להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין 
להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance 
with Malam and/or its subsidiaries (hereinafter : "Malam") regulations and 
signatory rights, no offer, agreement, concession or representation is binding 
on the Malam, unless accompanied by a duly signed separate document (or a 
scanned version thereof), affixed with the Malam seal.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

MARKSANDSPENCER.COM

 Unless otherwise stated above:
Marks and Spencer plc
Registered Office:
Waterside House
35 North Wharf Road
London
W2 1NW

Registered No. 214436 in England and Wales.

Telephone (020) 7935 4422
Facsimile (020) 7487 2670

www.marksandspencer.com

Please note that electronic mail may be monitored.

This e-mail is confidential. If you received it by mistake, please let us know 
and then delete it from your system; you should not copy, disclose, or 
distribute its contents to anyone nor act in reliance on this e-mail, as this 
is prohibited and may be unlawful.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Problem Mounting File system

[גדי בן אבי]

Hi,

We are in the process of building a new system running z/OS v2.2

When I try to mount a file system, I get:
MOUNT FILESYSTEM('CICS.V54.ZFS') MOUNTPOINT('/usr/lpp/cicsts/cicsts54') 
TYPE(ZFS) MODE(RDWR)
BPXF135E RETURN CODE 0079, REASON CODE EF096055.  THE MOUNT FAILED FOR FILE 
SYSTEM CICS.V54.ZFS.

In the system log, I see
ICH408I JOB(ZFS ) STEP(ZFS ) 467
  CICS.V54.ZFS CL(DATASET ) VOL(G22UC1)
  INSUFFICIENT ACCESS AUTHORITY
  FROM CICS.* (G)
  ACCESS INTENT(READ   )  ACCESS ALLOWED(NONE   )
BPXF274I FILE SYSTEM CICS.V54.ZFS 468
FAILED TO MOUNT.
RETURN CODE = 0079, REASON CODE = EF096055

It looks like there is no user associated with ZFS.
I do have a profile in the STARTED class for ZFS.*

What can be causing this?

Gadi

לתשומת ליבך, בהתאם לנהלי חברת מלם מערכות בע"מ ו/או כל חברת בת ו/או חברה קשורה 
שלה (להלן : "החברה") וזכויות החתימה בהן, כל הצעה, התחייבות או מצג מטעם החברה, 
מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או 
שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף 
להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין 
להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance 
with Malam and/or its subsidiaries (hereinafter : "Malam") regulations and 
signatory rights, no offer, agreement, concession or representation is binding 
on the Malam, unless accompanied by a duly signed separate document (or a 
scanned version thereof), affixed with the Malam seal.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN