Move Requests › Closing a Move Request › Move Request Closure Panel › Panel Field Descriptions

Panel Field Descriptions

Action

Display only. The selected action BAK entered earlier displays.

Current Status

Display only. The current status of the Move Request displays.

Move Req

Display only. Your Move Request number displays.

Description

Display only. The description of the Move Request displays.

Next Move Date

Display only. Format: system date.

This is the date that the move to the next level is to take place. Note that if this Move Request only moves one level (such as Test to Quality Assurance without moving any further) the Final Move date overlay this date when the close completes.

Final Move Date

Display only. Format: system date.

This is the date that the move to the final level is to take place.

Move Type

Display only. The Move Processing Cycle when CA‑PanAPT move this Move Request. The meaning of this value is controlled by your site.

Number of modules

Display only. The total number of entities in this Move Request.

Special Handling Move Requests can be closed with zero modules. To close a normal Move Request, at least one entity must be defined in it.

Early stop level

Display only. If an Early stop level was defined for this Move Request it is displayed here, otherwise this field is blank. An Early stop level is a way to cause a Move Request to end short of what is normally its final destination.

Entire function desired

Required. Length: 3. Type: alphanumeric. Valid values: CLO or C, VER or V, or END or E. No default.

CLO or C

Close the Move Request. CA‑PanAPT changes the request's status, resets restriction flags, and prohibits any further alteration of the request's description or module names.

VER or V

Verify the Move Request before Closing it. CA‑PanAPT verifies each member in the Move Request and resets the restriction flags, but does not close the Move Request.

END or E

Return to the original panel without changing the Move Request's status.

Verifying a Move Request

You cannot close a Move Request that has Close restrictions or outstanding Verification Procedure Requirements. You can ensure that the Move Request can be closed by Verifying it prior to trying to close it. On the Move Request Closure panel, type VER in the Enter Function Desired field to Verify the request and press ENTER.

If there are no Close restrictions, and no outstanding Verification Procedures, a message is displayed indicating that. If a close is performed, it be successful.

If there are outstanding Verification Requirements, CA‑PanAPT displays the Move Request Verification panel. This lets you run any outstanding procedures.

Correcting Close Restrictions

To identify the specific members that are restricting Closure, perform an Inquire on the Move Request and scroll through the member list looking for a non‑blank status field for a member. After restricted members have been identified, the owner can take steps to have Assignment transferred and Inventory Records approved as required.

There are five types of close restrictions and the actions for correcting each type of close restriction:

A (Assignment)

1. Inquire against the System Information in the Control File to determine the Close Assignment option. This option tells you what two user IDs are used to determine proper assignment. Also, in the System Information, look at the Move Req Assignment Option. This tells you whether the inventory has to be assigned to the Move Request being closed for proper assignment.
2. Check the MOVEREQ/CLOASSGN Control File activity to determine the relationship to the assigned user that is checked at close time. Use this information to determine whether another user can close the Move Request or whether to transfer assignment of the member to another user.
3. Inquire against the Inventory Record to determine the current assignment status. If the member is not assigned, assign it to a suitable user. If it is assigned, identify to whom it is assigned and have that user transfer the member to a suitable user.
4. If a member must be assigned, but the member is not assigned to any user, not even a CA‑PanAPT Systems Administrator can close the Move Request.

   If all members are assigned, the CA‑PanAPT Systems Administrator can close the Move Request. If your site has requested the MOVEREQ/CLOASSGN option, which tests the user IDs of the assigned user and the user closing the Move Request, a CA‑PanAPT Systems Administrator be able to close the Move Request. Otherwise, the Systems Administrator cannot close the Move Request because assignment requirements must always be met.

I (Unapproved Inventory)

Approve the Inventory Record or review the Library Code to determine whether approved Inventory Records are required for this Library Code.

C (Concurrent Development)

The Concurrent Development restriction tells you that since the time that you added the member to the Move Request, another instance of the member has been moved to its final destination. Presumably this other instance was being developed at the same time as the one for your Move Request, and its changes might not be accounted for in your copy of the member.

Once you are satisfied that the changes for this other copy of the member are accounted for in your copy, change your Move Request using the Move Request CHG action and issue the CDC Action command for your member. This clears the Concurrent Development restriction flag so that you can close your Move Request.Note that the Concurrent Development restriction flag hides the Unapproved Inventory restriction flag. If the member has unapproved inventory, the I flag is visible after clearing the C flag.

V (Rejected by Member Existence Exit)

1. Review messages written to the ISPF log.
2. Identify the Member Existence Exit named in the Library Code definition.
3. Ensure that the exit exists and that the load library in which it resides is accessible to the user who is trying to close the Move Request. See Load Libraries in Logon Procedure.
4. Determine the requirements of the Member Existence Exit specified in the Library Code. All sample exits supplied with CA‑PanAPT require only that the member exist on the starting level library. Your CA‑PanAPT Systems Administrator must tell you the requirements of any site‑specific exits.

   Make the member satisfy the requirements of the exit. For sample exits supplied with CA‑PanAPT, ensure that a copy of the member is on the starting level library for the Library Code.

* (Undergoing development)

You must finish development of the Move Request before it can be closed. After you are finished testing the members, use the Development Facility to check in the members for migration.

You might want to identify (online) those Move Requests that have Close Restrictions. After identifying them, you can initiate procedures to correct the conditions that are restricting Closure.

You can perform a Verification on a Move Request to reset the flags prior to final closure.

You can select Move Requests that cannot be closed from the Browse Move Requests panel. After displaying the selected Move Requests on the Browse Move Requests List panel, select any valid Move Request action to see the detail of an individual Move Request. Then scroll through the member list, reviewing the status to determine which members have close restrictions.