• The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
Menu
  • The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
  • 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 journaling a file named MYFILE.

    CRTJRNRCV JRNRCV(MYLIB/MYFILE0001)                           
    CRTJRN JRN(MYLIB/MYFILE) JRNRCV(MYLIB/MYFILE0001)           
    STRJRNPF FILE(MYLIB/MYFILE) 
             JRN(MYLIB/MYFILE)  
             IMAGES(*BOTH)       
             OMTJRNE(*NONE)
    

    The Display Journal (DSPJRN) command will retrieve the logged opens of the file.

    DSPJRN JRN(MYLIB/MYFILE) JRNCDE((F)) ENTTYP(OP)
    

    The entry-specific data of a logged open is defined as in the following table.

    Positions

    Description

    1 – 10

    File

    11 – 20

    Library

    21 – 30

    Member

    31

    I=opened for input

    32

    O=opened for output

    33

    U=opened for update

    34

    D=opened for delete

    You can use the Journal code finder to find the format of entry-specific data for journal codes.

    DSPJRN’s entry details panel will show you the name of the program that opened the file, the job that opened the file, the time the file was opened, and other pertinent information.

    You may be able to find the open of the logical file by viewing the entries, but if there are a lot of opens, you might prefer to copy the journal entries to a disk file and query them.

    DSPJRN JRN(MYLIB/MYFILE) 
    JRNCDE((F)) ENTTYP(OP) OUTPUT(*OUTFILE) OUTFILE (QTEMP/X)
    

    Having said all that, it is still possible that you won’t find your answer. If the program that is opening the file is one of IBM‘s, such as SQL/400 or Query/400, you won’t see IBM’s program’s name, but a program of your own that is higher in the call stack. In that situation, maybe the other information will give you enough of a hint that you’ll be able to track down the culprit.

    –Ted


    Share this:

    • Share on Reddit (Opens in new window) Reddit
    • Share on Facebook (Opens in new window) Facebook
    • Share on LinkedIn (Opens in new window) LinkedIn
    • Share on X (Opens in new window) X
    • Email a link to a friend (Opens in new window) Email

    Tags:

    Sponsored by
    FalconStor

    Simplify Secure Offsite Data Protection for IBM Power with FalconStor Habanero™

    IBM i teams are under growing pressure to ensure data is protected, recoverable, and compliant—without adding complexity or disrupting stable environments.

    FalconStor Habanero™ provides secure, fully managed offsite data protection purpose-built for IBM Power. It integrates directly with existing IBM i backup tools and processes, enabling reliable offsite copies without new infrastructure, workflow changes, or added operational overhead.

    By delivering and managing the service end-to-end, FalconStor helps organizations strengthen cyber resilience, improve disaster recovery readiness, and meet compliance requirements with confidence. Offsite copies are securely maintained and available when needed, supporting recovery, audits, and business continuity.

    FalconStor Habanero offers a straightforward way to modernize offsite data protection for IBM i: focused on simplicity, reliability, and resilience.

    Learn More

    Share this:

    • Share on Reddit (Opens in new window) Reddit
    • Share on Facebook (Opens in new window) Facebook
    • Share on LinkedIn (Opens in new window) LinkedIn
    • Share on X (Opens in new window) X
    • Email a link to a friend (Opens in new window) Email

    CHGPF Quirk Admin Alert: Turning Off ODBC Query Timeout Limits

    Leave a ReplyCancel reply

Volume 5, Number 27 -- July 13, 2005
THIS ISSUE
SPONSORED BY:

WorksRight Software
Profound Logic Software
COMMON

Table of Contents

  • CHGPF Quirk
  • What Program Uses That File?
  • Admin Alert: Turning Off ODBC Query Timeout Limits

Content archive

  • The Four Hundred
  • Four Hundred Stuff
  • Four Hundred Guru

Recent Posts

  • PHP’s Evolution On The IBM i Platform Continues
  • Protecting IBM i Data For The AI Revolution
  • Guru: Two More Small But Handy RPG Enhancements: LIKE(*EXT) And %LOOKUPNE
  • IBM i Integration Gives Costco Shoppers Real-Time Inventory
  • IBM i PTF Guide, Volume 28, Number 33
  • IBM “Price Harmonization” Increases For Power Systems Coming In The New Year
  • Code For i Continues To Grow. Here Is What’s New
  • PowerSC: Your One-Stop Shop For Security On IBM i – And Beyond
  • As I See It: You’ve Been Flocked
  • IBM i PTF Guide, Volume 28, Number 32

Subscribe

To get news from IT Jungle sent to your inbox every week, subscribe to our newsletter.

Pages

  • About Us
  • Contact
  • Contributors
  • Four Hundred Monitor
  • IBM i PTF Guide
  • Media Kit
  • Subscribe

Search

Copyright © 2025 IT Jungle