If I list the file using this dictionary item, the data comes out fine.
If I then do a SSELECT of the file BY that dictionary item, I get the errors...usually after a couple of minutes of "thinking". After the SSELECT errors, if I repeat the LIST, I get the following. I replaced the defendant names with the word "Name" in the listing (name actually was displayed). Despite the errors, the program is reading the information from the file. I R confused. LIST DA.CASES DEFENDANT 04:04:07pm 19 Sep 2008 PAGE 1 DA.CASES Defendant..................... Program "CJ.READ.PERSON": Line 31, Read operation failure. [EBADF] Bad file num ber 115758 *** No Defendant *** 57879 *** No Defendant *** 173637 Name 115759 Name 57880 Name Program "CJ.READ.PERSON": Line 31, Read operation failure. [EBADF] Bad file num ber 173638 *** No Defendant *** Program "CJ.READ.PERSON": Line 31, Read operation failure. [EBADF] Bad file num ber 115760 *** No Defendant *** 57881 *** No Defendant *** 173639 Name From: Bessel, Karen Sent: Friday, September 19, 2008 2:27 PM To: 'u2-users@listserver.u2ug.org' Subject: FW: Dictionary Item Problem Some more info.... Along with the errors I sent in the earlier email, I'm occasionally seeing [EBADF] Bad file number The file that is being read on line 31 of this subroutine (where the read operation failure is being generated) is a q-pointer. The file is a multi-level/directory file with a few "sections" - it is a type 3, which I have never seen before. When I select or count this file in the account where the file lives, I get no errors, which leads me to believe that it is not a data issue. The file that is being selected when this error is produced is also a q-pointer to a file in the other (same) account. This is a plain hashed file. From: Bessel, Karen Sent: Friday, September 19, 2008 1:36 PM To: 'u2-users@listserver.u2ug.org' Subject: Dictionary Item Problem Receiving a blink error when SSELECTing BY an I-descriptor that calls a subroutine, which uses COMMONed files that don't seem to be OPEN. Back in the olden days, if you had more errors than the system could process/display, it would result in a backward link or crossing frame limit error. Do you think this might be the same kind of thing? Program "CJ.READ.PERSON": Line 31, Read operation failure. Program "CJ.READ.PER SON": Line 31, Read operation failure. Program "CJ.READ.PERSON": Line 31, Read operation failure. Program "CJ.READ.PERSON": Line 31, Read operation failure. Program "CJ.READ.PERSON": Line 31, Read operation failure. Program "CJ.READ.PER SON": Line 31, Read operation failure. Program "CJ.READ.PERSON": Line 31, Read operation failure. Program "CJ.READ.PERSON": Line 31, Read operation failure. Program "CJ.READ.PERSON": Line 31, Read operation failure. Program "CJ.READ.PER SON": Line 31, Read operation failure. Program "CJ.READ.PERSON": Line 31, Read operation failure. Program "CJ.READ.PERSON": Line 31, Read operation failure. Program "CJ.READ.PERSON": Line 31, Read operation failure. Program "CJ.READ.PER SON": Line 31, Read operation failure. Program "CJ.READ.PERSON": Line 31, Read operation failure. Program "CJ.READ.PERSON": Line 31, Read operation failure. File '/train/jud/cj/PERSONS/SEC': Computed blink of 0x3B9400 does not match expected blink of 0x3B9000! Detected within group starting at address 0x3B9000! Program "CJ.READ.PERSON": Line 39, Internal data error. Line 31 is a read.... This is the dictionary item: 0001: I 0002: IF CASE.PERSON.ID # "" THEN SUBR("CJ.READ.PERSON",CASE.PERSON.ID,1,"") E LSE "" 0003: S;*;"*** No Defendant ***" 0004: Defendant 0005: 30L 0006: S CASE.PERSON.ID is a regular attribute descriptor type dictionary item. Do you have any suggestions? Karen Bessel Software Developer Tyler Technologies, Inc. 6500 International Parkway, Suite 2000 Plano, TX 75093 Phone: 972.713.3770 ext:6227 Fax: 972.713.3777 Email: [EMAIL PROTECTED] Web: http://www.tylertech.com ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/