Hello, Thanks for your answer. I also found a useful link about my question: http://ebookbrowse.com/chapman-tasha-and-lori-carlton-using-sas-with-oracle-pdf-d394357638 Null values In SAS, any selection criteria that includes “not equals” (^=, <>, or ne), “less than” (< or lt), or “less than or equal to” (<= or le) will include null or missing values. For example, the criteria Where Language ne “English” will pull records where the language is Spanish, French, Chinese, or blank. However, this is not the case in Oracle SQL. In Oracle, a null value is non-existent. It doesn‟t equal or not equal anything. For this reason, comparison operators will not apply for null records. Where Language ne “English” in an Oracle SQL statement will only pull records where the language is Spanish, French, or Chinese. Blank or null records will be excluded. To include null records in the selection criteria, this must be stated explicitly, i.e., Where Language ne “English” or Language is null Regards, Andreas ... View more

Thanks for your answer. This can be a solution but there must be an option to produce automatically the logits. EM produces so much output that i cannot imagine that it can;t produce the logits. I hope someone can answer. A turnaround that i just thought is to produce the log odds (logits) using the sas code node in the utility tab. Since the probability of the primary event is reported i guess we can produce it by a data step using an assignment statement to produce log(prob_b1/(1-prob_b1)). The expression can be assigned to a variable called logit. Let us see if the automatic way is done! Thnaks again  ... View more