When Sander's "loading tool" runs, it runs on ips05i, that is, to get to it, you go to http://ips05i/loading and since that node is not NAT'd to the Internet, the only way you can get to the loading tool from San Jose, is to logon to ips01i or ips06i (with Exceed if on Windows), Launch netscape, then go to http://ips05i/loading (This works because of this line in the web server's config file, ScriptAlias /loading /arc/ips/cgi-bin/admin/loading.html ) The userid/password you need is either admin/neubauten or rick using your standard Internet password. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The files that drive the loading tool are in the /dfs/prod/ips/cgi-bin/admin directory in Japan, or at the BIE, /ips/cgi-bin/admin - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - When the loading tool starts up, it says it can be used to - displays the number of free and the slot numbers of the attached jukeboxes, - displays the number of filled slots and which CD labels are in which slot, - Physically Insert a CD, - Physically Remove a CD, The loading tool also maintains 2 lists, an "Insert List" and a "Remove List", which is actually the file /ips/tmp/juke_state on the image server. <<< I'm not sure about that last sentence. /ips/tmp/juke_state actually exists >>> <<< on both the Verity web server and image server machines, and according to the >>> <<< loading tool code, there are actually 6 lists maintained (I think), >>> <<< insert and delete >>> <<< insert_ws and delete_ws ("ws" apparently stands for "Web Server") >>> <<< and insert_is and delete_is ("is" apparently stands for "Image Server") >>> <<< On 1-21-2003, Sander couldn't explain why there are two, kind of equal >>> <<< juke_state files on the two machines, nor could he tell me the differences >>> <<< between the 3 sets of insert/delete lists. >>> When you insert a CD, the loading tool puts that CD label into the "Insert List" and it stays there until you remove it. You can also add or remove a CD manually to either list by selecting it from the "Filled" half of the screen and selecting one of the "Add to ... List" buttons. And lastly, there's a "Clear Lists" button which clears both lists. Once you've selected the CDs you want to work on, you click the "Next" button, which takes you to a second screen with two parts; The top half is for the Image Server and allows you to - convert the bibliographic data of CD's to DB2 load format (Convert2DB2), - update the image servers' indexes (patbuild), - Refresh the image servers' indexes (patrefsh). The bottom half is for the Verity Server and allows you to - load the converted data into DB2 (importpat) and index into the Verity collection, - just do the Verity indexing step, - optimize the Verity collection. These screens also allow you to check the log files (see below) to see how things went. If there's something in the "Remove List", there must be something on the screen that allows you to - remove the data from the image server indexes, - remove the data from DB2, - remove the data from the Verity indexes, but I didn't actually go down that path. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - When the loading tool runs on the image server, its log files are at /ips/tmp. When the loading tool runs on the Verity server, see the /ips/coll/lists files. Here's a sample of the log files I found on 9-20-2002 from debugging a Patolis problem loading mepb2002038. They had corruption on the EPB1____.idx file, which evidently started when indexing mepb2002037. On the Image Server: => STDOUT & STDERR from the patbuild & Convert2DB2 juke_logips07ijb2.dev_395 => commands, when processing the mepa2002072 CD juke_errips07ijb2.dev_395 => from slot 395 of ips07ijb2 jukebox. When things work ok, this file shows the patbuild & Convert2DB2 commands used and little if no errors. These files were clean. On the Verity Server: mepa2002072 => Input file containing a list of patents to index. mepa2002072.out => mkvdk output. Image Server: => I'm not sure what these two files were from. They both showed juke_log_254 => the same "RC 6" error, which is a patrefsh error. Over in the juke_err_254 => /ips/logs/patrefsh0917.log file was this line ... 17:38:34 ... PAT2121E Invalid directory [/dfs/.rw/imgdata]. which I'm guessing was caused by the DFS crash they had that day. Image Server: => STDOUT & STDERR from the patbuild and Convert2DB2 juke_logips07ijb3.dev_254 => commands for mepb2002037. Besides the "RC 2" juke_errips07ijb3.dev_254 => cooresponding to the Sep 17 17:38:34, apparently-DFS error above, these were clean except they showed patbuild starting once at 16:28:42 and again at 16:29:18. I don't know why the first one failed, but the timestamp of the bad EPB1____.idx file is 16:29. Apparently, this CD only affected the EPB1 & EPB2 idx files. Image Server: => The loading tool's temporary work file for patbuild. jukelabel.63004 => Contains the CD label to work on, in this case, mepb2002037. Sep 18 16:27 Evidently left over from when the first patbuild command failed. Image Server: juke_errips07ijb2.dev_393 => STDOUT & STDERR from the patbuild and Convert2DB2 juke_logips07ijb2.dev_393 => commands for mepa2002074, which was indexed after Sep 20 16:46 the mepb2002037 failure above. But this indexing apparently hit only the EPA1, EPA2, and EPA3 indexes. juke_log_393 => Shows "RC 6" errors which is a patrefsh error. juke_err_393 => Sep 20 16:56 => juke_errrefresh_ => Best file to go to to see error messages from the patrefsh. It showed for both patrefsh attempt, : PAT2023I Loading [/dfs/.rw/imgdata/EPB1____.idx] : PAT2023I Loading [/dfs/.rw/imgdata/EPB1____.idx] ERROR: Invalid byte count: expected:[2209290] actual:[2203128] This message doesn't appear anywhere else, e.g. not in any file in /ips/logs. Interesting, isn't it that the /ips/idx/EPB1____.idx file is actually 2203160 bytes big. Neither number agrees. Hmmm. juke_logrefresh_ => Nothing interesting in this file. juke_state => I dunno what this is, but it contained insert=ips07ijb2.dev%2C393%2Cmepa2002074 is=10.150.172.85%3A80 submit=Next vs=10.150.172.83%3A80 juke_list => I dunno what this is, but it contained mode=memory insert=ips07ijb2.dev,393,mepa2002074 It looks like both juke lists, i.e. the "Insert" & "Remove" lists. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - At the BIE/NIPO, the loading tool runs on the internal web server which runs on port 180, so you need to jump through these hoops to get it up. 1) If from a Thinkpad, then start Exceed first (on AIX, X is already up). 2) ssh -l delphion biecws (with X packets getting forwarded, if on Windows) 3) Start netscape from there by netscape & (uses ~delphion/bin/netscape) Patience!! This will take a few minutes to come up. 4) The home page for the CWS delphion userid using Netscape, is already set to http://spn07:180/loading, so you should automatically get the loading tool. 5) Authenticate as delphion/m0nique0. You will have to do this twice - the first time will be to authenticate on spn07, the second time, spn09:81. Again, patience!! After the first authentication, you get the "CD-ROM Collection Maintenance" page from spn07, but it takes another couple of minutes for the second window to come up, the "Jukebox slots maintenance" page from spn09. This requires delphion to be in the internal users file on spn07 (the file /arc/ips/security/users_int.dir & users_int.pag on spn07) belonging to the admin group, as well as in /arc/ips/security/users.dir & users.pag on spn09. As of 12-9-2002, the delphion id was set up correctly in both files. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -