Field Definitions

The common fields used in ISPW are defined below. Fields that are specific to a certain dialog box are defined within the appropriate topic.

  • Action - The last action performed on a deploy package
  • Activate - For defined activation processes, this is the earliest date and time that they can be dispatched for execution
  • Activate date - For defined activation processes, this is the earliest date that they can be dispatched for execution
  • Activate time - For defined activation processes, this is the earliest time that they can be dispatched for execution

  • Application - Definition varies by context:

    • Container's primary application cod Containers may include components from multiple applications.
    • Application code associated with this change package
    • Application to which most of the tasks later associated with this release are expected to belong t
  • Application Group - Application owner group this component belongs to
  • Approver - Approver name (typically a group representing a set of users)
  • Approval status - Approval status of the set. May be unknown (set is not locked), required, not required, approved, or denied
  • Approver status - Approved, Denied, Not Required, Pending, Required, Unknown, or Wait Sequence
  • Assignment - The assignment name to be filtered on or a wildcarded partial assignment name. This field does not appear on the Releases Filter dialog box.
  • Category - Identifies the impact category, (whether it is a program or a job for example)
  • Change type - Type of change (such as standard or emergency). This list is provided by the ISPW host and is customizable there.
  • Check out from level - The life cycle level of the task to be checked out
  • CICS - Y=contains CICS, N=No CICS
  • Class - A class from the Set Class table (SC), where Class=A is somewhat analogous to an MIS job class
  • 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.
  • Config - host runtime configuration
  • Container - Ten-character container number. Assignment and set numbers are system-generated. Release numbers are manually created.
  • Control Actions: Action - Depending on the execution status of the set, may contain actions like Stop, Lock, or Unlock
  • Create - Date and time the request was created
  • Create date - Date the set was created
  • Create time - Time the set was created
  • Current replace version - The “can replace” value for the version being updated
  • Deploy request status - The overall current status of the deploy request, which may be Planned, Confirmed, Staged, Implemented, Completed, Failed, or Terminated

  • Description - Definition varies by context:

    • A free-form text field used to describe the purpose of the container
    • Text description of this set, obtained from the assignment container

  • End date - Definition varies based on context:

    • End date of last operation Use the date fields to restrict the search to components changed within a specific time period
    • Deployment end date/time

  • 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
  • Flags - Customizable field for the user's purpose
  • Generate parms - Customizable field that can be used to indicate generation information such as the way the component is generated via compile and link options or the name of a test job to run
  • Group - Application owner group this component belongs to
  • Hold set check box - C
  • Host name or IP address - Host name or IP address of the ISPW communications interface (CI) task
  • Inherit - All, Yes, or No
  • Implement - The earliest date and time that the Deploy Implementation process can begin
  • Implement date - The earliest date that the deploy implementation process can begin
  • Implement time - The earliest time that the deploy implementation process can begin
  • IMS - Y=contains IMS, N=No IMS
  • ISPW root - Local file system target for any copies to the workstation. Note: By default the application ID is appended as a directory after the root.
  • Job/Proc - JCL job name/procedure name of the Set
  • Join at level - Level at which the Sandbox codeline merges back into the main ISPW Lifecycle. This merge will occur when promoting tasks from the Sandbox codeline to the specified level (this functionality is dependent on the maintenance level of the ISPW server).
  • 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
    • Used to restrict the search to one Path/environment in the cycle
    • The Life Cycle level of the component whose "can replace" version is being updated
  • 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
  • Lock set check box -
  • Lock status - Whether the set is locked or unlocked

  • Name – Definition varies by context:

    • An up to eight-character component name
    • Name of the component whose "can replace" version is being updated
  • New replace version - The new "can replace" number representing a version that this one may safely replace/overlay

  • Operation - Definition varies by context:

    • Last operation performed on this component, such as checkout, edit, promote, or generate
    • Operation performed on the set when it was locked
    • Operation to be performed on the set when it is locked

  • 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 contain 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
  • 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.
  • Perform action - Executes the action selected by the Action box
  • Port - Port number for the communications interface (CI) task
  • Prior week - Filter on the previous week
  • Queue - Identifier to ensure single-threading across set classes
  • Reference - Reference name
  • Relationship - All, Static, or Dynamic

  • 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.
    • On the Releases Filter dialog box, the release name to be filtered on or a wildcarded partial release name. This field does not appear on the Assignments Filter dialog box.
    • On the Assignments Filter dialog box, the release ID that is associated with the assignment container. This field does not appear on the Releases Filter dialog box.

  • Release ID - Definition varies by context:

    • A unique release identifier that may be user-specified or system generated (if a release prefix has been defined by the ISPW administrator)
    • Release ID this package will be part of
  • Request ID - A unique numerical id assigned to this deployment request
  • Reset - Returns all filters to a default state
  • Sequence - Controls the order of generates during set processing (for example, compiling subroutines before the main routine). Processing is handled in character sort order
  • Server name - ISPW server ID, which can be found on the initial ISPW panel in ISPF
  • Set – A temporary container, identified by a 10-character ID, where the operation request takes place
  • Set ID - The 10-character ID for a set.
  • Set log - Contains a link to the set log, which is created when a set starts processing for the first time. The log includes information to help determine why a set may not have completed.
  • Set prefix - The set prefix for the set ID. ISPW appends a sequentially incrementing number for the suffix. The default is "S".
  • Set status - The current execution status of the set representing this deployment
  • Source - Source of impact information (e.g. Parsed)
  • SQL - Y=contains SQL, N=No SQL
  • Start - Deployment start date/time when the set will be dispatched for execution

  • Start date - Definition varies based on context:

    • Start date of last operation  Use the date fields to restrict the search to components changed within a specific time period
    • Deployment start date/time when the set will be dispatched for execution
    • The date that the set will be dispatched for execution
  • Start time - The time that the set will be dispatched for execution
  • Status - The overall current status of the deploy request, which may be Planned, Confirmed, Staged, Implemented, Completed, Failed, or Terminated

  • Stream - Varies based on context:

    • 2- to 8-character code defines the application structure with which the application is associated
    • Stream to which most of the tasks later associated with this release are expected to belong t
  • Tag - An optional, user-definable four-character field
  • Task count - Number of tasks in the set
  • Today's date - Filter on today's date

  • Type - Definition varies based on context:

    • The one- to four-character acronym for the type of component, such as COB for a Cobol program or COPY for a copybook
    • The component type of the component whose "can replace" version is being updated

  • User ID - Varies based on context:

    • User who performed the last significant operation (see Operation)
    • Defaults to the logged in use
  • Use selected dates check box - Select to enable filtering by date (in yyyy-mm-dd format).
  • User tag - An optional, user-definable four-character field. This field is only enabled if the logged in user ID matches the ID of the filtered owner.
  • 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*