Below code works when executed in SAS EG. The SAS Server is on a Unix AIX and is version is 9.13. However when I convert the code into a Stored Process using EG wizard and cut and past the same code ... it seems not to display the gif picture and it will only display the dataset and replace the picture with an X.......
I have tried changing the location of the gif file and placed it on a sever folder on where is it accessible (has read permission) to all SAS USERS.
If you need immediate or urgent then you should open a track with SAS Tech Support.
Generally speaking, an image that is used with ODS either has to be available when the result file is opened (ODS HTML) or has to be available when the result file is created (ODS RTF and ODS PDF). With a stored process the image has to be inserted into a result type that supports ODS ESCAPECHAR capability and the use of the PREIMAGE attribute. In addition, IF image insertion will work, the image has to be accessible (on the network) from the machine which serves as the Stored Process Server and/or Workspace Server, depending on where your Stored Process (SP) executes.
AND, images that are meant to be used with Web Report Studio (for example) -MUST- be registered in the Metadata. So, I would not expect your stored process with PREIMAGE in the TITLE statement to work at all in Web Report Studio.
Also, you are using ODS ESCAPECHAR in your TITLE statement to insert the preimage image -- this capability does not work in the LISTING destination, for example and may not work if your stored process results use SASReport XML as the result format. So even though you say that the preimage works in SAS EG -- that might be because EG sometimes uses HTML as default result output. However, other client applications use SASReport XML as the result format and some ODS ESCAPECHAR capabilities might not work with SASReport XML result format.
So, that's really several different possibilities for the -cause- of your issue and the best way to determine which one of the possibilities applies in your case might actually be to contact SAS Tech Support. They can look at ALL of your code and look at the client applications and result types that you're using and come up with a possible solution, if there is one.