CHGPF Quirk

July 13, 2005 Hey, Ted

I increased the size of a character field in the DDS of a physical file and ran the Change Physical File (CHGPF) command to apply the change. I was surprised to find that the changed field remained unchanged in one of my logical files. Can you explain why?

–Michael

Until recently, I was under the impression that CHGPF recreates all logical files, but I was wrong. CHGPF only changes the logical files that share the record format of the physical file. This is documented in the Database Programming manual. (See Record format relationships between physical and logical database files.)

What Program Uses That File?

July 13, 2005 Hey, Ted

We would like to delete a logical file that we no longer need. We got a list of programs that used the file from our documentation tool and changed those programs to use a newer logical. However, the Display Object Description (DSPOBJD) command tells us that the file is still being used. How can we find the program or programs that are accessing the file?

–Bobby

I suggest you journal the physical file(s) over which the logical file is built. Specify OMTJRNE(*NONE), because you need the system to record opens and closes. The following commands create a journal and start

Admin Alert: Turning Off ODBC Query Timeout Limits

July 13, 2005 Joe Hertvik

OS/400 ODBC processing is notorious for obscure error messages that offer little information about their causes or their solutions. One of the strangest is the SQL0666 error, which stops SQL query processing when the estimated query run time exceeds the system’s query processing limit. While others have documented how to avoid this error by changing an ADO property, newer iSeries Access ODBC drivers allow you to disable query timeouts directly within your Data Sources (DSN).

For those who have not run into it, the SQL0666 error usually happens when you are using ODBC to process a large query from your