Re: V7R1 - LDAP server failed to start with GLD040B, causing SSO via Kerberos to fail, folloiwng IPL with PTF apply -- MIDRANGE-L

Subject: Re: V7R1 - LDAP server failed to start with GLD040B, causing SSO via Kerberos to fail, folloiwng IPL with PTF apply
From: CRPence <crpbottle@xxxxxxxxx>
Date: Tue, 18 Apr 2017 11:04:19 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 18-Apr-2017 09:04 -0500, Steinmetz, Paul wrote:

IBM suggested I check my audit journal, might tell which PTF deleted
the object. I checked the QAUDITDO.

SELECT *
FROM QGPL.QAUDITDO
WHERE DOOLIB = QUSRDIRDB
and DOONAM = QAGLDCNV52

DO 2017-04-15-23.18.57.150176
DO 2017-04-15-23.18.57.173056

Found 2 entries matching the date/timestamp, but those entries did
not include the PTF detail.
Any thoughts from the group?

Look at more revealing details available as fields in that output file, such as the name of the user, job, and program [e.g. DOJOB, DOUSER, DONBR, DOPGM, DOPGMLIB] identified as responsible for generating those two Delete Object (DO) entries; then refer to the spooled joblog for the job.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: V7R1 - LDAP server failed to start with GLD040B, causing SSO via Kerberos to fail, folloiwng IPL with PTF apply , Steinmetz, Paul

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.