Display Settings:

Format

Send to:

Choose Destination
Eukaryot Cell. 2003 Oct;2(5):901-9.

Conservation of RNase III processing pathways and specificity in hemiascomycetes.

Author information

  • Department of Chemistry and Biochemistry and the Molecular Biology Institute, University of California Los Angeles, Los Angeles, California 90095-1569, USA. guillom@chem.ucla.edu

Abstract

Rnt1p, the only known Saccharomyces cerevisiae RNase III endonuclease, plays important functions in the processing of precursors of rRNAs (pre-rRNAs) and of a large number of small nuclear RNAs (snRNAs) and small nucleolar RNAs (snoRNAs). While most eukaryotic RNases III, including the Schizosaccharomyces pombe enzyme Pac1p, cleave double-stranded RNA without sequence specificity, Rnt1p cleavage relies on the presence of terminal tetraloop structures that carry the consensus sequence AGNN. To search for the conservation of these processing signals, I have systematically analyzed predicted secondary structures of the 3' external transcribed spacer (ETS) sequences of the pre-rRNAs and of flanking sequences of snRNAs and snoRNAs from sequences available in 13 other Hemiascomycetes species. In most of these species, except in Yarrowia lipolytica, double-stranded RNA regions capped by terminal AGNN tetraloops can be found in the 3' ETS sequences of rRNA, in the 5'- or 3'-end flanking sequences of sn(o)RNAs, or in the intergenic spacers of polycistronic snoRNA transcription units. This analysis shows that RNase III processing signals and RNase III cleavage specificity are conserved in most Hemiascomycetes species but probably not in the evolutionarily more distant species Y. lipolytica.

PMID:
14555472
[PubMed - indexed for MEDLINE]
PMCID:
PMC219366
Free PMC Article

Images from this publication.See all images (5)Free text

FIG. 1.
FIG. 2.
FIG. 3.
FIG. 4.
FIG. 5.
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for HighWire Icon for PubMed Central
    Loading ...
    Write to the Help Desk