Default language.

Column Definitions

The common columns used in ISPW are defined below. Columns that are specific to a certain view or dialog box are defined within the appropriate topic.

  • ! – A plus sign (+) indicates that there are messages for this task
  • Action - Action code can be any of the following:
    • blank- The task was created with no other actions
    • Compile only - The component was added for compile only, without going through the rest of the change cycle process
    • Delete Prod Source - Deletes the production-level source and executables from the production environment
    • Fallback - Component falls back to a previous component version at production
    • Implement - Deploy processing is taking place
    • Added fromHistory - Indicates that a historical version (for example, -1 or -2) of a component is requested for checkout
  • Activate Date/Time - The scheduled activation date and time in yyyy-mm-dd HH:MM:SS format
  • Address - Network (IP) address
  • Alternate Name - Adds the selected task to an assignment
  • Application - Definition varies by context:
    • In the Package Details dialog box's Items table, this is the application name to which an item belongs.
    • Container's primary application cod Containers may include components from multiple applications.
    • Application code associated with this change package 
  • Application Group - Application owner group this component belongs to
  • Approver - Approver name (typically a group representing a set of users)
  • Approver status - Approved, Denied, Not Required, Pending, Required, Unknown, or Wait Sequence
  • Assignment - Assignment container type that contains this component or task
  • Base Version - The "based upon" version number
  • Category - Identifies the impact category, (whether it is a program or a job for example)
  • Check Out Date - Date component was checked out
  • CICS - Y=contains CICS, N=No CICS
  • Class - The component class of the item. Used for generated component types. It can be used to specify different dataset names for the same component type (in conjunction with the Associations definitions). For example, CICS or IMS.
  • Codeline path - A codeline path is a unique identifier that refers to a specific instance or group of objects isolated from the main ISPW Lifecycle, such as tasks in an assignment tied to a Sandbox. A Sandbox enables a user to work in isolation from the rest of the lifecycle for a particular application or a feature under development, for instance.
  • Collection - Generate collection name
  • Component Description (or Description) - Text description of this component
  • Container - Ten-character container number. Assignment and set numbers are system-generated. Release numbers are manually created.
  • Create - Date and time the request was created
  • Dataset/Warehouse - Where the part is located, whether in a dataset or an ISPW warehouse
  • Date/Time - Date and time of last operation
  • Deploy - Y indicates that the server is used for the deploy feature
  • Deploy Category - The name of the category to which the deploy type is grouped for deployment constraints (for example, all types related to DB2 might be grouped together because they need to be deployed at the same time)
  • Deploy Type - The component or file type for deployment, which is the level at which the target files are defined. Can be used to determine the different activation processes required for a component. The deployment type corresponding to an ISPW type/class is specified against the Base ISPW "Stream Component Type" entry. For example, an ISPW type of LOAD, which has an ISPW class of CICS, could be specified with a deployment type of LOADCICS. Deployment type names are limited to 8 characters.

  • Description - Definition varies by context:

    • A free-form text field used to describe the purpose of the container
    • Descriptive information used to identify the serve
  • End Date/Time - In the Deployment Package Details dialog box's Items table, this is the deployment end date/time when the dispatched package ends execution

  • Environment - Definition varies by context:

    • ISPW environment for this version (such as Outs, Test, Hold, or Prod)
    • The logical execution environment where the components will be deployed for this request
  • Execution status - Execution status, which is the current phase of execution for the set, such as release, held, or failed
  • Extension – File extension
  • Flags - Customizable field for the user's purpose
  • Generate parms - Launches the Generate Options dialog box on which users can set parameters for the generate process. Displays only if customized in the ISPW instance.
  • Git Branch - The branch name associated with the component. This is the branch that was synchronized to ISPW.
  • Git Commit ID - The unique SHA-1 hash that can be used to find all the changes in a commit within Git.
  • Git Commit Message - The Git commit message that was entered during the commit/check-in.
  • Git Repository - A hyperlink to the Git repository's web location where the Git branch resides. The default web browser can be changed on the General tab of the Preferences dialog box.
  • Group (or Application group) - Component or task belonging to this application owner group
  • Icon
    • approvals-view.png - Indicates approver specified
    • assignment.png - Container is an assignment
    • release.png - Container is a release
  • Impact - May further qualify the type of impact for example DCLGEN, CICSLINK
  • Implement Date/Time- The scheduled implementation date in yyyy-mm-dd HH:MM:SS format
  • IMS - Y=contains IMS, N=No IMS
  • Inherit - All, Yes, or No
  • Internal version: ISPW's internal version number (0 until promoted to first controlled level)
  • Issue - In the Promotion Analysis view, shows the results of the promotion analysis performed, such as ready for promotion, generate required, or a version conflict.
  • Item ID - The ID of the item within a package.
  • Last updated by - User ID of the person who performed the last significant operation

  • Level - Definition varies by context:

    • Life cycle level where this component resides
    • Level of this component when the operation was requested
    • Life cycle level
  • Level of Indirection - An integer indicating how far above (positive numbers) or below (negative numbers) a component is relative to the selected component. Components that reference the target component are displayed above it as Seq +n, and components that are referenced by the target component are displayed below it as Seq n
  • Message - Displays additional, less critical messages than the Status column or displays informational messages
  • Modified: Date and time last modified

  • Name – Definition varies by context:

    • A component nam When a task or component has been changed, the name is prefixed with the greater than (>) character. The prefix is removed when the component has been promoted. For workstations components that reside in a folder structure, the name is prefixed with the plus (+) character. The prefixes apply only to views from which components can be edited.
    • In the Package Details dialog box's Items table, this is the component name of the item within a package.
    • The name of the defined servers in ISPW

  • Operation - Definition varies by context:

    • Last operation performed on this component, such as checkout, edit, promote, or generate
    • Operation performed that resulted in this history entry

  • Owner - Definition varies by context:

    • User who performed the checkout of the component
    • For an assignment or release, the user who created or currently owns the container. For a set, the user who has or will initiate the task operation in an assignment or release for processing.
    • The user who initiated the task operation in an assignment that requires an approval to proceed
    • Defaults to the logged in user
  • Package ID - The ID of the logical package
  • Part - ISPW part type (e.g. OBJ, LIST, LOAD)
  • Part ID - The part ID of the item within a package
  • Path (or Default path) - The checkout path or sign-out level. The default is the assignment's path/cycle but this can be changed to another checkout level.
  • Port: Server listener port number
  • Program - Y = executable component, N=subroutine/non-executable component
  • Promotion Analysis - Displays the results of a promotion analysis.

  • Reference - Definition varies by context:

    • Reference name
    • Reference type (orphaned, explicit or implicit)
  • Relationship - All, Static, or Dynamic
  • Relative Path - The subdirectory path (under ISPW root) in which this component resides on the workstation

  • Release – Definition varies by context:

    • Release a component belongs to
    • Release ID this package will be part of
    • 10-character release number, if associated with assignment The default release for this assignment.
    • Release ID associated with this operation
  • Replace version: Version this specific version may replace if it must be promoted over top of another version
  • Request ID - A unique numerical id assigned to this deployment request
  • Sequence - Controls the order of generates during set processing (for example, compiling subroutines before the main routine). Processing is handled in character sort order
  • Set – A temporary container, identified by a 10-character ID, where the operation request takes place
  • Set Approval Status - Approval status of the set. May be Unknown (set is not locked), Required, Not Required, Approved, or Denied
  • Size: File size
  • Source - Source of impact information (e.g. Parsed)
  • SQL - Y=contains SQL, N=No SQL
  • Start Date/Time- In the Deployment Package Details dialog box's Items table, this is the deployment start date/time when the package will be dispatched for execution

  • Status - Definition varies by context:

    • Highlights important component information such as current state
    • In the Package Details dialog box's Items table, this is the current state of the deployment package item.
    • The overall current status of the deploy request, which may be Planned, Confirmed, Staged, Implemented, Completed, Failed, or Terminated
    • May further qualify references that are incomplete or not applicable and advise if the component is already added to the current assignment.
  • Stream - 2- to 8-character code defines the application structure with which the application is associated
  • Storage - The logical storage entity. Storage entities describe the various attributes of the deployment targets like storage names and types
  • Sub Environment - The physical deployment details such as system type, storage names, and deploy targets
  • System - The type of server platform. Currently supported types are MVS, Windows, AIX, Linux, SUN, and HP-UX.
  • Tag: An optional, user-definable four-character field
  • Target - Level of this component when this operation completed
  • Technology - A high-level of grouping of component types by technology (or example, CIC or Natural), which may indicate special exit processing
  • Test Environment - Target environment

  • Type - Definition varies by context:

    • The type of serve Server supported types are Component Transport (CT), Remote Server (RS), Communications Interface (CI), and Communications Manager (CM).
    • Container typ Valid values are Assignment, Release, Set.
    • The one- to four-character acronym for the type of component, such as COB for a Cobol program or COPY for a copyboo Can contain either of the following icons:

      • ActiveTask.PNGindicates that the task is active in the ISPW life cycle datasets

      • InactiveTask.PNGindicates that the task is not active in the ISPW life cycle datasets
    • In the Package Details dialog box's Items table, this is the component type of the item.
  • User ID - User who performed the last significant operation (see Operation)
  • Variable - Generate variable name
  • Version - The external (visible) version number or label that is assigned to this component. Generally more meaningful than the internal version number.
  • Work Request: Optional, site-definable field typically used to associate the assignment with a problem ticket number or change request number. The name can be changed in the ISPW Maintenance Function by setting an M.ER variable named "HEAD2" to the preferred column name.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*