S36 OCL audits

35 pts.
Tags:
AS/400
OCL
Our auditors are requesting that we show all the times an OCL was changed during the year, as opposed to only the last change. Is there anything like Object Audit Level information that would apply to OCLs?


Software/Hardware used:
AS400, iSeries
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: 12  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.
  • ToddN2000
    Are they just looking for the dates it was changed or what was actually changed? If you use a change management system this may provide the details you need.
    134,585 pointsBadges:
    report
  • ccrone7
    They are looking to verify that the dates the OCL actually changed matches our change management system.
    35 pointsBadges:
    report
  • Splat
    I've never had much to do with the S/36 environment on the iSeries but, assuming OCL is interpreted rather than compiled, there'd be no object to audit but rather a source member in a source file.  

    DSPFD TYPE(*MBR) and DSPFD TYPE(*MBRLIST) both provide last change dates for the file members.
    12,915 pointsBadges:
    report
  • ToddN2000
    As far as I know, you can only get the last or most recent change information. The only way I can think of would have been if you backed up your source library on a daily basis and kept a years worth of back ups. Then you might be able to go back and review the changes dates for every day. Definitely not practical.
    134,585 pointsBadges:
    report
  • Splat
    Is the requirement to list differences in the last changed date of the OCL member with the last changed date from the change management software or is it to identify what changes were made?

    I had assumed the former from the descriptions.
    12,915 pointsBadges:
    report
  • ccrone7
    No, it is to identify all the times an OCL was changed in a certain period of time. For example, if I changed an OCL in March, and then changed it again in June, I need a report that had both those changes, since my change management system would have both those changes.
    35 pointsBadges:
    report
  • ToddN2000
    So they are looking for verification that the change management software and it's dates are accurate? I do not think there is a way to see all the historical date based on the object. Unless you have some custom procedure, the change management program would be the only place I know to get all the change dates.
    134,585 pointsBadges:
    report
  • ccrone7
    Yes, I also don't think there is any way to do that.  Thank you, everyone, for trying to help.
    35 pointsBadges:
    report
  • pdraebel
    Amazing, my S36 days are 25 years in the past and still people are running it. Never used System 36 environment on iSeries, AS400 or whatever.
    7,545 pointsBadges:
    report
  • aceofdelts
    You could create a new source file for the sole purpose of storing versions. With every OCL change, copy the source (old or new doesn't matter but nice to be consistent) into that file. You'd need a subscript to make it unique. Then, the member creation dates are your audit match to your change management dates.
    2,550 pointsBadges:
    report
  • Yorkshireman
    from the foregoing then, they are asking ' please prove the Change management system is accurate'  

    Have them contact the supplier for test results. 

    Did they request/insist on the CM system in the first place? 

    6,085 pointsBadges:
    report
  • TheRealRaven
    S/36 OCL procedures should be stored as members in source files named QS36PRC. Library QS36F is the default, but other libraries are possible.

    If you enable object auditing on the source file(s) for *CHANGE, the system audit journal will log change accesses.
    36,025 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: