Data is locked by PAC when it is being processed. Users can unlock data which they themselves have locked.
Note:
Only a PAC administrator can unlock data which has been locked by
other users.
If a migration event is not successfully completed, the data it locked remains locked. An uncompleted event can be resubmitted. In this case, an attempt is made to resume its processing from the beginning of the first uncompleted step. The PAC administrator can reset an uncompleted event. In this case, the data locked by the migration event remains locked. If, however, the event is resubmitted, it is restarted from the beginning rather than from the last step reached. The PAC administrator can also release an uncompleted event. If the event has not reached step 6, it is backed out. If it has reached step 6, its completion is forced.
On the Administrator Functions menu, enter Code L (Locked Data Maintenance). Or enter the command UNLOCK on the command line of any PAC menu.
The Locked Data Menu appears:
17:03:00 ***** PREDICT APPLICATION CONTROL ***** 2000-03-03
User SAGU - Locked Data Menu -
Code Sub-Function
---- ------------------------
D Display Locked Data
R Release Locked Data
S Select Locked Data
? Help
. Exit
---- ------------------------
Code ... _
User ... ________
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Menu Exit cancel
|
This document covers the following topics:
From the Locked Data Menu, you can display all locked data or data locked by a specified user if you are a PAC administrator. If you are not a PAC administrator, you can display the data which you yourself have locked.
This sectioncovers the following topics:
To access a list of data locked by a user, enter Code D (Display Locked Data) and the user ID of the user.
If you do not specify a user, a list of all data locked by all users is displayed.
A Display Locked Data screen appears:
17:03:37 ***** PREDICT APPLICATION CONTROL ***** 2000-03-03
User SAGU - Display Locked Data -
C Nr Name of Locked Entity Lock Type Reason User ID
- -- -------------------------------- -------------------- ---------- -------
_ 1 CLOVER Application Migration EDSW
_ 2 HEATHER-DEV0-CONTROL-1 Migration Event MODIFY SAGU
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
|
This screen lists the following: the name and the type of a locked entity; the cause of the locking (modification, deletion or migration); the user ID of the user who locked the entity. Each entry is assigned a number on the screen ("Nr" column), and an input field is provided for selecting an entry ("C" column).
Press PF11 to display the ID of the terminal from which the data were locked and the date and time at which the data was locked. Press PF10 to again display the cause of the locking and the user ID.
To display information about an entity listed as locked on the Display Locked Data screen, enter the number of the entry (from the "Nr" column) in the Mark Selection field, or enter D in the "C" column next to the entry, or mark the entry with the cursor.
The specified locked data is displayed in a Display Locked Data window:
17:03:37 ***** PREDICT APPLICATION CONTROL ***** 2000-03-03
User SAGU - Display Locked Data -
C Nr Name of Locked Entity Lock Type Reason User ID
- -- -------------------------------- -------------------- ---------- -------
+-----------------------------------------------------------+
| --- Display Locked Data --- |
| |
| Migration Event data was locked by User SAGU at TID PCM18 |
| on 1998-03-03 16:51:16 |
| |
| Migration Event .. HEATHER-DEV0-CONTROL-1 |
| Reason .......... MODIFY |
| |
+-----------------------------------------------------------+
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
|
This window identifies the following: the entity locked; the user who locked it; whether it was locked by a batch job or from an identified terminal; the time at which it was locked; the cause of the locking.
If the information you displayed is about an application locked by a migration event, the resulting Display Locked Data window looks like this:
17:03:37 ***** PREDICT APPLICATION CONTROL ***** 2000-03-03
User SAGU - Display Locked Data -
C Nr Name of Locked Entity Lock Type Reason User ID
- -- -------------------------------- -------------------- ---------- -------
+---------------------------------------------------------------+
| --- Display Locked Data --- |
| |
| Migration Event data was locked by User EDSW at TID Batch |
| on 1998-03-03 16:58:47 |
| |
| Event ........ CLOVER-DEV0-CONTROL-1 |
| Application .. CLOVER |
| From Status .. DEV0 |
| To Status .... CONTROL |
| Reason ....... Migration |
| Step Number .. 2 - Versions Created |
| |
| Display locked data for Migration Event ..... N |
| |
+---------------------------------------------------------------+
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
|
Some information is provided about the migration event that performed the locking: the origin and the destination statuses and the number and description of the step reached by the event.
To display the data which is locked by the migration event, type Y over the N default in the field "Display locked data for Migration Event".
A Display Locked Migration Event Data screen appears, displaying a list of the objects locked by the migration event which locked the application:
17:07:09 ***** PREDICT APPLICATION CONTROL ***** 2000-03-03
User SAGU - Display Locked Migration Event Data -
Event ........ CLOVER-DEV0-CONTROL-1
Application .. CLOVER
From Status .. DEV0 LIB .. ES0 (222,122)
To Status .... CONTROL LIB .. * PACS * (222,144)
Object Object Type Version Status
-------------------------------- ------------------- ------- -----------
ES_Z_L03 Local 00001 Locked
ES_Z_N99 Subprogram 00001 Locked
ES_Z_P04 Program 00001 Locked
ES_Z_P05 Program 00001 Locked
ES_Z_P09 Program 00002 Locked
ES_Z_P11 Program 00001 Locked
CLOVER-DEV0-CONTROL-1 Migration Event Locked
CLOVER Application 00001 Locked
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 the following additional information:
the Natural locations of the origin and non-production destination migrations which are identified by their library names, and data base and file numbers;
the name and type of each entity which has been locked;
the version number of each object migrated by the locked migration event;
The state of each locked object. The possible status values are:
| Check in | of an object being migrated from maintenance; |
| Check out | of an object being migrated to maintenance; |
| Roll in | of a compile time subordinate which is being entered into the PCF system file to be used at the compilation incident to migration; |
| Roll out | of a versioned object being replaced in the PCF system file by another of the same name to be used at the compilation incident to a migration; |
| Locked | of the migration event that has caused the locking; of the application locked; of an object being migrated from or to a type other than maintenance; of an object being aligned or retired. |
To release locked data use the following procedure.
To access a Release Locked Data screen, do one of the following:
On the Administrator Functions menu, enter Code R (Release Locked Data) and optionally enter a user ID in the User field to limit the list.
On the Display Locked Data screen, mark the locked entity with R in the "C" column.
17:08:07 ***** PREDICT APPLICATION CONTROL ***** 2000-03-03
User SAGU - Release Locked Data -
C Nr Name of Locked Entity Lock Type Reason User ID
- -- -------------------------------- -------------------- ---------- --------
_ 1 CLOVER Application Migration EDSW
_ 2 HEATHER-DEV0-CONTROL-1 Migration Event MODIFY SAGU
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
|
This screen provides the same information as the Display Locked Data screen - that is, it lists the name and type of a locked entity; the cause of the locking (modification, deletion or migration); the user ID of the user who locked the entity. Each entry is assigned a number on the screen ("Nr" column); and an input field is provided for selecting an entry ("C" column).
Press PF11 to display the ID of the terminal from which the data were locked and the date and time at which the data were locked. Press PF10 to again display the cause of the locking and the user ID.
Select the data you want to release by
either entering the number of the entry (from the "Nr" column) in the Mark Selection field;
or by entering Rs in the "C" column next to the entries;
or by marking the entry with the cursor.
If you select data that is not locked by a migration event, the Release/Reset/Undo Confirmation window appears:
17:03:37 ***** PREDICT APPLICATION CONTROL ***** 2000-03-03
User SAGU - Release Locked Data -
C Nr Name of Locked Entity Lock Type Reason User ID
- -- -------------------------------- -------------------- ---------- -------
+-------------------------------------------------------------------------+
| --- Release Confirmation --- |
| |
| Migration Event data was locked by User UKMJ at TID DAEETCAV |
| on 2001-05-03 10:04:08 |
| |
| Event ... TEST |
| Reason .. MODIFY |
| |
| The Release option has been invoked. Enter 'RELEASE' to confirm or '.'|
| to Exit .. _______ |
| |
+-------------------------------------------------------------------------+
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
|
It is similar to the Display Locked Data window because it provides the following information: the entity locked; whether it was locked by a batch job or from an identified terminal; the time at which it was locked; and the cause of the locking.
If you select data which is locked by a migration event, the Release/Reset Confirmation window appears:
17:03:37 ***** PREDICT APPLICATION CONTROL ***** 2000-03-03
User SAGU - Release Locked Data -
+---------------------------------------------------------------------------+
| --- Release/Reset/Undo Confirmation --- |
| |
| Migration Event record was locked by User UKMJ at TID DAEETCAV |
| on 2001-05-03 10:14:05 |
| |
| Event ........ UKMJ_TESTING_UNDO_002 |
| Application .. UKMJ_APPLICATION |
| From Status .. UKMJ_TEST_1 |
| To Status .... UKMJ_PRODUCTION |
| Reason ....... Migration |
| Step Number .. 6 - Versions Copied |
| |
| Enter 'RELEASE' to unlock, 'RESET' to reset, 'UNDO' to undo emigration |
| or '.' to Exit ... _______ |
+---------------------------------------------------------------------------+
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
|
It is similar to the Display Locked Data window because it provides the following information: the event that caused the locking; the origin and the destination statuses; and the number and description of the step reached by the event. You can release the locked data or reset / undo the migration event. The resetting is described in section Reset a Migration Event.
On either the Release or Release/Reset Confirmation window
To release the locked data, enter RELEASE.
To exit the window and display the Release Locked Data screen again without unlocking the data, enter a period (.), or press PF3 or PF12.
When you enter RELEASE, the Release Locked Data screen appears. The layout of the screen depends on the type of data being released.
If data locked by a migration event is being released, the screens look like this:
10:21:01 ***** PREDICT APPLICATION CONTROL **** 2001-05-03
User UKMJ - Release Locked Migration Event Records -
Event ........ UKMJ_TESTING_UNDO_001
Application .. UKMJ_APPLICATION
From Status .. UKMJ_DEVELOPMENT LIB .. UKMJD23 ( 164,00247)
To Status .... UKMJ_TEST_1 LIB .. UKMJT23 ( 164,00247)
Object Object type Vers. Action
JULES1 Program Saved deactivated
JULES1 Program Catlg deactivated
JULES1 Program 0003 Deleted
JULES1 Program 0002 Restored in PCF
JULES2 Program Saved deactivated
JULES2 Program Catlg deactivated
JULES2 Program 0003 Deleted
JULES2 Program 0002 Restored in PCF
JULES3 Program Saved deactivated
JULES3 Program Catlg deactivated
JULES3 Program 0003 Deleted
JULES3 Program 0002 Restored in PCF
JULES4 Program Saved deactivated
MORE.....
|
10:22:05 ***** PREDICT APPLICATION CONTROL **** 2001-05-03
User UKMJ - Release Locked Migration Event Records -
Event ........ UKMJ_TESTING_UNDO_001
Application .. UKMJ_APPLICATION
From Status .. UKMJ_DEVELOPMENT LIB .. UKMJD23 ( 164,00247)
To Status .... UKMJ_TEST_1 LIB .. UKMJT23 ( 164,00247)
Object Object type Vers. Action
JULES4 Program 0003 Deleted
JULES4 Program 0002 Restored in PCF
UKMJ_PREDICT_APPLICATION Dictionary Closed
UKMJ_TESTING_UNDO_001 Migration Event Backed Out
UKMJ_APPLICATION Application Unlocked
MORE....
|
The screens are similar to the Display Locked Migration Event Data screen with the exception that, in the rightmost column, actions performed on the entities are listed rather than the status of the entities.
To scroll through the complete list of entities, press ENTER.
To interrupt the unlocking and to return to the Release Locked Data screen enter a period (.) or press PF3.
Release Locked Data screen displays one of the following messages:
"... data released", if the selected data was released;
"... was not released", if some of the selected data was not released.
When a migration event is reset, the following occurs:
If the event is then resubmitted, the data locked by it is released and the event is immediately restarted from the beginning. Since the application remains locked between the resetting and the resubmission, the state of the application's compartment will be the same at both submissions. It can, however, occur that the states of the compartments of the steplib applications or application Predict are different at the two submissions. Also, the states of any migration may change from the first submission to the second.
To reset a migration event, use the following procedure:
Enter Code R (Release Locked Data) on the Locked Data Maintenance menu.
A Release Locked Data screen appears.
On the Release Locked Data screen, select the migration event to be reset either by entering an R or placing the cursor in the "C" column, or by entering the number (from the "Nr" column) in the Mark Selection field.
A Release/Reset Confirmation window for the migration event appears:
17:03:37 ***** PREDICT APPLICATION CONTROL ***** 2000-03-03
User SAGU - Select Locked Data -
+-------------------------------------------------------------------------+
| --- Release/Reset/Undo Confirmation --- |
| |
| Migration Event record was locked by User UKMJ at TID DAEETCAV |
| on 2001-05-03 10:26:13 |
| |
| Event ........ UKMJ_TESTING_UNDO_001 |
| Application .. UKMJ_APPLICATION |
| From Status .. UKMJ_DEVELOPMENT |
| To Status .... UKMJ_TEST_1 |
| Reason ....... Migration |
| Step Number .. 2 - Versions Created |
| |
| Enter 'RELEASE' to unlock, 'RESET' to reset, 'UNDO' to undo emigration |
| or '.' to Exit ... _______ |
| |
+-------------------------------------------------------------------------+
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
|
It is similar to the Display Locked Data window. It provides information about: the event that did the locking; the origin and the destination statuses; the number and description of the step reached by the event.
You have the option of releasing the locked data or reset the migration event.
A Special Event Processing screen appears:
17:25:53 ***** PREDICT APPLICATION CONTROL ***** 2000-03-03
User SAGU - Special Event Processing -
Event ........ CLOVER-DEV0-CONTROL-1
Date ... 97-03-03 16:58:47 Tot Lines ... 20 1625 Page ... 1
Del Line 0100 PAC6902: (A) Migration initiated at 97-03-03 16:58 by EDSW
Del Line 0100 PAC6905: (A) ACF System File assignment .. (222,144)
Del Line 0100 PAC6905: (A) PCF System File assignment .. (222,145)
Del Line 0100 PAC6920: (A) COPY Objects Online
Del Line 0100 PAC6904: (A) Applymods in effect for Migration .... (14)
Del Line 0100 PAC7020: (A) Application Lock applied at 97-03-03 16:58.
Del Line 0000 PAC6902: (A) Create Version initiated at 97-03-03 16:58
Del Line 0000 PAC7057: (A) ES_Z_P04.0001 (Progrm) -- created.
Del Line 0000 PAC7057: (A) ES_Z_P05.0001 (Progrm) -- created.
Del Line 0000 PAC7057: (A) ES_Z_P09.0002 (Progrm) -- created.
Del Line 0000 PAC7057: (A) ES_Z_P11.0001 (Progrm) -- created.
Del Line 0000 PAC7057: (A) ES_Z_N99.0001 (Subpgm) -- created.
Del Line 0000 PAC7057: (A) ES_Z_L03.0001 (Local) -- created.
Del Line 0000 PAC7053: (A) 6 Natural objects processed.
Del Line 0000 PAC6903: (A) Create Version completed at 1998-03-03 16:58
Del Line 0100 PAC6902: (A) Precomple initiated at 1998-03-03 16:58:56
Del Line 0100 PAC6906: (A) Compile List deleted at 1998-03-03 16:58:56
MORE
|
The Special Event Processing screen lists the actions being taken to reset the migration event.
Press ENTER to scroll.
17:27:02 ***** PREDICT APPLICATION CONTROL ***** 2000-03-03
User SAGU - Special Event Processing -
Event ........ CLOVER-DEV0-CONTROL-1
Date ... 97-03-03 16:58:47 Tot Lines ... 11 1730 Page ... 2
Del Line 0100 PAC6902: (A) PostCmple initiated at 1998-03-03 16:59:29
Del Line 0100 Errors with Compile
Del Line 0100 Object Error Line
Del Line 0100 -------- ----- ----
Del Line 0100 ES_Z_P04 0924 0130
Del Line 0100 Subroutine, GDA or external report not found.
Del Line 0100 ES_Z_P05 0924 0130
Del Line 0100 Subroutine, GDA or external report not found.
Del Line 0100 PAC7067: (C) 00000002 errors in Compile phase.
Del Line 0100 PAC7066: (A) 00000004 Natural objects successfully compiled.
Del Line 0100 PAC6903: (A) Compiling completed at 1998-03-03 16:59:30
Event CLOVER-DEV0-CONTROL-1 has been RESET -- Audit Report Flushed
MORE
|
When the migration event has been reset, a message informs you that the event has been reset and the audit report has been flushed.
From the Locked Data Menu, enter Code S (Select Locked Data).
A Select Locked Data screen appears:
17:28:47 ***** PREDICT APPLICATION CONTROL ***** 2000-03-03
User SAGU - Select Locked Data -
C Nr Name of Locked Entity Lock Type Reason User ID
- -- -------------------------------- -------------------- ---------- --------
_ 1 CLOVER Application Migration EDSW
_ 2 FURZE Application Migration SACUBAT
_ 3 HEATHER-DEV0-CONTROL-1 Migration Event MODIFY SAGU
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
|
This screen lists the following information: the name and the type of a locked entity; the cause of the locking (modification, deletion, or migration); the user ID of the user who locked the entity. Each entry is assigned a number on the screen ("Nr" column) and an input field is provided for selecting an entry ("C" column).
Press PF11 to display the ID of the terminal from which the data was locked and the date and time at which the data was locked. Press PF10 to again display the cause of the locking and the user ID.
The entries on the Select Locked Data screen are listed in alphabetical order by user ID.
To display information about an entity listed on the Select Locked Data screen, enter the number of the entity (from the "Nr" column) in the Mark Selection field or enter D in the "C" column next to the entry.
Selected locked data can be released by marking entries of the Selected Locked Data screen with R the "C" column.
This function is applicable to migrations to test or production and to retirements from test or production, provided the event has reached stage 6 and have not been unlocked.
When a migration event is undone, the following occurs:
The migration steps are reversed and ACF data is updated.
The event is unlocked.
To undo a migration event, use the following procedure:
Enter Code R (Release Locked Data) on the Locked Data Maintenance menu.
A Release Locked Data screen appears.
On the Release Locked Data screen, select the migration event to be undone either by entering an R or placing the cursor in the "C" column, or by entering the number (from the "Nr" column) in the Mark Selection field.
A Release/Reset/Undo Confirmation window for the migration event appears:
0:14:20 ***** PREDICT APPLICATION CONTROL **** 2001-05-03
User UKMJ - Release Locked Data -
+---------------------------------------------------------------------------+
| --- Release/Reset/Undo Confirmation --- |
| |
| Migration Event record was locked by User UKMJ at TID DAEETCAV |
| on 2001-05-03 10:14:05 |
| |
| Event ........ UKMJ_TESTING_UNDO_002 |
| Application .. UKMJ_APPLICATION |
| From Status .. UKMJ_TEST_1 |
| To Status .... UKMJ_PRODUCTION |
| Reason ....... Migration |
| Step Number .. 6 - Versions Copied |
| |
| Enter 'RELEASE' to unlock, 'RESET' to reset, 'UNDO' to undo emigration |
| or '.' to Exit ... _______ |
+---------------------------------------------------------------------------+
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Canc
|
It is similar to the Display Locked Data window. It provides information about:
the event that did the locking;
the origin and the destination statuses;
the number and description of the step reached by the event.
You have the option of releasing the locked data, resetting the migration event or undoing the migration event.
Enter UNDO.
10:45:52 ***** PREDICT APPLICATION CONTROL **** 2001-05-03
User UKMJ - Event Migrate Processing -
Event Name ... UKMJ_TESTING_UNDO_002
Application .. UKMJ_APPLICATION
From Status .. UKMJ_TEST_1 Lib .UKMJT23 (00164,00247)
To Status .... UKMJ_PRODUCTION Lib .* PAA * (00164,00239)
PAC6902: (A) Unlock initiated at 2001-05-03 10:45:52
PAC7053: (A) 4 NATURAL objects processed.
PAC6914: (W) Application Lock was removed at 2001-05-03 10:45:52
PAC6903: (A) Unlock completed at 2001-05-03 10:45:52
MORE....
|
When the migration event has been undone, a message informs you that the event has been undone.
