<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: PDF Multiple GMAPs into one Document in Graphics Programming</title>
    <link>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108619#M4061</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi:&lt;/P&gt;&lt;P&gt;You have 2 separate, but similar challenges:&lt;/P&gt;&lt;P&gt;1) your SAS/GRAPH job makes a GSEG entry EVERY time you run your code. It names the entries EVERY time by tacking a number onto the default name or whatever you specify for NAME=. So, a good practice is to close the GRAPH1 window and delete the GSEG entries before each run;&lt;/P&gt;&lt;P&gt;2) When you create your ODS DOCUMENT store, you should create it with an access of WRITE (not UPDATE), so that the DOCUMENT store will be overwritten and created new each time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; But philosophically, I probably wouldn't create the ODS DOCUMENT store -- every time you create the SAS/GRAPH output-- until the very, very, very end step in the process. I would get the graphs all working and then add the ODS DOCUMENT store syntax, with the appropriate "housekeeping" statements to make sure that the final job only runs once and creates the names that you need to have in the DOCUMENT store. Or else, if you need multiple graphs and multiple document stores, I would change the names, possibly with macro variables each time your job runs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; This Tech Support note shows you how to delete GSEG entries: &lt;A class="active_link" href="http://support.sas.com/kb/13/045.html" title="http://support.sas.com/kb/13/045.html"&gt;13045 - Unable to delete GRSEG entries from a graphics catalog using the displaymanager Results window.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you take care of the GSEG entries, then when you do make the document store (using WRITE access) you should have only the most current entries stored in the document store.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cynthia&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 03 Jan 2013 05:54:35 GMT</pubDate>
    <dc:creator>Cynthia_sas</dc:creator>
    <dc:date>2013-01-03T05:54:35Z</dc:date>
    <item>
      <title>PDF Multiple GMAPs into one Document</title>
      <link>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108614#M4056</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm using the following code to PDF a GMAP procedure and I'm having multiple problems.&amp;nbsp; First, my title doesn't show up in the PDF, only in the HTML.&amp;nbsp; Second, I would like to repeat this procedure to include multiple maps in one document (I'm thinking of proc document using the move&amp;gt;to statement, but I'm not sure how to reference the individual maps).&amp;nbsp; Any help is greatly appreciated.&amp;nbsp; Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;goptions reset=all cback=white htitle=14pt htext=10pt hsize=4in vsize=4in;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;options GSTYLE;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;pattern1 v=ms c=VLIGB;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;pattern2 v=ms c=LIGB;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;pattern3 v=ms c=STGB;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;pattern4 v=ms c=BIGB;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;pattern5 v=ms c=VIGB;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;legend1&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;across=6&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;shape=bar(3,4)pct&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;position= (middle bottom outside)&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;label=("Percent" Position=(center top));&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;title 'My Title';&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;proc gmap&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp; map=Proj&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp; data=Proj;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp; id maparea;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp; choro Change_Group / levels=6 legend=legend1;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;run;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;quit;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;ods pdf file="Map.pdf"&amp;nbsp; style=analysis&amp;nbsp; pdftoc=2;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;ods pdf close;&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;quit;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Dec 2012 22:58:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108614#M4056</guid>
      <dc:creator>P5C768</dc:creator>
      <dc:date>2012-12-26T22:58:09Z</dc:date>
    </item>
    <item>
      <title>Re: PDF Multiple GMAPs into one Document</title>
      <link>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108615#M4057</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi:&lt;/P&gt;&lt;P&gt;&amp;nbsp; Generally, your ODS "sandwich" surrounds the code you want to write to your destination. By default, if you are using SAS Display Manager, in SAS 9.3, ODS HTML is turned ON by default. I would normally expect to see something like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;ODS _ALL_ CLOSE; /* close all open destinations */&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;** 1) simple invocation;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;ods pdf file="Map.pdf"&amp;nbsp; style=analysis&amp;nbsp; pdftoc=2;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;...your SAS Graph code here....&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;ods pdf close;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;If you are running SAS 9.3, then you can use the GTITLE or NOGTITLE options with ODS PDF to control where the title goes. For example, in the code examples below, I turned on the BORDER goption, so you could see the impact of GTITLE or NOGTITLE. In #1 output, with NOGTITLE, the SAS title is "outside" the border; but with GTITLE option, the SAS title is "inside" the border. I know it's not a very interesting image, but the point is to see SAS TITLE behavior.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;ODS _ALL_ CLOSE; /* close all open destinations */&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;options nodate nonumber;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;goptions border;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;ods pdf file='c:\temp\gplot_examp1.pdf' nogtitle notoc;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;proc gplot data=sashelp.class;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp; title '1) GPLOT Example with NOGTITLE';&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp; title2 'Title is "outside" graph image border';&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp; plot height*age=sex /&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; description='Plot'&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; hminor=0;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;run;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;quit;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;ods pdf close;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;options nodate nonumber;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;goptions border;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;ods pdf file='c:\temp\gplot_examp2.pdf' gtitle notoc;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;proc gplot data=sashelp.class;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp; title '2) GPLOT Example with GTITLE';&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp; title2 'Title is "inside" graph image border';&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp; plot height*age=sex /&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; description='Plot'&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; hminor=0;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;run;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;quit;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;ods pdf close;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure what you mean when you say that you want to "create multiple maps in one document" -- normally all your code within one "sandwich" will get written to the open destination. So you could have this type of code and all your outputs would be put into the named PDF from your FILE= option:&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;ods pdf file="Map2.pdf"&amp;nbsp; style=analysis&amp;nbsp; pdftoc=2;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;...first map step....&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;...second map step...&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;...some other procedure step...&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;...another map step...&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;ods pdf close;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you may not need to go down the ODS DOCUMENT road if all you want to do is get multiple SAS/GRAPH outputs into 1 PDF file. You can prove this to yourself by running this code. Again, it's not GMAP output -- but GMAP would work the same way.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;options nodate nonumber orientation=landscape;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;goptions reset=all;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;ods pdf file='c:\temp\two_in_one_examp.pdf' nogtitle notoc;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;proc gchart data=sashelp.class;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp; title '3a) Gchart Example with SASHELP.CLASS';&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp; vbar age / discrete &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; sumvar=height type=mean &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; patternid=midpoint;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;run;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;quit;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;proc gchart data=sashelp.prdsale;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp; title '3b) Gchart Example with SASHELP.PRDSALE';&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp; vbar product / sumvar=actual type=mean &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; patternid=midpoint;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;run;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;quit;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-family: courier new,courier;"&gt;ods pdf close;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, if you do want to use ODS DOCUMENT and PROC DOCUMENT to do your replay, there are Tech Support notes (&lt;A href="http://support.sas.com/kb/36/505.html" title="http://support.sas.com/kb/36/505.html"&gt;36505 - Organizing output based on BY variable values: PROC DOCUMENT or Macro&lt;/A&gt; or &lt;A href="http://support.sas.com/kb/34/626.html" title="http://support.sas.com/kb/34/626.html"&gt;34626 - How to rearrange tables using PROC DOCUMENT&lt;/A&gt;) that will help you. To find out the names of the objects that you have saved into the document store, you would use PROC DOCUMENT with the LIST statement, as shown in the notes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An alternative to using ODS DOCUMENT/PROC DOCUMENT is to also investigate using PROC GREPLAY (&lt;A href="http://support.sas.com/kb/24/942.html" title="http://support.sas.com/kb/24/942.html"&gt;24942 - Use PROC GREPLAY to dynamically replay GCHART and GPLOT output on the same page&lt;/A&gt; or &lt;A href="http://support.sas.com/kb/48/546.html" title="http://support.sas.com/kb/48/546.html"&gt;48546 - Use PROC GREPLAY to simplify the table of contents when writing graphics output to a PDF file&lt;/A&gt; ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cynthia&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Dec 2012 21:13:52 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108615#M4057</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2012-12-27T21:13:52Z</dc:date>
    </item>
    <item>
      <title>Re: PDF Multiple GMAPs into one Document</title>
      <link>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108616#M4058</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, Cynthia, that worked perfectly.&amp;nbsp; One further question, when I use a similar process to combine numerous proc reports into one PDF, I use the "contents=" statement to set the text that will be displayed in the PDF.&amp;nbsp; Is there a way to do that in the GMAP or Document procedure, so that the output doesn't say "Choropleth Map of..." and "The GMAP Procedure?"&amp;nbsp; Thanks again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Dec 2012 20:10:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108616#M4058</guid>
      <dc:creator>P5C768</dc:creator>
      <dc:date>2012-12-28T20:10:24Z</dc:date>
    </item>
    <item>
      <title>Re: PDF Multiple GMAPs into one Document</title>
      <link>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108617#M4059</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;Hi:&lt;/P&gt;&lt;P&gt;&amp;nbsp; CONTENTS= is only an option for PROC PRINT, PROC REPORT and PROC TABULATE (and PROC FREQ multi-way tables). It does not work with graph procedures. You should be able to use NAME= and DESCRIPTION= on your action statement (like the CHORO statement). The doc is here: &lt;A href="http://support.sas.com/documentation/cdl/en/graphref/65389/HTML/default/viewer.htm#n0b7n2mnw4t6lhn0zoy86orv95z2.htm" title="http://support.sas.com/documentation/cdl/en/graphref/65389/HTML/default/viewer.htm#n0b7n2mnw4t6lhn0zoy86orv95z2.htm"&gt;SAS/GRAPH(R) 9.3: Reference, Third Edition&lt;/A&gt; for the CHORO statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; The NAME= value will be what you see in the GRSEG entry and, if you do make an ODS DOCUMENT, the NAME= value will be used to contruct the object name in the document store. So, if you had NAME='Mymap' in the code, the DOCUMENT object name will be something like:&lt;STRONG&gt; &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;\Gmap#1\Mymap1#1 &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;and then the DESCRIPTION= value would be the label used in the DOCUMENT store. DESCRIPTION= &lt;STRONG style="text-decoration: underline;"&gt;will&lt;/STRONG&gt; get rid of "Choropleth Map of..." in the SAS Results window and the PDF TOC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; But, using NAME= and DESCRIPTION= will &lt;STRONG style="text-decoration: underline;"&gt;not&lt;/STRONG&gt; get rid of the top level node that says "The GMAP Procedure" in the PDF table of contents. You would have to use ODS DOCUMENT to get rid of or rename the top level node. The Tech Support notes that I posted show how to change the node labels with PROC DOCUMENT syntax.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cynthia&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 29 Dec 2012 16:40:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108617#M4059</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2012-12-29T16:40:28Z</dc:date>
    </item>
    <item>
      <title>Re: PDF Multiple GMAPs into one Document</title>
      <link>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108618#M4060</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Cynthia, I believe the &lt;SPAN style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; background-color: #ffffff;"&gt;DESCRIPTION=&lt;/SPAN&gt; is what I was looking for.&amp;nbsp; I have noticed though that is I run the ODS PDF without exiting out of SAS, it appears &lt;SPAN style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; background-color: #ffffff;"&gt;the DOCUMENT object&lt;/SPAN&gt; continues to add maps and directories.&amp;nbsp; For example, the first time I run the code, it works perfectly, but the next time instead of having 2 maps for the 2 GMAP statements I am using, I have 4.&amp;nbsp; Then 6, then 8 and so on.&amp;nbsp; Is there a way to clear the prior results at run time?&amp;nbsp; I have tried using ods PDF newfile=proc; with no results.&amp;nbsp; Thanks again for all your help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Jan 2013 22:57:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108618#M4060</guid>
      <dc:creator>P5C768</dc:creator>
      <dc:date>2013-01-02T22:57:57Z</dc:date>
    </item>
    <item>
      <title>Re: PDF Multiple GMAPs into one Document</title>
      <link>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108619#M4061</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi:&lt;/P&gt;&lt;P&gt;You have 2 separate, but similar challenges:&lt;/P&gt;&lt;P&gt;1) your SAS/GRAPH job makes a GSEG entry EVERY time you run your code. It names the entries EVERY time by tacking a number onto the default name or whatever you specify for NAME=. So, a good practice is to close the GRAPH1 window and delete the GSEG entries before each run;&lt;/P&gt;&lt;P&gt;2) When you create your ODS DOCUMENT store, you should create it with an access of WRITE (not UPDATE), so that the DOCUMENT store will be overwritten and created new each time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; But philosophically, I probably wouldn't create the ODS DOCUMENT store -- every time you create the SAS/GRAPH output-- until the very, very, very end step in the process. I would get the graphs all working and then add the ODS DOCUMENT store syntax, with the appropriate "housekeeping" statements to make sure that the final job only runs once and creates the names that you need to have in the DOCUMENT store. Or else, if you need multiple graphs and multiple document stores, I would change the names, possibly with macro variables each time your job runs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; This Tech Support note shows you how to delete GSEG entries: &lt;A class="active_link" href="http://support.sas.com/kb/13/045.html" title="http://support.sas.com/kb/13/045.html"&gt;13045 - Unable to delete GRSEG entries from a graphics catalog using the displaymanager Results window.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you take care of the GSEG entries, then when you do make the document store (using WRITE access) you should have only the most current entries stored in the document store.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cynthia&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2013 05:54:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108619#M4061</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2013-01-03T05:54:35Z</dc:date>
    </item>
    <item>
      <title>Re: PDF Multiple GMAPs into one Document</title>
      <link>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108620#M4062</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you are careful you may find using the GOPTION GOUTMODE=REPLACE may be helpful. It helps to specify the GOUT catalog(s) in the graphic procedures and then specify the names. If everything starts empty the first time as you test the named items are replaced instead of continually incremented. Use a different NAME=for each call to a graphics procedure and watch the limits in length for names. If any are using by groups to create graphs then the name will be incremented and if you don't make the name short enough it may be difficult to sort out generated names. When I was spending lots of time with GREPLAY I usually used names of 6 or fewer characters to allow for the names to be numbered as I expected.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jan 2013 15:55:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Graphics-Programming/PDF-Multiple-GMAPs-into-one-Document/m-p/108620#M4062</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2013-01-03T15:55:25Z</dc:date>
    </item>
  </channel>
</rss>

