If you have problems moving datasets between computers, trying using PROC CPORT to create a transport file.  If all else fails, dump the dataset contents to a flat file then reimport it. ... View more

When you say combine, do you mean concatenate? Are the current values text or numeric? ... View more

Need more info to help, first off, did you mean SET in the second line? Where/how was the original dataset created? ... View more

An XML map can only be used to create an XML file from a single dataset. If you import into multiple datasets, you will need to create your export process. Hopefully the SAS XML facility to add functionality, but until then you are on your own. ... View more

No, XML Mapper does not support this. I would try importing each xsd, save the corresponding maps, then combine them in a text editor. It would probably also be helpful to create a map from a sample XML file as a reference. ... View more

Thanks the tips!  I will certainly try these out.  When I looked at my project settings, I found that the code submission action was set to "Continue execution".  I do not recall ever seeing that setting before, but the project was initially created in EG 7.100.  Perhaps that setting persisted from the prior version.   When I created a new project in 7.13, it did default to "Stop current brach". ... View more

I tend to agree with you @LinusH, but it is being pushed more and more as a development tool, and we all know how easy it is for something to start adhoc, and turn into something more.   I have had some success with linking directly between the "work" nodes instead of linking from an output to the next node.  Unfortunately, that is not default behavior, making it quite tedious.   This is another situation where it would be helpful to have a process flow stop in its tracks on a failure.  That is currently also tedious to implement. ... View more

Forecaster, We have the scenario of different end dates, and simply cater to the longest horizon then discard the unwanted periods.  The differing start dates is trickier to use Forecast Studio with.  It wants everything to have the same start date in the same project.  As Udo suggested, going straight to the forecast procedures is an option.  If you have a strong desire to utilize Forecast Studio, then the only method I can think of is to have fake time periods. This would require some pre-processing of the data to make all the history end in the same period, call it period 0.  You would need to store a reference dataset outside of Forecast Studio that detailed what period 0 was for each time series.  As long as the leading values are missing (before history is available), then those periods should be safely ignored by the model.  You would still need to forecast to the longest horizon as I described above. This approach could prove confusing, but workable as long as you are not reconciling to the hierarchy or have different time intervals. Sounds like a good challenge. ... View more

Thanks Jaap.  I mapped out all the references to different autoexecs and configuration files, but could only find the definition to be max.  I am leaning towards your options f or g, especially after a text search of the configuration directories and SAS installation did not turn up anything else.  When I use EG to connect to the SASApp workspace server, I get 102, but when I connect to SASMeta it picks up the max setting. Sounds like it is time to open a track. Thanks, Ryan ... View more