Batch Interface › Add Move Requests to the Pending File › Activity

Activity

This job reads records from the batch Add‑Move‑Request file, creates Move Requests using information from the input records, and adds the new Move Request(s) to the Pending file. The record format for the input file is the same one used by the batch Purge Move Request job (APJJ5955).

A report is produced to list each Move Request created and added to the Pending file. Use this report to obtain the Move Request numbers for Move Requests created by this job.

APJP5960 looks for groups of Add‑Move‑Request records on the file to create a Move Request. Each group of records consists of a Move Request Description record and a Member Name/Library Code record.

The first record in the group is the Description record. This record has a record ID of 01, and it is required to add a Move Request. The information in this record corresponds to the online Description of Move Request panel.

The next record is the Member Name/Library Code record that has a record ID of 02. The information in this record corresponds to the online Member Moves panel. There must be one Member Name/Library Code record for every member that is to be included in the Move Request.

The Description record indicates that a new Move Request is to be added. The data for the Service Request, Final, Next, and First Run Dates, Move Type, Early Stop level, Special Handling indicator, Short Description and the Expanded Description fields is taken directly from this record.

Validation is performed on these fields. If errors are detected, the Move Request is not added or is added as an invalid Move Request, depending on whether the invalid data was valid at some other time. Examples that cause Move Requests to be added as invalid are:

• Move dates prior to current date
• No expanded description when required by control file option

Note: The MR-VERSION-STAMP must be 03.1 or the entire Move Request is not added to the Pending file.

The Member Name/Library Code record contains the member data information for the Move Request. Use this to specify:

• From Member name on the Test-Level Library
• From User Data for the Test-Level member
• To Member name on the Production Level library
• To User Data for the Production Level member
• Library Code/Subcode associated with the member

Validation is performed on this record to determine if the Library Code listed for the member is found on the Library Code file and to verify that the From or To Member name is not blank. Also, all members must be presented in order by Library Code and To Member name, the same order they occur in a Move Request. If these errors occur, the entire Move Request is not added to the Pending file.

In addition, all online edits are performed. If applicable to the Library Code, Inventory is automatically added and assigned. Member existence exits are called. Online edits that would have prevented you from adding a member online, such as member names not conforming to the minimum and maximum lengths defined in the Library Code, causes the Move Request to be added as invalidated.

APJJ5960 creates a Move Request for each group of Description and Member Name/Library Code records. For Move Requests added as invalidated, you must use the Move Request Online Change option to validate all the input fields. For all Move Requests added, a new Move Request number is assigned.

APJJ5960 also produces the Batch Add‑Move‑Request Report. This report lists:

• All Move Requests created
• The Move Request's description and member data
• All invalid Library Codes and the member data to which they belong

For an example, see Appendix A, "Reports," in the CA‑PanAPT Reference Guide.

Move Requests created by this job can be changed and deleted only by the CA‑PanAPT online Move Request option.