Working with output of the RTVDIRINF and PRTDIRINF commands

0 - The object's data is not offline.

1 - The object's data is offline.

0 - The object is not checked out.

1 - The object is checked out.

1 - The object's data is stored locally.

2 - The object's data is on a remote system.

*NOUSRPRF - This special value is used by the Network File System to indicate that there is no user profile on the local iSeries server with a user ID (UID) matching the UID of the remote object.

*NONE - The object does not have a primary group

*NOUSRPRF - This special value is used by the Network File System to indicate that there is no user profile on the local server with a group ID (GID) matching the GID of the remote object.

0 (NOT_JOURNALED) - The object is currently not being journaled.

1 (JOURNALED) - The object is currently being journaled.

0 - The object is not journaled with subtree semantics.

1 - The object is journaled with subtree semantics. New objects created within this directory's subtree will inherit the journaling attributes and options from this directory.

0 - Object is not journaled with optional entries.

1 - Object is journaled with optional entries.

0 - Object is not journaled with after images.

1 - Object is journaled with after images.

0 - Object is not journaled with before images.

1 - Object is journaled with before images.

*NONE - No auditing occurs for this object when it is read or changed regardless of the user who is accessing the object.

*USRPRF - Audit this object only if the current user is being audited. The current user is tested to determine if auditing should be done for this object. The user profile can specify if only change access is audited or if both read and change accesses are audited for this object.

*CHANGE - Audit all change access to this object by all users on the system.

*ALL - Audit all access to this object by all users on the system. All access is defined as a read or change operation.

*NOTAVL - The user performing the operation is not allowed to retrieve the current object auditing value.

*SYSTEM - Object exists in system domain.

*USER - Object exists in user domain.

*NONE - No auditing occurs for this object when it is read or changed regardless of the user who is accessing the object.

*USRPRF - Audit this object only if the current user is being audited. The current user is tested to determine if auditing should be done for this object. The user profile can specify if only change accesses are audited or if both read and change accesses are audited for this object.

*CHANGE - Audit all change accesses to this object by all users on the system.

*ALL - Audit all accesses to this object by all users on the system. All accesses are defined as a read or change operation.

*NOTAVL - The user performing the operation is not allowed to retrieve the current create object auditing value.

*SYSVAL - The object auditing value for the objects created in the directory is determined by the system auditing value (QCRTOBJAUD).

Valid values are:

x'00' (SCANNING_NO) - The object will not be scanned according to the rules described in the scan-related exit programs.

x'01' (SCANNING_YES) - The object will be scanned according to the rules described in the scan-related exit programs if the object has been modified or if the scanning software has been updated since the last time the object was scanned.

x'02' (SCANNING_CHGONLY) - The object will be scanned according to the rules described in the scan-related exit programs only if the object has been modified since the last time the object was scanned. It will not be scanned if the scanning software has been updated. This attribute only takes effect if the Scan file systems control (QSCANFSCTL) system value has *USEOCOATR specified. Otherwise, it will be treated as if the attribute is SCANNING_YES.

Valid values are:

x'01' - After an object is created in the directory, the object will be scanned according to the rules described in the scan-related exit programs if the object has been modified or if the scanning software has been updated since the last time the object was scanned.

x'00' (SCAN_REQUIRED) - A scan is required for the object either because it has not yet been scanned by the scan-related exit programs, or because the objects data or CCSID has been modified since it was last scanned. Examples of object data or CCSID modifications are: writing to the object, directly or through memory mapping; truncating the object; clearing the object; and changing the objects CCSID attribute.

x'01' (SCAN_SUCCESS) - The object has been scanned by a scan-related exit program, and at the time of that last scan request, the object did not fail the scan.

x'02' (SCAN_FAILURE) - The object has been scanned by a scan-related exit program, and at the time of that last scan request, the object failed the scan and the operation did not complete. Once an object has been marked as a failure, it will not be scanned again until the object's scan signature is different than the global scan key signature or independent ASP group scan key signature as appropriate. Therefore, subsequent requests to work with the object will fail with a scan failure indication. Examples of requests which will fail are opening the object, changing the CCSID of the object, copying the object.

x'05' (SCAN_PENDING_CVN) - The object is not in a *TYPE2 directory, and therefore will not be scanned until the directory is converted.

x'06' (SCAN_NOT_REQUIRED) - The object does not require any scanning because the object is marked to not be scanned.

When an object is in an independent ASP group, the object scan signature is compared to the associated independent ASP group scan signature. When an object is not in an independent ASP group, the object scan signature is compared to the global scan signature value. This field will be one of the following values:

