SI60879 - OSP-DB DSPDBR shows dependent files with no libraries

TYPE PROGRAM  RELEASE   NUMBER   MIN/MAX  OPTION
---- -------- --------- -------  -------  ------
NONE



NOTICE:
-------
Application of this PTF may disable or render ineffective programs that
use system memory addresses not generated by the IBM translator,
including programs that circumvent control technology designed to limit
interactive capacity to purchased levels.  This PTF may be a prerequisite
for future PTFs.  By applying this PTF you authorize and agree to the
foregoing.

This PTF is subject to the terms of the license agreement which
accompanied, or was contained in, the Program for which you are obtaining
the PTF.  You are not authorized to install or use the PTF except as part
of a Program for which you have a valid Proof of Entitlement.

SUBJECT TO ANY WARRANTIES WHICH CAN NOT BE EXCLUDED OR EXCEPT AS EXPLICITLY
AGREED TO IN THE APPLICABLE LICENSE AGREEMENT OR AN APPLICABLE SUPPORT
AGREEMENT, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT,
REGARDING THE PTF.

The applicable license agreement may have been provided to you in printed
form and/or may be viewed using the Work with Software Agreements (WRKSFWAGR)
CL command.





APAR Error Description / Circumvention

-----------------------------------------------
DSPDBR shows dependent logical files with blank library name.

CORRECTION FOR APAR SE64868 :
-----------------------------
New support is added to delete the dependent logical file that
is currently out of context.

Assume that the physical file is named MYLIB/T1 and that a
dependent logical file is currently out of context.

Create the following data area:
CRTDTAARA DTAARA(QTEMP/QDB_NOLIB) TYPE(*CHAR) LEN(1)

Issue the following comand:
DSPDBR FILE(MYLIB/T1)

We will first attempt to move the out of context logical file
into QTEMP and then delete it.  If the logical file is locked
exclusively in another job, the move will fail.
You will have to end the job that is holding the lock. If the
lock is held in a system job, you will have to IPL and then try
the statements above again.

If the logical file is locked less than *SHRUPD, the move to
QTEMP will succeed, but the delete will fail. Since the file is
now in QTEMP, you should be able to issue commands against it
such as WRKOBJLCK, DSPFD, etc. You will have to end the job that
is holding the lock. If the lock is held in a system job you
will have to IPL and then try the statements above again.

If the logical file and logical file member are not locked by
another job, the move and delete will succeed.

CIRCUMVENTION FOR APAR SE64868 :
--------------------------------
None.


Activation Instructions


None.




Special Instructions


None.


Default Instructions

THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.



Supersedes

PTF/FIX NO(S).  APAR TITLE LINE
--------------  ------------------------------------------------------------
     NONE

Summary Information

IBM i Support