IBM Support

PK33983: SM FAILS TO INITIALIZE WHEN STARTUP PARMS ARE INVALID

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If there is a error in IMSSM init parameters ( or the member is
    missing in the proclib ), IMSSM attempts to initialize with
    default parameters. Because the default parameters were invalid,
    various messages were received that did not point to the
    problem.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IMSSM.                          *
    *                 If there is  error in IMSSM control region   *
    *                 init parameters ( or the init member is      *
    *                 missing in the proclib ), IMSSM initializes  *
    *                 with default parameters.                     *
    *                 The default parameters to start IMSSM in     *
    *                 control region are:                          *
    *                    XCF group name  - GJEISM01                *
    *                    XCF member name - IMS JobName||MVS sysid  *
    *                    DC job name     - blanks                  *
    *                    min/max LDBs/SDBs- 20/40                  *
    *                 After IMSSM is initialized with default      *
    *                 parameters, it can be stopped and            *
    *                 resinitialized with the intended             *
    *                 parameters, using the following DC commands: *
    *                  F dcjobname,stop sm                         *
    *                  F dcjobname,reinit sm                       *
    *                 DC has to be started  in the default XCF     *
    *                 group GJEISM01.                              *
    *                 There is an error in the code that sets the  *
    *                 default parms resulting in different         *
    *                 errors appearing:                            *
    *                 GJE2040E IMS SYSPLEX MANAGER ESTAE CREATE    *
    *                 FAILED, RC=20FD3681. ID51                    *
    *                 The message for error in init parameters     *
    *                 does not show.                               *
    *                 The message for initializing with default    *
    *                 parameters does not show.                    *
    *                                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: There is an error in the code that      *
    *                      sets the default parms resulting in     *
    *                      different errors appearing:             *
    *                      GJE2040E IMS SYSPLEX MANAGER ESTAE      *
    *                      CREATE FAILED, RC=nnnnnnnn. IMSid       *
    *                      The message for error in init           *
    *                      parameters does not show.               *
    *                      The message for initializing with       *
    *                      default parameters does not show        *
    ****************************************************************
    * RECOMMENDATION: Install the fix and reinit IMSSM in control  *
    *                 region.                                      *
    ****************************************************************
    Programs have been fixed to issue the correct messages.
    The control region has to be reinitialized after the
    APAR/PTF is installed.
    

Problem conclusion

  • Programs have been fixed to issue the correct messages.
    The control region has to be reinitialized after the
    APAR/PTF is installed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK33983

  • Reported component name

    IMS SYSPLEX MGR

  • Reported component ID

    5655P0100

  • Reported release

    120

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2006-11-01

  • Closed date

    2006-11-03

  • Last modified date

    2006-12-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UK19394

Modules/Macros

  • GJEIIPMX GJEIIPM8 GJEIIPM9
    

Fix information

  • Fixed component name

    IMS SYSPLEX MGR

  • Fixed component ID

    5655P0100

Applicable component levels

  • R120 PSY UK19394

       UP06/11/07 P F611

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.2.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX8AA","label":"IMS Sysplex Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.2.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 December 2006