> >We tried bring up the address space related to WAS. One region was up > >but another control region BBOS001 ended up with an abend : > > BPXP018I THREAD 0CD6426000000000, IN PROCESS 83886280, ENDED 343 WITHOUT BEING UNDUBBED WITH COMPLETION CODE 4FDC3000, AND REASON CODE > > 000C0008. > >
Jags There is a good redbook on debugging WAS http://www.redbooks.ibm.com/redpapers/pdfs/redp6880.pdf It has details on how to go about debugging problems in WAS. For the BBO0024I message BBOO0024I ERRORS WILL BE WRITTEN TO CERR FOR JOB BBOS001. BBOO0024I ERRORS WILL BE WRITTEN TO string string. Explanation: WebSphere for z/OS will be using the indicated repository for logging errors. For file repositories,the file is obtained from the BBOERROR DD specification. If no such specification is provided, and a system logger stream has been specified, the log stream will be used for logging errors. If logging to the designated file or log stream can not be done, then CERR will be used for error logging. Note that CERR is equivalent to SYSOUT by default. There may be interesting messages in this file CERR for your issue. This may be a unix file. Lizette ---------------------------------------------------------------------- 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
