I have a Stored Process which I display in the SAS portal. When I display two or more proc reports or graphics there is always a horizontal line displayed between two of them. When I view the created HTML code there is .
And this paper from NESUG shows how to use a customized template with a stored process: http://support.sas.com/rnd/papers/regional08/SP_Template.pdf (even though the paper talks explicitly about tagset templates, the same general rules apply for defining the item store, writing the template to the item store, etc.
In your case, you would NOT be creating a tagset template, so your _ODSDEST reserved parameter would NOT change. However, your _ODSSTYLE parameter would change. If your company is using CSS files instead of SAS Style templates to style your stored processes, then a CSS solution, may work for you, as described here: http://support.sas.com/kb/23/630.html
If you need more help with this task, I suggest you contact Tech Support.
Also see my NESUG paper link in the first posting. Your item store must be in a WRITEABLE location on your server (default name SASMAIN). Generally the best place is down under the LEV1 directory where the format library and macro autocall library are located, so that your code needed by SAS stored processes is all in one general vicinity for backup and maintenance purposes.
You will need the ODS PATH statement, but you will also need a "hard-coded" LIBNAME statement for this server location for the template item store. You cannot use the META libname engine to point to the template location. Without an ODS PATH statement, PROC TEMPLATE is trying to write to SASUSER.TEMPLAT, which is probably not available, or if available, not writeable on your SP server.
Another alternative would be to define your template in the WORK location it would have to be done in your SP and done BEFORE the %stpbegin. But, that also means no other SP could use that same style without having the same Proc Template code in the SP itself. So this is really not a long term solution.
You might want to work with Tech Support on this issue, as they could follow your track from beginning to end until you get everything working.