Many thanks for the responses to my query.
Based on these I changed all the SYSOUT statements for the WebSphere PROCs from
SYSOUT=*,SPIN=UNALLOC,FREE=CLOSE to SYSOUT=H. WebSphere came up fine. I
reverted back to the previous SYSOUT syntax and WebSphere came up fine again.
I have no real idea of what's going on. There are two of us working on this
box and between 1630 when I left yesterday and 0700 today no one was on and the
only thing going on is DB2 activity for our automated testers.
I am suspicious though, in that I am seeing JES2 resource shortages:
£HASP050 JES2 RESOURCE SHORTAGE OF TGS - 94% UTILIZATION REACHED
£HASP050 JES2 RESOURCE SHORTAGE OF JQES - 89% UTILIZATION REACHED
On another system (z/OS 1.4) I've seen output behave "strangely" (not as I
would have expected) with JES shortages, but nothing like this (z/OS 1.6).
Don't know that this is the cause, but at this point I have no other
explanation.
So, for now WAS is back up, but I don't really know why, which isn't a really
good feeling. But, if it happens again I'll know to modify the JES STC
processing options to make sure I can get any and all output.
Thanks again,
www
-----Original Message-----
From: William Walsh
Sent: 06 December 2005 15:01
To: 'IBM Mainframe Discussion List'
Subject: START fails no diagnostics!
Have you ever seen a situation where the START command is issued, but the
address space fails with no diagnostics:
05340 13:30:58.39 WWALSH 00000290 START
BBO6ACR,JOBNAME=BBOS001,ENV=CPAC.CPAC.BBOS001
05340 13:30:58.44 00000090 IRR812I PROFILE BBO6ACR.* (G) IN THE
STARTED CLASS WAS USED 561
561 00000090 TO START BBO6ACR WITH JOBNAME
BBOS001.
05340 13:30:58.45 STC09920 00000281 £HASP100 BBOS001 ON STCINRDR
05340 13:30:58.53 STC09920 00000290 IEF695I START BBO6ACR WITH JOBNAME
BBOS001 IS ASSIGNED TO USER ASCR1
, GROUP WSCFG1
05340 13:30:58.53 STC09920 00000090 £HASP373 BBOS001 STARTED
05340 13:30:58.53 STC09920 00000281 IEF403I BBOS001 - STARTED - TIME=13.30.58
05340 13:30:58.62 STC09920 00000090 IEF404I BBOS001 - ENDED - TIME=13.30.58
05340 13:30:58.63 STC09920 00000281 £HASP395 BBOS001 ENDED
I see nothing on the JES2 queues for this address space. I have checked the
WebSphere logger data, the WebSphere server1/logs filesystem, and EREP and
cannot find any reason for this. It was working on Friday and we cannot
identify the change that has caused this. I noticed the X33E SLIP trap being
met following the end of BBOS001, but turning it off doesn't produce any
additional information. I don't know LE, but tried adding the TRACE(ON,LE=3)
parm to the BBOCTL program, but that didn't provide any results. The system
dump datasets are empty.
I can unmount the /WebSphere/V6R0 filesystem to force a JCL error and I tried
creating a new WAS config file system. I can run this JCL as a job until I
fail on a security issue.
Any ideas?
Thanks,
William
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank you.
----------------------------------------------------------------------
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
