iiiintroducing the zpmtntroducing the zpmt · the customized jcl batch jobs that ultimately create...

WebSphere Application Server for z/OS V6.1

IIIIntroducing the zPMTntroducing the zPMTntroducing the zPMTntroducing the zPMT(z/OS Profile Management Tool)

This document can be found on the web at:www.ibm.com/support/techdocs

Search for document number WP100871 under the category of "White Papers"

Version Date: December 7, 2006Please see "Document Change History" on page 34 for updates provided in this version of the document.

IBM Washington Systems CenterIBM Washington Systems CenterIBM Washington Systems CenterIBM Washington Systems Center

Don BagwellIBM Washington Systems Center

[email protected]

Many thanks to Harvey McGee of the IBMWebSphere for z/OS development organization.

Table of Contents

28Location of response file (and other files generated by zPMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Response file recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Backup and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Renaming workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Copying workspaces and sharing them with others . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Subtle variation -- zPMT customization definitions outside of workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26General guidelines: one workspace or multiple? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25The workspace and what zPMT shows as saved configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Workspace recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Using the planning spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Other sources of essential WebSphere configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25General recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Some Recommendations for Getting the Most from zPMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Completion and uploaded jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Created jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Configured panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Selected configuration option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Configuring a "z/OS deployment manager" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13The planning spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 - Invoking zPMT function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122 - Selecting workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121- Launching AST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Launching the tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Example of Using the zPMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11A note about future enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10How is the AST started and the zPMT function invoked? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10How is the Application Server Toolkit (with zPMT) installed on a workstation ? . . . . . . . . . . . . . . . . . . . . . . . .9How do I know if updates or fixes are available for this software? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Is there a restriction on how many people can use it? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9What are the system requirements for the zPMT? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Where do I get the zPMT installation program? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7May I still use the planning spreadsheet? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Is there a way to bring an ISPF SAVECFG file down and use it with the zPMT? . . . . . . . . . . . . . . . . . . . . . . . .6The ISPF panels generated a handy set of instructions. Does the zPMT do that too? . . . . . . . . . . . . . . . . . . .6Where is the response file located on the workstation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6What's the best way to share my configuration information with someone else? . . . . . . . . . . . . . . . . . . . . . . . .5Is there a way to feed saved variables into this so I don't have to type so much? . . . . . . . . . . . . . . . . . . . . . . .5May I maintain my configuration work separate from other people's work? . . . . . . . . . . . . . . . . . . . . . . . . . . . .5The variables I enter into the zPMT are saved, correct? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5What kind of configurations can I build with this thing? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4Is the process of planning a cell the same with zPMT as it was with the ISPF panels? . . . . . . . . . . . . . . . . . . .4Does this replace the ISPF panels? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4What does it look like? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4Is zPMT a standalone application, or part of some other development tool? . . . . . . . . . . . . . . . . . . . . . . . . . . .4More Questions and Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4Why a document "introducing" the tool? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3What is the zPMT? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Information on the latest version available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Introduction and Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

WP100871 - Introducing the zPMT

Section: IntroductionVersion Date: Thursday, December 07, 2006

- 1 -© 2006, IBM Americas Advanced Technical SupportWashington Systems Center, Gaithersburg, MD

34Document Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Available AST and zPMT code and updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Deleting a customization definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Uploading the generated files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Making a modification to an existing configuration definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Managing existing customization definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Loading a response file into a new customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Sending a response file to others . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Making manual modifications to the files in the workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Using the copy/paste method of producing a response file to send to others . . . . . . . . . . . . . . . . . . . . . . . . . .


Section: IntroductionVersion Date: Thursday, December 07, 2006


Introduction and Overview

Information on the latest version available

See "Available AST and zPMT code and updates" on page 34.

What is the zPMT?

"zPMT" stands for "z/OS Profile Management Tool." It is a workstation-based tool used to generatethe customized JCL batch jobs that ultimately create your WebSphere Application Server for z/OScell up on the z/OS system.

The other way to generate the customized JCL batch jobs is to use the ISPF dialogs. They bothend up creating the same thing -- customized JCL batch jobs -- but the interface used to capturethe information from you is different. ISPF uses ... well, ISPF. The zPMT uses aworkstation-based graphical interface.

Note:

Consider the following picture, which tells the high-level story of the zPMT:

zPMT Tool

"Workspace"

customized JCL jobs

saved variables

CNTL, DATA data sets

1

2

3

4

Submit Jobs 5

6

Key points:zPMT captures information from you

zPMT generates customized JCL jobs

Jobs are uploaded to z/OS and run

Result is a WebSphere for z/OS configuration

Notes:

1. zPMT tool is started on your workstation. It presents a series of windows that ask for key information,much like the ISPF panels did. You key in the information.

It is possible to supply an input file. See "Loading a response file into a new customization"on page 30.

Note:

2. The information you provide is stored in the tool's "workspace," which is a directory structure on yourworkstation's hard drive. Within that "workspace" will be the generated JCL jobs that will create yourWebSphere for z/OS servers, as well as the variables you provided.

3. The JCL files are sent to the z/OS system using the "Upload" feature of the tool

4. The files are placed in two partitioned data sets -- CNTL and DATA -- just like the ISPF panels did.

The tool is able to allocate the data sets as part of the upload if you wish.

5. You run the jobs in sequence, just as you have in the past. In fact, the JCL jobs are at this point thesame as if you'd generated them with the ISPF panels.

6. The result is an operational WebSphere Application Server configuration.


Section: OverviewVersion Date: Thursday, December 07, 2006


That's the essential message of zPMT -- a workstation based tool used to generate the customizedJCL jobs that, when run successfully on a z/OS platform, result in a WebSphere Application Serverfor z/OS V6.1 configuration.

Why a document "introducing" the tool?

Because many z/OS users of WebSphere have become very accustomed to the ISPF panels andmay not be aware of this new tool. We very much wish to encourage you to understand what thisnew tool is, how it works, and perhaps take some time to explore its use.

More Questions and Answers

Let's start with a quick set of questions and answers:

Is zPMT a standalone application, or part of some other development tool?

It's a function of the "Application Server Toolkit" (AST) that is provided with WebSphereApplication Server. So to use the zPMT you have to install the AST on your workstation andstart it, then invoke the zPMT function from there.

What does it look like?

Here's a screen capture:

Fields where you enter your configuration information

Scroll bar to move to additional fields if not in the current window

"Back" and "Next" buttons

In many ways the zPMT tool will "look" like the ISPF panels -- the layout of the information issimilar (though not identical). The type of information called for is the same -- long names, shortname, IDs, UID, GID, JCL proc names, etc. Rather than a 3270 screen it's done within agraphical interface like shown.

Yes, the "planning spreadsheet" is still very useful in planning this information.Note:

Does this replace the ISPF panels?

The ISPF panels were "deprecated" in the V6.1 release. What that means is this: the panelsare still there, they still work, but the handwriting is on the wall. So for now the zPMT and theISPF panels perform the same function. Both still exist ... for now.

Is the process of planning a cell the same with zPMT as it was with the ISPF panels?

Yes, very much so. The zPMT will ask you for all the same information as the ISPF panels did,though in a few cases in a sequence that's slightly different. But all the stuff you've spent time




learning to do -- naming conventions, port allocation charts -- all are the same with the zPMT asthey were with the ISPF panels.

What kind of configurations can I build with this thing?

The same things you could build with the ISPF panels, with a very interesting additionalconfiguration option. The zPMT tool lists the following as the customization "environments"available. We've cross-referenced to the terms you may be familiar with in the ISPF panels:

Note 1: The zPMT tool is offering a nice, unique option here. The jobs generated by this option, whensuccessfully run, will result in an ND configuration on one MVS image -- a DMGR node and a federated nodewith an application server -- all as part of one set of jobs.

"Empty managed node"z/OS managed (custom) node

"Federate an existing standalone ..."z/OS federate an application server

"Network Deployment cell"z/OS deployment manager

(see note 1)z/OS cell (deployment manager and application server)

"Standalone Application Server node"z/OS Application Server

Equivalent ISPF optionzPMT tool option

The variables I enter into the zPMT are saved, correct?

Absolutely ... as part of the "workspace" on your hard drive. That workspace is really nothingmore than a place where the tool maintains all its information about your projects. You get topick where the workspace will be built.

Furthermore, the variables entered for one configuration are put into what's called a "responsefile" -- a flat file with the variables and your values. You can think of this response file as similarin concept (but not identical in format) to the SAVECFG files for the ISPF dialogs.

See "The workspace and what zPMT shows as saved configurations" on page 25 for a bit moreabout that, and see "Location of response file (and other files generated by zPMT)" on page 28for more on that file.

May I maintain my configuration work separate from other people's work?

Yes. This is done by maintaining a separate workspace from them. If your workspace is onyour PC, then you're all set. If the workspace is on some shared network drive, then you shouldmake sure their workspaces are different from yours. See "The workspace and what zPMTshows as saved configurations" on page 8.

Is there a way to feed saved variables into this so I don't have to type so much?

Yes. The input file is called a "response file," as we discussed earlier. You can tell zPMT toread in (or "load") a response file and it'll use whatever information was contained in that file.During the creation of a configuration definition you're given the option to load a response file:

Type the full path and file name, or use the "Browse"

button to locate the file

You may then go through the panels and modify whatever portion of the data you desire.




See "Loading a response file into a new customization" on page 30 for more on this topic.

What's the best way to share my configuration information with someone else?

The best way to do that is to send that person the "response file" created by the zPMT. Theresponse file is a flat file containing all the information for a configuration. If you send that file tosomeone, they can read that response file into their copy of zPMT. They may then makewhatever modifications to the data as they see fit. See "Sending a response file to others" onpage 30 for more.

Where is the response file located on the workstation?

The easiest way to determine this is to use the "View" function of the zPMT tool. The responsefile is created after you've gone through all the panels and input your data. At that point aconfiguration definition is created, and from there you can "view" information about thatdefinition:

Select the customization

definition

Click the "View" button

1

2

Click the "Summary"

tab

3

Instructions file

Response file

Target z/OS data sets

Type of definition (Deployment Manager here)

To see an illustration of where the files are located relative to the root of your workspace, see"Location of response file (and other files generated by zPMT)" on page 28.

The ISPF panels generated a handy set of instructions. Does the zPMT do that too?

Yes it does. It's important to keep in mind that the zPMT generates pretty much the same filesas does the ISPF panels. The difference is the zPMT does it on your workstation.




The previous section showed you how to find out where things are located. But in addition tosimply pointing to the file locations, the zPMT also allows you to view the instruction file and theresponse file. You can access them quite easily:

Select the customization

definition

Click the "View" button

Select the "Instructions" tab

Scroll through and read the instructions

1

2

3

4

Response file

Is there a way to bring an ISPF SAVECFG file down and use it with the zPMT?

This is a known requirement and is being considered for a future release of the tool.

May I still use the planning spreadsheet?

The reference here is to the Excel spreadsheet published at:

http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS1331

Note:

Yes you can ... and we encourage you do so. The planning spreadsheet has proved to be aninvaluable tool to organize your naming convention and port numbering. Many people rely quiteheavily on the spreadsheet, including the author of this document.

If you go to the PRS1331 site, you'll find there are several versions of the spreadsheet available:




For use with WebSphere z/OS V6.0.2

For use with WebSphere z/OS

pre-V6.0.2

V6.1 editions, one for the zPMT, one for ISPF

The two on the top -- V6.0.2 and pre6.0.2 -- do not apply to the zPMT. The zPMT is for use withWebSphere Application Server for z/OS V6.1 or later.

But the two on the bottom may be used with the zPMT, and in particular the one labled "zPMT"is specifically designed to be used with the zPMT.

The V6.1 edition labeled "ISPF" can be used with the zPMT, but the layout of the informationin the spreadsheet will be slightly different from the layout of the information in the zPMT.Still usable, but it requires a little more thinking about what information from the spreadsheetgoes where in the zPMT.

Note:

The edition labeled "zPMT" is designed to produce a "response file" -- a flat file with all the inputvariables the zPMT needs to complete the configuration definition. The data produced by thespreadsheet, once placed into a separate flat file, may then be loaded into the zPMT to fullypopulate all the fields of the configuration definition. All you would need to do is quickly keythrough the panels of the zPMT and then generate the customized jobs:

zPMT Tool

Spreadsheet

Notepad or some other

editor

Copy/Paste

Load

"Response File"

Customized jobs ready for upload

to z/OS

The zPMT edition of the spreadsheet captures key variables from you on one "worksheet,"then it uses that information to construct a long list of "name/value pairs" on anotherworksheet. That set of "name/value pairs" is in the format used by the zPMT. All you needto do is select the range, copy, and then paste into a Notepad session.

Note:

See "Loading a response file into a new customization" on page 30 for instructions on how toload a response file into the zPMT.

Where do I get the zPMT installation program?




It comes with the installation media for your copy of WebSphere Application Server. It's in the"Optional Materials" bundle of disks.

What are the system requirements for the zPMT?

It's a fairly typical GUI application. Here are the system requirements as recorded in the "IBMWebSphere Application Server Toolkit, Version 6.1 for Windows and Linux: Installation guide,"dated May 2006:

References to Linux are applicable to the Application Server Toolkit, but not the zPMTfunction. zPMT only supports Windows. AST supports both Windows and Linux.

Important!

Hardware:

� Processor requirements: Intel(R) Pentium(R) III 800 MHz processor minimum (Higher isrecommended).

� Memory requirements: 512 MB RAM minimum (1 GB RAM is recommended). � Disk space requirements:

� To install the full WebSphere Application Server Toolkit, you will require 900 MB of diskspace. If your file system is FAT32 instead of NTFS, more space will be required.

� You will also require additional disk space if you download the electronic image to installWebSphere Application Server Toolkit. For Windows: You will require 100 MB in theTEMP directory; for Linux: You will require 100 MB in the /tmp directory.

� Display requirements: Display resolution of 1024 x 768 or higher.

Operating System:

� Windows(R) XP Professional with Service Pack 2 � Windows 2000 Professional with Service Pack 4 � Windows 2000 Server with Service Pack 4 � Windows 2000 Advanced Server with Service Pack 4 � Windows Server 2003 Standard Edition with Service Pack 1 � Windows Server 2003 Enterprise Edition with Service Pack 1 � Red Hat Enterprise Linux(R) 3.0 with Updates 5 or 6 � Red Hat Enterprise Linux 4.0 with Update 2 � SUSE Linux Enterprise Server (SLES) 9 with Service Packs 2 or 3

User ID Requirements:

Both non-Administrator users (on Windows) and non-root users (on Linux) can install WebSphereApplication Server Toolkit in both silent and interactive (using the installation program) mode.When installing as a non-Administrator or non-root user, ensure that you have write permission tothe installation directory you choose and that you have write permission to the workspacedirectory you specify when you start the product.

Important: Your user ID must not contain double-byte characters

Is there a restriction on how many people can use it?

No. If you have a license for WebSphere Application Server (any platform), you have rights toas many seats of AST as you wish.

How do I know if updates or fixes are available for this software?

Because the zPMT tool is part of the Application Server Toolkit, it can take advantage of aproduct update feature that's common with all of IBM's tools based on Eclipse. It's called the"Rational Product Updater." This feature knows what product and features you have installed,its version and its fix packs. When you tell it to, it'll go out to an IBM update site and see if anynew updates are available. If updates do exist, you may then select the updates for downloadand installation. It's quite simple and easy.




How is the Application Server Toolkit (with zPMT) installed on a workstation ?

This is a typical Windows installation executable you double click to launch the installationprogram. From there it's really a matter of clicking "Next" several times. There's very little toconfigure. The default installation location works perfectly well.

How is the AST started and the zPMT function invoked?

From the "Start" button, go to:

IBM WebSphere � Application Server Toolkit V6.1 � Application Server Toolkit V6.1

This will bring up the Application Server Toolkit, which will look something like this:

The zPMT tool is a function under the "Window" pulldown

At this point we'll remind you that the zPMT is one piece of the Application Server Toolkit, butnot the whole thing. In other words, the AST offers more function that simply configuring thecustomized jobs. (Translation: please don't be intimidated by all the features and functions yousee in the pulldown menu of the AST. Most don't apply to the zPMT at all.)

Invoking the zPMT function of the AST is accomplished by navigating the following AST path:

� Window � Preferences ... then� Expand Server and then click on WebSphere for z/OS

What you then see is something like this:




Any saved "customization definitions" the zPMT tool knows about

(example here shows none)

Function buttons to create a new configuration, regenerate

an existing one, delete one, view or upload a configuration

See "Example of Using the zPMT" starting on page 12 for a better illustration of how to use thetool to create a configuration.

A note about future enhancements

It's really important to understand that what we're showing you in this document is not the end of thestory. IBM is very involved with customers in understanding what enhancements are desired. Youwill see many new things added to this tool over the coming months.

But the essential concepts will be the same:

� zPMT captures information from you� It generates the jobs and uploads them to the z/OS platform� You execute the jobs in sequence to build the configuration

This document will be updated periodically with new information as the function is made available.The last section of this document -- "Document Change History" on page 34 -- is used to tell thestory of the updates made to the document. Notice please that each page has a "Version Date" youmay use to know what copy of the document you have in your hand.

How this document is organized

We've organized this document into two sections following this overview section:

� "Example of Using the zPMT" (starting on page 12)

We'll go through an example of a Deployment Manager configuration to show how the tool is used tocapture your configuration information, how to generate the jobs and how to upload them.

Here we ask you to understand something -- this document is not trying to be the end-allreference for the tool, or for information about WebSphere on z/OS. This is an introduction.

Note:

� "Some Recommendations for Getting the Most from zPMT" (starting on page 25)

We'll offer some hints and tips to help your zPMT experience be as positive as possible. This sectionwill no doubt grow over time as we -- you, us -- learn more about how to use the tool in a real-worldpractical setting.




Example of Using the zPMT

In this section we'll offer you a quick introduction to how the zPMT tool is used. We'll do that by way ofan example.

In writing this section, we had our eye on providing three primary things to you, the reader:

� The zPMT has a look-and-feel somewhat close to the flow of the ISPF panels

� The configuration planning spreadsheet is still a very useful tool and we stronglyencourage you use it to plan your configuration

� The output from the zPMT is the same set of customized JCL batch jobs you createdthrough the ISPF panels. The configuration is created by running those jobs in thespecified sequence.

In short, the zPMT is very similar in concept to the ISPF panels..

What WeWish ToIllustrate:

Launching the tool

This really involves three steps:

1. Launching the Application Server Toolkit2. Selecting the workspace to use3. Invoking the zPMT function from within the AST

All are relatively easy things to do.

1- Launching AST

From the "Start" button, go to:

IBM WebSphere � Application Server Toolkit V6.1 � Application Server Toolkit V6.1

One of the first things it'll ask if what "workspace" you wish to work with.

2 - Selecting workspace

A "workspace" is nothing more than a folder structure in which the AST keeps all the informationit needs about the various projects and programs you're working on. The workspace can beanywhere the AST tool has write access to. That could be a local drive or a network drive. Aslong as the local operating system recognizes the drive and has write access, it should work.

You specify the workspace to use on a window that looks like this:

Type the drive and folder here, or use the "Browse" button

For your first use of zPMT you can simply name a location, such as C:\MYCONFIG. You should

understand that a workspace may contain multiple configurations, and the implications of that.See "The workspace and what zPMT shows as saved configurations" starting on page 25 formore on this topic.


Section: MainVersion Date: Thursday, December 07, 2006


3 - Invoking zPMT function

Once the Application Server Toolkit is up, you'll see a screen that looks something like this:

The zPMT tool is a function under the "Window" pulldown

The zPMT tool is invoked by selecting the "Window" pulldown, then clicking on "Preferences."Then you do the following:

Expand "Server"

Click on "WebSphere for z/OS"

The zPMT is then available to you:

This was the "launching point" for the example we'll now show you.Note:

The planning spreadsheet

To illustrate how the planning spreadsheet is still a very useful tool, and one that's quite easy to usewith the zPMT, we used it for the Deployment Manager configuration shown here.




The reference here is to the Excel spreadsheet published at:

http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS1331

Note:

The key variables we entered on the "Variables" sheet were:

9500Starting TCP Port

www.zpmt.ibm.comDeployment Manager host name

www.zpmt.ibm.comStandalone host name

2400Starting UID

2500Starting GID

YesReduced RACF

YesShared Procs

ZPMTSave customization data set HLQ

ZLPAR qualifier

ZPTwo character cell abbreviation

ZPMTSystem Name

ZPMTPlexSysplex Name

If you download a copy of the spreadsheet and key in those variables, you can follow along with ourexample.

Why didn't we use the new "zPMT edition" of the spreadsheet? Because here we wanted toillustrate how the zPMT captures information panel-by-panel, in a manner similar to how theISPF panels do. Had we used the new zPMT edition of the spreadsheet, and used its very nicecopy/paste of the response file information, the zPMT might have remained somewhatmysterious to some. The objective for this paper is to demystify the zPMT.

???

Configuring a "z/OS deployment manager"

To illustrate this, we ran through the "z/OS deployment manager" option of the zPMT.

Selected configuration option

� Clicked the "Create" button

� Clicked the "Next" button at the information panel

� Selected "z/OS deployment manager" option and clicked "Next":

Configured panels

� On the "Customization Name and Location" panel we did the following:




Arbitrary name by which zPMT will know this configuration

Workspace:C:\ZZZZZZ

Default value

For the sake of space we cropped from the previous picture most of the zPMT panelthat really appeared. On that panel was also the option to specify a "response file." Ifwe had a response file we wished to read in (or "load") we could have simply pointed toit there and the zPMT tool would have read in the file and loaded the variables into thevarious fields. We could have then simply clicked through, changing whatever valueswe wanted to change. See "Loading a response file into a new customization" on page30.

Note:

� On the "Target Data Sets" panel we did the following:

From the spreadsheet "DMGR" worksheet.

This defined the high level qualifier for the CNTL and DATA data sets that would be used

on the z/OS system.Note:




� On the "Configure Common Groups and Users" panel we did the following:

All this is straight off the "Common MVS Groups and Users" tab of the planning spreadsheet

� On the "System Location: names and data set qualifier" panel we did the following:

This information was derived from the "DMGR"

tab of the spreadsheet




� On the "System Location: Product data sets" panel we did the following:

We pulled this value from "Locations of HFS Resident Components" section of "DMGR" tab in spreadsheet. This is

the "intermediate symbolic link" between configuration and SMP/E HFS

Rest of this was calculated by zPMT based on HLQ

specification on previous panel

Note: panels are sometimes long ... always look for scroll bar

STEPLIB = Y

What is an "intermediate symbolic link?" It's a UNIX symbolic link that's created betweenyour configuration HFS and the actual WebSphere product (or SMP/E) HFS. The valueof this is it provides flexibility and isolation. For a complete description of the value ofintermediate symbolic links, see WP100396 on ibm.com/support/techdocs.

Note:

� On the "Server: cell, node and server names" panel we did the following:

Straight off the "DMGR" tab of the planning spreadsheet




� On the "System Environment: configuration file system" panel we did the following:

This is off the "DMGR" tab of the planning spreadsheet. We had to scroll up a bit in the spreadsheet.

The fact we had to scroll up a bit in the spreadsheet illustrates how the zPMT tool'slayout and flow is slightly different from the ISPF panels. The planning spreadsheet iscurrently based on the ISPF panel flow. But it was quite easy to capture the informationoff the spreadsheet, even if it was a slightly different sequence.

Note:

� On the "System Environment: log stream and CTRACE writer" panel we did the following:

Straight off the "DMGR" tab of the spreadsheet

� On the "Server: define App_Server_Root" panel we did the following:

We took the default of:DeploymentManager

� On the "Optional Application Deployment" panel we did the following:

We took the default




The option to deploy or not deploy the Admin Console into the Deployment Manager isnot part of the ISPF panels, and consequently is not mentioned on the spreadsheet.The only reason you would not deploy the Admin Console into the DMGR is if youplanned to do all of your configuration work with WSADMIN.

Note:

� On the "Server: process definitions" panel we did the following:

All this is straight off the "DMGR" tab of

the planning spreadsheet

� On the "Server: port value assignment" panel we did the following:






� On the "Server: location service daemon definitions" panel we did the following:



� On the "Server: SSL customization" panel we did the following:

The values as generated by the planning spreadsheet, at the

bottom of the "DMGR" tab

� On the "Security: administrative security selection" panel we did the following:

We selected the first option, which was to use SAF




� Based on the option we selected on the previous panel, we were presented with the"Security managed by the z/OS product" panel. we did the following:

These values were off the "DMGR" tab of the

planning spreadsheet, under the "1 - z/OS

security product" section near the bottom

� On the "Job statement definition" panel we added the userid information under which the jobwould run. The ID under which the jobs run must have certain authorities, but it does notnecessarily follow that the user must be specified on the JOB card. We did it to simplyillustrate that the JOB card can be updated in the zPMT:

This information is not on the planning spreadsheet.

As system programmer you should determine whether to modify the

JOB card or not.

You should read carefully the "instruction member" that's generated by the zPMT. It willexplain in detail the authority requirements of the ID under which the customization jobsshould run. You can either read the instructions found in the CNTL data set afterupload, or you can use the "View" function we showed under "The ISPF panelsgenerated a handy set of instructions. Does the zPMT do that too?" starting on page 6.

Note:

Created jobs

� The next panel that presented itself was the "Customization Summary" panel. It looked likethis:

The fields here were all protected. The instructions

advised us to use the "Back" button to correct anything

that didn't look right.

We saw the progress bar appears:




And then we were presented with this panel:

Another "summary" panel. Everything looked proper, so

we clicked "Finish"

Completion and uploaded jobs

� The zPMT tool showed us the following:

Our newly created customization

definition

Action buttons ...

1

2

3

4

5

Notes:

1. Create -- create a new customization definition.

2. Regen -- make a modification to the settings of the chosen definition and regenerate it.

3. Delete -- remove the customization definition from the workspace

4. View -- view the information: summary, instruction member and response file

You do not need to wait until the members are uploaded to read the instructionmember. Just click on "View" and then select the "Instructions" tab.

Note:

5. Upload -- upload the customized members to a z/OS system. This is what we used to upload

the members to the z/OS system.




� Out of curiosity we looked in the folder structure under our "workspace" root of C:\ZZZZZZ

and saw the following:

This represented our new customization definition:

response file was in "ZPCELL_SYSZ" folder

Customized JCL batch in "cntl" folder

Customized script files in "data" folder

We do not recommend you make any manual modifications to these files. Usethe zPMT tool to make modifications (the "Regen..." button). Just like with thefiles created by the ISPF panels, a particular piece of information may be held inmultiple places. Changing it in only one place could make things not workproperly..

Important!

� We clicked on the "Upload ..." button and received the following panel:

Host of target z/OS system

Userid and password used to upload files

Where the uploaded members will go

We chose to have data sets allocated by upload process




We saw the progress bar as the members were being uploaded and the "success" indicator:

Result

� Up on the z/OS system we saw our two data sets:

DSLIST - Data Sets Matching ZPMT.**

Command ===>

Command - Enter "/" to select action

--------------------------------------

ZPMT.ZPDMGR.CNTL

ZPMT.ZPDMGR.DATA

� The CNTL data set had the usual members:

BBOCCINS

BBODBRAJ

BBODBRAK

BBODCHFS

BBODCPY1

BBODCZFS

BBODHFSA

BBODHFSB

BBOIPCSP

BBOPDCR

BBOPDCRZ

BBOPDMNZ

BBOPDMN2

BBOPDSR

BBOPDSRZ

BBOSBRAJ

BBOSBRAK

BBOSBRAM

BBOSCHED

BBOTCPID

BBOWAPLD

BBOWISCD

BBOWWPFD

Instruction member

Jobs to create RACF profiles

Job to allocate/mount HFS

Job to copy JCL into PROCLIB

Generated procs ready for copying

Profile generation job (the one that takes a long time to run)

In other words, the exact same things you're familiar with when this

is generated by the ISPF panels

� All that remained was to submit the jobs in the sequence specified in the instructionmember. That process is identical to how it is done when the jobs are generated by theISPF panels.




Some Recommendations for Getting the Most from zPMT

We anticipate this list growing and maturing as our experience and knowledge of real-world usage ofthe zPMT expands. Check the Techdocs web site periodically and see if a new copy of this hasbeen published. You can check the "Document Change History" on page 34 for information onupdates to the document.

Note:

General recommendations

Other sources of essential WebSphere configuration information

The zPMT is simply a different way to create the customized jobs that are then used to build theruntime configuration on z/OS. Using the zPMT does not make the resulting runtimeconfiguration any different than it would be had the ISPF panels been run.

Using the zPMT does not introduce anything new to the essential information aboutplanning a WebSphere for z/OS configuration as provided in the WP100653 whitepaper on ibm.com/support/techdocs. Think of the zPMT as another way to

generate the customized jobs.

Key Point:

Using the planning spreadsheet

The planning spreadsheet (PRS1331 on ibm.com/support/techdocs) is a very useful Excel

spreadsheet used to help coordinate your configuration planning. It is still very much applicableto the planning of a configuration built using zPMT.

Workspace recommendations

The "workspace" is a folder structure in which the AST maintains all the information about theconfiguration.

The workspace and what zPMT shows as saved configurations

When you invoke an instance of the Application Server Toolkit and point to a workspace to use,the AST will load up information about the different projects and programs from that workspace.But not other workspaces you may have. Consider the following example:

But that invoked instance of the AST can't "see" anything

in this other workspace.

C:\

\workspace1

Sub-folders and files

\workspace2

Sub-folders and files

zPMT Tool

I "see" everything in C:\workspace1

If you wanted to work with things stored in C:\workspace2, it would mean invoking AST again

and pointing to that workspace. (The tool also has the ability to "switch workspaces" withoutrequiring stopping and restarting. That function is located under the "File" pulldown.)




The workspace specified at AST invocation determines what information is available tothe AST. It can't "see" other workspaces not specified.

Key Point:

There are two broad strategies here:

1. Maintain one workspace and configure everything in it.2. Maintain separate workspaces, either one workspace per project or some other grouping of

projects per workspace

What are the pros and cons? Let's list a few:

� If too many workspaces arecreated it may be difficult toremember what's kept where.

� Provides a nice way to keepthings separate from oneanother, if you feel a need tomaintain separation

� Provides a more granularmeans of backup and restore

� Makes it easier for differentpeople to work at the sametime.

Separate workspaces

� For application work -- EJBprojects, web projects -- itcan get a bit confusing. Thisis less true of zPMTconfigurations.

� Backup and restore is for allprojects. Not as muchgranularity.

� If the workspace is on anetwork drive, only one copyof AST can be accessing it ata time.

� No question about whatworkspace to specify

� Provides a single point forbackup/restore

One workspace for everything

ConsPros

General guidelines: one workspace or multiple?

There's no hard-and-fast rule here. But consider the following:

� One workspace for everything is probably not advisable, unless the number of configurationsyou're maintaining is relatively small.

� Give some thought to how your zPMT configurations might be separated based on things such asSysplex, or separated based on organizations within your company.

� You should keep zPMT configurations in a separate workspace from those used for moreapplication-oriented things. The zPMT tool is used to configure the runtime. That's a differenttype of work from application modifications.

Beyond these three general guidelines it's really up to you how to you organize yourworkspaces.

Subtle variation -- zPMT customization definitions outside of workspace

The workspace is really something used by the AST. The zPMT, which is part of AST, will bydefault create its customization definition files in the same workspace. But when you're creatinga new zPMT customization definition, you can override the default and point to another location.The following picture illustrates this:




Workspace pointed to when AST started

Different customization definition directory specified on the panel

C:\NEW_LOCATION\MY_CONFIG

We bring this up because we want you to be somewhat careful with this. Please note thefollowing key things:

1. The AST is still operating out of the original workspace specified. All you've really done here is tellthe zPMT tool to write its customized jobs out to a different place.

2. The AST knows about this new location because it maintains a registry of all customizations done.That registry is maintained in the original workspace. So the next time you start AST and point tothe workspace, the AST will know about this other location because information about it is kept inthe registry.

3. The response file is part of this other directory structure. It's located under the folder in thisexample shown as "MY_CONFIG". See "Location of response file (and other files generated byzPMT)" on page 28 for more.

4. You could bundle up this folder and sub-folders and send it to someone else, but that is not thesame thing as sending them the whole workspace. All you would be doing is sending them theresponse file and the generated jobs. Their AST and their workspace wouldn't recognize it. Theycould, however, create a new customization definition and read in the response file. That wouldallow them to create a customization in their workspace equal to what you created.

5. If you do create customization definitions outside of the workspace, you must be aware thatbacking up everything involves backing up the workspace and all the other directories you pointedoff to. If you maintain everything under one workspace root, you have one tidy backup andrestore point.

As we said: use caution. If you want to keep your individual customization definitions in adifferent location from the workspace, that's fine. Just be aware that AST is maintaininginformation about the definitions back in the workspace as well.

Let's say you accidentally deleted the non-workspace location. Would you customizationdefinition be lost? Not at all ... remember that the AST is maintaining a second copy of theresponse file. Your generated jobs are gone, but with the response file you can create a newdefinition, load in the response file, and essentially recreate the jobs exactly as they werebefore.

???

Copying workspaces and sharing them with others

It is possible to ZIP up a workspace and e-mail it to someone else, but it's not something werecommend you do. Do it only if you're looking to move the workspace to another workstation.Do not do it as a means of sharing configuration definitions with someone else.

If someone is interested in using one of your configuration definitions as a starting point fortheir configuration, the better thing to do is to send them your response file. (See "Sending aresponse file to others" on page 30.)

Note:




You should avoid the situation where the same WebSphere runtime configuration is supportedby multiple copies of the workspace. Difficult issues of change control come up ... for example,"Which copy is the master copy?" Or "Are the two workspaces the same, or did someone makea change to one but not the other?"

There is no easy way to "synchronize" (or merge) two copies of the same configuration that havedrifted apart from one another. Therefore, avoid duplicating the workspaces.

Renaming workspaces

This is not recommended. The root directory name of the workspace is incorporated into manyof the underlying configuration files. Simply renaming the root workspace folder will corrupt theconfiguration files.

Backup and restore

The point of backup and restore is at the workspace root. In other words, if you create aworkspace at C:\MYWORK, and that workspace has ten different configurations under it, you

backup starting from C:\MYWORK and capture all ten configurations. You can't simply backup a

portion of an AST workspace.

This is one of the reasons why you may wish to consider maintaining multiple workspaces. Thisprovides a greater degree of granularity and flexibility. For example, all the configurations forSysplex A are in one workspace; all the configurations for Sysplex B are in another.

Restoring a workspace involves copying back the saved workspace, including all sub-foldersand files.

Do not rename the workspace root folder. That value is maintained in other locationswithin the workspace, and simply renaming the folder will corrupt the workspace.

Important:

Response file recommendations

The response file is a flat text file generated by the zPMT that contains all the information about agiven configuration definition. It is useful as a way to save the variables from a configuration, or as away to import variables into the zPMT from someone else. There are two ways to get at theresponse file: pull it from the workspace, or copy/paste from the "view" function.

Location of response file (and other files generated by zPMT)

Here's a map showing where the files are located:

The workspace root

zPMT puts its stuff under this folder

Each customization definition has its own folder under "profiles"

The "cntl" and "data" folders are where the

generated jobs are placed.

The response files are kept in these

two folders




The key thing to note about this picture is that the response file is really located in two locations:

1. Under the customization definition's folder. That folder will have the name you gave thecustomization definition.

2. Under the profileDefinitions folder. Think of this as the place where all the response files

for all the customizations definitions for the workspace.

If you're going to send a response file to someone else, it's best to pull it from the folder thatbears the name of your customization definition. Our reason for saying this is simply this: thatfolder will contain only one response file, while the profileDefinitions folder will possibly

have many response files. The chances of grabbing the wrong response file are less if you goto the customization definition's folder.

But the truth is it doesn't really matter ... the response files are identical in both places. If you gointo the profileDefinitions folder you can pretty easily pick out the right response file

based on the name:

The name you provided in the "Customization definition name" field

ZPCELL_SYSZ.responseFile

Fixed value:responseFile

Using the copy/paste method of producing a response file to send to others

Another way to produce a response file to send to others is to use the "view" action of the zPMTand then select the "Response File" tab. From there, a simple "select all," then "copy" will putthe data into the Windows clipboard. You may then paste it into a Notepad file of your choice.

"Select All", then "Copy"

Notepad, or some other editor

Making manual modifications to the files in the workspace

Don't do it. AST and the zPMT maintains information in several different places. Making achange in one location may not be sufficient. It's always better to make modifications to yourcustomization definition through the zPMT tool. See "Making a modification to an existingconfiguration definition" on page 31.




Sending a response file to others

This is simply a matter of e-mailing a copy of the response file to that person. For the twomethods of producing a file to send, see "Location of response file (and other files generated byzPMT)" on page 28, or "Using the copy/paste method of producing a response file to send toothers" on page 29.

They in turn would read the response file into their copy of zPMT. We'll look at that next.

Loading a response file into a new customization

The zPMT tool allows you to specify a response file as input to a new customization definition.It's done on the "Customization name and location panel":

Type the full path and file name, or use the "Browse"

button to locate the file

By loading the response file, you "prime" (pre-load) the variable fields with the values found inthe response file.

Recall that there are five different "environments" (customization types) -- application server, anentire cell, a deployment manager, etc. Each response file has within it an indication of whattype of environment was created. If you create a Deployment Manager customization, then theresponse file for that will have within it an indicator saying the file is for a DMGR configuration.

If you're creating another Deployment Manager and you load this file as a starting point, then thezPMT will be perfectly happy. All the variable fields will be populated with the values from theresponse file.

But let's say you're creating a "federation" customization and you load a Deployment Managerresponse file. Is that okay? The zPMT will permit the loading of the response file. But therequirements of the "federation" customization are different from the Deployment Manager.Therefore, some fields -- primary host name fields -- in the federation customization will beempty. The response file did not have variables corresponding to those fields, so the zPMT willsimply leave them blank.

That's acceptable -- simply fill in the blank fields and proceed to generate the customized jobsas you normally would.




Managing existing customization definitions

Here we'll say a few words about what to do with your existing customization definitions.

Making a modification to an existing configuration definition

Let's say you have a customization definition and you discovered that one of the values youprovided earlier is incorrect. Here's how you would correct it:

� First, select your customization definition and click on the "Regen" button:

Select definition, then click on "Regen"

� When you get to the "Environment Selection" panel -- the one where you pick "ApplicationServer" or "Deployment Manager," etc. -- make sure you select the same environment typethat was originally used. If you don't you'll get a warning: "Customization definition type willbe changed!" That means the JCL batch jobs that are created will be for the newconfiguration type, not the old. Be careful.

� Then go through the panels as you did before. Make whatever modifications you deemnecessary.

� When you get to the end, click on the "Create" and "Finish" button to regenerate the jobsand update the information in the workspace.

An interesting thing happens: the original profile folder name -- let's say ZPMT_SYSZ --

is incremented with a kind of version number: ZPMT_SYSZ.1. If you regenerate the

definition again, the 1 is turned into a 2. This is really just trivia to you ... it should not

affect how you create customizations or create your z/OS runtime.

Note:

Uploading the generated files

Once you've generated the jobs in the zPMT, you may upload them to your z/OS system.

� Select your customization definition and click on the "Upload" button:

Select definition, then click on "Upload"




� The next panel asks you for information needed to upload the files:

1

2

3

4

5

Notes:

1. The host name of the target z/OS system to which the upload will take place. By default thiswill be set equal to the host name specified for the node. You may override that value here ifyou wish.

The jobs should be executed on the same system where the WebSphere serversthemselves are intended to run.

Note:

2. The userid and password used to perform the upload.

3. The target data sets. These fields are grayed-out. They are based on the information youprovided in the definitions. To change them requires you go back into the definitions andregenerate the jobs.

4. You may have the tool allocate the z/OS data set on the fly, or you may uncheck this if you'vepre-allocated the datasets. If you pre-allocate, the allocation values are:

General DataOrganization . . . : PORecord format . . . : VBRecord length . . . : 255Block size . . . . : 279981st extent tracks . : 5Secondary tracks . : 5

General DataOrganization . . . : PORecord format . . . : FBRecord length . . . : 80Block size . . . . : 80001st extent tracks . : 15Secondary tracks . : 15

DATA data setCNTL data set

5. If you want zPMT to allocate and you wish to specify the volume and unit, do so here.

� When you click the "Upload" button, the transfer will take place.

Once on the z/OS system, the process of executing the jobs is the same as it would be if thejobs had been generated by the ISPF panels. Consult the instruction member in the CNTL dataset and follow the steps as indicated.




Deleting a customization definition

This is easily accomplished through the zPMT:

� Highlight the customization definition and click the "Delete" button:

Select definition, then click on "Delete"

The zPMT will clear the information from the workspace.




Available AST and zPMT code and updates

� AST V6.1.1.0 with zPMT 6.1.1.v200611161118

http://www.ibm.com/support/docview.wss?uid=swg24014241

Prerequsite: "This refresh pack can be installed on an existing IBM WebSphere Application Server

Toolkit Version 6.1.0.0, 6.1.0.1, or 6.1.0.2 installation."

You can determine your current level of AST and zPMT code by invoking the AST and clickingon "Help" and "About." The version of the AST will be reported on that panel. To see theversion of the zPMT feature, click on the button "Feature Details" and scroll to the bottom. Find"zPMT Plug-in".

Note:

Document Change History

Check the date in the footer of the document for the version of the document.

Updated document with pointer to AST V6.1.1.0 refresh pack information (this page).December 7, 2006

Added more information about the new zPMT edition of the planning spreadsheet,available at ibm.com/support/techdocs under number PRS1331. Also published

along with this paper a Powerpoint presentation covering the essential points of thiswhite paper.

November 17, 2006

Document number WP100871 added to document and re-published.October 13, 2006

Original document.October 10, 2006

Document Change History

End of Document WP100871


Section: Document Change HistoryVersion Date: Thursday, December 07, 2006


iiiintroducing the zpmtntroducing the zpmt · the customized jcl batch jobs that ultimately create...

Documents