16.06.2013 Views

The Bible and the Dead Sea Scrolls: The ... - josephprestonkirk

The Bible and the Dead Sea Scrolls: The ... - josephprestonkirk

The Bible and the Dead Sea Scrolls: The ... - josephprestonkirk

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

104 FORMATION AND RE-FORMATION OF DANIEL<br />

of <strong>the</strong> formative influence of Daniel on <strong>the</strong> language, motifs, <strong>and</strong> ideas<br />

(re)expressed in <strong>the</strong> Qumran texts.<br />

A. PRE-DANIELIC TRADITIONS IN THE SCROLLS<br />

4QPrayer of Nabonidus (4Q242)<br />

Perhaps <strong>the</strong> first source from <strong>the</strong> scrolls to be linked with <strong>the</strong> formative<br />

background of <strong>the</strong> biblical Daniel was this much-discussed fragmentary<br />

manuscript. 5 Already twelve years before <strong>the</strong> first <strong>Dead</strong> <strong>Sea</strong> discoveries,<br />

Wolfram von Soden had advanced a plausible case that <strong>the</strong> stories associated<br />

with Nebuchadnezzar in Daniel 3 <strong>and</strong> 4 actually derive from legends<br />

that had been told about ano<strong>the</strong>r figure, Nabonidus, <strong>the</strong> last ruler<br />

of <strong>the</strong> Neo-Babylonian Empire (556–539 B.C.E.). 6 On <strong>the</strong> basis of a comparison<br />

with Mesopotamian sources, von Soden found good reason to<br />

question <strong>the</strong> note in Dan 5:2, which identifies Nebuchadnezzar as <strong>the</strong><br />

fa<strong>the</strong>r of <strong>the</strong> king Belshazzar. As is well known, <strong>the</strong>re is no evidence that<br />

Nebuchadnezzar ever had a son by that name. <strong>The</strong> name Bel-sharra-usur,<br />

however, does appear in materials relating to Nabonidus. Before his<br />

downfall Nabonidus is known to have been absent from <strong>the</strong> capital<br />

Babylon, residing some ten years in Taiman, Arabia, in <strong>the</strong> south; <strong>and</strong><br />

during this period he left his son, Bel-sharra-usur, in charge of Babylon<br />

as governor. 7 According to <strong>the</strong> Babylonian inscriptions, Nabonidus’s<br />

absence from Babylon, combined with his attempt to introduce <strong>the</strong> cult<br />

of <strong>the</strong> lunar deity Sin from Harran into <strong>the</strong> capital city by force, led to a<br />

perception of him as an irresponsible ruler; among <strong>the</strong> priests of Marduk,<br />

for example, he was portrayed as a “weakling.”<br />

<strong>The</strong> fragmentary text from two columns of 4Q242, first published by<br />

Jozef T. Milik in 1956, 8 refers by name to Nabonidus (written nbny) “king<br />

5. See Jozef T. Milik, “‘Prière de Nabonide’ et autres écrits d’un cycle de Daniel:<br />

Fragments araméens de Qumrân 4,” RB 63 (1956): 407–11.<br />

6. See Wolfram von Soden, “Eine babylonische Volksüberlieferung von Nabonid<br />

in den Danielerzählungen,” ZAW 53 (1935): 81–89.<br />

7. For a recent <strong>and</strong> accessible review of <strong>the</strong> Mesopotamian materials concerning<br />

Nabonidus, see Ida Fröhlich, “Time <strong>and</strong> Times <strong>and</strong> Half a Time”: Historical Consciousness<br />

in <strong>the</strong> Jewish Literature of <strong>the</strong> Persian <strong>and</strong> Hellenistic Eras (JSPSup 19; Sheffield: Sheffield<br />

Academic Press, 1996), 19–43. <strong>The</strong> Babylonian Chronicle about Nabonidus is<br />

printed in English translation in James B. Pritchard, ed., Ancient Near Eastern Texts (3d<br />

ed.; Princeton: Princeton University Press, 1969), 306–11.<br />

8. See n5 (above). For fur<strong>the</strong>r bibliography, see Klaus Beyer, Die aramäischen Texte<br />

vom Toten Meer (Göttingen: V<strong>and</strong>enhoeck & Ruprecht, 1984), 223 (hereafter ATTM);

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

Saved successfully!

Ooh no, something went wrong!