The sons of Judah Pherez, Hezron, and Carmi, and Hur, and Shobal.
Chapter 4 turns back to Judah a second time. It names men who lived generations apart, and still calls them "sons of Judah." That raises two questions: why Judah comes round again after chapters 2 and 3, and why God kept a family list this loose.
Commentators read the repeat as a change of subject. Chapter 2 traced one family line. Chapter 4 opens out the whole tribe.
Now that God has made known His purposes about His King, the list names the children of the kingdom through the heads and chiefs of families. The tribes come in the appointed order, and the royal tribe of Judah comes first (1 Chron. 4). Judah appeared earlier in 1 Chron. 2 because David belongs to that tribe. There the point is David's genealogy, not the families of Judah. Here in chapter 4 the tribe itself comes first. It has first place as the royal tribe, next in importance to the royal family of David. Most of the great and honoured names of that tribe are connected with his family.
Carmi, Hur and Shobal were not born to Judah. They stand generations below him, and the text still calls them his sons. Here the word means descent, not a direct father-son link.
The list calls Carmi and Hur sons of Judah because they came from him in a direct line. They were clearly not his own sons, and neither was Shobal. Verse 50 of chapter 2 shows that Shobal was at least the great-grandson of Judah's grandson, and Reaiah was his son. So there were at least six generations.
The gaps in these lists say something about the people who came back from captivity.
In Chronicles the accuracy of the genealogies depends largely on how much value the Jews placed on them during their captivity. The disorder these lists show matches the state of the remnant we meet in the books of Ezra and Nehemiah. Quite a number among the people and among the priesthood could not prove their genealogy. They had no heads, yet people could still recognise them by the names of their families, groups and cities. In this way those names became, in effect, a "moral person," recognised as the stem of their ancestry… The great disorder that came in also helps explain why people counted very distant descendants of a clan's head as his sons.
Judah is not just one tribe among many here. The line is heading somewhere.
Judah is then introduced to lead us to the royal race of David, the object also of the promises according to the election of God.
One name in this verse turns up elsewhere in Israel's history. Hur belongs to Caleb's family, and so does a man named later in this chapter.
Two names stand out in 1 Chronicles 2-4. The first is David, for Judah's kingship is, as we have seen, the main subject of Chronicles. The second is Caleb the son of Jephunneh, who stands for the energy and the perseverance of faith. Hur, who plays a large part in Israel's history (Ex. 17:12; Ex. 24:14), is a son of Caleb's (1 Chron. 2:19, 50; 1 Chron. 4:1, 4). Jabez (1 Chron. 4:9-10) is of the same clan.
Commentators differ over which Caleb this is.
There is no proof that Caleb was the son of Hezron, son of Perez. If he was the same Caleb as in Numbers, he was the son of Jephunneh.
A page of names can look like dead paperwork. But God Himself is keeping this record.
At the same time He records the names of those who came through the trials in this history without being blotted out of the book… Not all of Israel is there; and not all who are descended from Israel are Israel.
That truth reaches past Judah to the reader.
There is something deeply sobering about being allowed to read through a record of names that people forgot long ago. God has remembered every one of them, with every detail of their path through this world. One day our own names will be lost to people too, but God will forget neither us nor our ways.
- Repeated — chapter 2 traced David's own line. Chapter 4 sets out the royal tribe itself, first in order.
- Descended — son of Judah here means descendant. Shobal alone stands at least six generations down.
- Damaged — the disorder in these lists matches the people who came back from captivity. Many could no longer prove their descent.
- Directed — for all its gaps, the line runs somewhere: Judah leads to the royal race of David and the promises.
- Remembered — God keeps the names of those who came through the trials. He will forget neither us nor our ways.
And Reaiah the son of Shobal begot Jahath; and Jahath begot Ahumai and Lahad. These are the families of the Zoreathites.
Four names, and then a family: this verse sits inside the second run through the tribe of Judah in 1 Chronicles. It raises the questions every reader of these lists asks. Who were these men, why does the record turn from people to a clan, and why did God keep it?
The closing phrase names a family, and it points back to the Shobal named just before. A dictionary of Bible names gives the descent and the likely reason for the name:
A family descended from Shobal, son of Judah. They were probably given this name because they lived in Zorah. 1 Chr. 4:2. They are called ZAREATHITES in 1 Chr. 2:53.
So the clan took its name from the town where it lived. That town had a history of its own:
A city in the west of Judah, but counted as part of Dan, on the Philistine border. Samson was born there, and he was buried nearby.
Read as a list of four men, the verse tells us almost nothing. Read as a record of families and places, it fits the pattern of this whole section of Chronicles. One commentator sets out the kinds of entries these lists hold, and names this passage among them:
Sometimes the genealogies of Chronicles contain very old names that we do not find anywhere else in the Old Testament. Many names are not the names of people, but of clans or families. Others are family lists we might call geographic. For lack of other material, they include the names of tribes, of districts, of cities. We find this again in 1 Chron. 2:18-24, 25-33, 42-55; 1 Chron. 4:1-23, 28-33.
Verse 1 calls Shobal a son of Judah. Verse 2 calls Reaiah the son of Shobal. Those words do not mean what they would in a modern family tree:
Carmi and Hur are called sons of Judah because they came down from him. They were not his own sons, and neither was Shobal. Verse 50 shows that Shobal was at least the great-grandson of Judah's grandson, and Reaiah was Shobal's son. So there were at least six generations.
Another writer points to who stands behind the shape of these lists:
the genealogies leave out names on purpose, or put them in a different order, to bring out the purpose of the Spirit of God. This is especially true in the book we are studying.
Chapter 2 already went through Judah. Chapter 4 starts again, and the two chapters trace different things:
Now that God has made known His purposes about His King, the record names the children of the kingdom through the heads and chiefs of families. The tribes come in the appointed order, and first is the royal tribe of Judah (1 Chron. 4). Chronicles named Judah earlier, in 1 Chron. 2, because David belongs to that tribe. There the point is not the families of Judah but David's family line. Here in chapter 4 the tribe comes first, holding first place as the royal tribe, next in importance to the royal family of David.
These lists reach forward to one person above all:
Above all, they were essential because of Messiah's kingship. His line had to run back through the series of kings to Judah, "the lawgiver," and then from Judah to Jacob, Isaac, Abraham, Noah, Adam and God!
The nearer use was practical. These lists came to a people who had just returned home and had to know where they belonged:
When they returned, these genealogies would matter enormously to the Israelites. They mattered so that the people would not seize what was not theirs — so that they would not be unjust — so that they would be content with what God had given them — so that they would tie themselves to all that was great and glorious in God's sight in the past. These genealogies counted for a great deal here. In their weakness they needed every cheer and encouragement.
- Recorded names. Scripture keeps Reaiah, Jahath, Ahumai and Lahad as the line running down from Shobal.
- Recorded family. The four names end in a clan, the Zorathites, called Zareathites elsewhere. They took their name from Zorah, a town in western Judah counted as part of Dan.
- Recorded on purpose. "Son of" here can skip generations. The record leaves names out or changes their order to serve the purpose of the Spirit of God.
- Recorded as the royal tribe. Chapter 2 traced David's own line. Chapter 4 traces the families of Judah, the tribe that comes first because the king came from it.
- Recorded for the King, and for the weak. The lists reach forward to Messiah's line. They also steadied those who returned home, so they claimed nothing that was not theirs and rested content with what God gave.
And these [were of] the father of Etam Jizreel, and Jishma, and Jidbash; and the name of their sister was Hazlelponi;
Four names sit in the middle of Judah's family record. Three brothers and a sister, with no story attached to any of them. Most readers reach Chronicles with the same questions. Who were these people? Why does the list pause to name a sister? And why did God keep the record at all?
Chapter 4 returns to a tribe already covered. One writer explains the change of angle between the two passes:
Now that God has made known His purposes about His King, the record names the children of the kingdom through the heads and chiefs of families. It gives the tribes in the appointed order, and the royal tribe of Judah comes first (1 Chron. 4). Chapter 2 mentioned Judah earlier because David belongs to that tribe. The point there was not the families of Judah but David's genealogy. Here in chapter 4 the tribe comes first. It holds first place as the royal tribe, next in importance to the royal family of David.
So the sons of Etam are not stray names. They stand inside the tribe from which the king came.
Manuscripts differ over the wording of this verse, and that changes how the name reads:
A descendant of Judah. 1 Chr. 4:3. The meaning is doubtful. Some manuscripts read "sons of Etam," and others, "sons of the father of Etam." It may refer to the founder of the city named above.
That blurring of person and place runs through this whole section of Chronicles:
Sometimes the genealogies of Chronicles contain names of very ancient origin, which we do not find elsewhere in the Old Testament. Many names are not those of people, but of clans or families. Others are genealogies we might call geographic. For lack of other source material, they include the names of tribes, of districts, of cities… We find these again in 1 Chron. 2:18-24, 25-33, 42-55; 1 Chron. 4:1-23, 28-33.
The verse names three brothers, and then a sister: Hazzelelponi. Women appear often in these chapters. One writer reads that as a mark of when the lists were put together:
Here, as elsewhere in these genealogies, women come up again and again. This is one more proof that these lists date only from after the captivity, from the middle of the disorder that marked Israel's ruin. The female line of descent gave them markers to trace a genealogy back. In normal times no one would have needed such mentions.
So her name is not filler. It could be the marker that led a family back to its own record.
One writer explains why names like these were worth guarding:
Chronicles comes from the time after the captivity, when everything had fallen into disorder. The destruction had left the Jews disheartened, and they never would believe in it till it came. They might have thought, "What is the use of a genealogy? Why care now about our lands or houses? Everything is ruined. All is gone." But the man who believed God knew that in seventy years they would return from their captivity. So care for God and confidence in His Word would make them guard their genealogies closely. Then, when they did return, they could enter into the portion God had allotted them. For this was what made every homestead in Israel so precious — that it was God who gave it.
So keeping the name of Etam's family was an act of faith. God had given the land, and He would give it back.
The same writer is honest about how these pages are usually treated:
I have no doubt that most of us have read these genealogies, thinking it was high time to skip over them… But I am quite sure that very few people, in comparison, have a clear, definite judgment as to why God has attached so much importance to these genealogies.
And the lasting comfort in a verse like this lies in the simple fact that the names were kept:
There is something deeply solemn about being allowed to go over such a record of names. Man forgot them long ago, but God has remembered every one of them, with every detail of their pathway through this world. Some day our names likewise will be lost to mankind, but neither we nor our ways will be forgotten by God.
- Placed. These four names belong to Judah, the royal tribe, set first in the list because of the King who came from it.
- Disputed. Manuscripts differ between "sons of Etam" and "sons of the father of Etam." Many names here are clans and towns, not people.
- Included. Hazzelelponi has her name in the record, and the female line could supply the markers that traced a family back.
- Guarded. Guarding a genealogy was faith that God would bring His people back to the land He had given them.
- Remembered. People forget these names. God has not forgotten one of them, or any detail of their path — and He will not forget ours.
and Penuel the father of Gedor, and Ezer the father of Hushah these were the sons of Hur, the firstborn of Ephratah, [and] father of Bethlehem.
Chronicles opens with nine chapters of names, and this verse sits deep inside Judah's family line: a few men, a town, and the town's older name. Why did a scattered people keep such a list, and why did God keep it?
The phrase may not mean what it sounds like. Here the title may point to rank, not to fatherhood.
In 1 Chronicles 2:51, 54 and 4:4, "father of Bethlehem" may mean "prince of Bethlehem." The town is Beit Lahm today, six miles south of Jerusalem, on a narrow ridge that runs out from the central range of hills.
Ephrathah is what Bethlehem used to be called, and the prophet Micah reached back for that older name.
Micah used a different name for the town in Judah. He prophesied that out of "Bethlehem Ephrathah," though it was "too little to be among the clans of Judah," would come the One who would be the Judge and Ruler of Israel (Micah 5:1-2). Ephrath or Ephrathah was Bethlehem's ancient name (Gen. 35:16, 19; 48:7). The town bore it when Rachel, the mother of Joseph and Benjamin, died.
The name carries a meaning of its own, and the promise tied to the town later brought Herod's sword there.
In one place it is called Bethlehem Ephrathah, that is, "the fruitful," because the ruler of Israel was to come from there. Micah 5:2; Luke 2:4, 15; John 7:42. This led Herod to massacre the infants. Matt. 2:16-18.
Commentators link the Hur named here to Caleb's family, and to a man who appears at two key moments in Israel's story.
Two names stand out in 1 Chronicles 2-4. First, David, for Judah's kingship is the main subject of Chronicles, as we have seen. Then Caleb the son of Jephunneh, who stands for the energy and perseverance of faith. Hur, who plays a large part in Israel's history (Ex. 17:12; 24:14), is a son of Caleb's (1 Chron. 2:19, 50; 4:1, 4).
One of those moments explains why he is worth noticing. Hur helped hold up Moses' hands, and one writer reads both helpers as pictures of something greater.
No one man could be a perfect picture of Christ. Moses' hands were heavy, so Aaron and Hur held them up. This only brings out more clearly the truth of the intercession of Christ. Aaron, though not yet set apart for the office, represents the priesthood, and Hur, if the meaning of his name may guide us, stands for light or purity. Together, then, they mean the priestly intercession of Christ kept in holiness before God — an intercession that always works and always prevails, because it rests on all that Christ is and has done.
These chapters skip generations, repeat names, and sometimes put a town where a person should stand. One writer traces that disorder back to the state of the people who kept the records.
In Chronicles the accuracy of the genealogies depends largely on how much the Jews valued them during their captivity. The disorder in them matches the state of the remnant we meet in the books of Ezra and Nehemiah. Many among the people and among the priests could not prove their line. They had no family head left, yet the names of their families, groups, and cities still marked them out. Such a name became, in effect, a "moral person," standing as the stem of their ancestry (see Ezra 1, and here 1 Chron. 2:50, 54-55; 4:4).
Some conclude from the gaps that the book is worthless as history. The same writer answers that charge head-on.
Must we conclude from all this that Chronicles is a human, random compilation, and that the book has no historical value at all? That is what those who trust human reason alone claim. But thank God, their reasoning is always at fault when it attacks His Word. No thoughtful Christian will deny that the genealogies of Chronicles are made up of fragments gathered while everything was in confusion. They are still documents on which God sets His seal of approval.
Holding on to a family record far from home looked pointless. That is what made keeping it an act of trust.
These genealogies were imperfect. Israel's condition carried the mark of the ruin that had fallen on them, but also the mark of God's goodness. He had brought back a remnant, and He had preserved all that was needed to place them in the record of His people. These genealogies served as a way to recognise the people. Happy the man who had kept his own, and who valued the heritage of Jehovah enough to treasure it! It was a proof of faith. Someone might have asked, "What use are these genealogies in Babylon?"
- Title — "father of Bethlehem" may mark Hur out as prince of the town, not just as an ancestor of its people.
- Name — Ephrathah, "the fruitful," was Bethlehem's older name, and Micah used it when he foretold the Ruler who would come from there.
- Man — Hur belongs to Caleb's line, and to the pair who held up Moses' hands: a picture of priesthood and purity.
- Fragments — the gaps in these lists match the broken state of the returned people, yet God sets His seal of approval on them.
- Faith — keeping such a record in Babylon looked useless, and that is what made it proof of faith.
-- And Ashhur the father of Tekoa had two wives, Helah and Naarah.
One line of a long family list names a man, the town that carried his name, and his two wives. Why does Scripture slow down for something so ordinary? And why here, in the family record of Judah?
Judah has already appeared in the earlier chapters. One writer notes that this second pass has a different aim:
Chapter 4 begins a new section, though we have had Judah before. This is another feature peculiar to Chronicles. It repeats things even where nothing is complete, but it never repeats for no reason. The earlier section brings in Judah so that David and the royal line can follow. Here Judah comes forward because he is a leader among the tribes of Israel.
So Ashhur is not a link in the chain to the throne. He is one household inside the leading tribe — which is why the record has room for his wives and sons.
One dictionary entry sums up the whole man in a single line:
Son of Hezron and father of Tekoa. 1 Chr. 2:24; 1 Chr. 4:5.
"Father of Tekoa" likely means the founder of a town, not the parent of a boy. The town's history grew far larger than the man's:
A city of Judah, probably founded by the man just named. Rehoboam built or fortified it "for defence" (2 Chr. 11:6). The "wise woman" whom Joab sent to speak to the king about bringing Absalom back came from this city (2 Sam. 14:2, 4, 9). It stood on a hill, so it was a good place to blow the trumpet in time of danger, as in Jer. 6:1. The prophet Amos was among its herdsmen.
Women seldom appear in these lists. When one does, there is a reason:
It was very unusual for women's names to appear in a genealogy. They might be needed as links in the chain of descent — for example, where a man had different wives and the record had to show which wife a title came through.
That is why the verses just after this one keep each wife's sons separate. But two wives is a departure from what God set up at the start. The same writer traces where that order first broke, and how God treated the families that broke it:
All this shows what God set up for marriage: the union of one man and one woman, the two and only two, becoming one. Anything more than this is not of God, but comes from human lust. Lamech, the sixth from Adam, was the first to break this order, and he had two wives. Long after this, Jacob's two wives gave their servants to him, so that he had four wives. God counted the twelve sons of these four women equally as sons of Jacob, and they became the heads of the twelve tribes. It might have been thought that God would not bless the children of these unions, but He did.
Names like Helah and Naarah appear nowhere else. That is the point:
There is something deeply solemn about being allowed to read such a record. People forgot these names long ago, yet God has remembered every one of them, with every detail of their path through this world. Some day our names too will be lost to people, but God will never forget us or our ways.
Chronicles was put together after the kingdom fell. Its first readers had come home from exile with almost nothing:
It is all the more striking to find in Chronicles the picture of grace at work in the heart of man, because these books were written, as we have seen, after the final ruin of the people and of kingdom rule. But what comfort for the poor remnant, back from Babylon in servitude and contempt, to find their own history here, written in those disastrous times by the Spirit of God Himself. Every page shows that no unfaithfulness on the part of the people could change God's counsels or alter the grace by which He would establish His eternal purposes for His people in the person of Christ.
So a man back from exile could find his own town and his own family line still held in God's memory.
- Place. Chapter 4 returns to Judah as one tribe among many, not as the road to David's throne. That is why small households like Ashhur's get space.
- Name. Ashhur was a son of Hezron and "father of Tekoa." Rehoboam later fortified that town. It was home to the wise woman who spoke to the king about Absalom, and to the prophet Amos.
- Household. Both wives are named because a title had to be traced through the right mother. God set marriage up as one man and one woman. Lamech broke that order first — yet God still owned the sons born in such homes.
- Remembered. People forgot these names long ago. God remembers every one — and He will not forget us or our ways either.
- Grace. Written after the kingdom fell, these lists told a broken remnant one thing: no failure of theirs could change God's counsels or stop His grace moving toward Christ.
And Naarah bore him Ahuzzam, and Hepher, and Temeni, and Ahashtari these were the sons of Naarah.
Naarah was one of Ashhur's two wives, and this verse names her four sons as Chronicles works through Judah's family tree a second time. Ahuzzam, Hepher, Temeni and Haahashtari come with no story attached, which raises an honest question: why does God keep a record like this?
Chapter 4 does not repeat chapter 2 by accident. The earlier list traced one family; this one opens out to the whole tribe.
Now that God has made known His purposes about His King, He names the children of the kingdom through the heads and chiefs of their families. The tribes come in the order God appointed, and the royal tribe of Judah comes first (1 Chron. 4). Judah was mentioned before in 1 Chron. 2, because David comes from that tribe. There the point is David's genealogy, not the families of Judah. Here in chapter 4 the tribe comes first. It has first place as the royal tribe, next in importance to David's royal family.
Read these lists as a simple father-to-son chain and you will get lost.
Sometimes the genealogies of Chronicles hold very old names that we find nowhere else in the Old Testament. Many names are not people at all, but clans or families. Other lists we might call geographic. For lack of any other source, they give us the names of tribes, of districts, of cities. We find this again in 1 Chron. 2:18-24, 25-33, 42-55; 1 Chron. 4:1-23, 28-33.
Ashhur himself, the father of these four sons, illustrates the overlap. A reference work built from the Bible's own usage notes that Tekoa, named alongside him, is:
Son of Ashur, or a city founded by Ashur, a descendant of Judah. 1 Chr. 2:24; 1 Chr. 4:5.
The date of the book changes how this list reads.
It is all the more striking to find in Chronicles this picture of grace at work in the heart of man, because these books were written, as we have seen, after the final ruin of the people and of the kingdom. But what comfort for the poor remnant, back from Babylon in servitude and contempt, to find their history here! The Spirit of God Himself wrote it in those disastrous times. It shows on every page that no unfaithfulness of the people could change God's plans, or alter the grace by which He would establish His eternal purposes for His people in the person of Christ.
For the people coming home, a name in a list was not trivia. It decided where a family could settle.
The Jews would not believe the destruction was coming until it came, and it left them disheartened. They might have thought, "What is the use of a genealogy? Why care now about our lands or houses? Everything is ruined. All is gone." But the man who believed God knew that in seventy years they would return from captivity. So care for God and confidence in His Word made them guard their genealogies closely. Then, when they did return, they could enter on the portion God had allotted them. This is what made every home in Israel so precious — God Himself gave it. A man did not earn it by his own labour or skill. It was the gift of God to them.
The objection is old: what could anyone learn from a string of names?
What are we to learn from these genealogical records? We believe they teach us a precious lesson about the Lord's faithful care of His people Israel, and about His loving interest in them and in everything that concerns them. He watches over them, from generation to generation, even though they are scattered and lost to human view. He knows all about "the twelve tribes," and in due time He will bring them out into the open. He will plant them in the inheritance He destined for them, in the land of Canaan, as He promised Abraham, Isaac and Jacob.
The four sons of Naarah are one link in a chain with a destination.
The object of the Holy Spirit in Chronicles is not history, except as a secondary thing, but the bringing in of the Son who is to reign over all. Christ the Son will not only be King of the Jews as Son of David, and the Heir of the promises as Son of Abraham; as Son of Man He will be King of kings and Lord of lords. Other names come in and shine among their fellows, and side purposes are reached along the way, but the great purpose of God centres in His Son. The genealogy points to Him.
- Recorded. God keeps four unknown sons of Naarah on record. He watches over His people from generation to generation, even when they are scattered and lost to human sight.
- Royal. These names sit in Judah. Chapter 4 puts that tribe first because it is the royal tribe, next in importance to David's own family.
- Read carefully. Many names in these lists are clans, districts or cities, not people — one name can stand for a family or a town.
- Restored. Chronicles came after the nation collapsed. It showed a despised remnant that no unfaithfulness could alter God's grace or His purposes.
- Reaching Christ. Names shine along the way, but the line has one centre: the genealogy points to God's Son.
And the sons of Helah Zereth, and Zohar, and Ethnan.
Verse 7 is three names inside a list: the sons of Helah, one of the two wives of Ashhur, whose family fills verses 5–8. Two verses later the same chapter slows down for the prayer of a man named Jabez. So why did God keep these plainer names at all?
These three men belong to Judah's line through their father. Translations differ over the second name: some read Izhar, others Zohar. A reference work identifies the first of them:
Zereth. Son of Ashur, a descendant of Judah. 1 Chr. 4:7.
The same work links their father Ashhur to Hezron before him and to Tekoa after him:
Ashur. Son of Hezron and father of Tekoa. 1 Chr. 2:24; 1 Chr. 4:5.
The chapter is not a random file of names. It follows an order, and the order is about the kingdom:
God has now made known His purposes about His King. So the record names the children of the kingdom through the heads and chiefs of their families. The tribes come in the appointed order, and first is the royal tribe of Judah (1 Chron. 4). Judah came up earlier in 1 Chron. 2, because David belongs to that tribe. The point there was David's genealogy, not the families of Judah. Here in chapter 4 the tribe itself comes first. It holds first place as the royal tribe, second in importance only to David's royal family.
So Zereth, Izhar and Ethnan appear here because they belong to the royal tribe.
One writer explains what these lists meant to a people who had lost everything:
The genealogies became so important because the books of Chronicles were written after the captivity, when everything was thrown into disorder. The Jews had never been willing to believe the destruction would come, and when it came they lost heart. They might have thought, "What use is a genealogy? Why care now about our lands or houses? Everything is ruined. All is gone." But the man who believed God knew that in seventy years they would return from their captivity. So care for God and confidence in His Word made them guard their genealogies closely, in order that, when they did return, they might take up the portion God had given them. This is what made every home in Israel so precious: God gave it. It was not something a man earned by his own work or skill. It was God's gift to them.
So the three names in verse 7 were not filler. They were a claim on land waiting for the exiles at home.
Nobody today knows anything about Zereth, Izhar or Ethnan beyond this single line. That is where the comfort lies:
It deeply sobers the soul to be allowed to read through such a record of names. Men forgot these names long ago, but God has remembered every one of them, with every detail of their path through this world. Some day our own names will be lost to mankind too, but God will not forget us or our ways.
Two verses later, one man in the same chapter stands out from his brothers:
"Jabez was more honorable than his brothers." Is this a hint that his brothers had forgotten that God was the Giver of their good things? Here the record does not say they prayed, and they have no such answer. God grants Jabez what he asked for. Among that rebellious and stubborn people there were men of faith, and Jabez was one.
Verse 7 is the plain background for that one prayer. The brothers get a name; Jabez gets an answer.
The whole register runs back to the first man, and that shapes how we read every entry in it:
Chronicles opens with the genealogies of the children of Israel, tracing the chosen race right back to Adam. The record begins with his name, and as far as nature goes, every name that follows is only one more addition to the first man. "The second man is from heaven." … all through these lists, which God chose to preserve and which will be kept on high forever, we see in one person after another the fruit of the new life, shown to the glory of Him who gave it.
Note: older translations read "the second man is the Lord from heaven."
- Named. Zereth, Izhar and Ethnan are the sons of Helah, in Ashhur's line in Judah; Ashhur was son of Hezron and father of Tekoa.
- Placed. They stand in the royal tribe, which Chronicles names first as it traces God's purpose about His King.
- Kept. Faith guarded the list through the captivity, because a name in it was a claim on land God had given, not on anything earned.
- Remembered. Men forget these names; God remembers each one, with every detail of their path — and He will not forget ours.
- Answered. Two verses on, Jabez asks and God grants his request; the record never says his brothers prayed, and they receive no answer.
And Koz begot Anub, and Hazzobebah, and the families of Aharhel the son of Harum.
This verse sits in the middle of Judah's family record, and it gives little more than a short string of names with no stories attached. So why does God keep a record of people we know nothing else about?
Judah's line was already traced earlier in Chronicles. One writer explains why it is taken up again here:
after_note: DELETE
Now that God has made known His purposes about His King, the record names the children of the kingdom through the heads and chiefs of families. The tribes come in their appointed order, and the royal tribe of Judah comes first (1 Chronicles 4). Judah appeared earlier, in 1 Chronicles 2, because David belongs to that tribe. There the point is David's own line, not the families of Judah. Here in chapter 4 the tribe comes first. It holds first place as the royal tribe, next in importance to David's royal family.
The verse ends not with a son but with "the clans of Aharhel." One writer notes that these lists hold more than one kind of name:
Sometimes the genealogies of Chronicles hold very old names that we find nowhere else in the Old Testament. Many of the names are not people at all, but clans or families. Other lists are what we might call geographic. For lack of any other material, they include the names of tribes, of districts, and of cities. We meet this again in 1 Chronicles 2:18-24, 25-33, 42-55 and 1 Chronicles 4:1-23, 28-33.
A reference work gives all that is known of Aharhel, along with a different reading of his name:
Son of Harum, of the tribe of Judah. 1 Chronicles 4:8. The old Greek translation of the Old Testament has Rechab, the son of Jarin.
Chronicles comes from the years after the exile and the return. At that point a family record looked worthless, and that is what made keeping one an act of faith:
The books of Chronicles come from the time after the captivity, when everything had fallen into disorder. That is why the genealogies mattered so much. The Jews were crushed by a ruin they refused to believe until it came. They might have thought, "What use is a genealogy? Why care now about our lands or our houses? Everything is ruined. All is gone." But the man who believed God knew that seventy years would see them come back from their captivity. So care for God and confidence in His Word made them guard their family records, so that when they did return they could take up the portion God had given them. This is what made every home in Israel so precious: God gave it. It was not just something a man earned by his own work or skill. It was the gift of God to them.
The chapter leaves out far more names than it records. One writer takes that as the clue to why names like Koz and Anub are kept at all:
The tables do not give every name; many are left out. That shows at once what these long lists of names are for. The record keeps only those who had a part in accomplishing the purpose of God, the channels God chose for carrying out His purpose. There are many lessons to gather from these genealogies, which people so often think unprofitable. Even those opening chapters of Chronicles come under the statement of 2 Timothy 3:16: "All Scripture is breathed out by God and profitable for teaching, for reproof, for correction, and for training in righteousness."
One writer draws the lesson of these lists: God keeps track of people no human eye can follow:
As for what we are to learn from these genealogical records, we believe they teach us a most precious lesson about Jehovah's faithful care of His people Israel, and His loving interest in them and in all that concerns them. He watches over them, from generation to generation, even though they are scattered and lost to human view. He knows all about "the twelve tribes." He will bring them to light at the right time, and plant them in the inheritance meant for them, in the land of Canaan, just as He promised Abraham, Isaac and Jacob.
- Purpose — Chronicles keeps the names tied to God's purpose. The many left out show a chosen record, not a complete one.
- Place — Judah stands first here as the royal tribe, so even its small families stand close to the promised King.
- Persons — Some entries are men, others are clans or places. That is why the verse ends with families, not one son.
- Proof — Keeping a family record in exile looked useless. Doing it anyway was faith that God would bring His people home.
- Preserved — God tracked what no human eye could follow. That is why these lists are still profitable for teaching today.
And Jabez was more honoured than his brethren; and his mother called his name Jabez, saying, Because I bore him with pain.
In a long list of names in Judah's family line, one man gets praise no one else receives. His mother had named him after the pain of his birth, so the name Scripture honours is a name of sorrow.
Chronicles is mostly a list of names. One writer values the short notes tucked among them.
It is sweet and helpful to the soul to trace out the brief notes of what divine grace had done in one person and another. If this were only a human book, such notes would seem out of place among long lists of names. These were people who walked their often lowly paths, with faith at work and the conscience active. The passage about Jabez is of this kind. He was more honourable than his brothers because he set the Lord before him.
The mother's words explain the name. One commentator reads her choice as an act of faith — she owned the sentence God pronounced in Eden and passed its memory on in her son's name.
Jabez's mother had borne him with sorrow and had named him Jabez: "Sorrow." She had herself experienced the consequences of sin. She acknowledged the curse that followed for man, God's righteous sentence on the woman whom the serpent had deceived. For God had said, "I will surely multiply your pain in childbearing; in pain you shall bring forth children" (Gen. 3:16). Jabez's mother accepted this sentence by faith. She made so little effort to escape it that she passed it on to her son, giving him the name "Sorrow." On man's side the fall destroyed all hope of happiness, and sorrow was his fatal portion.
His name means pain, yet the verse calls him honourable. One writer asks where that honour came from.
The very first words about Jabez are, "Jabez was more honorable than his brothers." The Spirit of God leaves us in no doubt about the reason for this praise from God. His name means "sorrowful," or "causing pain." So the reason he was more honourable than his brothers had nothing to do with what he was by nature. He was more honourable than his brothers because of his dealings with God.
One writer looks at another man Scripture calls honourable, and finds the same quality there.
When David was fleeing from Saul, Ahimelech the priest fed David and his followers. The priest also spoke up for David, saying to Saul, "And who among all your servants is so faithful as David, who is the king's son-in-law, and captain over your bodyguard, and honored in your house?" It seems to me that in David faithfulness was a mark that showed he was honourable... Yes, that is what it means to be honourable: to be faithful to God, faithful to the saints in relation to the truth, faithful to what you know.
Why were the brothers not honoured too? One writer answers with a question of his own.
"Jabez was more honorable than his brothers." Is this a hint that his brothers had forgotten that God was the Giver of their good things? Here the record does not say that they prayed, and they have no such answer. God grants Jabez what he requested. Among that rebellious and stiff-necked people there were men of faith, and Jabez was one.
Who was Jabez, and where did he come from? One writer notes that the chapter never links him to Judah by birth.
No connecting link is given in chapter 4 to show that he was born of Judah, yet his name appears in the middle of that family register. Was the land the Lord enlarged in answer to his prayer named after him? If so, 1 Chronicles 2:55 supports the idea that he belonged to the Kenites. They were the descendants of Hobab, who came with Israel at Moses' express invitation, and their children lived among the people of Judah. A Kenite could not claim a portion in Israel on the ground that he was of Israel; yet he might call on the God of Israel, and ask to be blessed with Israel.
By now the kingdom lay in ruins. One writer shows what God still did then.
Wherever there has been faith, God has blessed His people individually. Jabez, the son of affliction, seeking blessing in the presence of the God of Israel, did not fail to find it... So the power of the king was gone, and the order of the kingdom with it. Yet wherever there was faith, God blessed those of His people who trusted in Him.
- Sorrow named. His mother accepted the pain of Genesis 3 and wrote it into her son's name. His story starts with the curse admitted, not avoided.
- Sorrow turned. His honour came from his dealings with God, not from his birth or his name.
- Honour defined. David shows what the word holds: faithfulness to God, to the saints, and to what you already know.
- Honour tested. The record does not say his brothers prayed, and they receive no answer. The difference in the list was who called on God.
- Honour recorded. When the kingdom lay in ruins, God still blessed faith one person at a time — and kept one man's name in the record.
And Jabez called on the God of Israel saying, Oh that thou wouldest richly bless me, and enlarge my border, and that thy hand might be with me, and that thou wouldest keep me from evil, that it may not grieve me! And God brought about what he had requested.
A single prayer breaks into the long family lists of Chronicles, and it comes from a man whose name means sorrow. He asks God for four things, and receives all four.
Chronicles lists a people under God's condemnation.
What has been preserved here of the genealogies of the people is a moving remnant, through grace, of those who had fallen under a sad condemnation. It shows us something else: wherever there has been faith, God has blessed His people as individuals. Jabez, the son of affliction, seeking blessing in the presence of the God of Israel, did not fail to find it.
His name appears with no link to the family around it. So who was he, and on what ground could he ask?
Chapter 4 gives no link to show that he was born of Judah. His name simply appears in the middle of Judah's family register. Was that border, which the LORD enlarged in answer to his prayer, named after him? If so, 1 Chronicles 2:55 supports the impression that he belonged to the family of the Kenites, who came with Israel at Moses' invitation and lived among the people of Judah. A Kenite could not claim a share in Israel on the ground that he was of Israel. Yet he might call on the God of Israel, and ask to be blessed with Israel.
Jabez took the curse of sin as a settled fact, and prayed on that ground.
Jabez began with this conviction, and so he was "more honourable than his brothers." Then he "called on the God of Israel." He knew that only the LORD could deliver him from the curse of sin. He knew, moreover, that this deliverance could be so complete that he, Jabez, would be able to be without sorrow!
The first request goes back to the curse itself.
God had cursed man and the earth from which he was taken (Genesis 3:17). He alone could cancel this sentence and replace it with blessing, the first proof that sorrow has ended... "I will bless you," the LORD had said to Abraham. When everything is in ruin, Jabez' faith goes back to the counsels of grace and to the promises of God... In the same way, God has abolished all the consequences of sin through Christ's sacrifice. So we can be blessed in Him with every spiritual blessing in the heavenly places.
He asked for more ground when the nation had taken little.
Here and there these genealogies highlight people whose borders God extended in the promised land. At that time most of the people had failed to conquer their inheritance... So it is with us: our spiritual borders expand in the heavenly sphere while we are on earth. To reach this we must recognise our hopeless ruin. We have shown that we cannot extend our borders ourselves. So we must show humble dependence that relies on the grace of God alone to possess them.
Asking for enlargement is not asking for oneself alone.
"Oh, that you would bless me indeed!" I wish that were our prayer all the time, wanting to receive blessing from God. Why? Just for our own personal advancement? No, first for our encouragement and strengthening, so that we can then be of help to others, because if we have blessing in our souls it is bound to flow out to others.
The third request names the power he counted on.
He does not rely on his natural energy to enlarge his borders, but rather on the power of God. This is all the more striking since he came from a family known for its energy.
The fourth request assumes evil is still here. (The ESV reads "harm"; older translations read "evil.")
The evil that brought sorrow into this world has not disappeared; it is always present. Jabez knows this well, for he does not ask that it be removed, but he wants to be kept from the evil whose existence he sees. Here again, he recognises that it is not his will, but the power of God alone that is able to keep him.
Frank Wallace turns the test to our own sin.
How easy it is to point the finger at someone else and be grieved because they have said or done something wrong! And how easy it is to forget our own failures. Are we grieved when we sin, when we fail? It is a mark of a tender conscience.
So what became of the sorrow in his name?
How could sorrow still remain in the heart of this man of God when God had granted all his requests? No doubt sorrow has not disappeared from the earth, and neither has the evil that caused it. But Jabez' heart was full of the excellent things granted to him, so it had no room for sorrow.
- Sorrow — He carried a name meaning pain, and made that starting point the reason to depend wholly on the LORD.
- Call — He had no claim by birth, yet he could call on the God of Israel and ask to be blessed with Israel.
- Blessing — He asked God to undo the curse. Commentators link this to every spiritual blessing we now have in Christ.
- Border — God enlarges those who first admit they cannot enlarge themselves.
- Kept — He asked not for evil's removal but for God's hand to keep him from it; God granted it all, leaving no room for sorrow.
And Chelub the brother of Shuah begot Mehir, who was the father of Eshton.
This verse gives four names and nothing more — no story, no deed, no explanation. Why did the Spirit of God preserve names like these, and what can a reader do with them?
Most readers skim a verse like this. One writer admits doing the same, then points to what was at work behind these lists.
In Israel there were sad failures, and failures in the best of men. Still, for all that, something truly divine was at work in that poor people from the beginning onward. So we can see that these genealogies had a character far higher than might appear at first sight. I have no doubt that most of us have read them thinking it was high time to skip over them. Few of us have a clear, settled judgment why God has attached so much importance to them.
This chapter mixes famous men with men we would otherwise never have heard of. Both kinds are there on purpose.
Our chapter deals with the genealogies of the tribes of Judah and Simeon. It brings before us some who were well known in Israel, such as Caleb, who brought back a good report from the land. God allowed him, along with Joshua, to enter the promised land. Others, like Jabez, have no mention in Scripture outside this book. Yet God has put their names in the divine record, to teach us what He values in His people, and what should occupy us as the people of God.
The same writer takes the Chelub of this verse to be the Caleb named a few lines later, and draws a lesson from him about the inheritance God gives.
In verse 11 of our chapter we have Chelub, who is the Caleb of verse 15. In Numbers 13 we read of him: "But Caleb quieted the people before Moses and said, 'Let us go up at once and occupy it, for we are well able to overcome it.'"... These devoted men teach us valuable lessons about the inheritance of God. We are not only to prize God's inheritance; we are to possess it; we are even now to lay hold of what soon shall be fully ours with Christ. By the Spirit we can enter into the spiritual reality of what is ours in Christ.
"Fathered" here need not mean the next generation. One writer says the lists in Chronicles were never meant to be complete chains.
The idea that genealogies give all the steps has no foundation, and in Chronicles they are only a gathering up of memorials.
For the first readers, a name in these lists was the claim to a God-given portion of land.
The books of Chronicles were written after the captivity, when everything was thrown into disorder. The Jews would never believe the ruin was coming until it came, and now they were disheartened. They might have thought, "What is the use of a genealogy? What is the use of caring now about our lands or houses? Everything is ruined. All is gone." But the man who believed God knew that seventy years would see them return from their captivity. So care for God and confidence in His Word would make them guard their genealogies closely, so that when they did return they might enter on the allotment of God. For this was what made every homestead in Israel so precious — that it was God who gave it. It was not just something a man earned by his own labour or skill. It was the gift of God to them.
Names like Chelub's are not the point of the list; they are steps in it. The line has one destination.
In Chronicles the Holy Spirit's object is not history, except as a side matter. It is the bringing in of the Son Who is to reign over all. Christ the Son will not only be the King of the Jews as Son of David, and the Inheritor of the promises as Son of Abraham; as Son of man He will be King of kings and Lord of lords. So His genealogy runs down from Adam, that He, the last Adam, should win back the headship over the lower creation which the first Adam lost. Other names come in and shine among their fellows, and side purposes are served along the way, but the great purpose of God centres in His Son. The genealogy points to Him.
- Recorded — Names with no story attached still stand in the divine record. They show what God values in His people.
- Remembered — Men known nowhere else in Scripture stand here beside famous ones like Caleb. Being unknown is not being forgotten.
- Incomplete — Chronicles gathers up memorials instead of listing every link. So "fathered" can skip generations.
- Restored — A ruined people guarded these lists so they could return to the allotment of God. Every homestead was precious because God gave it.
- Christ — Many names shine here, but God's purpose centres in His Son. The line runs down to Him.
And Eshton begot Bethrapha, and Paseah, and Tehinnah the father of the city of Nahash these were the men of Rechah.
One line in Judah's family record gives us a handful of obscure names, a place called Ir-nahash, and a group called "the men of Recah." Why would God give a verse of Scripture to names no one remembers?
The chapter is not starting a new subject. It goes back over ground already covered. Commentators point out the two names it turns on.
Verses 1 to 23 take up the family line of Judah for the second time. Two names stand out in 1 Chronicles 2-4. The first is David, because Judah's kingship is, as we have seen, the main subject of Chronicles. The second is Caleb the son of Jephunneh, who stands for the energy and the perseverance of faith.
Judah stands first here for a reason. It is not the reason that put Judah first in chapter 2.
Now that God has made His purposes about His King known, the children of the kingdom are named through the heads and chiefs of families. The tribes come in the appointed order, first the royal tribe of Judah (1 Chron. 4). Judah was mentioned earlier in 1 Chron. 2 because David is of that tribe: the point there is not the families of Judah, but David's own line. Here in chapter 4 the tribe comes first, holding first place as the royal tribe, next in importance to the royal family of David. Most of the great and honoured names of that tribe are connected with his family.
In these lists "father of" does not always mean the father of a child. Some of these lists are drawn as much on a map as on a family tree.
Sometimes the family lists in Chronicles hold very ancient names that we do not find anywhere else in the Old Testament. Many names are not those of people, but of clans or families. Other lists we might call geographic: for lack of any other source material, they include the names of tribes, of districts, of cities.
Readers take Ir-nahash two ways. The difference is a son or a settlement.
Son of Tehinnah, 1 Chr. 4:12; or, as suggested in the margin, "Tehinnah, founder of the city of Nahash."
Of the first name in the verse, one reference work says only this:
Obscure name in the genealogy of Judah. 1 Chr. 4:12.
One writer admits how most readers treat these pages, and then asks what they are for.
So we can see that these family lists have a far higher character than they seem to have at first sight. I have no doubt that most of us have read them and thought it was high time to skip over them. I have no doubt we have often wondered why they were ever written at all, and why they should be in the Bible... But I am sure that relatively few people have a clear, distinct judgment about why God has attached so much importance to these lists.
One writer draws out what hung on these records.
These genealogies were imperfect. The state of Israel carried the mark of the ruin that had come on them, but also the mark of the goodness of God, who had brought back a remnant and had preserved all that was needed to place them in the record of His people. If the proof needed to give them that title was missing, those who belonged to the people stopped enjoying their proper privileges, and the priests their place as priests, until a priest stood up with Urim and with Thummim. These records served as a way to recognise the people. Happy is the one who had kept his own, and who valued the inheritance of Jehovah enough to prize it! It was a proof of faith, for it might have been said, What use are these genealogies in Babylon?
One writer puts the highest use of these records last.
Last of all, and above all, they were essential for Messiah's kingship, for His line must go back through the series of kings to Judah "the lawgiver," and then from Judah to Jacob, Isaac, Abraham, Noah, Adam and God!
- Recorded. Beth-rapha, Paseah and Tehinnah are obscure names, and commentators claim no more than the text says. Yet these lists carry a higher character than a first glance suggests.
- Read with care. Many names in these chapters belong to clans, districts and cities, not to people. Ir-nahash may be a city Tehinnah founded, not a son he fathered.
- Retained. In Babylon a family record looked useless. Keeping one proved faith and showed that a man valued the inheritance God had given.
- Royal. Chapter 4 lists Judah's families because Judah is the royal tribe. Chapter 2 traced Judah only as far as David.
- Reaching Christ. Above every other use, the record had to carry Messiah's line back through the kings to Judah, and on to Adam and God.
-- And the sons of Kenaz Othniel and Seraiah; and the sons of Othniel Hathath.
This verse is little more than a family list: a father, two sons and two grandsons, dropped into Judah's long register. Yet one name here, Othniel, belongs to a man Scripture tells us much more about — so why does Chronicles keep the bare names at all?
Othniel appears here only as a son of Kenaz, but the rest of Scripture fills the outline in.
Son of Kenaz, brother or nephew of Caleb. He took Kiriath-sepher, and married Achsah, Caleb's daughter. Later he became one of the judges. He defeated Chushan-rishathaim, king of Mesopotamia. Under him the land had rest forty years. Joshua 15:17; Judges 1:13; Judges 3:9, 11; 1 Chr. 4:13.
Commentators differ on whether Othniel was Caleb's brother or his nephew.
Who was Kenaz? One writer follows the name back and finds a family that did not start out in Israel at all:
In Numbers 32:12 and Joshua 14:6, 14 Caleb is called "the son of Jephunneh the Kenizzite." Caleb's younger brother Othniel, to whom Caleb gave his daughter Achsah as wife, is likewise called "the son of Kenaz." And in Genesis 36:11 we learn that Kenaz is an Edomite name. So at some point the family of Kenaz, and with it the family of Caleb the son of Jephunneh, was brought into the tribes of Israel, like so many other foreigners — Jethro, Rahab and Ruth — who became members of the people of God because of their faith. So Caleb, who by birth really had no right of citizenship in Israel, received that right in the middle of Judah because of his faith. He became part of the family of Caleb the son of Hezron, as 1 Chronicles 2:49 and the passages already cited in Joshua show. The surviving fragments of the genealogy of Caleb the son of Hezron confirm the place God gave to Caleb the son of Jephunneh. This substitution is one of the important points the Spirit of God calls our attention to here.
One writer groups Othniel with Caleb and others like him, and names the quality they share:
To summarise, the name of Caleb is highlighted in this chapter. This name carries the thought of "virtue," that is, of moral energy. With a goal in view, it enables the believer to overcome obstacles. It separates him from every weight and from the sin that so easily entangles him. 2 Peter 1:5 says, "In your faith have also virtue." Caleb is an example in this. The same name is linked with people of the same calibre as the son of Jephunneh: Othniel and Achsah (1 Chron. 4:13), Hur, Jair — though Jair later lost everything his energy had at first won — and the house of Rechab.
Othniel's first recorded fight won him a wife and a field. Only afterwards was he sent out for the nation, and the order is deliberate:
We have already spoken of Othniel in his private, domestic life (Judges 1). God had in this way fitted him to be the first judge in Israel. Having fought to win a wife, he became the owner of his own personal inheritance and of springs to water it. God now uses him to fight for others, and it is always like this. Before God uses a Christian in public, that Christian must first have grown in the knowledge of the Lord and in the power of his privileges. Where this is missing, it usually explains why our service is so limited and our hearts so little taken up with heavenly things.
Othniel's name and his tribe together point beyond him:
It is the same Othniel of whom we read in chapter 1:13 and Joshua 15:17. Othniel means "lion of God," and as he was of Judah, he is the type of Him who is the Lion of the tribe of Judah. Upon him rested the Spirit of the Lord. The king of Mesopotamia was given into his hands, and a rest followed for Israel. So we too must return to the Lord and expect our deliverance from Him. What grace towards His people is shown in this first deliverance!
These names also teach something about the inheritance God gives:
Verse 13 gives the honoured name of Othniel. At Caleb's challenge he took Kiriath-sepher, and received Caleb's daughter Achsah as his wife. She received from her father "the upper springs and the lower springs" (Joshua 15:16-19). These devoted men teach us valuable lessons concerning the inheritance of God. We are not only to value God's inheritance; we are to make it ours. Even now we are to lay hold of what will soon be fully ours with Christ.
- Outsider. Kenaz was an Edomite name, and his line had no birthright in Judah. Faith gave Caleb the Kenizzite a place there, and God put that substitution in the record on purpose.
- Energy. The names gathered round Caleb, Othniel and Achsah among them, carry one stamp. It is moral energy that presses past obstacles toward the goal.
- Home first. Othniel fought for a wife, a field and its springs. Only then did God make him Israel's first judge. Private progress comes before public usefulness.
- Deliverer. His name means "lion of God," and he was of Judah. So he pictures the Lion of the tribe of Judah. His victory shows God's grace to His people.
- Inheritance. Othniel's honoured name teaches more than valuing what God gives. We are to take hold of the inheritance now.
And Meonothai begot Ophrah and Seraiah begot Joab, the father of the valley of craftsmen; for they were craftsmen.
Four names pass by in one line, and the last of them is tied to a valley of workmen. Why does Scripture stop to record a family of craftsmen, and what does that say about the work God hands to ordinary people?
Verse 14 sits inside a short family record in Judah's line. One commentator names the two brothers this line comes from, and notes that the record breaks off early:
Finally, in 1 Chronicles 4:13-15 we find the descendants of Caleb the son of Jephunneh and of his brother Kenaz. But here now, in this portion, this genealogy is truncated.
The family behind the verse matters. Chronicles gives these chapters two figures of first importance:
Two names especially stand out in 1 Chronicles 2-4. First, that of David, for Judah's kingship is, as we have seen, the principal subject of Chronicles. Secondly, that of Caleb the son of Jephunneh who represents the energy and the perseverance of faith.
"Ge-harashim" is not a person but a place, and its name is its description. Older translations keep the Hebrew word and render the phrase "the valley of Charashim":
'Craftsmen,' as in the margin. 1 Chr. 4:14: compare Nehemiah 11:35.
Joab is therefore identified not by a battle or an office but by a trade settlement. He is the head of the place where the skilled workers lived:
Son of Seraiah: described as "the father of the valley of Charashim," or craftsmen. 1 Chr. 4:14.
Earlier in the same chapter Jabez prays for enlarged borders. One commentator sets Joab's craftsmen beside that prayer, along with the linen workers, potters and gardeners named later in the chapter:
The people of God have yet other duties and other activities beside enlarging their borders as Jabez. Joab is "the father … of craftsmen" (v. 14). God has entrusted us with certain functions. They are humble, but very useful in their place. We do well to attend to them without coveting higher things. This will keep us in humility. Among the sons of Shelah are found "linen workers," potters, and gardeners (vv. 21, 23). These were not noble occupations. Their importance came from this: these men "… lived with the king for his work." Although very humble, they were his fellow workers within the limits that his work assigned to them. For this reason the king kept them around him. Theirs was the great privilege of living near him — a privilege many nobles and princes wanted and never got.
The same holds for anyone serving God now. The reward named here is not promotion but nearness:
So it is with us too. Let us each fulfill our task. Let us beware of wanting a high position among the people of God. Let us be content with humble things instead. What our Lord asks is that we carry them out diligently. Let us be faithful in little things as long as we work together in His works. Leave the future reward aside. Even now we will gain the priceless advantage of "living with the king" and of looking on His face.
A list of names like this can feel like paperwork. One writer found it solemn reading, and said why:
There is something deeply solemn to the soul in being allowed to go over such a record of names. People forgot them long ago. Yet God has remembered every one of them, with every detail of their pathway through this world. Some day our names likewise will be lost to mankind, but neither we nor our ways will be forgotten by God.
- Line — The verse traces the family of Caleb and Kenaz. Chronicles links that name with the energy and perseverance of faith.
- Trade — Scripture ties Joab, son of Seraiah, to the valley of craftsmen. A trade, not a title, marks him out.
- Task — God's people have work beyond enlarging their borders as Jabez did. God entrusts humble but useful jobs, and doing them without coveting higher things keeps us humble.
- Nearness — The linen workers, potters and gardeners lived with the king for his work. Many nobles and princes wanted that closeness and never got it.
- Record — People forgot these names long ago. God remembers each one, with every detail of their path — and He will do the same with ours.
-- And the sons of Caleb the son of Jephunneh Iru, Elah, and Naam; and the sons of Elah, ... and Kenaz.
Four names close this short block: Caleb's three sons, and a grandson through Elah. Why does a list this thin matter, and which Caleb is it?
Chapter 4 runs through Judah's line a second time. The book is not gathering names at random.
Verses 1 through 23 take up the genealogy of Judah for the second time. Two names stand out in 1 Chronicles 2-4. First, David, because Judah's kingship is, as we have seen, the main subject of Chronicles. Second, Caleb the son of Jephunneh, who stands for the energy and perseverance of faith.
Chronicles names two different men called Caleb. This one is marked out by his father, Jephunneh.
And besides Jabez we have Caleb, a well-known name, the son of Jephunneh, the son of Kenaz, if we may conclude that from Numbers 32:12: "Caleb the son of Jephunneh the Kenizzite." He matched Joshua in faithfulness, and the two of them were the only men who left Egypt and reached the promised land. Everyone else who entered Canaan was born in the wilderness.
This list is shorter than the fuller accounts of the same family elsewhere in the book.
Finally, in 1 Chronicles 4:13-15 we find the descendants of Caleb the son of Jephunneh and of his brother Kenaz. But here, in this part, the genealogy is cut short.
A short, broken list raises an obvious question: can a record like this be trusted?
Must we conclude from all this that the text of Chronicles is a human and random compilation, and that the book therefore has no historical value? That is what those who rely on human reason claim. But thank God, their reasoning always fails when it attacks His Word. No well-taught Christian will deny that the genealogies of Chronicles are made up of fragments picked up in a time of general confusion. Yet they are documents on which God sets His seal of approval.
By birth, this family did not belong in a list of Judah at all.
So Caleb, who by birth had no right of citizenship in Israel, received that right inside Judah because of his faith. He was brought into the family of Caleb the son of Hezron, as we see in 1 Chronicles 2:49 and in the passages from Joshua already mentioned.
One writer draws the line from that adoption straight through to the New Testament.
Joshua 14 tells us that Caleb was the son of Jephunneh, a Kenizzite who had probably come from the mountains of southern Canaan and had attached himself to the tribe of Judah. So by birth he was a stranger to the covenants of promise. He was one of the first-fruits of the Gentile harvest, and the Old Testament holds many other examples. But the barrier of his birth did not stop him from being an Israelite in spirit. The apostle Paul wrote to the Christians in Ephesus as people once separated from the commonwealth of Israel. Now, in Christ Jesus, they had been brought near by the blood of Christ, so they were no longer strangers but fellow citizens with the saints (Ephesians 2).
Caleb's name carries more than family history.
To sum up, the name of Caleb stands out in this chapter. The thought tied to this name is "virtue" — that is, moral energy which, with a goal in view, enables the believer to get past obstacles, separating him from every weight and the sin that clings so closely. 2 Peter 1:5 tells us to "supplement your faith with virtue." Caleb is an example of this. Other people of the same calibre as the son of Jephunneh are linked with this name: Othniel, Achsah (1 Chronicles 4:13; 1 Chronicles 2:49); Hur (1 Chronicles 2:19, 50; 1 Chronicles 4:1, 4).
Kenaz closes the verse. One writer asks what the name itself means.
Caleb is here, as once before, the Kenizzite, and elsewhere a Kenaz is said to be his brother. We will not go into the difficulties of his genealogy here. But what does the name mean? "Container of strength" is at least as good as any meaning offered, and it fits the whole line of Caleb's history. Read that way, Othniel, whom we hear of in the next chapter and in Judges, would be the fitting son of Kenaz.
Caleb's faith did not stop with Caleb.
One person's faithfulness, even in the darkest days of the church, stirs up spiritual energy in others. Othniel sees Caleb's faith and is moved to act the same way. He serves his first campaign under Caleb, and wins a good standing for himself, for he becomes the first judge in Israel.
- Faith — Caleb stands out for the energy and perseverance of his faith, not for his ancestry. That is why his name sits beside David's in these chapters.
- Citizenship — Faith, not birth, gave a man with no claim on Israel a place inside Judah's register.
- Virtue — The name Caleb carries the thought of moral energy: faith that keeps the goal in view and pushes past every obstacle.
- Overflow — That energy spread. Othniel saw Caleb's faith, served his first campaign under him, and became Israel's first judge.
- Fragments — The record is short and broken, picked up in a time of confusion, yet God set His seal of approval on it.
-- And the sons of Jehalleleel Ziph and Ziphah, Tiria and Asareel.
This verse lists four sons of Jehallelel. They sit inside a family line of Judah that Chronicles goes over a second time. Why does Scripture keep names like these, and what is a reader who knows nothing about these men meant to do with them?
This list sits in a part of Chronicles with a clear focus.
Verses 1 to 23 go through the family line of Judah a second time. Two names stand out in 1 Chronicles 2-4. First, David, because Judah's kingship is, as we have seen, the main subject of Chronicles. Second, Caleb the son of Jephunneh, who stands for the energy and endurance of faith.
A name in these lists does not always point to one man.
After the captivity the people had lost everything they owned. A list of names still mattered.
The Jews were discouraged by the destruction they had refused to believe in until it came. They might have thought, "What is the use of a genealogy? Why care now about our lands or houses? Everything is ruined. All is gone." But the man who believed God knew that seventy years would see them come back from their captivity. So his care for God and his confidence in His Word would make him guard his family records closely. Then, when they did return, they could take up the portion God had given them. This is what made every homestead in Israel so precious — that God gave it. It was not just something a man earned by his own labour or skill. It was God's gift to them.
Names we cannot place still sit inside something God is ordering.
What importance can we attach to this genealogy of unknown names? Remember that we are in the kingdom of God, where one wheel fits the next in His chariot as it moves forward. How good it is to leave meaningless chatter behind for a world like this, where everything has meaning! No doubt there are depths and heights here that we cannot explore. Even so, this encourages us onward, and at every step we gain something in view.
David himself came to learn what the first name in this verse means.
David learned by experience what the name of Ziph means; it means "refining." Suffering and endurance refined him, and that process made the shepherd-king ready for the high place ahead of him.
These forgotten names say something about our own.
It deeply sobers the soul to be allowed to read through a record of names that people forgot long ago. God has remembered every one of them, with every detail of their path through this world. One day our names will be lost to people too, but God will never forget us or our ways.
A name written down now points forward.
There is little to say here except that the Lord is glad to record even the names of His servants... He has been a dwelling place for His own in every generation. More than that, He honours those who honour Him. He records their names in His word now, and He will glorify them in person on the great day that is coming quickly.
Chapter after chapter of descent leads to one settled conclusion.
Everything that comes from nature ends in complete failure and is worth nothing before God. Grace is the only thing we can count on, as we rest on the counsels and election of grace, which are settled forever.
- Recorded — Jehallelel's four sons sit inside Judah's line. Chronicles goes over that line twice, because Judah's kingship is its main subject.
- Represented — a name in Chronicles can stand for a family, a clan or a town. That kept a household's line known when no head could be traced.
- Restored — the exiles guarded these lists so that each family could come home and take up what God had given. No one had earned it.
- Remembered — God keeps names people have long forgotten, with every detail of the road each person walked.
- Rested — nature's line runs out and fails; only grace, settled forever, holds.
-- And the sons of Ezra Jether, and Mered, and Epher, and Jalon; and she conceived [and bore] Miriam, and Shammai, and Jishbah the father of Eshtemoa.
Four sons, an Egyptian princess, and three more children — verse 17 reads like an entry nobody would miss. Yet it sits inside a long chain of family records. Commentators ask why God kept it, and what a daughter of Pharaoh is doing in the tribe of Judah.
The chapter returns to a line already traced twice before, and it is the royal line. Judah is not listed for its own sake:
Verses 1 to 23 take up the genealogy of Judah for the second time. Two names stand out in 1 Chronicles 2-4. First, David, because Judah's kingship is, as we have seen, the main subject of Chronicles. Second, Caleb the son of Jephunneh, who stands for the energy and perseverance of faith.
The verse calls Ishbah "the father of Eshtemoa" — and Eshtemoa sounds more like a place than a person. That is normal here, and it explains much of the strangeness of the list:
Sometimes the genealogies of Chronicles contain very ancient names that we find nowhere else in the Old Testament. Many names are not people at all, but clans or families. Other genealogies we might call geographic. For lack of any other source material, they include the names of tribes, districts and cities.
The gaps and jumps have a cause. Exile had left many families unable to prove who they were:
In Chronicles the accuracy of the genealogies depends largely on how much the Jews valued them during their captivity. The disorder these lists show matches the state of the remnant that we find in the books of Ezra and Nehemiah. Quite a number of the people, and of the priests, could not prove their genealogy.
Commentators differ over how to read this marriage. (Some translations place Bithiah in verse 18 rather than verse 17.) One writer sets it beside another Egyptian marriage in the same book and reads both as a failure:
Sheshan married his daughter to his servant Jarha, an Egyptian, and their children were counted with Israel (1 Chron. 2:34-41). On the other hand, Mered the son of Ezra married Bithiah, the daughter of Pharaoh (1 Chron. 4:17-18), and had sons. If Joseph's wise advice had been followed (Gen. 46:33-34), these mixed marriages would never have happened as the years went on.
Another writer reads the same lists and sees God refusing to keep His grace inside one nation. Outsiders keep appearing in the leading tribes, and the cross makes that grace wider still:
And it makes no difference who the person is — low and vile, or high and noble! Gentiles are woven into the two tribes that led the house of Israel: Joseph, through Ephraim, ruling by right of the birthright, and Judah, from whom the true David comes. Egypt's noble daughter Asenath is joined to Joseph; the disgraced Tamar to Judah; further down the line Rahab, from the doomed city; and Ruth, a woman of Moab… God would not be limited to Israel when it was a question of showing grace… Now that the work of the cross is done, how much more is the boundless character of grace — God's grace — proclaimed.
Jether, Epher, Jalon, Shammai — the Bible tells us nothing else about them. That silence is exactly what makes the record weigh on you:
It deeply sobers the soul to be allowed to go over a record like this — names people forgot long ago, yet God has remembered every one of them, with every detail of their path through this world. One day our names too will be lost to the world, but God will forget neither us nor our ways.
The writers put these chapters together after the kingdom had already fallen. That timing gives a list like this its weight:
It is all the more striking to find in Chronicles this picture of grace at work in the heart of man, for these books were written, as we have seen, after the final ruin of the people and of the kingdom. But what comfort for the poor remnant, back from Babylon, still in servitude and despised, to find their history here, written in those disastrous times by the Spirit of God Himself! Every page shows that no unfaithfulness on the part of the people could change God's counsels or alter the grace by which He would establish His eternal purposes for His people in the person of Christ.
- Recorded for the King. Judah fills chapters 2 to 4:23 because Judah's kingship is the subject of Chronicles. David and Caleb are its standout names.
- Recorded in ruins. Exiles drew up these lists, and many of them could not prove their own descent. The disorder in the text matches the broken state of the people.
- Recorded as clans and places. Not every name here is a man. Some are families, districts and towns — which is why Ishbah can be called the father of Eshtemoa.
- Recorded beyond Israel. Commentators differ on Bithiah. One reads Mered's marriage as a mixed marriage Israel should have avoided. Another sees Gentiles woven through these tribes, because God would not limit His grace to Israel.
- Recorded by God. God keeps the names the world forgot. He set them in a book that shows no failure of His people can alter His purposes in Christ.
And his wife the Jewess bore Jered the father of Gedor, and Heber the father of Socho, and Jekuthiel the father of Zanoah. And these are the sons of Bithiah the daughter of Pharaoh whom Mered took.
This verse lists a Jewish wife and her three sons, and ties each son to a town. The lines around it name a second wife: Bithiah, a daughter of Pharaoh. Why does the record of God's people make room for an Egyptian princess? And what does it mean to call a man the "father" of a place?
Judah's family already fills chapters 2 and 3. This second pass has a different aim:
Chapter 4 begins a section that is somewhat new, though we have had Judah before. This is another feature that marks Chronicles — it repeats things now and then, even where nothing is complete, but it never merely repeats. In the earlier section, Judah comes in to bring us David and the royal line. Here Judah comes forward because he is a leader among the tribes of Israel... Here we have Judah again simply in his place among the different tribes. So his line is carried on in a general way as before, but with a view to the people, and not the kingdom.
Gedor, Soco and Zanoah are places, not people. The verse ties each son's name to one of them:
Jered. Father or founder of Gedor. 1 Chr. 4:18.
Readers have taken the last name two ways, which shows how tightly packed these lines are:
Zanoah. Son of Jekuthiel. 1 Chr. 4:18. The Rabbis interpret "Jekuthiel was chief of Zanoach," referring to No. 2.
Some translations keep the Hebrew here as a name, Jehudijah. A dictionary of Bible names treats it as a description instead, and links her to a wife named a verse later:
Hodiah. One of the wives of Ezra, of Judah. 1 Chr. 4:19. The same apparently as JEHUDIJAH, which signifies "the Jewess," in 1 Chr. 4:18.
Commentators differ on how to read this marriage. One writer puts Bithiah next to another Egyptian marriage in these chapters, and weighs both against Joseph's advice:
Sheshan married his daughter to his servant Jarha, an Egyptian, and Israel counted their children as its own (1 Chron. 2:34-41). On the other hand Mered the son of Ezra married Bithiah, the daughter of Pharaoh (1 Chron. 4:17-18), and had sons. If Joseph's wise advice had been followed (Gen. 46:33-34) as the years went by, these mixed marriages would not have happened.
Another writer looks at the non-Jews scattered through these lists and sees grace at work:
How sovereign the grace which will not overlook the outcast Gentile!... Gentiles are interwoven with the two tribes, the most prominent as being leaders in the house of Israel: Joseph, through Ephraim, ruling in virtue of the birthright, and Judah, of whom is the true David; Egypt's noble daughter, Asenath, with Joseph; the ignoble Thamar, with Judah; lower down the line, Rahab, of the doomed city; and Ruth, a Moabitess... God would not be limited to Israel when it was a question of showing grace; He was as to law, but even under the old covenant, which was special to Israel, He chooses from among the Gentiles whom He will bless.
So why keep a list of forgotten names at all? One writer says God Himself is doing the recording:
At the same time He records the names of those who came through the trials this history describes, and who were never blotted out of the book. Here it is only the outward picture of that blessed memorial of the people of His grace, but this is in fact what we find. Not all Israel is there; and not all who come from Israel are Israel.
That is why a chapter of obscure names still rewards reading:
It stirs the soul deeply to be allowed to read through such a record of names. People forgot them long ago, yet God has remembered every one, with every detail of their path through this world. One day our own names will be lost to mankind too, but God will forget neither us nor our ways.
- Record. The chapter traces Judah a second time. The first pass led to David; this one sets the tribe in its place among the people.
- Names. Jered, Heber and Jekuthiel stand as fathers, or founders, of Gedor, Soco and Zanoah. The tight Hebrew allows more than one reading.
- Jewess. Older translations call the first wife Jehudijah. The word means "the Jewess".
- Grace. Commentators differ over Bithiah. One sees a mixed marriage Joseph's advice would have prevented. Another sees grace that will not overlook the outcast Gentile.
- Remembered. God keeps the names men forget. This list is the outward picture of His memorial of the people of His grace — and a pledge that He will not forget our ways either.
-- And the sons of the wife of Hodijah, the sister of Naham the father of Keilah the Garmite, and Eshtemoa the Maachathite.
This verse sits inside a long list of Judah's descendants. It ties a woman's household to two names that are also towns in Judah. So why does Scripture keep a record of people whose stories we will never hear?
Chapter 2 already traced Judah, but it followed his line to reach David. Here the purpose shifts.
Chapter 4 begins a partly new section — not that we have not had Judah before. This is another unusual feature of Chronicles. It repeats at times, even where nothing is complete, but it is never only repetition. The earlier section brings Judah in so as to bring in David and the royal line. Here Judah comes forward because he is a leader among the tribes of Israel… Here we have Judah again simply in his place among the different tribes. So Chronicles carries his line on in a general way as before, only with a view to the people, and not the kingdom.
Part of the difficulty in reading a verse like this is that we assume every name is a single man. One writer lists this very passage as an exception.
Sometimes the genealogies of Chronicles contain very old names. We do not find them anywhere else in the Old Testament. Many names are not names of people, but of clans or families. Others are genealogies we might call geographic. For lack of other source material, they include the names of tribes, of districts, and of cities… We find this again in 1 Chron. 4:1-23.
That fits Keilah and Eshtemoa, which are both towns in Judah. Keilah was a real place on the map, not just a name in a list.
Keilah was about six miles south-east of Adullam. David heard that the Philistines had invaded and were fighting against this walled city. So he asked the Lord about it.
The record turns on a woman. One reference work reads Hodiah as a woman, one of Ezra's wives, and links her to a name in the verse before.
Hodiah: one of the wives of Ezra, of Judah. 1 Chr. 4:19. Apparently the same as Jehudijah, which means "the Jewess," in 1 Chr. 4:18.
Translations read the family ties in more than one way. In the ESV, her sons are the fathers of Keilah and Eshtemoa. Other readings make Naham their father.
Naham: a man of Judah, father of Keilah and Eshtemoa. 1 Chr. 4:19.
Eshtemoa carries the tag "the Maacathite." Israel never drove the Maacathites out of the land.
The enemies are all conquered, but not all driven out… But Israel has to dispossess them. As long as the enemies hold anything, the enjoyment of the people of God is not complete. More than that, Israel is allowing something among them that could keep making them fail. If the enemy is not destroyed, he will be quick to lift his head and corrupt the people, if he cannot overcome them. This was in fact the snare once the Israelites were settled in the land of their possession. It says of the two and a half tribes: "Yet the people of Israel did not drive out the Geshurites or the Maacathites, but Geshur and Maacath dwell in the midst of Israel to this day" (Joshua 13:13).
That answers the question this verse raises.
There is something deeply solemn about being allowed to go over a record of names that people forgot long ago. Yet God has remembered every one of them, with every detail of their path through this world. One day people will lose our names too. But God will never forget us or our ways.
The same holds wherever such lists appear. God names the small and the overlooked on purpose.
And God even takes account of those we might have forgotten: the temple servants and Solomon's servants. These people may not have been of Jewish descent, and they did lowly work. But God is pleased to mention all the names of the fathers of those who went up to Jerusalem. In the same way, members of the body of Christ have different tasks, duties, and abilities. The most prominent ones may not be the most important ones (1 Cor. 12).
- Placed — Chronicles lists Judah a second time, not to reach David, but to set the tribe in its place among the people.
- Named — a woman's household carries the line here. Jehudijah, the name in the verse before, means "the Jewess." Translations trace the family ties in more than one way.
- Bordered — Keilah and Eshtemoa are towns as well as names. Many names here are clans and places. "Maacathite" recalls a people Israel never drove out.
- Remembered — God holds the names the world forgot, with every detail of the road they walked.
- Counted — God names the lowly and unnoticed on purpose. The most prominent are not always the most important.
-- And the sons of Shimon Amnon and Rinnah, Ben-hanan and Tilon. -- And the sons of Jishi Zoheth and Ben-Zoheth.
This verse names two fathers and their six sons, and then moves on. Why does God keep a record of men whose whole story is their name, and what were such lists for?
This verse sits in a chapter about the whole tribe of Judah, not only David's family. One writer explains why Judah's families come here rather than earlier:
Now that God has made known His purposes about His King, the record names the children of the kingdom through the heads and chiefs of families. It gives the tribes in the appointed order, first the royal tribe of Judah. Judah appeared before, in 1 Chronicles 2, because David is of that tribe. There the point is not the families of Judah but David's genealogy. Here in chapter 4 the tribe comes first. It has the pre-eminence as the royal tribe, next in importance to the royal family of David.
Commentators warn against reading such a verse as a plain father-to-son chain. One of them lists the stretch this verse sits in among the lists that work differently:
Sometimes the genealogies of Chronicles contain names of very ancient origin, which we do not find elsewhere in the Old Testament. Many names do not belong to single people, but to clans or families. Others are genealogies we might call geographic. Where no other source material existed, they include the names of tribes, of districts, of cities. We find this again in 1 Chronicles 4:1-23.
The gaps and rough edges in these lists are themselves a witness. The same writer links the disorder in these lists to the state of the people, and explains why a man's sons here may be distant descendants:
In Chronicles the accuracy of genealogies depends in large measure on the importance the Jews placed upon them during their captivity. The disorder these lists reveal matches the state of the remnant as we find them in the books of Ezra and Nehemiah. Quite a number among the people and among the priesthood could not prove their genealogy. The great disorder that came in also explains, at least in part, why very distant descendants of the head of a clan were counted as his sons.
For the families themselves, a name on this list was not a curiosity. It was a title deed:
The books of Chronicles were written after the captivity, when everything was thrown into disorder. The Jews were disheartened by the destruction they had refused to believe in until it came. They might have thought, "What is the use of a genealogy? What is the use of caring now about our lands or houses? Everything is ruined. All is gone." But the man who believed God knew that seventy years would see them return from their captivity. So care for God and confidence in His Word would make them guard their genealogies closely, in order that, when they did return, they might enter upon the land God had allotted them. For this was what made every homestead in Israel so precious — that it was God that gave it.
Chronicles also has a narrower aim than the books of Kings:
The books of Chronicles are much more fragmentary than those of Kings. At the same time they are more closely tied to what follows. The reason is this: they look at the line of promise and purpose, and so they keep to David and those who inherited the kingdom of David's race. The books of Kings, on the other hand, look at the kingdom of Israel as a whole… there it is not purpose, but responsibility.
One writer applies these forgotten names to the reader's own life:
There is something deeply solemn to the soul about being allowed to go over such a record of names. People forgot them long ago, but God has remembered every one, with every detail of their pathway through this world. Some day our names likewise will be lost to mankind, but neither we nor our ways will be forgotten by God.
One writer states the objection as a blunt question, then answers it:
But we may still be challenged with a question like this: "Do you believe that the long string of names in the opening chapters of 1 Chronicles — those genealogical tables — are divinely inspired? Were they written for our learning? And if so, what are we to learn from them?" We declare without hesitation our reverent belief that all of these are inspired by God. And we have no doubt at all that their value, interest and importance will be proved in full, in time, in the history of that people to whom they specially apply.
- Purpose — Chronicles follows the line of promise in David's race. So a list of Judah's families belongs to the story of God's King. It is not filler.
- Place — Chapter 4 names the tribe, not only the royal house. Judah comes first, as the royal tribe.
- Proof — For the returning captives, these names were their claim to the land God had allotted them. Faith kept the registers when everything else looked ruined.
- Patchiness — Many entries stand for clans, districts or cities. In the disorder after the captivity, a man's "sons" can even be distant descendants, and many could not prove their descent at all.
- Permanence — God remembers each name that people have long forgotten, with every detail of their path. Commentators hold that the full value of such chapters will be shown in time.
The sons of Shelah the son of Judah Er the father of Lechah, and Laadah the father of Mareshah, and the families of the house of byssus-workers, of the house of Ashbea,
Judah's family record turns here from kings and warriors to a quieter household. Shelah's descendants are remembered by the places tied to their names and by the cloth they wove. Why does Scripture keep such names at all? And why is a whole family remembered by its trade?
Most readers skip these chapters. One writer admits the instinct, then answers it:
In Israel there were sad blots, and blots on the best of them. Yet even so, something truly divine was at work among that poor people from the beginning onward. So we can see that these genealogies had a far higher character than they seem to have at first sight. I have no doubt that most of us have read them thinking it was high time to skip over them, and have often wondered why they were written at all.
"Er the father of Lecah" and "Laadah the father of Mareshah" read strangely. Lecah and Mareshah sound like towns, not sons. One commentator flags that very difficulty in these chapters:
Sometimes the genealogies of Chronicles contain very ancient names, which we do not find anywhere else in the Old Testament. Many names are not those of single people, but of clans or families. Others are genealogies we might call geographic. For lack of other source material, they include the names of tribes, of districts, of cities. We find this kind of list again in 1 Chron. 2:18-24, 25-33, 42-55; 1 Chron. 4:1-23, 28-33.
A reference work still lists them as people, calling Mareshah "son of Laadah of the tribe of Judah" (Morrish Bible Dictionary). So commentators differ: some of these names may be men, some families, some the places they settled.
A reference work calls Shelah the "youngest son of Judah by the daughter of Shuah, a Canaanite" (Morrish Bible Dictionary). That mother's name points back into Judah's own failure. One writer sees what God did with such material:
In Judah's history we find Judah's utter wandering and misery. Yet in it, and out of it, comes the genealogy of grace. He marries Canaanites. Sin is in his family. He sleeps with his own daughter-in-law. All was gone wrong. Yet out of this sprang the One in whom men would find blessing.
The verse does not credit these clans with victories or land. It names their craft. A few verses later the same list adds potters and gardeners:
God has entrusted us with certain duties. They are humble, but very useful in their place, and we do well to attend to them without wanting higher things. This keeps us humble. Among the sons of Shelah we find fine linen workers, potters, and gardeners (vv. 21, 23). These were not noble occupations. Their importance came from one thing: these men "lived with the king for his work." Though very humble, they were his fellow workers, within the limits his work set for them. For this reason the king kept them near him. Theirs was the great privilege of living close to him — a privilege many nobles and princes wanted in vain.
Beth-ashbea in the verse is the same "house of Ashbea" named below. Fine linen appears again at the end of the Bible, where its meaning is stated:
In Revelation 19:8 we are taught that "the fine linen is the righteous deeds of the saints." So the workers of the house of Ashbea bring before us a precious privilege that belongs to the people of God. It is the privilege of working out, in the practical details of life, the features of divine righteousness that are for the pleasure of God. Each act of practical righteousness in the lives of the saints of this present age is a stitch in that beautiful garment. In it the Bride of Christ will appear before His eye on the day of the marriage of the Lamb. Many of these ornamental stitches are made in times of deepest sorrow, in the trials and persecutions of the saints, as well as in the ordinary, day by day work of life.
- Recorded — These name-lists are not filler. Something truly divine was at work among a flawed people, so these genealogies carry a higher character than they first appear to.
- Grace — Shelah came from Judah's marriage to a Canaanite. In a family where "all was gone wrong," this is a genealogy of grace first, and a genealogy of families second.
- Craft — Weaving marks these clans, not conquest. Humble duties are worth our care, without wanting higher things.
- Nearness — Their trade mattered because they "lived with the king for his work." Nobles and princes wanted that closeness and never got it.
- Garment — Every act of practical righteousness now, even in sorrow, is a stitch in the fine linen. The Bride will wear it at the marriage of the Lamb.
and Jokim, and the men of Chozeba, and Joash, and Saraph, who ruled over Moab, and Jashubi-lehem. And these are ancient things.
Four little-known names sit inside Judah's long family record, and the verse closes by calling its own records old. Why does Scripture pause over men we otherwise know nothing about, and what happened to the rule they once held?
One writer reads these verses not as filler but as a deliberate pause in the genealogy:
Another bright jewel shines among the seemingly dull genealogies of the early chapters. It is the one in chapter 4:21-23. This seems to please God so much that He turns aside to draw attention to it. No doubt He does so to teach and encourage those who want to serve Him in a way He accepts, in their own day and measure.
Another writer weighs what it means to read a list of names that no one on earth remembers:
It deeply sobers the soul to be allowed to go over such a record of names. Man forgot them long ago. Yet God has remembered every one of them, with every detail of their pathway through this world. One day our names will be lost to mankind too. But God will forget neither us nor our ways.
These men come from the line of Shelah, one of Judah's three branches. One commentator weighs what that line produced, and what became of the honour it held:
Then comes Shelah (v. 21). So the three branches from Judah — Pharez, Zerah, and Shelah — have a place here. Shelah was the eldest, since Er and Onan were killed in judgment. Yet there is no name of note among them such as Jabez and Caleb. They are workers in fine linen, as others were craftsmen (v. 14). There were princes among them "who had dominion in Moab," perhaps those appointed to gather gifts (tribute) from Moab (18:2). But "these are ancient things." Remember that this genealogy was written after the return from Babylon. They lost what honour they had through their sin.
One writer works through the names, and notes that Moab itself has a character in Scripture:
Jokim (Jah sets up) and Joash (Jah supports) need no interpretation in the line of purpose. Moab in Jeremiah 48:11 and 29 speaks of ease, pride, haughtiness. Saraph means burning, or judgment. It reminds us of the self-judgment we need, so that we may obey the word which says, "walk ... as wise, making the best use of the time" (that is, not at ease, not idlers) "because the days are evil."
One dictionary treats Cozeba (Chozeba) as a town, not a man, and links it with places named elsewhere:
City of Judah. 1 Chr. 4:22. Probably the same as Chezib, Genesis 38:5, and Achzib, Joshua 15:44; Micah 1:14.
Commentators read the closing note in more than one way. One writer starts from the word itself:
The word "ancient" means "removed." Matters relating to God's purpose are not connected with this world. They lie far removed from the sphere of natural man's interests. "Our citizenship is in heaven." The features expressed in the names we have considered are old and unchanging.
Others use the same note to settle a date. One writer rejects the idea that the king in view here was Nebuchadnezzar, and this phrase is his reason:
The words "And these are ancient things" contradict the rather peculiar notion that this king was Nebuchadnezzar.
If these records are old fragments, can they be trusted? One writer meets that objection head on:
Must we conclude from all this that the text of Chronicles is a human and random compilation? Must we say the historical value of this book is therefore nothing? This is what the rationalists assert. But thank God, their reason is always at fault when it attacks His Word. No enlightened Christian will deny that the genealogies of Chronicles are made up of fragments gathered up in the middle of general confusion. Yet they are documents on which God sets His seal of approval. So it is true that a number of passages in these genealogies are very ancient in origin, and are not mentioned in the other books of the Old Testament.
- Purpose — This little group of names is not leftover material. God turns aside to point it out, like a jewel among the lists.
- Names — Jokim means "Jah sets up," Joash "Jah supports," and Saraph burning, or judgment. Cozeba is a town of Judah.
- Dominion — Shelah's line produced no famous names, yet it produced princes. Their rule in Moab may have meant collecting tribute. It was real honour.
- Loss — The honour did not last. One writer says their sin cost them what they had, so the verse records a height already behind them.
- Remembered — What man forgot, God kept. These are fragments gathered out of confusion, yet God has sealed them. The God who remembered these names will not forget ours.
These were the potters, and those that abode among plantations and enclosures there they dwelt with the king for his work.
The verse closes a long genealogy of Judah with a line about working men: potters who lived in one place and served the king. Older translations turn those place names into "plants and hedges," and the writers below ask why God recorded these men at all.
The list has just passed Jabez, who prayed for larger borders. Then it drops to linen-workers, potters and gardeners. One writer finds a lesson in that drop:
The people of God have other duties and activities besides enlarging their borders as Jabez did. Joab is "the father… of craftsmen" (v. 14). God has entrusted us with certain functions. They are humble, but very useful in their place. We do well to pay attention to them without coveting higher things. This will keep us in humility. Among the sons of Shelah we find linen-workers, potters, and gardeners (vv. 21, 23). These were not noble occupations. Their importance came from one thing: these men "dwelt with the king for his work."
What lifted these men was not the trade itself:
They were very humble, yet they were his fellow workers, within the limits his work set for them. For this reason the king kept them around his person. Theirs was the great privilege, coveted in vain by many nobles and princes, of dwelling near him.
The line before this one says, "these are ancient things." Commentators read it in two ways. One takes the genealogy as written after the return from Babylon, so the trade marks a loss:
Let us remember that this genealogy was written after the return from Babylon. What honour they had was lost through their sin… These descendants of princes seem to be gardeners to the king of Babylon.
Rossier disagrees:
The words "And these are ancient things" contradict the rather odd idea that this king was Nebuchadnezzar.
A third writer takes the word itself:
The word "ancient" means "removed." Matters that relate to God's purpose are not connected with this world. They are far removed from what interests the natural man. "Our citizenship is in heaven." Further, a vessel useful to the Master must be a purged — that is, separated or removed — vessel.
A potter's job is to shape and form:
Now we come to the character of the service. "These are the potters" — to fashion or form. This was true of the man who writes in Galatians 4:19: "my little children, for whom I am again in the anguish of childbirth until Christ is formed in you!" Here is the New Testament potter at work, as the LORD Himself is the potter in Jeremiah 18:6.
Another writer notes where a potter has to work:
The potters formed vessels that would serve the king. They worked outside, among the clay they took their material from. And are there not devoted servants of the Lord who care for those who are to be vessels in His service? Their work lies outside, but it receives honourable mention.
The older rendering names two kinds of growth, and one writer hears a lesson in them:
It has a voice for all who care for the tender plants of the Lord's garden. It speaks too for those who tend the hardier ones that make up the hedges, and who are set to mark the boundaries in divine things.
There was the fragrant atmosphere of the divine plantations, where God's servants laboured and lived with Him. There was also the protection of the "hedges." God's plants need shelter from the influences of the outside world. They must be kept separate from everything that would damage them and so spoil the pleasure of the One whose plants they are.
One writer asks who else was already in that place:
Shelah and his descendants lived there, yet not alone. One is already there: "they dwelt with the king for his work." The Lord is in His assembly, He delights to be there, and such are with Him. "With Him" speaks of holy intimacy and companionship. Dwelling with comes before working for. As we know Him, we are able to serve Him properly.
- Dwelt — the verse's own order is the lesson: living with the king comes first, working for him second.
- With — nearness, not rank, is the honour here. Humble craftsmen had a place near the king that nobles and princes wanted and never got.
- The king — commentators differ on who he was. One reads the trade as a fall from princely honour into gardening for Babylon's king. Rossier answers that "ancient things" rules that out.
- For — the work is forming vessels and tending plants. It happens outside, among the clay, and God's record still gives it honourable mention.
- His work — God gives humble but useful jobs. Take yours without coveting a higher one. The "hedges" keep His plants from the world that would spoil them.