Just out of curiosity I let Google play with the abend and as usual it found a 
couple of answers. Maybe something is applicable under the hood of your system. 

I read in the papers last week that Google is about to know everything there is 
to know, so soon...

Kees.


AABEND BB7 (U2999)

Explanation: An ACTEST user issues the ABEND command. SOLVE:TCPaccess 
terminates with a dump.

Action: None, if the ACTEST user intended to terminate SOLVE:TCPaccess. If 
ACTEST is not protected by command security and a curious user entered the 
command (and terminated SOLVE:TCPaccess), the system programmer responsible for 
SOLVE:TCPaccess might consider implementing command security for ACTEST.

Quite similar:
--------------
AABEND BB7 (U2999) 
 
Explanation    An ACTEST user issues the ABEND command. Cisco IOS for S/390 
terminates with a dump. 
 
Recommended Action    None, if the ACTEST user intended to terminate Cisco IOS 
for S/390. If ACTEST is not protected by command security and a curious user 
entered the command (and terminated Cisco IOS for S/390), the system programmer 
responsible for Cisco IOS for S/390 might consider implementing command 
security for ACTEST.

--------------

The V7 Spawner program on MVS may fail with the following errors:

OMVS SEGMENT NOT DEFINED.
+LSCX041 **** ERROR ****
IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=SPAWNER , ASID=0079.
+        ABEND occurred in     MAIN(VSOCKET),offset 000DE8
+        Program terminated by operating system. ABEND code = U2999
+Calling trace:
+    Function        Line    Offset    Context
+    MAIN(VSOCKET)   ----    000DE8
IEF450I SPAWNER SAS7 SAS7 - ABEND=S000 U2999 REASON=00000000 986
ICH408I JOB(ASCHINT ) STEP(        ) 987
  BX29RJ.SPAWNER.JOBLOG CL(DATASET )
  INSUFFICIENT ACCESS AUTHORITY
  ACCESS INTENT(UPDATE )  ACCESS ALLOWED(NONE   )

This problem will occur if SECACPT=CONV is set in the APPL defintion of
the LU used to launch the OS/390 spawner transaction program.

To correct the problem, set SECACPT=ALREADYV.

-----------------


OA28604: ABENDU2999 IN CIKICSVC 
A fix is available
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
ABEND u2999 in CIKICSVC at offset x'174e' caused by a
SVC 11 (x'b') which has an out of range value in register 15.
Local fix
KEYWORDS: u2999 2999 CIKICSVC TICSVC SVC B
AB0C4 ABEND0C4 ABEND0C6 AB0C6

---------------------




-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Paul Schuster
Sent: Saturday, September 06, 2014 02:58
To: [email protected]
Subject: abend code BB7 ?

Abend code BB7 does not seem  to be documented in the System Codes manual, even 
at the z.os 2.1 level.  As in:

IEC615I ABEND=000BB7-00001101 OCCURRED IN THE (nameremoved) EXIT MODULE FOR 
DYNAMIC EXIT IGGPRE00_EXIT

The IEC615I message only indicates that abend  000BB7-0000110 occured in exit 
routine (nameremoved) .

Is this not documented on purpose, or has the manual not caught up with Dynamic 
Exits?  Does anyone know what the BB7 abend is caused by? 

Thank you.

Paul

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN
********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************
                        


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to