Home > IT Answers > OPNDBF then CLOF – the joblog indicates that the file was closed but it still appears in dspjob #14
Gzbintech
5 pts.
 OPNDBF then CLOF – the joblog indicates that the file was closed but it still appears in dspjob #14
AS400 iseries, CLOF, OPNDBF
                                 Member/    Record     File    I/O  ----Open--- File            Library    Device     Format     Type       Count Opt Shr-Nbr

B99FL161   XYZISDTA   B99FL161   B99FX161   LGL        4 IO  YES  3

 

When the NBR is > 1 the close only reduces the NBR by 1 - and the file still appears in the joblog. When the OPNDBF is

used to actually open the file it opens the file in XYZISDTA because it was left behind from the close. This is a problem

because this file is now pointing to the wrong library.



Software/Hardware used:
iSeries
ASKED: March 29, 2012  8:07 PM
UPDATED: March 30, 2012  12:25 PM
RELATED QUESTIONS
Answer Wiki:
Last Wiki Answer Submitted:  Be the first to answer this question.
All Answer Wiki Contributors:  Be the first to answer this question.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

This part of your sample output shows what might be part of your problem: 

----Open---
  Shr-Nbr

  YES  3

The file that you show is set for “shared processing”. The data you show says that the job currently has three shared connections to it. Use the <help>-key to see something about what those columns refer to.

Without seeing how you’re declaring, opening and closing the file (plus any overrides that might have been run earlier along with any override deletions), and also seeing how the sharing attribute is set on the file itself, there’s no way to know what changes you might want to make.

Also, it might be necessary to tell us what version of the OS is involved.

Tom

TomLiotta
 108,330 pts.