Container List
ISPW Option P displays the ISPW Container List. The following figure shows the partial Container List associated with the user MCGILL.
Container List for User MCGILL
Command ===> Scroll ===> CSR
More -->
View: U
Closed: N User: MCGILL
Appl T Container Tag Owner Release Description
____ _ __________ ____ ________ __________ ______________________________
__ DOCS A DOCS000002 MCGILL RFP DOCS AND LETTERS
__ +PLAY A PLAY000299 USER29 CHANGE CYCLE EXAMPLE 1
__ +PLAY A PLAY000280 USER16 CHANGE CYCLE EXAMPLE 1
__ +PLAY A PLAY000223 USER11 CHANGE CYCLE EXAMPLE 1
__ PLAY A PLAY000218 MCGILL THIS IS A NEW PACKAGE
__ PLAY A PLAY000216 PAUL BATCH REPORTS
__ PLAY A PLAY000145 MCGILL COLLECTIONS OF MODULES FOR DMV
__ PLAY A PLAY000135 MCGILL Example User Manual
__ PLAY A PLAY000133 MCGILL abcd test 123
__ +PLAY A PLAY000118 WERNER CHANGE CYCLE EXAMPLE 1
__ +PLAY A PLAY000115 MCGILL CHANGE PACKAGE FOR PROSPECTIVE
__ +PLAY A PLAY000093 MCGILL CUSTOMER DEMO CHANGE PACKAGE
__ +PLAY A PLAY000074 CRAIG2 NEW WORK
__ +PLAY A PLAY000027 MCGILL CHANGE CYCLE EXAMPLE 1 FOR LEE
__ +PLAY A PLAY000015 MCGILL USER20 DEMO ASSIGNMENT
__ PLAY A PLAY000011 MCGILL PAYROLL SYSTEMS UPDATES
__ PLAY A PLAY000009 PAUL HFS EXAMPLES
Container Definition
A Container is a collections of components/modules that belong to an Application change request. Your organization may call these projects, work packages, or change requests. ISPW has three types of Containers:
- Assignment – the most basic Container, used to help Applications staff structure and organize their project work.
- Release – a grouping of Assignment Containers (or Assignments) into a larger package, or a collection of modules from various Assignments.
- Set – a temporary Container used to bundle modules for mass operations such as authorizations, generations, or promotions from level to level.
Containers have Task Lists, where Tasks are the modules that need to be added, deleted, or changed for some particular piece of work.
Container Type Designations
In the example shown in the following figure, there are twelve work Containers associated with user KARYNS. By default, ISPW users see only the Containers with which they are associated. Different ISPW users will see different Container Lists, depending on their work. Notice the Container types designation in column T:
- The first nine rows are Assignments (A in the second column).
- The tenth row is a Release (R in the second column).
- The last two rows are Sets (S in the second column).
All of these containers belong to an Application called PLAY, which is listed in the Appl column.
The following figure shows a customized view of the Container List for user KARYNS.
Container List for User KARYNS
Command ===> Scroll ===> CSR
More -->
View: U Closed: N User: KARYNS
Appl T Container Tag Owner Release Description
PLAY _ __________ ____ ________ __________ ______________________________
__ +PLAY A PLAY000302 USER28 ABC123 DAVID GORR TEST PROGRAMS
__ +PLAY A PLAY000300 KARYNS OUR NEW ASGN
__ +PLAY A PLAY000058 KARYNS GL DB2 CHANGES
__ PLAY A PLAY000022 USER01 CHANGE CYCLE EXAMPLE 2
__ PLAY A PLAY000015 MCGILL USER20 DEMO ASSIGNMENT
__ PLAY A PLAY000011 MCGILL PAYROLL SYSTEM UPDATES
__ PLAY A PLAY000010 KARYNS THE WEBSITE
__ PLAY A PLAY000009 PAUL HFS SAMPLES
__ PLAY A PLAY000002 MCGILL GUI DEMO
__ PLAY R R5445 MCGILL DEMO SYSTEM RELEASE
__ PLAY S S000003778 KARYNS USER20 DEMO ASSIGNMENT
__ PLAY S S000003762 KARYNS USER20 DEMO ASSIGNMENT
------------------------------- Bottom of List -------------------------------
The following table describes the Container List Columns:
Column | Description |
|---|---|
Appl | the Application or System this Container is associated with |
T | the type of Container (Assignment, Set, or Release) |
Container | the system-generated container number |
Tag | a user-definable 4-character field |
Owner | the UserID of the person who created the Container |
Release | used to group Containers together |
Description | a text field |
Path | the circuit or change cycle that the modules will transit through |
WorkRef | an associated budget or change ticket number |
Stream | defines the level structure and other rules (including types, flags, and associations) about the application definition. |
Codeline Path | a field used to identify a codeline |
Input Fields Color
In ISPW, input fields, masks, and filters are displayed in a contrasting color. The default color is pink.
Filtering the Container List
A column filter can further narrow the Container List to specific Containers. The following figure shows Containers for user MCGILL with Descriptions beginning with the word CHANGE. The filter CHANGE* (* = wildcard character) looks for descriptions beginning with the word CHANGE followed by any characters.
By using different filters you can further change the displayed results. Clearing all fields and filters will cause all of the Containers to be displayed. Try filters under various column headers, such as filtering on the Path column or the Description column.
Filtered Container List
Command ===> Scroll ===> CSR
More -->
View: U Closed: N User: MCGILL
Appl T Container Tag Owner Release Description
____ _ __________ ____ ________ __________ CHANGE*________________________
__ +PLAY A PLAY000299 USER29 CHANGE CYCLE EXAMPLE 1
__ +PLAY A PLAY000280 USER16 CHANGE CYCLE EXAMPLE 1
__ +PLAY A PLAY000223 USER11 CHANGE CYCLE EXAMPLE 1
__ PLAY A PLAY000118 WERNER CHANGE CYCLE EXAMPLE 1
__ PLAY A PLAY000115 MCGILL CHANGE PACKAGE FOR PROSPECTIVE
__ PLAY A PLAY000027 MCGILL CHANGE CYCLE EXAMPLE 1 FOR LEE
------------------------------- Bottom of List -------------------------------
Arranging Columns
Users can customize displays under ISPW Main Menu Option U to show the information most important to them (see Option U – User Preferences). For example, QA staff may want to see different columns on their display than programmers. However these are just different logical views of the same data.