A fix is available
APAR status
Closed as program error.
Error description
When bringing up a z/OS 2.1 system in a non shared file system configuration, the following messages and errors may occur when bringing up automount: BPXF260I AUTOMOUNT POLICY WAS CHANGED AT 2014/05/31 00:43:11 BY USER ibmuser ON SYSTEM SY1 WITH POLICY /etc/auto.master BPXF274I FILE SYSTEM *AMD/u FAILED TO MOUNT. RETURN CODE = 00000086, REASON CODE = 055B04AE This will occur if parent of target automount managed file system has been mounted as AUTOMOVE=UNMOUNT when running in non shared file system environment.
Local fix
* Identify and unmount the parent file system containing the mountpoint for your automount managed directory. Once unmounted, mount this file system again without specifying the AUTOMOVE UNMOUNT attribute. Once mounted, automove status can be verified by looking at D OMVS,F output or ISHELL mount table. Once mounted without UNMOUNT attribute, try running /usr/sbin/automount again. Example: If automount managing /usrs/usr1, with parent file system POSIX.USRS.HERE mounted at mount point /usrs, unmount POSIX.USRS.HERE and mount it again without UNMOUNT attribute. Note that a chmount or 'change attributes' from ISHELL will not succeed in changing AUTOMOVE setting in non sysplex environment.
Problem summary
**************************************************************** * USERS AFFECTED: All users of z/OS UNIX System Services for * * HBB7790 using automount facility in the * * non shared file system configuration * * environment. The automount managed * * directory resides in a file system that * * is mounted with UNMOUNT attribute. * **************************************************************** * PROBLEM DESCRIPTION: In a single system environment, * * mounting an automount file * * system (*AMD/) failed with * * ENOSYS RSN055B04AE when the AUTOMOVE * * attribute of the file system * * containing the directory that *AMD/ * * is to be mounted on is UNMOUNT. * **************************************************************** * RECOMMENDATION: * **************************************************************** Automount file system (*AMD/) uses parent file system's owning system as its owning system when the parent file system has automove attribute UNMOUNT. FOMFAMT (automount facility) sets the sysname field with the parent's owning sysname and invokes the syscall mount. 'sysname' is a field for the sysplex enviroment and it's not allowed for mounting the file system in a single system environment. This causes mount processing to fail with ENOSYS JrMustBeSysplex in a single system environment.
Problem conclusion
FOMFAMT is changed to check for the sysplex environment before it sets the sysname for mounting *AMD/.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
OA45317
Reported component name
OPENMVS SYS SRV
Reported component ID
5695SCPX1
Reported release
790
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-06-02
Closed date
2014-06-23
Last modified date
2014-08-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA73932
Modules/Macros
FOMFAMT
Fix information
Fixed component name
OPENMVS SYS SRV
Fixed component ID
5695SCPX1
Applicable component levels
R790 PSY UA73932
UP14/07/09 P F407
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 August 2014