Sb37 Install Of Db2tools

book

Article ID: 50163

calendar_today

Updated On:

Products

CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA Mainframe Software Manager (Chorus Software Manager) CA MICS Resource Management CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Datacom/AD

Issue/Introduction

Description:

After downloading the product CA Insight Database Performance Monitor r15, or another large CA product, the installation fails. During the install at the unpax it stays on 'Please wait'. The install wizard is not yet showing.

The gimunzip fails with - INFO - Error occurred during GIMUNZIP

The log shows:

IEC030I B37-04,IFG0554A,D351692,STEP1,SYSPRINT,4C19,BPR101,X00CV02.R3.SYSPRINT...

SB37-X'4' occurred while processing data set X00CV02.R3.SYSPRINT on volume...

Cause: SYSPRINT runs out of space during the install.

Additional Information: This could also happen during install of any other large product packages

Solution:

MSM allocates the SYSPRINT output dataset initially with cyl(30,30).

The SYSPRINT file is closed and opened many times after an action, but not deleted.

Here the SMS management routines/management class kicks in at the first close and optimize/reduce the allocation to cyl(1,1).

The size is adjusted to the size of the first output file created.

Lateron however, during the receive and apply, this small allocation will cause the SB37 abend.

Check the SMS rules/routines and verify that no optimization rules are in place for these datasets.

Environment

Release:
Component: MSM