zMC STC Hangs at Shutdown

Technote (troubleshooting)


Problem(Abstract)

zMC Management Console started task did not shutdown in a normal fashion and it hangs.

Symptom

Messages seen in the Started Task output/Joblog for Mgmt Cons v410 (zMC) on z/OS 1.10 follow:

...BPXP018I THREAD 18DC700000000002, IN PROCESS xxx1627,ENDED WITHOUT BEING UNDUBBED WITH COMPLETION CODE 0000012C, AND REASON CODE 00000000.
...BPXP018I THREAD 18DB900000000000, IN PROCESS xxx1627,ENDED WITHOUT BEING UNDUBBED WITH COMPLETION CODE C000012C, AND REASON CODE 00000000.

...zMCtaskname IEF450I zMCjobname zMCstepname step - ABEND=S000 U0300 REASON=00000000

Cause

TCP/IP goes away but it is required for zMC eventhough the requirement may not be explicitly stated in product documentation.


In this example, TCP/IP is running as expected then TCP/IP is shutdown causing a shutdown to be issued for BPXtask resulting in BPX threads ended without 'undubbing' and the threads did not exit cleanly and disconnect from z/OS. In addition, the IEF450I zMCjobname [procstep] stepname step abnormally ends and System ends the job.

These actions result in the UNDUBBED messages with COMPLETION CODE 0000012C, and REASON CODE 00000000 plus Abend=S000 U0300 REASON=00000000 cited above in the Symptom section.

The BPXP018I message says that the thread or TCB was undubbed or undetached gracefully. The completion code 12C means that an abend occurred in a fork exit and during processing the system found that the specified subtask had not completed processing. OMVS creates the BPXP018I message and OMVS requires TCP/IP, so effectively TCP/IP is required for zMC eventhough the requirement may not be explicitly stated in product documentation.


Resolving the problem

Maintain the Shut-down and Start-up sequence for zMC and TCP/IP because zMC (z/OS Management Console) requires TCP/IP. Add the prerequisite of TCPIP to the zMC Started task in OPS/MVS which then requires the STC for zMC shut-down before TCPIP and z/MC start-up after TCPIP is initialized. This could be added for any and all IP stacks being used on the LPAR.


In addition, if z/MC connects to the TEMS and TEPS then TCP/IP is required for connectivity and correct operation. Page 44 of zMC Planning and Config guide, (URL good 8/2012), GC32-1954-00, points out the need for TCPIP - snippets from Pg 44 follow below:

Requirements for TCP/IP communication protocols... Review the following TCP-related requirements before you configure OMEGAMON z/OS Management Console.

Default OMVS segment... To use the TCP/IP communication protocols, a Tivoli Enterprise Monitoring Server on z/OS requires a default OMVS segment. See the z/OS Communications Server IP Configuration Guide,(URL good 8/2012), SC31-8775-11, Pages 63-65, beginning with the Section for Requirement for an OMVS segment for an explanation of how to provide an OMVS segment.


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM OMEGAMON z/OS Management Console

Software version:

4.1.0

Operating system(s):

z/OS

Reference #:

1447319

Modified date:

2012-08-03

Translate my page

Machine Translation

Content navigation