General Page
CHKDUPLIBS command
This command can be used to identify library conflicts between SYSBAS and IASPs.
Libraries of the same name cannot exist in both SYSBAS and an IASP. If a conflict does exist, the IASP will not be able to complete vary-on processing until the conflict is resolved.
This should be executed during the implementation of the environment, and at incremental times thereafter, on all nodes.
Parameters
IASP - Name of the IASP
IASP is available
When the IASP is Available (e.g. primary PowerHA cluster node), there are no current library conflicts, but the command will store a current list of IASP libraries in the cluster device domain data.
IASP is not available
This is typically run on a PowerHA backup, replicate or flashcopy node, where the IASP is not available.
The command will pull the information stored in the device domain data and compare those libraries with a list of libraries in SYSBAS on that node and report any conflicts in the job log of the user who ran the CHKDUPLIBS.
When the IASP cannot complete the vary-on process due to a duplicate library name conflict, the IASP remains in an "Active" status until the conflict is corrected.
At V7R1, a message CPDB8EB (Library &1 exists in *SYSBAS and ASP device &2) is posted to QSYSOPR, allowing the user to fix the problem and then reply to the message to continue/complete the vary-on process.
At any release with SmartAssist, the CHKDUPLIBS command may be run, and a list of conflicting libraries (libraries in both *SYSBAS and IASP) will be retrieved and provided to the user.
Was this topic helpful?
Document Information
Modified date:
07 January 2020
UID
ibm11169254