Activity (MOVEREQ/ENTRY)

Who can enter Move Request Maintenance?

Adding Move Requests (MOVEREQ/ADD)

Who can add Move Requests?

The delivered system allows any CA‑PanAPT user to add Move Requests.

Approving Move Requests (MOVEREQ/APM-level)

Who can approve Move Requests before the move to is done?

Each move level is separately authorized. Those who should approve movement into Quality Assurance are not necessarily the same as those who should approve movement into Production.

The delivered system allows the operations personnel to approve Move Requests into QA and Production. Users must also be authorized to grant specific approvals (1‑21) using the User ID Maintenance panel.

When another move level is defined to CA‑PanAPT a MOVEREQ/APM‑level activity record is created for it, with no one authorized to perform the approval. You must update this activity record before any approvals at the new level can be granted.

The user‑written Security Event Exit can further control users when approving Move Requests. See Appendix B.

Approving Move Request for Back Out (MOVEREQ/APB‑level)

Who can approve Move Requests before backing them out?

Each move level is separately authorized. Those who should approve Quality Assurance back outs are not necessarily the same as those who should approve Production back outs.

The delivered system allows the operations personnel approve Move Requests for QA and Production back outs. Users must also be authorized to grant specific approvals (1‑21) using the User ID Maintenance panel.

When another move level is defined to CA‑PanAPT a MOVEREQ/APB‑level activity record is created for it, with no one authorized to perform the approval. You must update this activity record before any back out approvals at the new level can be granted.

The user‑written Security Event Exit can further control users when approving Move Requests for back out. See Appendix B.

Creating an Online List of Move Requests (MOVEREQ/BRO)

Who can use the Browse function to create an online list of Move Requests?

The delivered system lets any user use the Browse function.

Updating Move Requests (MOVEREQ/CHG)

Who can update Move Requests before they are closed?

The delivered system allows the following users to change Move Requests: the user who added the request (the owner), any user who shares a group with the owner, group administrators in the owner's group, and users with the Operations attribute.

Changing Closed Move Requests (MOVEREQ/CHGAWAPP)

Who can change Move Requests while awaiting approval?

A Move Request cannot be changed once all approvals have been granted.

The delivered system lets operations personnel change the Move Request while it is awaiting approvals.

Once all approvals have been granted, the status of the Move Request must be changed to Being Created or Awaiting Approval before it can be changed. Changing the status removes all authorizations granted to date. See the Move Request Maintenance (CHG) function described in the "Move Requests" chapter in the CA‑PanAPT Reference Guide for more information on this function.

Closing Move Requests (MOVEREQ/CLO)

Who can close Move Requests?

The delivered system allows the following to close Move Requests: the user who added the request (the owner), any user who shares a group with the owner, group administrators in the owner's group, and operations.

Assignment Requirements At Close (MOVEREQ/CLOASSGN)

What criteria will be used to determine whether a member is properly assigned when a Move Request is closed?

Proper assignment is determined by testing the relationship specified in this activity against two user IDs. The Close Assignment option under Control File Maintenance System Information specifies which user IDs to use for the test. The CA‑PanAPT Reference Guide describes proper assignment in greater detail.

The delivered system allows users who meet any of the following tests to fulfill assignment requirements:

• The user who added the Move Request
• Any user who shares a group with the Move Request owner
• Group administrators in the Move Request owner's groups
• Users with the operations attribute.

Back Out a Move Request (MOVEREQ/BAK)

Who can set up a Move Request for Back Out processing?

The delivered system allows no users to back out Move Requests. Access to this activity is granted by the CA‑PanAPT system administrator once the appropriate models, JCL, and Library Codes have been set up to perform this action.

Copying a Move Request (MOVEREQ/COP)

Who can Copy the contents of one Move Request to create a new one?

The delivered system allows any CA‑PanAPT user to copy Move Requests.

Activity (MOVEREQ/CR)

Who can copy the contents of one Move Request to create another one for rework purposes?

The delivered system only allows the CA‑PanAPT system administrator to do this.

Changing Move Dates for Move Requests (MOVEREQ/DAT)

Who can change the Move date for Move Requests?

The delivered system lets the Operations personnel to change the Move Request Move Date.

Deleting Move Requests (MOVEREQ/DEL)

Who can delete Move Requests before they are closed?

The delivered system allows the Operations personnel, the user who created the Move Request, any user who shares a group with the owner, and group administrators in the owner's group to delete the Move Request.

Deleting Closed Move Requests (MOVEREQ/DELCLOSD)

Who can delete closed Move Requests?

The delivered system lets the Operations personnel delete closed Move Requests.

Viewing Move Requests (MOVEREQ/INQ)

Who can see Move Requests (Inquire)?

The delivered system lets any user inquire Move Requests.

Adding Members to a Move Request (MOVEREQ/MEMBER)

Who can add members to a Move Request?

The delivered system allows any CA‑PanAPT user to add members to a Move Request. For the online preparation of Move Requests to be streamlined, keep the authorizations for MOVEREQ/MEMBER the same as those for MOVEREQ/ADD and MOVEREQ/CHG.

The user‑written Security Event Exit can further control users from adding members to a Move Request. See Appendix B.

Changing Members in a Move Request (MOVEREQ/MEMCHG)

Who can change members in a Move Request?

The delivered system allows any CA‑PanAPT user to change members in a Move Request. For the online preparation of Move Requests to be streamlined, keep the authorizations for MOVEREQ/MEMCHG the same as those for MOVEREQ/ADD and MOVEREQ/CHG.

The user‑written Security Event Exit can further control users from changing members in a Move Request. See Appendix B.

Deleting Members from a Move Request (MOVEREQ/MEMDEL)

Who can remove members from a Move Request?

The delivered system allows any CA‑PanAPT user to delete members from a Move Request. For the online preparation of Move Requests to be streamlined, keep the authorizations for MOVEREQ/MEMDEL the same as those for MOVEREQ/MEMBER.

The user‑written Security Event Exit can further control users from deleting members from a Move Request. See Appendix B.

Deleting Members from a Move Request and the Test Libraries (MOVEREQ/MEMPURGE)

Who can remove members from a Move Request and scratch them from the Test Libraries at the same time?

The delivered system allows any CA‑PanAPT user to delete members from a Move Request and the Test Library.

The user‑written Security Event Exit can further control users from purging members from a Move Request and Test Library. See Appendix B.

Printing Move Requests (MOVEREQ/PRT)

Who can print a hard‑copy authorization form for a Move Request?

The delivered system lets any user print a Move Request authorization form.

Run Verification Procedures (MOVEREQ/RVP)

Who can run Verification Procedures for a Move Request?

The delivered system allows users currently authorized to CLOSE a Move Request, to Run Verification Procedures. This activity can be changed using online Control File maintenance.

Changing Status for Move Requests (MOVEREQ/STA)

Who can change the status of Move Requests?