Implications of Improper Startup and Shutdown

	a. Select option 2 (Change) from the CFGTCP menu to add a name for an
	address.
	b. Select option 1 from the CFGTCP menu to add an entire new address with
	names.
	6. Verify that the names LOOPBACK and LOCALHOST are associated with the IP
	address 127.0.0.1 in the host table.
	7. Verify that the long and short names of each NFS server you need access to
	are included in the host table. You only need to do this if you will be using the
	system as an NFS client. If they are not in the host table, and a DNS is not
	being used, then you must add the long and short names.
	Here is an example of a TCP/IP Host table:
	Internet	Host
	Opt Address	Name

	19.45.216.4	THISHOST
		THISHOST.COMPANY.DOM1.COM
	19.45.216.93	NFSSERV1
		NFSSERV1.COMPANY.DOM1.COM
	127.0.0.1	LOOPBACK
		LOCALHOST

Implications of Improper Startup and Shutdown

The various components of the Network File System make up a complex and interdependent system. This means that they rely on each other for common, efficient functioning. There are, therefore, many functions that can fail if users startup or shutdown improperly:

vIf the user does not start the RPC binder daemon ®rst, then all local server ports will fail to map properly. No requests from the client will be processed.

vIf the client starts before the server has loaded the mount daemon, any mount requests the client makes will fail. Furthermore, the NLM and NSM daemons will not be able to grant locks until users start them on both the client and the server.

vShould the client be started and make mount requests before the server has issued the export command, all mount requests will fail.

vIf a user ends the RPC binder daemon (port mapper) ®rst, then all the other daemons cannot unregister with the RPC binder (port mapper) daemon.

vIf users do not end all the daemons, then there can be confusion on the next startup of which daemons are operating and which are not.

Proper Startup Scenario

In a typical NFS server startup:

1.The user starts the RPC binder (port mapper) daemon (QNFSRPCD). This daemon then waits on a known port (#111) for local RPC requests to register a service. This daemon also waits for remote RPC requests to query a local service.

2.The user calls the export command, creating a list of exported directories in the export table from information contained in the /etc/exports ®le.

3.The user starts the NFS server daemon (QNFSNFSD) or daemons. It registers to the local RPC binder daemon, which knows on which port the NFS server

66OS/400 Network File System Support V4R4

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.

IBM AS/400E manual Implications of Improper Startup and Shutdown, Proper Startup Scenario

Models: AS/400E

Implications of Improper Startup and Shutdown

Proper Startup Scenario

AS/400E specifications