Planning the Implementation › Group and Operation Personnel Decisions › Retrieve Processing Setup Decisions › Library Codes and Inventory File Interrelation

Library Codes and Inventory File Interrelation

Relating Library Codes and the Inventory file as follows:

1. When you define a Library Code (see Library Code Setup Form in Appendix A), you can specify Inventory is enabled for this Library Code. You would expect that Inventory Records exist for all Move Request Members that use this Library Code.

   You can specify that if CA‑PanAPT does not find an Inventory Record for a member being added to a Move Request, it will automatically prompt the user to create one and provide default values on the creation panel (Automatic Create).

   If you specify that Inventory is enabled, the Inventory Record does not exist, and Automatic Create is not enabled, then each member involved is identified by a flag in the status column of the Member Moves panel. Members that require an Inventory Record or an approved Inventory Record have an I in the status column. Members that require assignment have an A in the status column.

2. You can indicate that a member must be properly assigned.

   Move Requests that contain the member cannot be closed until the member is properly assigned. Your site defines proper assignment through values selected for the Close Assignment option (Control File Maintenance; System Information) and the MOVEREQ/CLOASSGN activity (Control File Maintenance Activity).

   Alternately, you can indicate that if the member is not already assigned to that user (and not assigned to anyone else), CA‑PanAPT will do an Automatic Assignment to the user when the member is added to the Move Request.

   When a member is assigned to a user, no other user can assign or Retrieve it. This ensures that duplicate moves are not done without knowledge of the assigned user.

   Note: Assignment does not stop other users from adding a member to more than one Move Request.

3. You can indicate whether CA‑PanAPT automatically Releases the Inventory Assignment when an assigned member is finally moved to Production or deleted from a Move Request or when a Move Request is deleted.

   If a member to be released exists on any other Move Request in an active status, the assigned-to Move Request is changed to the Move Request containing the member with the earliest Move Date. The member can be reassigned to the owner of this other Move Request depending on the value of the Reassign/Transfer flag on the Control file.

4. You can specify that all members of the Library Code must have Approved Inventory Records before any Move Request containing them can be closed. CA‑PanAPT flags any members of the Library Code that do not have Approved Inventory Records.

   You must approve each flagged Inventory Record before the Move Request can be closed and processed. This helps ensure that the Inventory Records contain data acceptable to the models that will use the records during daily move processing. If a model detects bad data, it might signal an error that terminates processing for all Move Requests being processed in that Job.

   An inventory edit exit can assist in ensuring correct inventory data. The exit is invoked for Inventory maintenance activities. It ensures that appropriate data is entered when a Move Request is added or changed; this decreases the need for manual inspection.

5. You can specify whether newly‑added Inventory Records for the Library Code are marked Approved or Unapproved. You might want to mark them Unapproved to require manual inspection later. If the Library Code models do not have stringent data requirements, you can choose to have CA‑PanAPT mark each new record Approved.
6. You can specify whether members can be retrieved. You can only retrieve members after they have been assigned to you. Retrieve can be initiated as part of the assignment request or, later, as part of a specific Retrieve request.

   To Retrieve members, their Library Code definition must have Inventory, Assignment, and Retrieve enabled.

7. You can specify an Inventory Qualifier that is different from the default. The default is the Library Code.

   CA‑PanAPT treats members with the same name but different Inventory Qualifiers as different members. For example, a source module and a load module could have the same member name, be resident in different libraries and be treated differently.

   When Library Codes share the same Production Library, however, their members are not different. These Library Codes must specify the same Inventory Qualifier so that CA‑PanAPT recognizes that their members are the same for purposes of assignment and release.