IBM Session Manager Implementation

Chapter 1. Session Manager overview 3

1.2 Administration

How Session Manager is administered will depend upon the basic configuration

option you chose for product setup and running. The basic configuration choices

are Classic, Online, and Batch Administration (OLA). Session Manager retains

all configuration information in memory; therefore, changes you make to

definitions will have to be installed to make them effective. Changes can be

installed upon a restart of Session Manager or dynamically via the appropriate

Session Manager command for dynamic updates.

1.2.1 Classic configuration

You administer the classic configuration by editing members of the configuration

file. The configuration file can be a single PDS or a concatenated (linked

together) set of PDSs allocated to the DDNAME of CONFIG in the Session

Manager started task. Editing of configuration file members is done using the

Time Sharing Option/Interactive System Productivity Facility (TSO/ISPF). Edited

changes are implemented at Session Manager initialization or they can be

processed dynamically using the update command.

Example 1-1 Concatenated classic configuration files

//ISZSMGR EXEC PGM=ISZSMGR,PARM='CONFIG 01 START YES PRINT NO',

// REGION=0M,TIME=1440

//CONFIG DD DSN=ISZ.V1R2M0.ISZCONF,DISP=SHR

// DD DSN=ISZ.V1R2M0.ISZWSOS,DISP=SHR

// DD DSN=ISZ.V1R2M0.ISZHELP,DISP=SHR

//STEPLIB DD DSN=ISZ.V1R2M0.ISZAUTH,DISP=SHR

Example 1-1 above illustrates the CONFIG DD statement concatenation for a

classic implementation. This illustration shows three PDSs in the CONFIG DD

statement concatenation. The third PDS in the concatenation,

ISZ.V1R2M0.ISZHELP, contains panels and scripts for the Session Manager

help function. The second PDS in the concatenation, ISZ.V1R2M0.ISZWSOS,

contains panels and scripts for the Session Manager window feature. The first

PDS in the concatenation, ISZ.V1R2M0.ISZCONF, is the primary configuration

PDS and it contains all of the information used to configure a classic Session

Manager instance.

Note: Once a definition is installed into Session Manager the only way to

remove it is to delete the definition from the Session Manager Partition Data

Set (PDS) and restart Session Manager. For some definitions, their effect can

be negated by dynamic installation of a definition with the same name and no

parameters.

4 IBM Session Manager Implementation

Since the PDS ISZ.V1R2M0.ISZCONF is distributed with Session Manager, it is

good practice to create a user version of the PDS. This will allow the distributed

library to remain unchanged and modified members placed in the user PDS. The

new user configuration PDS would then be placed as the first PDS in the

CONFIG DD statement concatenation. Since this PDS will be the target of many

changes over the life of the product, it is recommended that the user

configuration library be allocated as a Partition Data Set Extended (PDSE) with

ample space for growth. These two steps will lessen the need for library

maintenance due to space issues and eliminate the need for periodic

compressions of the library.

Example 1-2 Concatenated classic configuration with user PDS

//ISZSMGR EXEC PGM=ISZSMGR,PARM='CONFIG 01 START YES PRINT NO',

// REGION=0M,TIME=1440

//CONFIG DD DSN=ISZ.V1R2M0.USERCONF,DISP=SHR

// DD DSN=ISZ.V1R2M0.ISZCONF,DISP=SHR

// DD DSN=ISZ.V1R2M0.ISZWSOS,DISP=SHR

// DD DSN=ISZ.V1R2M0.ISZHELP,DISP=SHR

//STEPLIB DD DSN=ISZ.V1R2M0.ISZAUTH,DISP=SHR

Example 1-2 illustrates the updated classic JCL with the user configuration PDS

added. With this approach, all modified members are placed in the user

configuration PDS and they are called in lieu of supplied members. In the user

configuration PDS, a user version of ISZCON01 should be created and used as

the primary configuration member. Session Manager naming standards mandate

that the member name be ISZCONxx, where the xx is the two-character suffix

used in the started task JCL parameter CONFIG xx.

Example 1-3 illustrates how a user configuration member might be coded. This

example member holds all configuration information specific to the installation,

and the Copy iszcon01 statement will include all of the general configuration

information required for Session Manager to initialize and run. The Copy

iszcon01 statement must appear prior to the SYSTEM statement. For SYSTEM

parameters, Session Manager will use the last version of the parameter it

encounters. Therefore the SYSTEM parameters in the user configuration

member will override the SYSTEM parameters in the supplied ISZCON01

member. For other definitions such as applications, profiles, scripts, users and

panels, Session Manager will use the first definition it encounters.

Example 1-3 User configuration member

*--------------------------------------------------------------------*

* *

* User primary configuration member *

* *

*--------------------------------------------------------------------*