IBM Support

Application Minor Node goes into a RESET state upon activation

Troubleshooting


Problem

Application Major Node with 9 minor nodes is activated. 8 of the minor nodes come up in a CONCT state as they should and 1 minor node comes up in a RESET state.

Symptom

Display of the Application Major Node shows the minor node in a RESET state:
D NET,ID=Appl_major_node,E
IST075I NAME = Appl_major_node , TYPE = APPL SEGMENT
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST360I APPLICATIONS:
IST080I APPL1 CONCT APPL2 CONCT APPL3 CONCT
IST080I APPL4 CONCT APPL5 CONCT APPL6 CONCT
IST080I APPL7 CONCT APPL8 CONCT APPL9 RESET
IST314I END

Cause

A model application was also defined. Before the predefined Application Major Node was activated, APPL9 issued an OPEN ACB to VTAM. A dynamic application was built from the model definition with the same name as the predefined APPL name. When a dynamic application is already active to VTAM, the predefined APPL with the same name will go into a RESET state upon activation.

Diagnosing The Problem

IST1700I NAME CONFLICTS WITH DYNAMIC APPL will be seen in the log when the Application Major Node is activated if there is a dynamic application already open by the same name.

Resolving The Problem

The Application Major Node must be activated before the application issues an OPEN ACB if there is a model APPL definition for the same name. VTAM will prefer the predefined application over the model definition when the OPEN ACB is issued if the predefined APPL is in a CONCT state.

[{"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"All","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"1.9;1.10;1.11;1.12;1.13;2.1;2.2","Edition":"All Editions","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
15 June 2018

UID

swg21316619