The PFSI structure

The PFS initialization structure (BPXYPFSI, referred to as the PFSI) contains the following fields (each name is prefixed with the characters pfsi_):

Field: Description
: Supplied Fields
ver: The version number of this PFSI.
ook: An indication that this PFS is running outside the kernel.
alone: An indication that this PFS is the only PFS running in the address space.
new: An indication that this is the first time this PFS has been initialized in the address space.
romntclient: Set on to indicate that the PFS does not support simultaneous R/O mounts from multiple systems; the LFS is responsible for making R/O file systems available for sharing in a sysplex system.
The default value is off. This indicates that the PFS supports sharing of R/O file systems in a sysplex.
rwmntsysplex: Set on to indicate that the PFS does not support simultaneous R/W mounts from multiple systems; the LFS is responsible for making R/W file systems available for sharing in a sysplex system.
The default value is off. This indicates that the PFS supports sharing of R/W file systems in a sysplex.
initcompecb: The ECB that the PFS posts when its initialization is complete.
pfsecb: The ECB that the LFS posts when z/OS UNIX is stopped. The PFS must be waiting on this ECB.
restart: The address of the restart option byte. The PFS sets this byte any time during its processing, to control if and how it is to be restarted if it should terminate.
dumpptr: The address of dump information. This information is used by the PFS to add significant LFS areas to the dumps that are taken by the PFS.
pfsid: The PFS identifier that is used with osi_sleep and osi_wakeup.
asname: The value of the ASNAME parameter of the FILESYSTYPE statement.
ep: The value of the ENTRYPOINT parameter of the FILESYSTYPE statement.
: Returned Fields
pfsanchor: The PFS initialization token. This token value is passed back to the PFS on every subsequent call from the LFS as part of the token_structure, which is the first parameter of every call. This field typically contains the address of the PFS's main anchor block.
vfso: The address of the PFS's VFS operation vector table.
vnop: The address of the PFS's vnode operation vector table.
srb: An indication that SRB mode is supported.
asyio: An indication that asynchronous I/O is supported.
usethreads: An indication that the PFS is requesting support for the osi_thread service. This field can be set only by PFSs that are running outside the kernel.
disableLLA: An indication that the LFS should not provide lookup lookaside function for this PFS. If there is not a strict one-to-one correspondence between the spelling of a file name in a directory and the vnode-inode pair that represents the file, the PFS should set this bit. For example, if '/usr/dl/fl,attr=fb' and '/usr/dl/fl' represent the same file in the /usr/d1 directory, you must disable the LFS lookup lookaside function. If directories are remote and files may be removed from them remotely, the LFS's LLA cache should also be disabled.
stayalone: An indication that the LFS should not initialize any other PFSs in this address space. This field can be set only by PFSs that are running outside the kernel.
immeddel: An indication that the PFS supports deleting a removed file's data when its open count becomes zero, rather than waiting for vn_inactive to free the space.
cpfs: An indication that the PFS is written in C, and is requesting that the LFS invoke it with pre-initialized C environments.
datoffmove: An indication that the PFS supports DATOFF move for page read operations. For more information, see Reading from and writing to files.
pfstype: The type of the PFS. This identifies the PFS as a local file PFS, a remote file PFS, or a socket PFS.
pipebuf: pathconf() _PC_PIPE_BUF value, if applicable
maxcanon: pathconf() _PC_MAX_CANON value, if applicable
maxinput: pathconf() _PC_MAX_INPUT value, if applicable
chownrstd: pathconf() _PC_CHOWN_RESTRICTED value, if applicable
vdisable: pathconf() _PC_VDISABLE value, if applicable.
Pathconf() values that are not constant for all files supported by the PFS may be reported through the vn_pathconf operation.
compon: The PFS's three-letter component (or module) prefix.
compid: The PFS's five-letter component (or product) ID.
The component prefix and ID are used in dump titles for dumps that are taken by the LFS when there is an abnormal end in the PFS from which it does not recover.
modind: An indication that the PFS is supplying indirect addresses in the VFS and vnode operations vector tables for the various VFS and vnode operations routines.
complow: The low value for the PFS reason code high byte. For more information, see PFS support for reason code error text.
comphigh: The high value for the PFS reason code high byte. For more information, see PFS support for reason code error text.