Introduction › CA-PanAPT Features

CA-PanAPT Features

CA‑PanAPT provides the following features:

• The ability to schedule, revise, or approve a turnover request interactively using ISPF.
• The ability to customize for site‑specific turnover requirements using modeling, parameters, and user‑coded exits. CA‑PanAPT controls the Production implementation of any entity that can be controlled by a batch job.
• The ability to handle turnover as part of a regularly scheduled process or as an emergency.
• The ability to set up and enforce standards by including them in models. User‑coded exits can also help enforce site standards.
• The definition of libraries, such as Test, Quality Assurance, or Production, with backup and backout counterpart libraries for these (with the exception of the starting "Test" library).
• As many as 14 optional intermediate levels of libraries between your starting level and final production level. This allows for preproduction staging and testing.
• The control of moves from a starting test level, through any intermediate preproduction staging levels, up to production, with provisions to back up older versions of members before replacing them, and provisions to back changes out of any level, reinstating what was there before.
• The ability to assign responsibility for specific entities to an individual. After assignment under CA‑PanAPT, only that person (or group) can designate that the entity be moved into Production.
• The ability to group related entities into a Move Request so that all entities are moved together.
• Zero to 20 different Verification procedures can be required at each stage before a move can be processed.
• Zero to 20 different online approvals can be required at each stage before a move is begun.
• An Inventory of all Production entities contained in all Production libraries.
• A comprehensive set of audit, management, and historical reports plus reports that show future planned moves. These reports identify items that are to be moved into Production and when this will happen.
• A default user sign‑on to allow most users the ability to create and close Move Requests without having to maintain individual security entries for each user.
• Security groups with different levels of authority.
• The Retrieve function copies Assigned members to the Test Library of a Library Code under control of CA‑PanAPT models. The Retrieve function is available for Library Code definitions for which the Assignment and Retrieve options have been enabled.
• The Back Out function replaces all members of a Move Request on any level's libraries (either a preproduction staging level or the final production level) with members for a Backup Library when the new members at that level are causing problems. Back Out also lets you save the faulty members on Back Out libraries.
• Detailed written documentation and online HELP panels to assist you throughout the entire process.
• Centralized audit and reporting functions for moves that actually take place outside of the OS/390 environment.
• Audit or control of any system or vendor software moves or changes (such as CA‑Panvalet, CA-Panexec, CICS tables, database updates, and hardware changes).
• Validation of the existence of the entities at the appropriate library levels prior to performing the move.
• CA‑PanAPT provides a Development Facility that is a functional extension to CA‑PanAPT. The Development Facility provides:
  • Change management during the development portion of the life cycle before any migration is started.
  • An environment to control Checkout, Checkin, Compile, Link, and many other functions.
  • Three way merges can be done if CA‑Pan/Merge is available.
  • Integrated tools such as the CA‑Panvalet ISPF Option (if available), CA‑Librarian ELIPS (if available), and ISPF for the use of the Edit and Browse functions.
  • Two development levels: one development level to use for Checkin and one development level to use for Checkout. This is in addition to the 16 levels that were introduced in CA‑PanAPT release 2.0.
• CA‑PanAPT provides an independent logon facility, the User Identification Facility (UIF).
  • You can create, change, or deactivate logon system IDs. You can also enforce the use of this facility by using external security (Unicenter for OS/390 Common Services CAISSF) and restrict specific logon system IDs.
  • The UIF feature is an ISPF table that contains information for the Table Entry Name (CA‑PanAPT logon system ID). The logon system ID instructs CA‑PanAPT which environment to set up for a session for individual users, groups, or departments.
• Capability to name a Move Request with a Change Name. You can use the Change Name or Move Request Number for selection processing.
• Many Selection Lists are available to simplify the setup of Move Request (Change Name):
  • Access Method MSL
  • Inventory MSL
  • Library Code MSL
  • Move Request (Change Name) MSL
  • Project MSL.
• Capability to copy members that are in any level in the migration path for rework.
• Capability to use Wildcard notation when specifying selection criteria for Change Names, Library Code/Subcodes, Member names, Project names, Service Requests, and user Ids.
• Capability to browse members in any data set that has a Library Code defined to CA‑PanAPT.
• Capability to build a Member Scratchpad when browsing members. The Member Scratchpad can be used later to add members to a Move Request.