In article <[EMAIL PROTECTED]> you wrote: > Sorry, I should have mentioned that the security softare is CA-TSS. Not > Walt's > problem!
> For completeness, the socket application is implemented via SAS/C and its > socket > library and the stack is Interlink/Sterling/CA's. Makes problem determination > more challenging. > > > > I don't own stock in any breweries. In cases where we know that OMVS is needed, the SAS/C library will issue a querydub call and give back (I believe) an error that should point to the problem. It's not possible to get control in all cases though and I've had to look at way more dumps than I should have. Forcing a default OMVS segment sounds like a great idea to me. In looking over what we do, I came across this amusing tidbit in the doc that I hadn't seen before: "However, in the event of mysterious problems with UNIX Systems Services facilities (especially TCP/IP), this information might clarify the nature of the problem." -- Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive [EMAIL PROTECTED] (919) 531-5637 Cary, NC 27513 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
