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

 

QPWFSERVER Authorization List

 

The QPWFSERVER is an authorization list (object type *AUTL) that provides

 

additional access requirements for all objects in the QSYS.LIB ®le system being

 

accessed through remote clients. The authorities speci®ed in this authorization list

 

apply to all objects within the QSYS.LIB ®le system.

 

The default authority to this object is PUBLIC *USE authority. The administrator can

 

use the EDTAUTL (Edit Authorization List) or WRKAUTL (Work With Authorization

 

List) commands to change the value of this authority. The administrator can assign

 

PUBLIC *EXCLUDE authority to the authorization list so that the general public

cannot access QSYS.LIB objects from remote clients.

Mounting and QSYS.LIB

Users can mount the QSYS.LIB ®le system on a client, but users cannot mount

over the QSYS.LIB ®le system. Users should export and mount a sub-library from

QSYS.LIB rather than mounting QSYS.LIB directly on the client. The reason for this

is that QSYS.LIB contains hundreds of objects. Trying to display or process all of

the objects can affect client performance.

 

Support for User Spaces

 

NFS supports the exporting and mounting of user spaces, with the following

 

exceptions:

 

v User spaces cannot be over 16 megabytes

 

v User spaces are not CCSID-tagged or tagged for a code page by default. If a

 

CCSID is asked for, NFS will translate the data if the user speci®es the CCSID.

 

v User space ®les (*USRSPC object type) can be appended to using NFS, but this

 

may produce unpredictable results with how data is written.

 

File Modes of Database Members

 

The ®le mode of any database members needs to be the same as the ®le mode of

 

the parent ®le. No matter what users specify, NFS will always create new database

 

members with the ®le mode of the parent. If users specify other ®le modes than that

 

of the parent, they will not receive an error return code. NFS will create the new

 

member with the ®le mode of the parent no matter what the user speci®es.

 

Path Names of .FILE Objects

Users need to be aware of the maximum database record length when editing database members. Users specify the record length when creating a physical ®le. The default record length for all .FILE objects created in QSYS.LIB is 92 bytes if created with one of the following methods:

1.mkdir() API

2.MKDIR (Make Directory) command

3.MD (Make Directory) command

4.CRTDIR (Create Directory) command

Source physical ®les contain a date stamp (6 bytes) and sequence number (6 bytes), using 12 total bytes of data. This is accounted for by subtracting 12 bytes

58OS/400 Network File System Support V4R4

Page 75 Page 77
Page 76
Image 76
IBM AS/400E Qpwfserver Authorization List, Mounting and QSYS.LIB, Support for User Spaces, File Modes of Database Members
Page 75 Page 77

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