• Article Type: General
• Product: Aleph
• Product Version: 16.02

Description:
The p_cir_32 log in $alephe_scratch has the following two errors:

(1) I/O error : file 'TP_OUT'
error code: 9/194 (ANS74), pc=0, call=1, seg=0
194 File size too large

(2) I/O error : file '/aleph/aleph/u16_1/tmp/cun502229467'
error code: 4/6 (ANS85), pc=0, call=12, seg=0
146 No current record defined for sequential read

The parameteres for the job were:
Fixed param: ABC50,patron_sc,300,N,Y,Y,,Y,,Y,Y,N,
setenv p_active_library "ABC50"
setenv p_report_file_name "patron_sc"
setenv p_number_of_days "300"
setenv p_update_z31 "N"
setenv p_update_z36h "Y"
setenv p_item_status_yes_no "Y"
setenv p_item_status_filter ""
setenv p_sub_library_yes_no "Y"
setenv p_sub_library_filter ""
setenv p_update_z37h "Y"
setenv p_update_z35 "Y"
setenv p_update_z40 "N"

Resolution:
We see this in the abc50 $data_scratch:

-rw-rw-r-- 1 aleph aleph 2147483647 Jan 25 02:12 cir_32_report

This file is at 2 gig. That's why it says "File size too large".

util f/4 shows that the pre-version-16 ID fields have the text "Removed" in them.

Version 16-up puts "SCR + today's date" into the ID field. And following SQL shows that there are none of those in the z35:

SQL> select count(*) from z35 where z35_id like 'SCR%';

It wants to change all the "Removed" to "SCR20070125".

You may want to use SQL to update the z35_id, z36h_id, and z37h_id, changing 'Removed' to, for instance, 'SCRpre16', before running p_cir_32.

If this change is made, then p_cir_32 should work OK with 300 days (days-to-save).

Or, you could run p_cir_32 with a much greater number of days. And then, once you find a value that works, do subsequent runs with successively lower "days-to-save" values.