10.No tabs or line feeds can be used in the path name

11.All characters following the pound sign '#' are considered comments until the end of the line. The only exception to this rule is the HOSTOPT parameter, which uses the '#' character as a starting point for each HOSTOPT entry.

Formatting the HOSTOPT (Host Options) Parameter

In /etc/exports, you can provide additional information for each export entry related to the remote NFS clients who will access your entry. For each remote NFS client, you can specify the following items:

/path_name #HOSTOPT HostName=client1, PathNameCodePage=NNN, DataFileCodePage=NNN, NoWaitForWrites

HostName

The name of the remote NFS client for which you are specifying additional export options. You should specify this client by name in one of the lists as a host that has access to this export entry. You can also use netgroups for this entry. You can list multiple clients and netgroups for every entry, each with its own list of speci®c export options.

For more information about the HostName option on the HOSTOPT parameter, see ªCHGNFSEXP/EXPORTFS Displayº on page 31.

PathNameCodePage

The path name code page is used for the path name components of the ®les exported to and mounted on the speci®ed NFS client or netgroup. For any clients or netgroups not speci®ed on the HostName parameter, the default network path name code page (ASCII) is used.

DataFileCodePage

The data ®le code page is used for data of the ®les exported to and mounted on the speci®ed NFS client or netgroup. For any hosts not speci®ed on the HostName parameter, the default network data code page (binary, no conversion) is used.

If the entry being exported resolves to an object within the QSYS.LIB ®le system and the network data ®le code page is speci®ed, then data ®les are

opened by OS/400 Network File System Support. NFS will use the open() API with the O_TEXTDATA and O_CODEPAGE options.

Note: See the System API Reference, SC41-4801 book for more details on the open() API and the O_TEXTDATA and O_CODEPAGE options.

NoWaitForWrites

The NoWaitForWrites option speci®es whether write requests are handled synchronously or asynchronously for the NFS client or netgroup name. The absence of this option means that data will be written to disk immediately (synchronously). If this ¯ag is used, then the data is not guaranteed to be written to disk immediately and can be used to improve performance (asynchronously).

Additional Format Rules for the HOSTOPT (Host Options) Parameter

1.The options must start with #HOSTOPT. There must only be one #HOSTOPT although you could have many host names.

2.Additional host names and their options must be separated by a colon.

Appendix B. Understanding the /etc Files 95

Page 113
Image 113
IBM AS/400E Formatting the Hostopt Host Options Parameter, HostName, PathNameCodePage, DataFileCodePage, NoWaitForWrites

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.