BPXP023I for thread in the sysview main address space

Products

• SYSVIEW Performance Management
• NXBRIDGE - SYSVIEW/ENDEVOR

Issue/Introduction

Receiving the following messages from an unix initiator (BPXAS) with the same name as the Sysview address space
(since the STC name has 8 bytes and there was no space for the number we usually see for forked processes to another address space):

IEA989I SLIP TRAP ID=XEC6 MATCHED. JOBNAME=SYSVIEW, ASID=xxxx.
BPXP023I THREAD 2FBC480000000000, IN PROCESS 67371240,
     WAS TERMINATED BY SIGNAL SIGKILL,
     SENT FROM THREAD 2FC0280000000000,
     IN PROCESS 84148452, UID 2000061, IN JOB SYSVH120.
IEF450I SYSVIEW STEP1 - ABEND=SEC6 U0000 REASON=0000FF09

Environment

Release:
Component: SYSVW

Resolution

Check if PTF SO04675 (Feature ptf 9) is applied.
Prior to SO04675, SYSVIEW was creating a BPXAS Open MVS Transaction (OTX) to do some UNIX work on behalf of the JVMDATA subtask in SYSVIEW.
Once the work was complete we were issuing a SIGKILL for it. Not the best solution.
With SO04675 and after, we are issuing a SIGTERM, thus you will not see these message as a SIGTERM is a much more normal event that does not produce these messages, which are causing the automation to be confused with the naming conventions.