Troubleshooting
Problem
This document explains how to find logical files that have an invalid access path.
Resolving The Problem
This document explains how to find logical files that have an invalid access path.
To confirm if all access paths are valid for logical files in a certain library, do one of the following:
Option A:
1. For current releases you can use our system catalogs and run the following SQL:
SELECT SYSTEM_INDEX_SCHEMA, SYSTEM_INDEX_NAME, INDEX_PARTITION, INDEX_TYPE FROM qsys2/syspartitionindexes
WHERE INDEX_VALID = 'NO'
and MAINTENANCE <> 'REBUILD' and
table_schema = 'LIBNAMe'
Replace 'LIBNAME' with library you want to look at.
Option B:
| 1. | Issue the following CL command to create an outfile: DSPFD FILE(LIBNAME/*ALL) TYPE(*MBR) OUTPUT(*OUTFILE)OUTFILE(LIB/DSPFDOUT)FILEATR(*LF) |
| 2. | Run the following SQL statement to list the library name and file name of those files that have an invalid access path: SELECT MBLIB, MBFILE FROM LIB/DSPFDOUT WHERE MBINDX = 'N' and MBMANT = 'I' |
CHGLF FILE(LIB/FILE)FRCRBDAP(*YES)
Note: You must have an exclusive lock on the file. This rebuilds the file so it can be resource intensive, and it can take a long time depending on the size of the file. Provide as much memory as possible to the job to assist with this.
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"6.1.0"}]
Historical Number
468712192
Was this topic helpful?
Document Information
Modified date:
11 November 2019
UID
nas8N1014018