PI53182: IMS START-UP FAILS WITH ABENDU0016 / DFS1990I SID INITIALIZATIONFAILED WHEN MSNI1 / MSNI2 ARE USED ON MSNAME DEFINITIONS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Initial IMS start-up fails with abendU0016 / msgDFS1990I SID
  CONTROL BLOCKS INITIALIZATION FAILED when MSNAME MSNI1 / MSNI2
  are defined. In V9, IMS has been working just fine with the same
  MSNAME definitions.
  .
  DFSXCIC0-11/09/12-12.57KD10184 0                  +0236
  DFSIINB0+S203+DFSYSSP+1310+10/17/12               +00A2
  DFSAINB0+S203+SP53+1310+05/16/13PM86260 ABC       +0EC0
  DFSIINU0-10/17/12                                 +004C
  INITSID                                           +0088
  INUERROR                                          +????
  

Local fix

• Change SYSDEF input to change MSNIn / MSNSn to other names
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IMS V14 users having MSC MSNAME macro                    *
  * defined in the sysgen stage 1 definition.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Abendu0016 occurs in subroutine INITSID of DFSIINU0 because  *
  * an                                                           *
  * internal LNB with the same name was found.                   *
  *                                                              *
  * This is a forward fit of P51685.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
  ****************************************************************
  Customer has a MSNAME macro with the name of MSNI1 defined in
  the system stage 1 definition.
    The sysgen process creates 1 entry for the defined MSNI1
  msname.
    The sysgen process also creates another entry for MSNI1 as an
  internal msname for the logical link 1.
    The difference between the defined entry and the internal
  entry is that the defined entry does not have the CNT3SYS flag
  set (x'08').
    During an IMS initialization, the subroutine INITSID in
  DFSIINU0 is called to initialize the SID table.  A finddest is
  called to locate the LNB block with the name of MSNI1.
    The finddest finds the LNB block with the name of MSNI1 but
  this LNB has the CNT3SYS flag set.  Thus, the finddest is
  considered failing, leading to abendu0016 and MSGDFS1990I
  SID  BLOCKS INITIALIZATION FAILED.
  

Problem conclusion

• The sysgen macro PCHCOMC has been modified to add the checks for
  the reserved name to issue an MNOTE with G142 or G143 when it
  detects an invalid msname being specified in the sysgen stage 1
  definition.
  The sysgen macro PCHCOM1 has been modified to correct some
  comments of PCHCOMM1 to DFSCOMM1.
  
  DFSCKWD0 prolog has been updated to state that the command
  keyword tables in DFSCKWD0 and PCHCOMC should stay in sync with
  each other.
  
  Document changes:
  ****************************************************************
  ***
  Messages and Codes, Volume 2: Non-DFS Messages (GC18422000)
  ****************************************************************
  ***
  Add 2 new G messages:
  G142   MSNAME BEGINS WITH NUMERIC CHARACTER - msname
  
  Explanation
  
  The specified msname has been detected in the execution of the
  PCHCOMC macro during a stage 1 assembly as its name starts with
  a numeric character.
  
  msname: the label of the MSNAME macro in the sysgen stage 1
  definition.
  
  System action
  
  The NOGO switch is set and the stage 1 does not complete
  normally.
  
  Programmer response
  
  Correct the msname and attempt to rerun the stage 1 assembly.
  
  **************************************************
  
  G143   MSNAME IS A RESERVED NAME - msname
  
  Explanation
  
  The specified msname has been detected in the execution of the
  PCHCOMC macro during a stage 1 assembly as it matches with one
  of the following reserved words or one of the command keywords.
  
  
  - Starts with numeric character
  - BASICEDT
  - DBCDM  : starts with DBCDM
  - DBRC   : starts with DBRC
  - DFS    : starts with DFS
  - ISCEDT : starts with ISCEDT
  - MSDB   : starts with MSDB
  - MSNI   : starts with MSNI
  - MSNS   : starts with MSNS
  - SDB    : starts with SDB
  - SECURITY
  - WTOR   : starts with WTOR
  
  msname: the label of the MSNAME macro in the sysgen stage 1
  definition.
  
  System action
  
  The NOGO switch is set and the stage 1 does not complete
  normally.
  
  Programmer response
  
  Correct the msname and attempt to rerun the stage 1 assembly.
  
  
  ****************************************************
  System Definition                              (GC19422600)
  ****************************************************
  Modify the Label field description for the MSNAME macro as
  follows:
  
  Label field
  
  The label field msname is a one- to eight-character alphanumeric
  name used externally in commands. Link names, msnames,
  transaction codes, and logical terminal names, collectively,
  cannot contain duplicates. Specifying the msname label field is
  required.   |For further restrictions, refer to Resource naming
  rules.
  

Temporary fix

Comments

APAR Information

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

  PI51685

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

  UI34791

Modules/Macros

• PCHCOM1  PCHCOMC  DFSCKWD0
  

Fix information

• Fixed component name

  IMS V14

• Fixed component ID

  5635A0500

Applicable component levels

• R400 PSY UI34791

     UP16/01/29 P F601

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.