Streams define the scope for configuration management for a group of Applications. ISPW ’s configuration management feature will look for relationships between components within a Stream. Streams consist of a level structure definition, and all Applications defined within a Stream must use a subset (or all) of this structure.
Streams
Stream Definition
On selection of a Stream, the following figure is displayed:
Stream Definition
Templating
Most of the Stream Definition screens are similar to those described in AD (S,L) – Levels. Unless otherwise specified, values that are set against the Stream are used as a template for when the Application is defined within the Stream. These values are also not used for any processing within ISPW , and will need to be specified at the Application level to be used.
ST(L,S)
Entering L or S will initiate the definition of level information. See AD (S,L) – Levels for a description of the fields.
Important
The Levels defined for the Stream define the level structure limits for any Application defined to that Stream. Applications defined to the Stream do not have to have all of the paths, but each path defined must conform to a path in the Stream definition.
ST(M)
Entering M against the Stream name will initiate the following figure:
Modify Stream Definition
This is similar to the Application Definition screen. The Component Reference field is not used.
ST(T)
The Type information specified against the Stream is similar to that defined in M.AD(T), although there are some extra attributes, as illustrated in the following figure, that apply to all Applications defined to that Stream.
Additional Attributes
ISPW MODIFY STREAM ABN COMPONENT TYPE (INT)
Command ===>
Enter required details: Component Type (KEY) ==> LOAD Component Domain ==> Component Class (KEY) ==> BAT Deployment Type ==> LOADBAT Warehouse Storage ==> Description ==>
*Content Type ==>
*Generate Skeleton ==> *Test Gen. Panel ==>
*Generate Table ==> *Hold Gen. Panel ==>
*Generate Job ==> Cust Gen. Panel ==>
*Prod. Move Job ==> Hold Move Time ==> (HH:MM)
*Model DSN(MEMBER) ==> Sandbox Allocations DSN/Path Template ==> Storage Type ==> (HFS/PDS) Management Class ==> (Blank for default management class ) Storage Class ==> (Blank for default storage class ) Volume Serial ==> (Blank for no volume specification ) Device Type ==> (Generic unit or device address ) Data Class ==> (Blank for default data class ) Space Units ==> (BLKS,TRKS,CYLS,MB ) Primary Qty ==> Secondary Qty ==> Record Format ==> (V,F,U, etc) Record Length ==> Block Size ==>
Press END to returnField Descriptions
Field Name | Description |
|---|---|
Deployment Type | If ISPW Deploy is installed and used, this relates the ISPW Type to the Deployment Type. |
Warehouse Storage | This determines whether the Component or Part is to be primarily stored in the Component Warehouse. If set to “N”, there must be an external dataset defined to store the component. If set to “Y”, an external copy may still be specified and kept. |
VSAM Considerations
If component type is for a VSAM (KSDS) file, Warehouse Storage must be set to “Y”.
ST(N)
The Name information specified against the Stream is identical to the way it is defined for M.AD(N) and provides a useful way to template the dataset names. See AD (N) – Names for a description of these fields.
ST(A)
The Association information specified against the Stream is identical to the way it is defined for M.AD(A) and provides a useful way to template the dataset names. See AD (A) – Associations for a description of these fields.
ST(P)
The Plans information specified against the Stream is identical to the way it is defined for M.AD(P) and provides a useful way to template the dataset names. See AD (P) – Plans for a description of these fields.
