Specifies the short name of the server. For WebSphere Application
Server for z/OS, the server short name must be unique within a cell. The short
name is also the default z/OS job name, which identifies the server to the
native facilities of the operating system, such as Workload Manager (WLM),
Automatic Restart Manager, SAF (for example, RACF), started task control,
and others.
The name is 1-8 characters, alpha-numeric or national language. It cannot
start with a number.
The system assigns a default short name that is automatically unique within
the cell. You can change the generated short name to conform with your naming
conventions.
Converting a 7-character server
short name to 8 characters:
By default, WebSphere Application
Server for z/OS assumes you will be using a 7-character server short name
(JOBNAME). If your naming standards require 8 characters, you can lengthen
the 7-character server short name to 8 characters by performing the tasks
below. Before doing this, it is important to consider the following:
- The Resource Recovery Services (RRS) log names are based on the server
short name. When you change the server short name, you are changing the server's
identity to the RRS. This means that the previously existing transaction and
partner logs will be abandoned, or will not match the new name, and either
of these situations will result in restart problems. To prevent this from
happening, ensure that there are no outstanding RRS units of recovery (URs)
for your server before changing its name. See z/OS MVS Programming:
Resource Recovery for instructions on using the RRS panels to view
information about URs.
Note that the only safe way to provide an 8-character
short name for a server is to do so before it is initially started.
- Converting your 7-character server short name to 8 characters requires
you to change the JOBNAME used by the servant's start command. This means
that the System Authorization Facility (SAF) started class that previously
matched this job may no longer match. Review your SAF STARTED class profile
and, if necessary, define a new class.
- Because the JOBNAME appears as part of a start command's arguments, you
need to review your COMMNDxx PARMLIB member, as well as any other form of
automation you use that issues a start command to start a WebSphere server.
- Review the start parameters of your Workload Management (WLM) static APPLENV
definitions. These are the parameters that are used to start the servant process
(server region). If you are using static APPLENVs, the start parm string used
by the WLM for your server looks similar to JOBNAME=BBOS001S,ENV=... You will
need to decide if you want to keep this JOBNAME or change to the new JOBNAME
that you specify in the steps below. The original JOBNAME should be sufficient.
Note
that this consideration does not apply to you if you are using WLM dynamic
APPLENVs.
- Review and update the necessary Resource Access Control Facility (RACF)
profiles to support these server short names. See RACF server class profiles
Steps for this task:
- Change the 7-character server short name to the 8-character name you wish
to use:
- Navigate to Servers > Application Servers > server_name.
- In the short Name field, replace the 7-character name with the
8-character short name you wish to use.
- Click OK.
- Update the servant's start command arguments to use the new 8-character
name. Note that if you are reconfiguring a nodeagent or jmsserver, you can
skip this step because neither has an associated servant process.
- Navigate to Servers > Application Servers > server_name >
Process Definition > Servant.
- In the startCommandArgs field, replace the 7-character name, designated
by the JOBNAME argument, with the 8-character name you wish to use. Do not
include the S character at the end of the JOBNAME. For example, JOBNAME=P5SVR1D,ENV=P5CELL.P5NODED.P5SVR1D
.
- Click OK.