Planning the Implementation › Group and Operation Personnel Decisions › Online Inventory Usage Decisions › Inventory Record Initialization

Inventory Record Initialization

You can build Inventory Records in three ways:

• Use Inventory maintenance panels to build the records.
• Allow CA‑PanAPT to build the records automatically when entities without Inventory Records are added to a Move Request.
• Run the batch jobs that build the Inventory Records, fill most of the required fields, and add the records to the Inventory file.

You can use any combination of the previous three methods.

CA‑PanAPT provides two Jobs: APJJ6910, which reads the directory of a library, and APJJ6920, which produces Inventory Records for each member. APJJ6910 reads PDS, CA‑Panvalet, and CA‑Librarian library formats. APJJ6920 uses the library information from Job APJJ6910 to create Inventory Records.

Because the directory does not contain all the information fields supported by CA‑PanAPT, most of these fields are blank. You must specify the Library Code where you are adding members. You must run APJJ6910 and APJJ6920 for each Library Code.

APJJ6920 creates Inventory Records for CA‑PanAPT using the directory information extracted by APJJ6910. As delivered, APJJ6920 will mark all Inventory Records it creates as NOT‑APPROVED. This is an indication that they contain only the basic information extracted from the library directory. They will not contain any of the optional fields that CA‑PanAPT does not validate.

If your Models require specific values in any of these fields, use the CA‑PanAPT panels to change the Inventory Record values (see the "Inventory Records" chapter in the CA‑PanAPT Reference Guide). As you review each member, mark it APPROVED as a record of your progress.

The records created during APJJ6910 execution are in the format mapped by copybook APCCDIB2. For detailed information, refer to Appendix C. As an alternative to running APJJ6910, you can write your own program to create Inventory Records in APCCDIB2 format; then run APJJ6920, using these records as input.

You can define a Library Code that requires all members to have an Approved Inventory Record before a Move Request that contains the members can be closed. This helps to ensure that inventory data is in a correct form for models. You can also add an Inventory Edit Exit to help ensure correct data.