DFS3600I UNABLE TO INITIALIZE EXTERNAL SUBSYSTEM(S) - member, RC=mm, JOBNAME=JJJJJJJJ


or

SUBSYSTEM DEFINITION SPECIFICATION ERROR FOR SSM = member, JOBNAME=JJJJJJJJ

or

STMNT (nnn), 'xxxxxxxxxxxxxxxxxxx' (yyyyyyyyyy)

or

STMNT (nnn), (DB2AF DEF INVALID FOR DEP REG)

or

STMNT (nnn), KEYWORD 'xxxxxxxxx' (yyyyyyyyyy)

Explanation

IMS found an error while processing the External Subsystem PROCLIB Member (SSM). The member name consists of the 4-byte IMSID followed by the 4-byte SSM parameter. The SSM parameter is specified either as an execute parameter in the member, DFSPBxxx or on the /START SUBSYS SSM xxxx command. The JOBNAME value where applicable specifies the job name of the region where the error was detected. At least one of three versions of the DFS3600I messages is displayed depending on the type of error. The versions are the following:
  • UNABLE TO INITIALIZE
    This message indicates that IMS found an error which prevented the PROCLIB member from being processed. Any external subsystem defined in the member is not connected to IMS. The character string, member, indicates the name of the PROCLIB member which was being processed. The value mm is one of the following return codes:
    Code (hex)
    Meaning
    04
    A failure occurred while attempting to read the PROCLIB member. Ensure the member name specified is correct and resides in PROCLIB.
    08
    Storage could not be obtained for a buffer to contain the PROCLIB member statements.
    0C
    Storage could not be obtained for an external subsystem definition element.
    18
    The PROCLIB member did not contain any valid subsystem definitions.
    Note: If RC=18 is received from a dependent region, the SSM= parameter might point to a PROCLIB member which contained no entries. This problem prohibits the dependent region from any subsystem connections. In this case, this message is for information only. The dependent region initialization continues normally.
  • SUBSYSTEM DEFINITION SPECIFICATION ERROR
    If one or more errors were found while processing an external subsystem definition, then this message is issued. The variable member, indicates the name of the PROCLIB member which was being processed. For each definition error, a message is issued to indicate which statement was in error and the text in error. One STMNT error message is issued for each error in the PROCLIB member. Multiple errors in a single statement produces multiple messages. The value nnn is the statement number within the member. The character string xxxxx is the text in error. If the character string, KEYWORD, precedes the error text, then the error text represents a keyword parameter. The character string yyyyyyyy is one of the following error reason codes:
    OMITTED
    A required parameter was omitted from the external subsystem definition. The subsystem definition is found to be invalid, therefore, a subsystem connection is not established.
    IGNORED
    A parameter is specified in the external subsystem definition which is not applicable to the type of subsystem being defined. This parameter is ignored and processing continues. If the rest of the subsystem definition is valid, a subsystem connection is established at the appropriate time.
    INVALID
    The error text represents invalid data in the subsystem definition statement. If the character string, KEYWORD, precedes the error text, then the value for the parameter was invalid. Otherwise, the error text represents data that could not be interpreted as part of a subsystem definition. The subsystem definition was found to be invalid, therefore, a subsystem connection is not established.
    DUPLICATE
    A specific value for a parameter was specified for more than one subsystem definition. The subsystem definition is considered invalid and is ignored. All SSN parameter values must be unique within a member.
  • DB2AF DEF INVALID FOR DEP REG

    An SSM parameter was provided to the dependent region job; the parameter identified the PROCLIB member that included a definition for a DB2 subsystem to be accessed with the DB2 Attach Facility. This definition is unavailable in an MPP or BMP region and is ignored. Processing continues. Definitions for the DB2 Attach Facility can only be provided to the control region in the SSM parameter.

System action

If the UNABLE TO INITIALIZE message is displayed, IMS external subsystem initialization processing failed. None of the external subsystems defined in the member are connected to IMS.

If a statement is processed and an error occurs that causes the subsystem definition to become invalid, then that external subsystem are not connected to IMS.

Programmer response

Correct the errors in the SSM PROCLIB member.

For UNABLE TO INITIALIZE errors, use the /START SUBSYS SSM command to start the external subsystem initialization process, which starts all valid subsystems defined in the member.

For STMNT errors, use the /START SUBSYS command to start one or more external subsystem connections.

Problem determination

1, 3, 34 and save the SSM PROCLIB member