28.12.2013 Views

cheenc03a.pdf

cheenc03a.pdf

cheenc03a.pdf

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

SHAPHER<br />

SHAREZER<br />

but aimorr more probably mmer from Jerahme'eli ; a sam~,nrCnn. -~g?n?, XN, ~.OI~I..N.C~,I mrnrio!.cd<br />

similar origin fur Sh~phathen hecomcl plausible.<br />

in I > jJ%a; jn s: :cu:,a Q < l . ~ i? r ~ i: r.,rde.r.c1 ',~m.ctach').<br />

2. The father of ELlsH.4 [g.~.](I K. 19x6 ~ gt, oa$oO, TIr, I, x.. .. .,.,!1111 .,..,r.,,,rn<br />

.I.eri)m.l AS, t!'s,c#.,t. i;;;r..lr pl uyr;l.rrc, L.: ~hr.i.<br />

#a$., [U us. 19 ; AL]). His residence. Ahel-meholah,<br />

represented here by 2th (n!), 'coulter,' elrewhere rendcred<br />

is usually thought to have been in Issachar. But if the<br />

arrangement in MT is correct, it war when Elijah<br />

'pioughrhnre: @a ndp~~~po~. .. erp;lrlv (e* wanting, BIPL,,-<br />

nip~ov.. ~~piv,<br />

ably he aware (see KINGS [BOOK]. 5 8) that critics<br />

have been inclining to the belief that MTs arrangement<br />

so Ba. Gi., cp Del. CompIuf. Var. 16; '. . . protect<br />

is nut correct, and Kittel. in his commentary(HK1~4),<br />

the king' ; cp NERGAL-SHAREZEX).<br />

I.<br />

giver a blank space between v. r8 and v. ig to indicate<br />

An Assyrian, perhaps n son of Sennacherib, who,<br />

with Adrammelech (perhaps his brother), slew that king<br />

that a section of the narrative has been omitted. The<br />

(z<br />

matter, however, is not so clear as to require no recon-<br />

K. 1937 Is. 3738 ; capocap [BAO], oapooo [LKAQ]).<br />

sideration. We know that Elijah had a<br />

It is urged elsewhere (SENNACHERIB. 9 i), that in the<br />

close conadmittedly<br />

composite narrative<br />

nection with the far S, of Canaan irce PROPHET, 8<br />

of the peril from 'Sen-<br />

"<br />

6). , nacherib' two different invasions have been mined up,<br />

If is plausible. therefore, to suppose that Elirha war<br />

and that parts of the existing narrative relate to the one<br />

originally called, not 'b. Shuphat.' but either ,b.<br />

and parts to the other. The<br />

$Zfath'-ic., a Zephathite, or<br />

one invasion was, it is<br />

' b. Se6thi'-i.e, the<br />

held, the well-known Assyrian invarion of Sennacherib.<br />

son of a Zephathite. In the farmer case Elisha, in the<br />

the other<br />

latter Elisha's father (a<br />

an invasion of a N. Arabian people sometimes<br />

more probable view), was recalled<br />

Arihur, but perhaps more correctly Ashhur (,,n*5).<br />

resented as a man of Zeohath or Zareohath who<br />

iad rstablirhed hinlself at Ahel-meholah-'i.6.. Abel- Whether we can ray that each of the accounts which<br />

jerahmeel (cp MEHOLATHITE). The site of this Jerah- have ken welded together relates solely and entirely to<br />

meelite place (cp r S. 30q) we do not know. The rite one of the two invasions, is doubtful : bur it is at any<br />

of Zeohath (or probably 7~rephath) has probably been rate very possible that the passage 2 K. 1936 f. = Is.<br />

identined : ;ee ZAREPI~AT~.<br />

373,f. refers to the death of the king of the N. Arabian<br />

3. A late dcrcendant of David 1% Ch.S~zt: r [BI Asshur, who was said (xe may reasonably hold) to have<br />

, IALI). . ~. ~h~ orc~umablv . rueKe3ted%v -- SHE: perished in the house of his god Nimrod, by the sword<br />

PY*TI*", I.<br />

,. A Gadite, in Bvhan (I Ch.5x.t: B however [ravcrvl 6<br />

of ' Jerahmeel, u prince of Asrhur' (read ,a?!<br />

yp +.a's i s iB1 [r.va,l & yp. CAI; [,'".".I ! yp. <br />

is an arbitrary . expansion . of ib ij, and Mmti renders the<br />

text the house (i.6.. family) of ElLiarezer (ib SX) rent.'<br />

If however, we are right in explaining REGEM-MELECH<br />

(=Raamiah) as a corruption of Jerahmeel, the question<br />

arises whether im.2 may not be a corruption of<br />

(the N. Arabian Tubai). In this care we can hardly read<br />

4430

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!