Having issues with DBC and DBO FFE abend related to SVC

Products

• Database Analyzer (IMS Tools)
• Mainframe Configuration Manager for IMS for z/OS
• IMS TOOLS - MISC
• Compress Data Compression (IMS Tools)
• Database Analyzer for IMS for z/OS
• Database Copier for IMS for z/OS
• Database Organizer for IMS for z/OS
• Mainframe Extended Terminal Manager (IMS Tools)
• High Performance Recovery for IMS for z/OS
• Database Organizer (IMS Tools)
• Mainframe Program Restart Manager for IMS for z/OS
• Secondary Index Builder for IMS for z/OS
• Secondary Index for IMS for z/OS

Issue/Introduction

Last time DBO and DBC jobs ran successfully was on Aug 5 2018 but all jobs are failing now with "FFE" abend.

Cause

Asked IBM about the Stage 2 SYSGEN and the default SVC of 254, and they stated DO NOT NEED to change the
SVC number in the STAGE 2 JCL. However..

It appears the vendor may need to make an update to support the changes introduced by these IMS APARs:
.
APAR Identifier ...... PI83450
DISABLE THE IMSCTF MACRO IN IMS 15.
.
PTF UI50511 available 17/10/05 - PE
.
APAR Identifier ...... PI88828
ABEND S18A AFTER INSTALLING PI83450/UI50511 DISABLE THE IMSCTF
MACRO IN IMS 15
.
PTF UI51310 available 17/10/30
.

Know IMS Tools had problems in this area as well. They do have fixes available:
.
FABLRTRF
APAR Identifier ...... PI90271
INTEGRICY CHECKER DOES NOT WORK CORRECTLY AFTER IMS V15 APAR
PI83450 IS APPLIED
.
PTF UI52819 available 17/12/22
.
FABLRTRF
APAR Identifier ...... PI95061
INTEGRITY CHECKER : PREVENTIVE APAR FOR IMS V13 PI81325, V14
PI85816, AND V15 PI85817
.
PTF UI55289 available 18/04/24 

Resolution

Yes, there were cases where our IMS Tools did not use SVC numbers the new way, but used the old one, which was usually correct (customer had some SVC number before,
that number got left in now obsolete location, but the new location had the same number), but not if customer chose new SVC number – in that case customer needs to install these fixes:

SO03627
SO04747
SO04748