Integrated File System Introduction

 

Use QNTC through the integrated file system interface

By using either the OS/400 file server or the integrated file system commands, user displays, and APIs, you can access the QNTC file system through the integrated file system interface. You should be aware of the following considerations and limitations.

 

Authorities and ownership in the QNTC file system

The QNTC file system does not support the ownership concept of a file or directory. Attempts to use a command or API to change the ownership of files that are stored in QNTC will fail. A system user profile, called QDFTOWN, owns all of the files and directories in QNTC.

The authority to NT server files and directories is administered from the Windows NT server. QNTC does not support the WRKAUT and CHGAUT commands.

 

Case-sensitivity in the QNTC file system

The QNTC file system preserves the same uppercase and lowercase form in which object names are entered, but does not distinguish between uppercase and lowercase in the names. A search for object names achieves the same result regardless of whether characters in the names are uppercase or lowercase.

 

Path names in the QNTC file system

• The path name must begin with a slash and can be up to 255 characters long.
• Path names are case sensitive.
• The path consists of the file system name, the Windows NT server name, the sharename, the directory and sub-directory names, and the object name. Path names have the following form:

       /QNTC/Servername/Sharename/Directory/ . . . /Object
  (QNTC is a required part of the path name.)
  

• The server name can be up to 15 characters long. It must be part of the path.
• The sharename can be up to 12 characters long.
• Each component of the path name after the sharename can be up to 255 characters long.
• Within QNTC, 130 levels of hierarchy are generally available. If all components of the path name are included as hierarchy levels, the directory hierarchy can be as many as 132 levels deep.
• Names are stored in the Unicode CCSID.
• Each functional Windows NT server in the local subnet will automatically appear as a directory under /QNTC. Use the Make Directory (MKDIR) command (see Table 2) or mkdir() API (see Perform operations using APIs) to add Windows NT servers outside the local subnet.

 

Links in the QNTC file system

The QNTC file system supports only one link to an object. You can not create or store symbolic links in QNTC. You can use a symbolic link from the "root" (/) or QOpenSys file system to access data in QNTC.

See Link for a description of links.

 

Use integrated file system commands and displays in the QNTC file system

The commands listed in Perform operations using CL commands can operate on the QNTC file system, except for the following:

ADDLNK

APYJRNCHG

CHGOWN

CHGAUT

CHGPGP

CHKIN

CHKOUT

DSPAUT

ENDJRN

RST

SAV

SNDJRNE

STRJRN

WRKAUT

WRKOBJOWN

WRKOBJPGP

The same restrictions apply to the user displays that are described in Perform operations using iSeries menus and displays.

 

Use the MKDIR command in the QNTC file system

Use the Make Directory (MKDIR) command to add a server directory to the /QNTC directory. All functional Windows NT servers in the local subnet are automatically created. Those Windows NT servers outside the local subnet must be added using the MKDIR command or mkdir() API. For example:

MKDIR '/QNTC/NTSRV1'

would add the NTSRV1 server into the QNTC file system directory structure to enable access of files and directories on that server.

You can also add the a new server to the directory structure by using the TCP/IP address. For example:

MKDIR '/QNTC/9.130.67.24'

would add the server into the QNTC file system directory structure.

If you use mkdir() API or the MKDIR CL command to add directories to the directory structure, they will not remain visible across IPLs. The MKDIR command or mkdir() API must be reissued after every system IPL.

 

Use integrated file system APIs in the QNTC file system

The C language functions listed in Perform operations using APIs can operate on the QNTC file system, except for the following:

• The chmod(), fchmod(), utime(), and umask() functions will have no effect on objects in QNTC, but attempting to use them will not cause an error.
• The QNTC file system does not support the following functions:

  chown()

  fchown()

  givedescriptor()

  link()

  QjoEndJournal()

  QjoRetrieveJournalInformation()

  QJORJIDI()

  QJOSJRNE()

  QjoStartJournal()

  Qp0lGetPathFromFileID()

  readlink()

  symlink()

  takedescriptor()

---

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]