x'00' - The compared signatures are not different.

x'01' - The compared signatures are different.

x'00' - The object was not scanned in binary mode.

x'01' - The object was scanned in binary mode. If the object scan status is SCAN_SUCCESS, then the object was successfully scanned in binary. If the object scan status is SCAN_FAILURE, then the object failed the scan in binary.

0 - The object can be shared with readers only.

1 - The object can be shared with readers and writers.

0 - The object does not have anIBM i digital signature.

1 - The object does have anIBM i digital signature.

0 - None of the signatures came from a source that is trusted by the system.

1 - The object was signed by a source that is trusted by the system. If the object has multiple signatures, at least one of the signatures came from a source that is trusted by the system.

0 - The object has only one digital signature.

1 - The object has more than one digital signature. If the QEZSYSSIG field has the value 1, at least one of the signatures is from a source trusted by the system.

0 - The auxiliary storage will be allocated normally. That is, as additional auxiliary storage is required, it will be allocated in logically sized extents to accommodate the current space requirement, and anticipated future requirements, while minimizing the number of disk I/O operations.

1 - The auxiliary storage will be allocated to minimize the space used by the object. That is, as additional auxiliary storage is required, it will be allocated in small sized extents to accommodate the current space requirement. Accessing an object composed of many small extents may increase the number of disk I/O operations for that object.

2 - The system will dynamically determine the optimum auxiliary storage allocation for the object, balancing space used versus disk I/O operations. For example, if a file has many small extents, yet is frequently being read and written, then future auxiliary storage allocations will be larger extents to minimize the number of disk I/O operations. Or, if a file is frequently truncated, then future auxiliary storage allocations will be small extents to minimize the space used. Additionally, information will be maintained on the stream file sizes for this system and its activity. This file size information will also be used to help determine the optimum auxiliary storage allocations for this object as it relates to the other objects sizes.

0 - The main storage will be allocated normally. That is, as much main storage as possible will be allocated and used. This minimizes the number of disk I/O operations since the information is cached in main storage.

1 - The main storage will be allocated to minimize the space used by the object. That is, as little main storage as possible will be allocated and used. This minimizes main storage usage while increasing the number of disk I/O operations since less information is cached in main storage.

2 - The system will dynamically determine the optimum main storage allocation for the object depending on other system activity and main storage contention. That is, when there is little main storage contention, as much storage as possible will be allocated and used to minimize the number of disk I/O operations. And when there is significant main storage contention, less main storage will be allocated and used to minimize the main storage contention. This option only has an effect when the storage pool's paging option is *CALC. When the storage pool's paging option is *FIXED, the behavior is the same as STG_NORMAL. When the object is accessed through a file server, this option has no effect. Instead, its behavior is the same as STG_NORMAL.

0 - The directory format is *TYPE1.

1 - The directory format is *TYPE2.

0 - The stream file format is *TYPE1.

1 - The stream file format is *TYPE2.

0 - The stream file format is *TYPE1.

1 - The stream file format is *TYPE2.

0 - Object will be saved.

1 - Object will not be saved. Additionally, if this object is a directory, none of the objects in the directory's subtree will be saved unless they were explicitly specified as an object to be saved. The subtree includes all subdirectories and the objects within those subdirectories.

0 - Object is not virtual disk storage.

1 - Object is virtual disk storage.

0 - File system is not case sensitive.

1 - File system is case sensitive.

0 - Auxiliary storage pool is not overflowed.

1 - Auxiliary storage pool is overflowed.

0 - The object can be changed.

1 - The object cannot be changed.

0 - The object is not hidden.

1 - The object is hidden.

0 - The object is not a system file.

1 - The object is a system file.

0 - The object has not changed.

1 - The object has changed.

0 - The object has not changed and does not need to be saved.

1 - The object has changed and does need to be saved.

*SYSBAS - The journal receiver resides in the system or user ASP.

ASP device - The name of the ASP device that contains the journal receiver.

x'00' (NONE) - There are no partial transactions.

x'01' (PARTIAL_TRANSACTION) - The object was restored with partial transactions. This object cannot be used until the Apply Journaled Changes (APYJRNCHG) or Remove Journaled Changes (RMVJRNCHG) command is used to complete or rollback the partial transactions.

x'02' (ROLLBACK_ENDED) - The object had a rollback operation ended using the "End Rollback" option on the Work with Commitment Definition (WRKCMTDFN) screen. It is recommended that the object be restored as it cannot be used. As a last option, the Change Journaled Object (CHGJRNOBJ) command can be used to allow the object to be used. Doing this, however, can leave the object in an inconsistent state.