AS/400 log who changed source member

Tags:
AS/400
Power 7 machine
Accountants audit IT. He asks for log user change program member information. Does any one have the solution or suggestion? Thanks.


Software/Hardware used:
Power7 V7R1M0 SEU
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • CharlieBrowne

    There is nothing automatic in the AS400 to give you that information, unless you were journaling the source file. (You would NEVER) want to do that.

    The best solution is to get a source control software package. There are many good ones available: HAWKEYE, ABSTRACT,  and more

    62,385 pointsBadges:
    report
  • lance2221357
    I found exit point  QIBM_QSU_ALW_EDIT can know user edit member, But can't confirm actual changed? Maybe IBM can support another exit point.
    270 pointsBadges:
    report
  • ToddN2000
    I have used HAWKEYE in the past with a lot of success. Other than that you would have to be running some form of change management software. A lot of the information that is captured by IBM would only show the very last occurrence. If a program was changed multiple time by multiple users and recompiled for use, the the DSPOBJD would just show the very last user that created it. IF you do not have one in place currently, I cannot think of a way you would be able to get any historical info. You could only capture today forward.
    135,295 pointsBadges:
    report
  • TheRealRaven
    Unfortunately, there is no product that tells you who last changed a source member in a source physical file. Products might only tell you who last used the product to change a source member. As CharlieBrowne mentioned, only database journaling will actually track such changes (and that can be a problem since most source member updates actually replace entire members every time).

    By using strict controls such as limiting access methods,  removing special authorities (and any private authorities to source), limiting access to commands, and enforcing the use only of the source control software, you can configure a system such that the product becomes the only viable method of changing source.

    In addition, object auditing should be enabled for source files. The audit journal entries can then act as a control to verify that only your chosen product is being used.
    36,320 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: