What are the Implications of Not Changing the HOSTID for JES3 Hosts in the HSC CDS from the JES3 Main Name to the SMF System ID? (Doc ID 1014520.1)

Last updated on JUNE 13, 2017

Applies to:

Sun StorageTek Storage Management Component (SMC) - Version 6.1 and later
Sun StorageTek Host Software Component (HSC) - Version 6.0 and later
Sun StorageTek Client System Component (CSC) for MVS - Version 6.1 and later
IBM z/OS on System z

Goal

What are the risks of not changing the HOSTID for JES3 hosts in the HSC CDS from the JES3 main name to the SMF system ID?
How does HSC, SMC and MVS/CSC derive the host sysid?

Some messages that list the SYSID:

SLS1712I HOSTID sysid NOT FOUND IN cds_name
SLS1715I sysid INITIALIZING ON: cds_name
SLS4500I date, time HSC SUBSYSTEM subsystem_name ACTIVE ON HOSTID sysid
SCS4500I date, time MVS/CSC SUBSYSTEM subsystem_name ACTIVE ON HOSTID sysid
SMC0084 date time subsystem_name (version) ACTIVE ON HOSTID sysid

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms