UDP does not guarantee the delivery or order of data returned to clients. A client may receive any one of the following return codes for a successful operation:

1.Return code=0 (RC=0). The operation is completed successfully.

2.EEXIST. The operation is completed successfully. This error condition was returned to the client because the return code of 0 (RC=0) was either lost or received out of order.

3.ENOENT. The operation is completed successfully. This error condition was returned to the client because the return code of 0 (RC=0) was either lost or received out of order.

Client Timeout Solution

To reduce the confusion of receiving unexpected return codes and error conditions for ®le creation and removal, users can perform the following tasks:

1.Increase the period of client timeout so that the client will timeout less often when making server requests. This will cause fewer repeats of the same request to be transmitted to the server. See ªDirectory and File Attribute Cacheº on page 13 for more details on client timeout and mount command options that determine timeout.

2.Increase server throughput in the following ways:

v Start more NFS server daemons (NFSD) to handle client requests

vDecrease the load of requests on the server

vDecrease the amount of clients who access and make requests of the server

Network File System Differences

The following APIs have an updated set of usage notes for when users work with the Network File System:

vopen()

vcreate()

vmkdir()

vaccess()

vfstat()

vlseek()

vlstat()

vstat()

vread()

vwrite()

vfcntl()

In general, users of these APIs should remember that local access to remote ®les through the Network File System may produce unexpected results. Conditions at

the server dictate the properties of client access to remote ®les. Creation of a ®le or directory may fail if permissions and other attributes that are stored locally are more restrictive than those at the server. A later attempt to create a ®le can succeed when you refresh the local data or when you remount the ®le system. Several options on the Add Mounted File System (ADDMFS) command determine the time between refreshes of local data.

78OS/400 Network File System Support V4R4

Page 95 Page 97
Page 96
Image 96
IBM AS/400E manual Client Timeout Solution, Network File System Differences
Page 95 Page 97

AS/400E specifications

The IBM AS/400E, now more commonly known as IBM i, is a robust and versatile midrange server that has been designed to provide a comprehensive computing solution for businesses of all sizes. First introduced in the late 1980s, the AS/400 series has undergone multiple enhancements and rebranding, with the AS/400E being one of the notable iterations. This powerful platform is closely associated with IBM's commitment to reliability, scalability, and integrated business solutions.

One of the main features of the AS/400E is its highly integrated architecture that combines hardware and software into a cohesive system. This integration allows for seamless operations, reducing the complexity typically associated with managing disparate systems. The system is powered by IBM's proprietary OS/400 operating system, which has evolved into IBM i, featuring advanced capabilities like object-oriented programming, integrated database management, and security features that are essential for enterprise environments.

A key characteristic of the AS/400E is its robust database support, primarily through the use of DB2 for i. This integrated database management system enables efficient data handling and retrieval, facilitating real-time business analytics and reporting. Furthermore, the platform supports a variety of programming languages, including RPG, COBOL, and Java, making it flexible for developers who require diverse tools for application development.

The AS/400E is also known for its exceptional reliability and uptime, making it a preferred choice for critical business applications in industries such as finance, healthcare, and manufacturing. This reliability is backed by advanced error detection and correction mechanisms, as well as redundancy features that help prevent data loss and minimize downtime.

In terms of scalability, the AS/400E can effortlessly expand to accommodate growing business demands. Organizations can increase processing power by adding more resources without significant disruption. This scalability, combined with the system’s built-in virtualization capabilities, allows businesses to optimize resource usage and streamline operations.

Security is another defining feature of the AS/400E. The platform incorporates various layers of security measures, including user authentication, encryption, and comprehensive auditing capabilities, ensuring that sensitive business data is protected against unauthorized access.

Overall, the IBM AS/400E remains a powerful tool in the enterprise computing landscape, providing businesses with an integrated, reliable, and secure solution for their technological needs. Its enduring popularity is a testament to its capability to evolve with changing business requirements while maintaining its core attributes of high performance and stability.
Top Page Image Contents