Display only. Displays the action you selected.
Display only. Displays the current status of the Move Request. If you are Copying or Adding a Move Request, the status is CRE (Being Created). Otherwise, CA‑PanAPT displays the status of the Move Request as it exists on the Pending File.
Display only. Displays your Move Request number. The Move Request is identified by the Move Request number. If you are Copying a Move Request or adding a new Move Request, CA‑PanAPT generates a new Move Request number and places it in this field. Otherwise, this is the Move Request number you indicated.
Display only. If this Move Request was created by the Copy for Rework action, the original Move Request number you copied from is displayed here. Otherwise, this field is not displayed.
Required. Length: 1‑55. Type: alphanumeric.
Use this field to describe a Move Request. This field appears on Move Request reports. CA‑PanAPT does no editing on the contents of this field other than to verify that it is not blank and to convert it to upper case.
Required. Length: 1-16. Type: alphanumeric.
Use this field to enter an internal project identifier, work order, service request, problem reporting, or problem tracking number that is associated with the Move Request. CA‑PanAPT does no editing of the contents of the field other than to verify that it is not blank.
Optional. Valid values: Y (Yes) or N (No):
An expanded description must be entered for this Move Request. You cannot override the default value when it is set to Y. After the Move Request panel has been displayed and processed, the Expanded Description panel is displayed. You must enter at least one line of data into the expanded description.
This is the default. An expanded description can be entered for this Move Request. To do this, change this value from an N to a Y. The Expanded Description panel is displayed after the Move Request panel has been displayed and processed, but you are not required to enter an expanded description. If you leave the value as N, you are not presented with the Expanded Description panel.
Optional. Length: 1‑16. Type: alphanumeric.
Use this field to give your Move Request a unique name you can remember. This name can be entered on the Move Request Maintenance panel instead of a number.
Optional. Length: 1‑16. Type: alphanumeric.
If you want to use the Development Facility with this Move Request, you need a Project to assign Development and Work libraries to be used. The name of that Project is specified here. You can also:
Required. Format: system date.
Enter the date when these modules should be moved to their final destination level (typically production). CA‑PanAPT does not accept a date that is prior to the current (system) date. Modules are not moved to their final level until this date is reached and all approvals and verifications for this level are satisfied.
In most cases, when a Move Request completes a move to a level prior to the final move level, the Next Move date field is updated to match the Final Move date. The exception case is when the Next Move date field contains all zeros.
For moves where the final level is the only level, as in a move straight from test to production, this date overlays the Next Move date when you close the Move Request.
While the year is displayed as four digits, you need only enter two digits. CA‑PanAPT converts the two‑digit year into four‑digits, including the century. To enter today's date, simply enter an equal sign (=) in the first position of the date.
Optional. Format: system date or all zeros.
Enter the date when these modules should be moved to their next destination level (such as quality assurance). CA‑PanAPT does not accept a date that is prior to the current (system) date. Modules are not moved to their next level until this date is reached and all approvals and verifications for this level are satisfied.
If this field is blank or all zeros, the next move is not restricted by date.
In most cases, when a Move Request completes a move to a level prior to the final move level, the Next Move date field is updated to match the Final Move date. The exception case is when the Next Move date field contains all zeros.
For moves where the final level is the only level, as in a move straight from test to production, this date is overlaid by the Final Next Move date when you close the Move Request.
While the year is displayed as four digits, you need only enter two digits. CA‑PanAPT converts the two‑digit year into four‑digits, including the century. To enter today's date, simply enter an equal sign (=) in the first position of the date.
Optional. Format: system date.
Although the year displays as four digits, you can enter a two digit year of the current century into the first two positions of the field. CA‑PanAPT converts the two-digit year into four-digits, including the century.
You can leave this field blank. If the First Run Date is the same as the Final Move Date, enter an equal sign (=) in the first position of the First Run Date. CA‑PanAPT copies the current value of the Final Move Date field into this field. The First Run Date, if entered, cannot be a date earlier than the Final Move Date.
This field is for documentation purposes only. It appears on CA‑PanAPT reports. This is intended to be the date that these modules are first run in Production.
Display only. CA‑PanAPT displays the level names (in place of LEVL) and the date that the move took place for the last two moves completed for the Move Request. If no moves have taken place, this area of the panel is blank.
If the completion of a move is indicated by the on‑line status change function, the level for that move is shown, but the date is blank. The move might have taken place on a different date than the online status change.
To see the move dates for levels beyond the last two, you must run reports. Most reports that display Move Request information show a complete move date history.
Required. Length: 1. Valid values: alphanumeric. Default: M.
Enter the value for the Move Processing Cycle when this Move Request be processed. The valid values are defined by your site and are not checked by CA‑PanAPT.
A default value of M is presented on the panel. This value provides for compatibility with the earlier versions of CA‑PanAPT.
CA‑PanAPT has the ability to process multiple Move Processing Cycles simultaneously.
Required. Valid values: Y (Yes) or N (No):
This is a Special Handling Move Request and is meant to document a change to the environment external to CA‑PanAPT. No approvals are ever required for a Special Handling request.
This is the default. This is a normal Move Request.
This flag indicates whether or not the Move Request is intended to document events without doing any actual moves. Special Handling Move Requests contain only the descriptive part of a standard Move Request. No member names or Library Codes can be specified.
Optional. Valid values are short level names that are defined to your CA‑PanAPT system, or spaces.
You can prevent a Move Request from moving through all of its destination levels by specifying an Early Stop Level. This is the level at which it ends movement.
All members of this Move Request must use Library Codes that use this level. If any of the Library Codes skip this level then CA‑PanAPT prohibits the close.
This is typically used to correct a small portion of a Move Request that has already moved to some level. If, for instance, some changes to an application are not working after it has been move to a quality assurance level, rather than backing out the Move Request and starting all over, you can create another Move Request to handle the failing members. Once you have made the corrections at the test level you can move them up to the quality assurance level in a Move Request that has QA (quality assurance) specified as the Early Stop Level.
Display only. This area of the panel shows the Approvals Verifications that are required and that have been satisfied for the Move Request. If the Move Request is in a Being Created status, all that is shown is the Verifications required to close the Move Request. Otherwise, it shows the ones for the current level.
In the Approvals and Verifications Required area, the values can be:
indicating that the approval or verification is required
indicating that it is not required.
In the Approvals so far area, the values can be:
indicating that the approval has been granted
indicating that the approval has been denied
indicating that the approval has neither been granted nor denied yet.
In the Verifications so far area, the values can be:
indicating that the verification has been satisfied
indicating that the verification has failed (unverified)
indicating that the verification job began but has not finished yet (or was canceled or abended before it finished)
indicating that the verification has not been run.
Display only. Not available to Models.
the date this Move Request was added. Format: system date.
the time this Move Request was added. Format: system time.
the TSO userid of the CA‑PanAPT user who originally added this Move Request.
Display only. Not available to Models.
the date of the last update of this Move Request. Format: system date.
the time of the last update of this Move Request. Format: system time.
the TSO userid of the CA‑PanAPT user who last updated this Move Request or the last utility that updated this Move Request.
When you have reviewed or modified fields as required, press ENTER.
If you decide to not continue processing this Move Request, enter the END command (PF3) while viewing this panel. You return to the panel you came from (the Move Request Maintenance panel or the Browse Move Requests List panel). The action is not taken and the file is not updated.
If you type the END command (PF3), the new Move Request has already been created. After you press ENTER on the Description of Move Request panel, the new Move Request exists on the Pending file and the Member Moves panel displays.
If you are in the DEL Action (Deleting) when you press ENTER, the Expanded Move Request Description panel is displayed when an Expanded Description is present for the Move Request. When you press ENTER on the Expanded Move Request Description panel, the Move Request is marked as deleted and you return to the panel from which you came (the Move Request Maintenance panel or the Browse Move Requests List panel).
If an Expanded Description is not present when you press ENTER, the Move Request is marked as deleted and you return to the panel from which you came.
When a Move Request is deleted, Reassign/Release Processing occurs for each member in the Move Request. See the topic Reassign/Release Processing earlier in this chapter.
If this is a Special Handling Move Request, (Y in the Special Handling field) the Expanded Move Re
When you press ENTER, you return to the panel from which you came (the Move Request Maintenance panel or the Browse Move Requests List panel).
If you are in the ADD Action (Adding), when you press ENTER, the Expanded Move Request Description panel displays if:
If an Expanded Move Request Description panel is not to be displayed, when you press ENTER, you see the Member Moves panel, APIP140.
When you press ENTER and the next panel appears, the Move Request has been added. If you press PF3 (END) on any of the rest of the panels, you do not delete the new Move Request.
If you are Updating (CHG) or Inquiring (INQ) about a Move Request and an Expanded Description is present for the Move Request, when you press ENTER, the Expanded Move Request Description panel displays. Otherwise, the Member Moves panel displays.
If you are Updating a Move Request and you enter a Y in the Expanded Description field on the Description of Move Request panel, when you press ENTER, the Expanded Move Request Description panel displays.
|
Copyright © 2004 CA.
All rights reserved.
|
|