- Article Type: General
- Product: Aleph
- Product Version: 20, 21, 22, 23
After an update of ./xxx50/tab/tab31, all existing Z305 records (local permissions) should be updated according to the new tab31 definition.
The tab31 columns correspond to particular z305 Oracle table columns. For example, tab31 column 15, "Cash overspend limit", corresponds to the z305_cash_limit field.
First, back up the Oracle table Z305 in your XXX50 library.
Then export the Z305 table using Export Database Tables (file-03).
"Procedure to Run" = "Go"
"Number of Records per File" = "999999999"
"File Format" = "Fix"
Then import the table using the file-06 Service ("Import Database Tables - With Checks"). Do not perform this action during working hours!
All permission flags, the cash limit, and the expiry date will be fixed according to tab31 by file-06, that is, the z305 values for each patron will be changed to those given for that patron's sublibrary/patron status (columns 1 and 2) in tab31.
p_file_06 will update these Z305-fields:
[Note that the patron's Z305-BOR-STATUS can *not* be changed via this method -- because that's what's used to determine which entry in tab31 to use.]
Alternatives to this would be using the file-20 (Patron load) Service, or use SQL to make the changes.
In the case of file-20 flat/sequential-format input, most of the z305 fields cannot be specified via the PLIF "BOR" segment. However, the z305 records for the patrons being loaded could be deleted prior to running p_file_20. The service will then create a new z305, based on the tab31 defaults.
Or SQL can be used to make the update. (Note: the patron expiration date is found only in the z305_expiry_date field; there is no other place it needs to be updated.)
But the file-03/file-06 procedure described in Resolution section is preferable.
In all cases, be sure to back up the z305 table before running such an update.
Category: Circulation (500)
- Article last edited: 27-May-2016