APAR status
Closed as canceled.
Error description
Component ID: 5695DF121 Releases: 1NP 1NE Information APAR to document additional information and temporary restrictions for MVS NFS server feature of DFSMS v1r2m0: 1). APAR dependency list : Product APAR Symptom Comments OE Socket OW08076 hang HDZ11NE only OW05135 HDZ11NE only OE Kernel OW06094 Racf Permission denied If access HFS LE 1.3 PN55785 Must install PN55980 PN56000 DFSMS 1.2 OW07230 Cannot access legacy OW06999 External link fails OW08101 Damage HFS TCP/IP 3.1 PN62474 NFS appears hang 2) Dispatching Priority Problem: When TCP/IP and NFS are assigned to the same mean-time-to-wait dispatching priority in MVS SP 5.1 there can be times when NFS will have a higher dispatching priority than TCP/IP. This seems to affect NFS performance adversely. Solution: Assign fixed priorities to TCP/IP and NFS such that TCP/IP has a higher priority than NFS. 3) Problem: NFS Server shuts down on startup, issues - GFSA402I READ FAILED FOR THE ATTRIBUTE DATA SET. GFSA330I SERVER SHUTDOWN COMPLETE. check your nfstasks attributes. APAR OW08266 reduced the maximum of n+m from 100 to 25: "nfstasks (n,m) limits in the installation attributes data set. The sum of n and m cannot exceed 25." Be sure to reduce the value to 25 or below. The documentation change is done with APAR OW19389. . 4) Temporary restriction of mounting HFS : Mounting on a child or parent directory of an existing mount point for OpenEdition HFS is not allowed and will be blocked. e.g. If a mount is made against /u/smith, the mount against /u/smith/project or against /u will be rejected. GFSA785I MOUNT ON CHILD/PARENT OF AN ALREADY MOUNTED DIRECTORY string FAILED (TEMPORARY HFS RESTRICTION: REFER TO INFO APAR: II08210). This restriction is removed with application of OW12199 - HDZ11NE/UW18827 HDZ11NP/UW18828. . 5) Temporary restriction of accessing data set with recfm of VS OR VBS: Read and write accesses are blocked. . This restriction is removed with application of APAR OW12200, HDZ11NE/UW18827 HDZ11NP/UW18828. 6) Updated message: GFSA898I - EOL SEQUENCE MISMATCH FOR DATA SET dsname(mem-name). - Apply only to textmode processing with end-of-line character - Condition that may influence the processing: -- Append or update a record and overwrite the end-of-line characters is not allowed. -- File timed out before the continuation of data packet ar- rive. It may occur due to the inefficiency of network traffic, clients delayed write algorithm of the last data packet. Processing attribute writetimeout value should be lengthened if the error occurs frequently. Some information about NFS's useage of port 2049. Both DFSMS/MVS NFS Server and Client use port 2049 to communicate with any other NFS Client or Server in the network. Any reservation of this port number will cause a communications problem. If your TCP/IP profile and/or OpenEdition MVS file system profile have a reserve statement for port 2049, you will have a communication problem between DFSMS/MVS NFS and any other NFS Server or Client. 1) TCP/IP profile The statement under PORT reservation 2049 UDP MVSNFS ; NFS Server causes TCP/IP to reserve port 2049. This means the DFSMS/MVS NFS server cannot register port 2049. This causes the communications problem between DFSMS/MVS NFS Server and any NFS Client. THIS STATEMENT SHOULD BE COMMENTED OUT. 2) OpenEdition MVS file system profile During OpenEdition MVS file system initialization, the FILESYSTYPE PARMLIB statement for the network in the SYS1.PARMLIB(BPXPRMxx) member may have incorrect port information. This causes the DFSMS/MVS NFS Server and/or Client communicaitons problem. If your BPXPRMxx member looks like the following: FILESYSTYPE TYPE(INET) ENTRYPOINT(BPXTCINT) NETWORK DOMAINNAME(AF_INET) DOMAINNUMBER(2) MAXSOCKETS(64) TYPE(INET) INADDRANYPORT(2000) INADDRANYCOUNT(325) SUBFILESYSTYPE NAME(INETONE) TYPE(INET) ENTRYPOINT(BPXTIINT) DEFAULT This statement causes OpenEdition to reserve a range of ports starting at 2000 until 2324. DFSMS/MVS NFS port, 2049, happens to be within this reserved range. This causes port 2049, to be unavailable to DFSMS/MVS NFS. This causes the communications problem. To correct this statement you should: change the ENTRYPOINT name to BPXTIINT and MAXSOCKETS to 2000. delete the lines beginning with: INADDRANYPORT INADDRANYCOUNT SUBFILESYSTYPE TYPE ENTRYPOINT DEFAULT Once you have done this you should end up with a FILESYSTYPE statement that looks like this: FILESYSTYPE TYPE(INET) ENTRYPOINT(BPXTIINT) NETWORK DOMAINNAME(AF_INET) DOMAINNUMBER(2) MAXSOCKETS(2000) TYPE(INET) Using the DFSMS/MVS NFS Server to access conventional MVS data sets, the server generates dummy values for the UNIX attributes of file system information because they have no meaning in the MVS context. The hard coded values for the filesystem are as follows: - block size (in bytes) = 4096 - total number of blocks = 30000 - number of free blocks = 15000 - number of blocks available = 15000 The file size for conventional MVS dataset as a directory has a hard coded value of 8192 bytes. The NFS Server starts and message GFSA348I is not received. If TCP/IP is terminated, NFS Server ends with the console message: GFSA559I CANNOT CREATE UDP SERVICE. Check to see that Portmapper is active. msgGFSA348I msgGFSA559I
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
Closing
APAR Information
APAR number
II08210
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1994-09-20
Closed date
1997-07-30
Last modified date
1997-08-11
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:
11 August 1997