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

Description:
We have been getting many errors appearing in the pc_server_logs for the "bad op date format...".

Here's an example for ADM library xyz50:

Load: /exlibris/aleph/u18_3/xyz50/tab/tab16
Error: bad op date format in line 000000010
Error: bad op hour format in line 000000010
Error: bad op date format in line 000000011
Error: bad op hour format in line 000000011
Error: bad op date format in line 000000012
Error: bad op hour format in line 000000012

Resolution:
The ./com_io/io_dates program issues eight distinct (but similar) messages in regard to tab16 date/time values:

Message Cause The program does this:

1. Error: bad op date format in line Column 5 is not "A" or "+" Uses "+" as the operator

2. Error: bad op hour format in line Column 8 is not "A" or "+" Uses "+" as the operator

3. Error: bad op req date format in line Column 15 is not "A" or "+" Uses the col. 5 value as the operator

4. Error: bad op req hour format in line Column 17 is not "A" or "+" Uses the col. 8 value as the operator

5. Error: bad date format in line Column 6 is not numeric Uses "00000000" as the value

6. Error: bad hour format in line Column 9 is not numeric Uses "2400" as the time

7. Error: bad req date format in line Column 16 is not numeric Uses the col. 6 value as the date

8. Error: bad req hour format in line Column 18 is not numeric Uses the col. 9 value as the time

In every case the message is just informational; the program proceeds regardless.

Note: the "Error: bad op hour format in line nnnnnnnnn" message can occur if the Group-ID/item-status/patron-status combination is missing entirely from tab16 (as described in KB 16384-64147).

• Article last edited: 10/8/2013