LISTBC may be getting run by your logon proc or some such, which makes getting additional info difficult. Once you're logged on, try typing LISTBC yourself. ? should work then.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: John Norgauer <[email protected]> To: [email protected], Date: 09/16/2014 10:09 AM Subject: Re: MSG IKJ56961E LISTBC TERMINATED Sent by: IBM Mainframe Discussion List <[email protected]> For some reason, there was no dynalloc return / reason code displayed. This is the text of the message: THE MESSAGE LOG COULD NOT BE ALLOCATED.+ The + sign indicates that there is additional info available, but I can not get that info. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Anthony Thompson Sent: Monday, September 15, 2014 5:19 PM To: [email protected] Subject: Re: MSG IKJ56961E LISTBC TERMINATED The full IKJ56961E message should have supplied dynalloc return / reason codes, which the OP didn't supply but would have helped. Skip may have it right with regards to SYS1.BRODCAST, but the OP should check his IKJTSO member is see if TSO/E userlogs are being used instead (SEND statement, USERLOG parameter). Given that 'many volumes were eliminated', it may be that his private TSO/E userlog was trashed, and the SMS ACS routines crippled to the point a new one can't be allocated (check the form of the TSO/E USERLOG filename, if used, and throw it through a SMS ACS test case). Ant. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Skip Robinson Sent: Tuesday, 16 September 2014 5:59 AM To: [email protected] Subject: Re: MSG IKJ56961E LISTBC TERMINATED My first inclination was to say that SYS1.BRODCAST had resided on a volume that was removed. Then I remembered this line in MSTJCLxx: //SYSLBC DD DISP=SHR,DSN=SYS1.BRODCAST which would make IPL pretty dicey. Then it occurred to me that as long as the data set it cataloged, maybe the system doesn't really look for it until LISTBC needs to do I/O. So do LISTCAT on SYS1.BRODCAST . If the volume is missing, that's the problem. Otherwise, check for a personal 'userlog' data set cataloged to a missing volume. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: John Norgauer <[email protected]> To: [email protected], Date: 09/15/2014 11:03 AM Subject: MSG IKJ56961E LISTBC TERMINATED Sent by: IBM Mainframe Discussion List <[email protected]> Getting this at TSO logon time. This is on a test LPAR which had many volumes eliminated(because of clean-up). Any thoughts as to identifying the volume? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
