Libraries & implementation tool (Turnover, Implementer, Aldon)

100 pts.
Tags:
AS/400
AS/400 migration
AS/400 Source Files
PGM
  1. Let's say you have 3 libraries which contain the source data and financial files and programs. You have a tool call Turnover to put changes in production. Only IBM can have level 40 + and put in production the changes. However, when I look at the authorities on those 3 libraries, I see PUBLIC set to *CHANGE and other groups. Does that mean anybody can access those libraries and change the data (source and financial)? Is the tool then useless? What's the nuance here in terms of authority at the library level vs. the changes Tool Turnover or Implementer.
  2. Say I have a financial system that is the G/L application resides on that AS/400 server. If I want to look at the authorities on the financial data, does that mean I have to look at the source libraries? Are those the same libraries as the financial data or the source is purely changing the application code only?
  3. What is the difference between the physical files, PGM, and source files?
THANKS SO MUCH IN ADVANCE!
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: 2  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.
  • Splat
    1) It would sort of render your system useless if your users couldn't change data.  It's unlikely that IBM is the only agent authorised to promote objects to production (I'm not familiar with Turnover so I can't say what authorities are required but it would be surprising if only a third-party could control that aspect of your system).  I would suggest you look at the IBM manuals to gain an understanding of what the *CHANGE authority entails.

    2) Object security relates to objects, not source.  Your review should therefore be of the objects.

    3) Program objects are executable.  Physical files (of which source files are a subset) contain members which contain data.  Source files are a specific type of physical file specially formatted to contain members which contain both source for compilation and source for execution.
    12,915 pointsBadges:
    report
  • TheRealRaven
    *CHANGE for a "library" is mostly irrelevant for files and programs within the library. A library is like a directory (or perhaps an index). Changing the library refers to changing (i.e., adding or removing) entries in the directory. That's a separate authority from that needed for any objects that the entries point to.

    The idea for *CHANGE to a library is usually for users to be able to create objects in the library, thereby simultaneously 'changing' the library by adding a new entry to it. Then, of course, a user might delete objects that are created, thereby removing the entry.

    It doesn't mean that objects created by other users in that library are available to change nor even to see or read. Additional authority at the object level is needed for that. 
    36,880 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: