Define variables to configure integral JMS provider - definitions

This article lists definitions for the terms you will come across in the WebSphere Application Server for z/OS Customization Dialog.

Note: Some term definitions--those that you cannot set in the related panel--are not displayed. To see the definition, you must to go to the Information Center article for the panel on which you can change that particular term.

1 System locations (directories, HLQs, etc)

System Locations (1 of 2)

System name
The system name, designated in your base cell customization, for the target z/OS system on which WebSphere Application Server for z/OS is installed.
Sysplex name
The sysplex name, designated in your base cell customization, for the target z/OS system on which WebSphere Application Server for z/OS is installed.

Tip: If you are not sure what the system name (&SYSNAME) and sysplex name (&SYSPLEX) are, use the console command D SYMBOLS on the target z/OS system to display them.

Jes3 (Y/N)
Indicate "Y" if you are using JES 3 or "N" if you are using JES 2.

Full Names of Data Sets

For the following, specify the fully qualified data set names without quotes.

Rule: You can specify up to 42 characters for the data set names.

MACLIB
The data set that contains the macro definitions for the system macro instructions that are provided by IBM.
PROCLIB
An existing procedure library where the WebSphere Application Server for z/OS cataloged procedures are added.
PARMLIB
An existing parameter library for system definitions to support WebSphere Application Server for z/OS. This data set must be in the parmlib concatenation for the target z/OS system.

Specify the following Language Environment and WebSphere Application Server for z/OS data sets and whether they are ("Y") or are not ("N") in the link list or the link pack area (LPA). "N" indicates the generated JCL will contain STEPLIB statements for these data sets. Refer to your SMP/E installation for the location of these data sets listed by their DD Name.

SCSQAUTH
The main repository for all MQSeries product load modules. It also contains the default parameter modules CSQZPARM and CSQXPARM. Ensure this library is APF-authorized.

Note: It is recommended that you place this library in LNKLST rather than the LPA because you can update LNKLST after maintenance by issuing the z/OS command REFRESH LLA. If you do decide to place it in the LPA, you need to manually copy any changed modules into the LPA whenever you apply maintenance.

SCSQANLx
Contains the load modules for various versions of MQSeries. The different versions, designated by letters in place of the "x", are U.S. English: mixed case ("E"), U.S. English: uppercase ("U"), Simplified Chinese ("C"), and Japanese ("K").

Note: It is recommended that you place this library in LNKLST rather than the LPA because you can update LNKLST after maintenance by issuing the z/OS command REFRESH LLA. If you do decide to place it in the LPA, you need to manually copy any changed modules into the LPA whenever you apply maintenance.

SCSQLINK
The early code library. Contains the load modules that must reside in the link list because they are loaded at system initial program load (IPL). Ensure this library is APF-authorized and in the link list.

Note: It is recommended that you place this library in the LPA.

SCSQMVR1
Contains the load modules for distributed queuing when using LU 6.2 or TCP/IP with either the OpenEdition sockets or IUCV interface. Ensure this library is APF-authorized.

Note: It is recommended that you place this library in LNKLST rather than the LPA because you can update LNKLST after maintenance by issuing the z/OS command REFRESH LLA. If you do decide to place it in the LPA, you need to manually copy any changed modules into the LPA whenever you apply maintenance.

SCEERUN
A Language Environment run-time load module library. Access is required. If it is not in your link list, concatenate it in the STEPLIB DD statement. You need to stop and restart your queue manager to do this.
USER LOAD
System parameter module that controls the logging, archiving, tracing, and connection environments that MQSeries uses in its operation. You need to create this linkedit target data set from scratch, using another data set as a template.
SCSQLOAD
The load library. Contains load modules for non-APF code, user exits, utilities, samples, installation verification programs, and adapter stubs. The library does not need APF-authorization nor must it reside in the link list.
SCSQMACS
Contains Assembler macros including sample macros, product macros, and system parameter macros.
SCSQPROC
Contains sample JCL and default system initialization data sets.
SCSQSNLx
Contains the load modules for various versions of the MQSeries modules that are required for special purpose function (for example, the early code). The different versions, designated by letters in place of the "x", are U.S. English: mixed case ("E"), U.S. English: uppercase ("U"), Simplified Chinese ("C"), and Japanese ("K").

Note: It is recommended that you place this library in the LPA.

System Locations (2 of 2)

Each MQSeries subsystem in WebSphere Application Server for z/OS contains two bootstrap data sets (BSDSs), two sets of log data sets, and nine page data sets. Along with the volume 0 page data set, which is fixed and untailorable, there are eight other page data sets that you can organize to suit your needs.

Note: You must define all the BSDS, LogCopy, and PageSet volumes, but you can choose to make the values different or all the same. You might specify the same value for all the volumes if, for example, you run only a test system, but the system performs better if they are spread out.

High Level Qualifier of IJP Operational Data sets:

CSQHLQ
The high level qualifier that you create for your IJP operational data sets.

Integral Provider Output Volumes

BSDS Vol1
The bootstrap data set volume 1.
BSDS Vol2
The bootstrap data set volume 2.
LogCopy 1 Vol1
Volume 1 of copy 1 of the log data set.
LogCopy 1 Vol2
Volume 2 of copy 1 of the log data set.
LogCopy 2 Vol1
Volume 1 of copy 2 of the log data set.
LogCopy 2 Vol2
Volume 2 of copy 2 of the log data set.

Integral Provider Page Volumes

PageSet Vol0
The volume 0 page data set, which is fixed and untailorable.
PageSet Vol1 - PageSet Vol8
Eight volumes of page data sets. You must define them all, but you can choose to make the values different or all the same.

2 Server Customization

Server Customization (1 of 2)

