IBM Support

JR55461: "DSDLOCKD -P" DOES NOT FOLLOW SETTINGS IN DSDLOCKD.CONFIG

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • If there are specific logfile settings in dsdlockd.config,
    these will be respected during normal dsdlockd invocations.
    
    However, cleanup invocations from "dsdlockd -p" do not read the
    file, and always write to the default log location at
    dsdlockd.log
    

Local fix

  • The cleanup invocation will always write to dsdlockd.log
    If there is a need to suppress or remove this logfile, you can
    set permissions on dsdlockd.log (and prevent the process from
    writing to this file), or you can use a symbolic link from this
    file to /dev/null
    

Problem summary

  • Will be considered for a future release.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR55461

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    912

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-03

  • Closed date

    2016-03-03

  • Last modified date

    2016-03-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R912 PSN

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"912","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 March 2016