Re: Tracking Changes On Command CHGJOBQE -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Tracking Changes On Command CHGJOBQE
From: Bryan Dietz <bdietz400@xxxxxxxxx>
Date: Fri, 01 Aug 2014 09:40:05 -0400
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>

you should be able to also use one of these:
QIBM_QCA_CHG_COMMAND
QIBM_QCA_RTV_COMMAND

then you could save(log) any of the information entered in the command.

using the audit journal you can see who used the command.
Not sure that you see what changed.

--
Bryan

Jack Kingsley said the following on Fri, 8/1/2014 5:45 AM:

It appears the only way to log these changes to QAUDJRN is with CHGOBJAUD.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Tracking Changes On Command CHGJOBQE , 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.