Note: The Application Server information is provided for reference purposes only, so the definitions will not appear here.

WebSphere HFS Information

Mount point
Read/write HFS directory mount point where application data and environment files are written. The customization process creates this mount point, if it did not already exist.

Application Server Definitions

Rule: In the following, unless specified otherwise, names must be 8 or fewer characters.

WebSphere Application Server home directory
Directory in which the Application Server configuration resides.

Note: You can alter only the portion after "/WebSphere/V5R0M0."

Cell name (short)
Parameter passed to the server's start procedures that specifies the location of the cell's configuration files and identifies the cell to certain WebSphere Application Server for z/OS-exploited z/OS facilities (for example, SAF).

Note: If WebSphere Application Server 5.0 is already installed and you are installing WebSphere Application Server 5.1, the cell short name should be unique.

Rules:

  • Name must be 8 or fewer characters and all uppercase.
  • Name must be unique among all other cells in the sysplex.

Cell name (long)
Primary external identification of this WebSphere Application Server for z/OS cell. This name identifies the cell as displayed through the administrative console and also appears as part of the directory path under the WebSphere Application Server for z/OS home's configuration directory.

Note: If you intend to ever add this base server node to a deployment manager cell, ensure that the base server cell name is different than the deployment manager cell name.

Rules:

  • Name must be 60 or fewer characters and can be of mixed case.
  • Name must be unique among all other cells in the sysplex.

Node name (short)
Parameter passed to the server's start procedures that specifies the location of the node's configuration files and identifies the node to certain WebSphere Application Server for z/OS-exploited z/OS facilities (for example, SAF).

Rules:

  • Name must be 8 or fewer characters and all uppercase.
  • Name must be unique within the cell.

Node name (long)
Primary external identification of this WebSphere Application Server for z/OS node. This name identifies the node as displayed through the administrative console and also appears as part of the directory path under the WebSphere Application Server for z/OS home's configuration directory.

Note: If you intend to ever add this base server node to a deployment manager cell, ensure that all the nodes in the deployment manager cell are unique.

Rules:

  • Name must be 60 or fewer characters and can be of mixed case.
  • Name must be unique within the cell.
  • The Application Server must be defined on its own node; no other server may exist on the same node as the Application Server.

Server name (short)
Name of the Application Server. This is the server's job name, as specified in the MVS START command JOBNAME parameter. This value is also passed as a parameter to the server's start procedures to specify the location of the server's configuration files and identify the server to certain WebSphere Application Server for z/OS- exploited z/OS facilities (for example, SAF).

Note: The server short name is used as the server JOBNAME.

Rule: Name must usually contain 7 or fewer all-uppercase characters. If you wish to instead specify 8 characters, you must follow the steps outlined in the Information Center article "Converting a 7-character jobname to 8 characters."

Server name (long)
Name of the Application Server and the primary external identification of this WebSphere Application Server for z/OS server. This name identifies the server as displayed through the administrative console and also appears as part of the directory path under the WebSphere Application Server for z/OS home's configuration directory.

Rule: Name must be 60 or fewer characters and can be of mixed case.

Integral JMS Definitions

JMS server name (short)
MQSeries subsystem base server name. This value defines the Integral JMS Queue Manager as a z/OS subsystem and forms the name of the Integral JMS Broker.

Rule: The JMS Server name must contain only 4 characters.

Command prefix
Character string value that WebSphere System Manager uses, in conjunction with the JMS Server short name, to form system commands that direct both the operation and administration of the Integral JMS Queue Manager.

Server Customization (2 of 2)

Integral JMS Server Parameters

Archive retention (days)
Specifies the retention period, in days, set when you create the archive log data set. The default is 9999.

Rule: The parameter must be in the range 0 through 9999.

Stat Interval Time (secs)
The interval, in seconds, between listener restart attempts. The default is 60.
JMS Server Queued Address port
Specifies the host and port number used to configure the WebSphere JMS Provider topic connection factory. The JMS Server Queued Address port is the listener port used for full-function JMS-compliant, publish/subscribe support. The default Queued Address port number is 5558.

Since the queue manager and queue broker for the WebSphere JMS Provider are configured outside the administrative console, changes to this endpoint require corresponding configuration changes to the queue manager and queue broker.

JMS Server Direct Address port
Specifies the host and port number used to configure the WebSphere JMS Provider topic connection factory. The JMS Server Direct Address port is the listener port used for direct TCP/IP connection (non-transactional, nonpersistent, and non-durable subscriptions only) for publish/subscribe support. The default Direct Address port number is 5559.

Since the queue manager and queue broker for the WebSphere JMS Provider are configured outside the administrative console, changes to this endpoint require corresponding configuration changes to the queue manager and queue broker.

JMS Server Security port

3 Security Customization

For more information about security, see related security sections.

Security Customization (1 of 1)

Queue Manager Security

Default user ID for commands
Specifies the default user ID used for command security checks. Ensure this user ID is defined to the ESM.

Rule: The name must be between 1 and 8 alphanumeric characters and start with a letter.

In the following, specifying "Y" (yes) tells the Dialog to define the profile or enable an option in RACF. Specifying " N" (no) tells the Dialog to not define the profile or enable the option.

Resource auditing (Y/N)
If you want to enable the creation of an audit trail, specify "Y". Otherwise, specify "N". Creating an audit trail may impact performance.


Related concepts
Setting up WebSphere Application Server for z/OS security
Related tasks
Warning: no string named [tins_dialogdefvarsteps] found.
Related reference
Define variables to configure integral JMS provider - worksheets



Searchable topic ID:   rinsdefvar3def
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/rins_defvar3def.html

Library | Support | Terms of Use | Feedback