Unmatched User Of NETVIEW.
search cancel

Unmatched User Of NETVIEW.

book

Article ID: 48461

calendar_today

Updated On:

Products

Cleanup Datacom DATACOM - AD CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CA ECOMETER SERVER COMPONENT FOC Easytrieve Report Generator for Common Services INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA ON DEMAND PORTAL CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware Top Secret Top Secret - LDAP Top Secret - VSE

Issue/Introduction

Description:

Receiving the following messages when NETVIEW starts:

IEF695I START CNMPROC WITH JOBNAME CNMPROC IS ASSIGNED TO USERS +++++++

Why is user ++++++++ assigned to NETVIEW, since NETVIEW is defined to TSS STC record?

Why is there no OWNER visible either with IBM SDSF or CA SYSVIEW.

Solution:

If NETVIEW is started after TSS and JES full initialization and it is defined in the STC record, yes the OWNER should be visible.

When procedures are started before TSS and JES initialization without SUB=MSTR, then all are waiting for JES.

When JES is ready, they can start. And when TSS is up and running, they can be signed on when the first security event occurs in their address space.

Example:

JES and TSS are not started yet when HZS is launched:

07:42:20.69 INTERNAL 00000290 START HZS

When JES and TSS are up, then HZS is placed on STCINRDR:

07:51:11.71 S0000007 00000090 $HASP100 HZS ON STCINRDR

TSS signs HZS::

07:51:11.72 00000290 IEF170I 1 HZS TSS7000I HZSPROC Last-Used

HZS is finally started, but JSAB is zeroed to due the early start. JASB is the field where the OWNER is derived from.

07:51:11.94 S0000007 00000290 IEF695I START HZS WITH JOBNAME HZS IS ASSIGNED TO USER ++++++++

The content of the address space shows that the ACEE is correctly HZSPROC, which is the acid name from the STC record.

007F5C88 00000000 C1C3C5C5 FF000218 03000000 00000000 *ACEE............*
007F5C98 00000010 00000000 07C8E9E2 D7D9D6C3 4007D6D4 *.....HZSPROC .OM*

Environment

Release: TOPSEC00200-15-Top Secret-Security
Component: