APAR status
INTRAN
Error description
In the UNIX System Services Planning manual, there are several statements about ownership and the AUTOMOVE parameter for the system-specific file systems (/dev, /etc/, /tmp, /var). The pur- pose of this INFO APAR is to expand on the explanation using the /dev system-specific file system as an example. The UNIX System Services Planning manual does state that the system-specific file systems should not be mounted with the AUTOMOVE=YES param- ter, nor should they be moved to a system other than the proper owner. In this example, the /dev system-specific file system was mounted via BPXPRMxx as AUTOMOVE=YES (the default). As a result of a scheduled IPL, ownership of this /dev file system moved to another system in the shared HFS sysplex. When users tried to enter the OMVS shell on the original system (proper owner of the /dev system specific file system), they received: FSUM2150I Function = stat(), ending name = '/dev/ptyp0257', retu = -1, errno = 129 (X'00000081'), reason code = 053B006C, description 'EDC5129I No s uch file or directory.' FSUM2164I Function = open(), terminal name = '/dev/ptyp0000', r value = -1 , errno = 128 (X'00000080'), reason code = 0562004B, description 'EDC5128I No such device.' . Full function was restored by unmounting the file system and mounting it to the correct owner. Additional symptom: OMPROUTE fails with RC1. OMPROUTE uses the /dev/null file; a change in the ownership of the /dev file system will result in a failure in OMPROUTE. Ensure that the system where OMPROUTE runs is the owner of the /dev file system. . Note that in a DFS/SMB environment, the setting of the server configuration option _IOE_MOVE_SHARED_FILESYSTEM may affect the ownership of file systems.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II13129
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
INTRAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2002-01-07
Closed date
Last modified date
2009-02-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
02 February 2009