This section explains the steps required to define migration paths.
The migration path is the route between two statuses that an application is permitted to follow during its planned life-cycle. Each status specified in a migration path must have been previously defined to PAC and linked to the application. Migration events may be defined only for two statuses that have been paired in a migration path.
Migration paths specify the conditions of application object movement between statuses:
the origin and destination application statuses;
the person(s) or group(s) who may authorize the events that use the migration path;
whether the event using the migration path is run online or in batch, and whether a work file is to be used during migration;
whether the listed objects are to be moved or copied to the destination status when the event is processed; or, in the case of development, maintenance, and incorporation status types, whether the objects are to be included from a previously created work file;
whether and how the listed objects are to be expanded before the migration (the Expand option to be used).
To access the PAC migration path maintenance and reporting sub-functions, enter Code T (Migration Paths) on the PAC Main Menu.
Depending on your user profile, either the Migration Path Maintenance Menu or the Migration Path Reporting Menu appears. The Migration Path Maintenance Menu, which combines the maintenance and reporting sub-functions, is used in discussions throughout this section.
16:23:18 * PREDICT APPLICATION CONTROL * 2000-05-03
User PACUSR - Migration Path Maintenance Menu -
Code Sub-Function
---- ----------------------
A Add Migration Path
D Display Migration Path
M Modify Migration Path
N List Migration Paths by Origin
O List Migration Paths by Destination
P Purge Migration Path
S Select Migration Path
? Help
. Exit
---- ----------------------
Code ................ _
Application ......... ________________________________
Origin Status ....... ________________________________
Destination Status .. ________________________________
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Menu Exit Canc |
On this menu, you can enter the (existing) application for which the migration path is to be defined as well as existing statuses (origin and destination) that will be linked by the migration path. You may use the full name, an alias, or range notation.
If the Origin Status is left blank or a range is specified, and the Destination Status is specified, the Migration Path Destination screen is displayed.
If the Destination Status is left blank or a range is specified, and the Origin Status is specified, the Migration Path Origin screen is displayed.
Both of these screens display a list of the origin/destination status links that have already been defined for the status you specified.
Note:
All of the sub-functions listed on this screen, except Add, may be
selected for processing directly from the Migration Path Selection List that is
accessed using the Select Migration Path sub-function.
This document covers the following topics:
You may add a migration path from one of three screens:
Add Migration Path
Migration Path Destination
Migration Path Origin
You can define a migration path using either the "Add Migration Path" (A) function on the migration path main menu, or using the Migration Path Destination/Origin functions.
13:43:44 ***** PREDICT APPLICATION CONTROL ***** 2000-10-01
User PACUSR - Add Migration Path -
Application .. COMMON Modified: 1997-12-06 by PACUSR
From Status .. MAINTENANCE
To Status .... CONTROL
Event Authorizers .. SAGGP___ SYSPAC AUTHORIZATION GROUP
________
________
________
________
________
________
________
Auto Expansion ....... N Status ..____________________________
Separate Authority ... N
Copy/Move?Include .... C
Batch/Online ......... B Workfile Usage ... Y
Migration Job ........ OS_MIGRATE_WORKFILE ____________________
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Menu Exit Canc
|
To access the Add Migration Path screen, enter A (Add Migration Path), the application name, and the origin and destination statuses on the Migration Path Maintenance Menu.
To specify the migration event authorizers, enter in the Event Authorizers field the IDs of the users or groups who are allowed to authorize events for this migration path.
The user names are filled in automatically from the PAC profile or Natural Security definition.
You may use range notation to specify the user IDs as follows:
| Notation | Authorizers | |
|---|---|---|
|
|
||
| @* | Any user ID. | |
| @user* | All user IDs beginning with "user". | |
| @user> | All user IDs greater than or equal to "user". | |
| @user< | All user IDs less than or equal to "user". | |
Note:
The @ character should be replaced by the current job
substitution character defined in the PAC administrator profile
defaults.
To specify automatic expansion for the object list, enter one of the following options in the Auto Expansion field:
| Option | Description | |
|---|---|---|
|
|
||
| N | (Default) No auto-expansion; PAC migrates only the objects listed. | |
| C | Map auto expansion Rule auto expansion View/DDM auto expansion Copy code auto expansion Data area auto expansion Object auto expansion (Subordinate ObjectsCompile Time) Include the objects listed and all subordinate objects (data areas, copycode, views, rules, or maps). | |
| R | (Referenced ObjectsRuntime) Include the objects listed and all referenced objects. | |
| E | (Subordinate and Referenced Objects) Include the objects listed, all subordinate objects, and all referenced objects. | |
| U | Natural object auto expansion (Used by Objects) Include the objects listed and all Natural objects that reference that (Natural or foreign) object. | |
Refer to Creating and Validating an Object List for more information about expanding object lists.
(Optional) To specify a location for the subordinate objects at compile time, specify a status (Expand status) in the Status field.
Indicate whether separate authority is required by accepting the default N (no) in the Separate Authority field if the user who creates a migration event may also authorize it, or overtype the default with Y (yes) if someone other than the creator of an event must authorize it.
In the Copy/Move/Include field, enter the following:
| Option | Description | |
|---|---|---|
|
|
||
| C | (Copy, the default) if objects are to be copied, but also remain in the source location. | |
| M | (Move) if objects are to be moved from the source location with no copy remaining in the source location. | |
| I | (Include) if objects from a previously created work file are to be included. | |
In the Batch/Online field, specify whether the events that use this migration path are to be run in batch (B, the default) or online (O).
Indicate whether a work file is to be used by accepting the default N (no) in the Workfile Usage field, or overriping it with Y (yes) if a work file is to be used during migrations that use this migration path.
In the Migration Job field, specify the job that is to be used to process migration events that use this migration path.
Press ENTER to add the migration path and return to the Migration Path Maintenance Menu.
To add a migration path from the Migration Path Destination screen, either access the screen from the Add Application Status Link screen using Additional Options or from the Migration Path Maintenance Menu by leaving the Destination Status field blank.
11:12:49 ***** PREDICT APPLICATION CONTROL ***** 2000-07-01
User PACUSR - Migration Path Destination -
Application .......... ORDERS
Origin Status ........ PRODUCTION
C Status Name (Destination) Ty Auth 1 Auth 2 Auth 3 N Message
--- -------------------------------- -- -------- -------- -------- - ----------
__ MAINTENANCE_____________________ M PACUSR ________ ________ 1
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
Enter options (above), or '?' (help) or '.' (Exit):
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Menu Exit Job Canc
|
The Migration Path Destination screen identifies the existing paths defined for the specified application in the specified origin status. On this example screen, the only defined path for the application ORDERS is from production to maintenance.
To add a migration path from the Migration Path Origin screen, either access the screen from the Add Application Status Link screen using Additional Options or from the Migration Path Maintenance Menu by leaving the Origin Status field blank.
10:07:53 ***** PREDICT APPLICATION CONTROL ***** 2000-07-01
User PACUSR - Migration Path Origin -
Application .......... ORDERS
Destination Status ... PRODUCTION
C Status Name (Origin) Ty Auth 1 Auth 2 Auth 3 N Message
--- -------------------------------- -- -------- -------- -------- - ----------
__ DEVELOPMENT D PACUSR 1
__ SYSTEMS_TEST T PACUSR 1
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
________________________________ ________ ________ ________
Enter options (above), or '?' (Help) or '.' (Exit) ... _
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Menu Exit Job Canc
|
The Migration Path Origin screen identifies the existing paths defined for the specified application in the specified destination status. In the above example, the defined migration paths for the application ORDERS are development to production and systems test to production.
Previously defined migration paths displayed on the Migration Path Destination / Origin screens may be modified/displayed by entering the two-character code MO (Modify Path Definition) or DI (Display Link Definition), respectively, in the "C" column adjacent to the path. These codes invoke the Modify/Display Migration Path screen, which is similar to the Add Migration Path screen. Refer to Add (Define) a Migration Path and Authorization for more information.
Refer to Access Additional Sub-functions for Existing Migration Paths for information about sub-functions available for editing existing paths.
On the Migration Path Destination / Origin screen, enter the following information:
| Field Name | Enter the . . . | |
|---|---|---|
|
|
||
| Status Name (Destination) | destination status on a blank line. | |
| Status Name (Origin) | origin status on a blank line. | |
| Auth 1 / Auth 2 / Auth 3 | user ID or group ID of those users who may authorize the migration event. | |
You may add additional authorizers on the Modify Migration Path screen. Refer to Access Additional Sub-functions for Existing Migration Paths for more information.
Press PF9 (Job) to display the Job column.
Enter the name of the job that is to be submitted to process the event.
Press PF9 (Auth) to return to the previous screen.
Press ENTER to add the migration path and return to the previous screen.
The following attributes must be specified on the Modify Migration Path screen when you are defining a migration path on a screen other than the Add Migration Path screen:
Auto Expansion
Separate Authority
Copy/Move/Include objects
Batch/Online
Workfile Usage
PAC allows you to update or display existing (defined) migration paths by modifying/displaying
an individual migration path using the Modify sub-function on the Migration Path Maintenance Menu;
several migration paths at a time using the SCANPATH utility.
You may modify or display an individual migration path definition on the Modify Migration Path or Display Migration Path screens, which are accessed in the following ways:
On the Migration Path Maintenance Menu, enter Code M (Modify Migration Path) or D (Display Migration Path), the application, and the origin and destination statuses of an existing path in the relevant fields.
On the Migration Path Destination or Origin screen, select the path you wish to modify/display by entering the two-character code MO (Modify Path Definition) or DI (Display Link Definition) in the "C" column.
In both cases, the Modify/Display Migration Path screen appears. The screen is similar to the Add Migration Path screen. Refer to Add (Define) a Migration Path and Authorization for more information.
The SCANPATH utility allows you to modify (update) the defaults of several migration paths at a time. For migration paths that satisfy your selection criteria, you can
modify the default values such as execution mode (batch/online), work file use, and copy/move/include objects;
scan for paths that use a particular job to process migration events and (optionally) update/replace that job for all paths that use it.
Refer to the PAC Reference documentation for more information.
To access a selection list of existing migration paths, enter Code S (Select Migration Path) on the Migration Path Maintenance Menu.
16:23:37 * PREDICT APPLICATION CONTROL * 2000-05-03
User PACUSR - Migration Path Selection List -
SELECT Path Application * Status *
C Nr Application Name Status
- -- -------------------------------- --------------------------------
_ 1 ABC ARCHIVE
_ 2 ABC CONTROL
_ 3 ABC DEVELOPMENT
_ 4 ABC MAINTENANCE
_ 5 ABC PRODUCTION
_ 6 ABC SYSTEMS_TEST
_ 7 APL_EXAMPLE_1 CONTROL
_ 8 APL_EXAMPLE_1 DEVELOPMENT
_ 9 APL_EXAMPLE_1 PRODUCTION
_ 10 APL_EXAMPLE_1 TEST
_ 11 APL_EXAMPLE_2 CONTROL
_ 12 APL_EXAMPLE_2 DEVELOPMENT
_ 13 APL_EXAMPLE_2 INCORPORATION
Mark Selection, Enter Number or 'T' (Top) __
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Menu Exit -- + Canc
|
If you mark the listed application/status with the cursor or enter an X or an S in the "C" column, or if you enter the application/status number (from the "Nr" column) in the Mark Selection field..., you are returned to the Migration Path Maintenance Menu where the specified application and status are displayed in the Application and Origin Status fields, respectively.
Note:
If you accessed the Migration Path Selection List screen using
Code S (Select Migration Path) or the SELECT direct command, you may D
(Display), M (Modify), P (Purge), or S (Select) one or more of the listed
applications/status combinations directly by entering the sub-function code in
the "C" column.
16:23:52 * PREDICT APPLICATION CONTROL * 2000-05-03
User PACUSR - Migration Path Maintenance Menu -
Code Sub-Function
---- ----------------------
A Add Migration Path
D Display Migration Path
M Modify Migration Path
P Purge Migration Path
S Select Migration Path
? Help
. Exit
---- ----------------------
Code ................ S
Application.......... ABC_____________________________
Origin Status ....... PRODUCTION______________________
Destination Status .. *_______________________________
PAC2007: (I) No Migration Path selected.
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Menu Exit Canc
|
If you then press ENTER, the Migration Path Destination screen appears allowing you to complete your selection of an existing migration path by choosing the destination status.
To display and edit an existing migration path displayed on the Migration Path Destination screen or the Migration Path Origin screen, mark the desired status in the "C" column with a valid two-character code.
A list of valid codes is available by accessing Help or by marking the desired status with an asterisk (*).
If you access the Migration Path Destination / Origin screens using the Display (D) sub-function, maintenance is not allowed and you may only display information about existing paths.
If you use the Modify (M) sub-function to access the Migration Path Destination / Origin screens, the following sub-functions are available:
| Code | Sub-Function | |
|---|---|---|
|
|
||
| MO | Modify Link Definition | |
| PU | Purge Link Definition | |
| AP | Display Application Definition | |
| ST | Display Status Definition | |
| LI | Display Link Definition | |
| PO | Display Migration Path Origin | |
| PD | Display Migration Path Destination | |
You may display information about the migration paths defined for an application on the Migration Path Destination / Origin screen by entering Code N (Migration Path Destination) or Code O (Migration Path Origin) and the application name on the Migration Path Maintenance Menu.
The Migration Path Destination screen appears if you entered Code N:
10:01:34 ***** PREDICT APPLICATION CONTROL ***** 2000-07-01
User PACUSR - Migration Path Destination -
Application .. ORDERS
Library Predict
Status - Path Destination Name DBnr Fnr DBnr Fnr Auth-1
----------------------------------- ---------------- -------- --------
CONTROL * PACS * 235 054 235 055
>> DEVELOPMENT ORD-EXAM 235 017 235 016 SAGXX
>> MAINTENANCE ORD-MAIN 235 017 235 016 SAGXX
>> USER_TEST ORD-UTST 235 017 235 016 SAGXX
DEVELOPMENT ORD-EXAM 235 017 235 016
>> CONTROL * PACS * 235 054 235 055 SAGXX
>> PRODUCTION ORD-PROD 235 017 235 016 SAGXX
>> USER_TEST ORD-UTST 235 017 235 016 SAGXX
MAINTENANCE ORD-MAIN 235 017 235 016
>> CONTROL * PACS * 235 054 235 055 SAGXX
PRODUCTION ORD-PROD 235 017 235 016
>> MAINTENANCE ORD-MAIN 235 017 235 016 SAGXX
Press ENTER to continue or '.' to exit: _
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
HELP Menu Exit Canc
|
This screen provides a global view of the existing migration paths of the application. In essence, this screen answers the question "For each status defined, where may the objects be migrated?"
The Migration Path Origin screen appears if you entered Code O:
10:02:01 ***** PREDICT APPLICATION CONTROL ***** 2000-07-01
User PACUSR - Migration Path Origin -
Application .. ORDERS
Library Predict
Status - Path Origin Name DBnr Fnr DBnr Fnr Auth-1
----------------------------------- ---------------- -------- --------
CONTROL * PACS * 235 054 235 055
<< DEVELOPMENT ORD-EXAM 235 017 235 016 SAGXX
<< MAINTENANCE ORD-MAIN 235 017 235 016 SAGXX
DEVELOPMENT ORD-EXAM 235 017 235 016
<< CONTROL * PACS * 235 054 235 055 SAGXX
MAINTENANCE ORD-MAIN 235 017 235 016
<< CONTROL * PACS * 235 054 235 055 SAGXX
<< PRODUCTION ORD-PROD 235 017 235 016 SAGXX
PRODUCTION ORD-PROD 235 017 235 016
<< DEVELOPMENT ORD-EXAM 235 017 235 016 SAGXX
<< SYSTEMS_TEST ORD-STST 235 017 235 016 SAGXX
Press ENTER to continue or '.' to exit: _
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
HELP Menu Exit Canc
|
This screen shows where an application in a particular status originated. In essence, this screen answers the question "For each status defined, from which status may the objects be migrated?"
To refresh the screen and display more information, press ENTER.
To return to the Migration Path Maintenance Menu, enter a period (.) on the command line, and press ENTER.
The following table describes attributes of the Migration Path Origin and Destination screens:
| Attribute | Description | |
|---|---|---|
|
|
||
| Application | The application specified. | |
| Status - Path Destination | The current statuses in which the application is held (for example, DEVELOPMENT), and the statuses to which the application may be migrated (for example, >>PRODUCTION). | |
| Status - Path Origin | The current statuses in which the application is held (for example, MAINTENANCE), and the statuses from which the application may be migrated (<<PRODUCTION, for example). | |
| Library Name / DBnr / Fnr | The library name, the database ID, and the file number where each application status is stored. | |
| Predict DBnr / Fnr | The Predict database ID and file number where the Predict cross-reference data for each application status is stored. | |
| Auth-1 | The ID of the first user on a list of users who may authorize the migration of the application from one status to another. The complete list of authorizers may be viewed on the Migration Path definition screen that is accessed using the Display Migration Path sub-function. | |
To purge a migration path, enter Code P (Purge Migration Path), the application, and the origin and destination statuses that identify the migration path on the Migration Path Maintenance Menu.
The Purge Confirmation window appears displaying the migration path (From status / To status) that will be deleted for the specified application.