Messages XS6600 through XS6699

BBI/XS SRB ROUTINE ABENDED xxxxxxxx

Explanation: A BBI multiple-system support SRB routine ABENDed for some reason. The xxxxxxxx field will contain the target region name if available. This field will appear as '*' if the target region is the SS address space itself. A software record is logged to SYS1.LOGREC.

User response: Try and determine why the SRB may have abended. If the target region was experiencing problems at the time, that may have caused the failure. If the abend occurred for no apparent reason then contact BMC Software Customer Support after obtaining Logrec information. Sample job LOGRECS in BBSAMP can be used for this purpose.

BBI SOFTWARE RECORD LOGGED TO LOGREC

Explanation: A BBI multiple-system support SRB routine ABENDed and a software record was logged to the SYS1.LOGREC dataset.

User response: Contact BMC Software Customer Support after obtaining Logrec information. Sample job LOGRECS in BBSAMP can be used for this purpose.

SDWA EXTENSION WAS UNAVAILABLE

Explanation: A BBI multiple-system support SRB routine ABENDed and a software record was logged to the SYS1.LOGREC dataset. The SDWA extension was unavailable to the routine recording the error and therefore no eyecatcher could be written.

User response: Contact BMC Software Customer Support after obtaining Logrec information using EREP or BBSAMP member LOGRECS.

MVIMS/XS SRB ROUTINE TIMED OUT

Explanation: An OLT multiple-system support SRB routine has executed for longer than 15 seconds. This could be due to a looping routine or to the target address space being non-dispatchable. A software record will be written to the SYS1.LOGREC data set.

User response: Contact BMC Support and have the following documentation available:

• The S/390 release level, IMS release level, MAINVIEW product PUT level (browse BBLINK member BALPUTLV)

• LOGRECS for the time period several hours before and after this message

• Any SVC Dumps produced by IMS or the PAS

• JES job log/jcl for the IMS Control Region and the PAS

MVIMS/XS SRB ROUTINE RETRY WILL BE ATTEMPTED

Explanation: This message is preceded by XS6603E, SRB routine timed out. OLT will re-issue stimer and wait for SRB service completion.

User response: Contact BMC Support if a wait is being caused in the TS that requested the SRB service.Please have the follwing documentation available:

• The S/390 release level, MAINVIEW product PUT level (browse BBLINK member BALPUTLV)

• LOGRECS for the time period several hours before and after this message

• Any SVC Dumps produced by MV product address space (PAS)

• JES job log/jcl for the PAS

BBI/XS SRB ROUTINE TIMED OUT xxxxxxxx

Explanation: A BBI multiple-system support SRB routine has failed to be scheduled within 15 seconds. This may be due to the target address space being non-dispatchable for some reason. The xxxxxxxx field will contain the target region name if available. This field will appear as '*' if the target region is the SS address space itself. Standard cleanup routines proceed during recovery.

User response: If this occurs infrequently it is not of great concern. However, if it occurs often, it may indicate that the target address space is running at too low dispatching priority.

BBI/XS SRB ROUTINE RETRY WILL BE ATTEMPTED

Explanation: This message is preceded by XS6605E, SRB routine timed out. BBI will re-issue stimer and wait for SRB service completion.

User response: Contact BMC Support if this is causing a wait in the TS that requested the service.

REQSESS ULTIMATELY NOT ACCEPTED BY PLU

Explanation: A Notify RU was received from VTAM indicating that the REQSESS request originally accepted by VTAM, is now rejected by VTAM. The connection is not established.

User response: This is normally caused by a VTAM problem.  If the problem persists contact your local BBI support representative.

BBI CONNECTION TERMINATED FOR xxxxxxxx

Explanation: A Cleanup RU was received from VTAM. The connection with xxxxxxxx is terminated.

User response: Contact BMC Software Customer Support.

CLSDST FAILED - NEGATIVE RESPONSE FROM VTAM

Explanation: VTAM called the BBI TERMSESS exit. BBI issued a CLSDST macro, as required when this exit is called. VTAM returned a negative response return code. This message was probably the result of VTAM performing a QUICK shutdown. During a QUICK shutdown, BBI closes its ACB immediately. If VTAM schedules lostterm at the same time, the ACB will be closed before the CSLDST macro is issued, causing VTAM to issue the negative response.

User response: No action is required.

BBI/XS XMEM SERVICE xxxxxxxx ABEND yyyy

Explanation: An abend occurred while executing a service.

• xxxxxxxx - is the service module name.

• yyyy - is the system or user abend code.

User response: Obtain dump and logrec report. Contact BMC Software Customer Support.

BBI/XS XMEM SERVICE DISABLED

Explanation: An abend occurred in the cross memory service routine. Check accompanying message XS6621E. The service routine is disabled.

User response: Obtain dump and logrec report. Contact BMC Software Customer Support.

BBI/XS XMEM RECOVERY IN PROGRESS

Explanation: An abend occurred in the cross memory service routine. Recovery is in progress. The service routine is disabled. This message should be accompanied by XS6621E and/or XS6622E.

User response: Obtain dump and logrec report. Contact BMC Software Customer Support.

BBI/XS XMEM ECSA-GETMAIN XMEMW FAILED, REQUEST IGNORED

Explanation: The cross memory service routine could not obtain storage required in ECSA. The request is ignored and the service requestor is notified.

User response: Ensure that there is sufficient ECSA available in the system for a request of approximately 4K. If there is, contact BMC Software Customer Support.

BBI/XS XMEM REQUEST TIMED OUT

Explanation: The cross memory service routine detected a possible loop while executing a service routine. The service is terminated with a U3920 abend code.

User response: Contact BMC Software Customer Support.

BBI/XS SHOULD NOT OCCUR CASE xx ENCOUNTERED

Explanation: The cross memory service routine detected a should not occur event. The service is terminated with a U3921 abend code

User response: Contact BMC Software Customer Support.

BBI/XS XMEM FREEMAIN XMEMW FAILED

Explanation: The cross memory service routine was unable to FREEMAIN the GETMAIN'd ECSA work area. Continue process.

User response: Contact BMC Software Customer Support.