Great walk-through. One thing though, your last section says that the proc cas makes an astore file. I don't see how or where it creates an astore that can be used for deployment. It only creates a table in a session-scoped caslib that goes away when the session is over - thus, it is not deployable or portable as far as I can tell. Am I missing something and if so, can you explain more about the deployment piece? Deploying the model is arguably the most important part! To do that, I had to run "proc astore" to actually create the .astore file. Once I did that, I was able to bring the model into model manager (via import of the .astore).
... View more