Installing ZETALY Automated Capacity©

Installing ZETALY Automated Capacity© in z/OS

The installation process consists of:

• Restoring all ZAC delivered files;
• Setting values for installation parameters;
• Customizing installation jobs;
• Executing installation jobs and operations.

There are two kinds of installation: new installation “from scratch”, and migration from a previous version of ZETALY Automated Capacity©. In both cases, you must customize the SAMPLIB dataset, which will contain installation jobs and tools.

In the case of a migration, you also must customize the MIGRATE dataset, which will contain migration jobs.

Restoring of ZAC delivered files (required)

Zip file contents

ZCOST.ASCVnnnn.Lvvvvvvv.DUMP.zip file includes the ZCOST.ASCVnnnn.Lvvvvvvv.DUMP.XMI file. This file contains an ADRDSSU DUMP of the following files:

• ZCOST.ASCVnnnn.LEVELS Delivery Levels summary (Information only)
• ZCOST.ASCVnnnn.INSTDOC Quick install guide
• ZCOST.ASCVnnnn.LOADLIB Load modules library
• ZCOST.ASCVnnnn.HTM Html install files
• ZCOST.ASCVnnnn.INSTALL Installation & sample JCLs
• ZCOST.ASCVnnnn.PARMLIB Parmlib members raw samples
• ZCOST.ASCVnnnn.ZFS Main ZFS file (programs, images…)

Restore ZAC files

Extract ZIP file (required)

Extract (unzip) the delivered dump file ZCOST.ASCVnnnn.Lvvvvvvv.DUMP.zip described above

Upload XMI file (required)

Upload ZCOST.ASCVnnnn.Lvvvvvvv.DUMP.XMI to z/OS using FTP or IND$FILE.

Receive DUMP file (required)

In your TSO environment, issue the RECEIVE command to extract the "xmi" file.

Restore ZAC files from DUMP file (required)

Restore the files from &hlq..ASCVnnnn.Lvvvvvvv.DUMP using ADRDSSU.

Installing ZETALY Automated Capacity© for the first time

Once all delivered files are restored, you may use the hlq.ASCVnnnn.INSTDOC restored file as a guide to perform standard quick installation. This file is a PDS containing one member per step of the installation. The steps are named accordingly to the order they must be executed. Each member briefly describes the process, the action to do by the installer and the expected result of the step.

If necessary, to obtain more details about installation steps, refer to the process documentation below.

Customizing the installation file (required)

In this process, you will choose the values of all installation parameters and execute a job that generates a

SAMPLIB library, which will contain all customized installation jobs.

Update $INSTPRM member

Update $INSTPRM member in the ZAC INSTALL library accordingly to your environment.

In this member, you must provide all the values required to customize SAMPLIB JCLs. All the values originally set are the default installation values.

Considerations about Installation paths

Installation paths names are very important. They are used to access programs, to communicate with the HMC, to access current and backup HTML pages, and data of the HTTP server.

There are three installation paths:

• The main install path (path, used to access programs icons and images);
• The web installation path (pathweb, used to define where reporting data will be stored);
• The backup installation path (pathbkp, used to define where archived reporting data will be stored).

Define installation paths:

• The three installation paths are explicitly provided in a special file that must be defined in the monitor STC using the DDNAME PATH. This file may contain three records as follows:

The default installation path name delivered in the installation package are /u/asc/pgm, u/asc/web and u/asc/backup.

You may change them accordingly to your standards.

Generate customized installation jobs

Submit $ASCUSTM job from ZAC INSTALL library. This Job will create and customize the SAMPLIB library, where all jobs required for the installation will be located.

Installing ZETALY Automated Capacity© Monitor

All required installation jobs are located in the customized SAMPLIB library.

There are three parts in ZETALY Automated Capacity© which are managed by three Started Tasks.

• The Monitor (Main STC)
• The ZAC Agents (Collector STC)
• The Web reporter (Http Server STC)

Monitor, Collector agents and reporter are always required.

Define the RESTART Dataset

ZETALY Automated Capacity© is designed to allow for restarting in “WARM mode”. This feature requires storing the “restart” data into a file used at restart time.

Review and submit ALLORDS job of the SAMPLIB.

Define ZFS Files

ZAC uses 3 ZFS (HFS) files to store reports elements.

• The main ZFS file contains ZAC programs and elements requested to navigate in reports. It is provided.
• The Web ZFS file, contains current web reports. It is not provided; you must create it.
• The Backup ZFS file, contains archived reports. It is not provided; you must create it.

Define ZFS File for Web Reports

The ZFS file, which will contain current web reports, is not provided in the ZAC package; you must define your own allocated space. The size of your current reports depends on the number of reported objects (CPCs, LPARs, SYSPLEX, WLM Service Classes) and on the depth of the reporting (see ASC REPORTDEPTH parameter). On an indicative basis, the size will use 1000 k-bytes as fixed, 50 k-bytes per LPAR, 100 k-byres per container, plus 10 k-bytes per service class defined in the LPAR, 30 k-bytes per LPAR in a group, to store 24 hours depth data.

For example, if your ZAC manages 20 LPARs with an average of 20 Service Classes per LPAR, and 5 LPARs in groups, and your report depth is 36 hours, your current reports will use approximatively:

(1000 + 50*20 + 10*20*20 +30*5) * 36/24 = 9 225 k-bytes.

Review and submit ZFSWEBAL job of the SAMPLIB.

Define ZFS File for Archived Reports

The ZFS file, which will contain archived reports, is not provided in the ZAC package; you must define your own allocated space. The size of your archived reports depends on the number of reports you plan to keep. Each archived report will require the same size than the current report to archive. See details for size calculation in previous chapter 4.2.2.2.1 Define ZFS File for Web Reports.

Review and submit ZFSBKPAL job of the SAMPLIB.

Set APF Authorization for ZETALY Automated Capacity© Loadlib

Static Definition

Create or modify PROGxx in your PARMLIB.

Define the ZETALY Automated Capacity© loadlib and its volume (or SMS). Then, activate it (SET PROG=xx).

Dynamic definition

Use the following command to do a dynamic definition in console mode:

SETPROG APF ADD DSN=ZCOST.ASCVnnnn.LOADLIB,VOLSER=vvvvvv

A sample is provided in the APFADD member of the SAMPLIB.

Set TSO authorization for ZETALY Automated Capacity© main program

Add the ASCMAIN program into your IKJTSOxx member in segment AUTHCMD segment:

AUTHCMD NAMES(ASCMAIN) /* ZAC */

The command below allows a dynamic definition in console mode:

TSO PARMLIB UPDATE(xx) SET IKJTSO=XX

A sample is provided in the IKJTSOXX member of the SAMPLIB.

Create catalogued procedure for the Monitor (main STC)

You can find a procedure sample in ZCASC member of the SAMPLIB.

Customize the main procedure PROC statement.

//ZCASC PROC PRMGEN=xx,PRMLPA=xx,PRMALT=xx,PRMKEY=xx,PRMCTN=xx,

// DUP=N,RUNMODE=A,START=WARM,DIAG=0

Choose the parmlib member suffixes (xx) that will be used to start the STC.

• START parameter is provided with value WARM. Code START=COLD if you wish to use COLD mode when starting the STC (see chapter 4.4.1 “Starting ”). This parameter can be overridden at start time, in the start command.
• RUNMODE parameter default value is A. Code RUNMODE=M if you wish to always start in message mode or RUNMODE=R if you wish to always start in reporting only mode. This parameter can be overridden at start time, in the start command.
• DUP parameter allows several main STCs to be started on the same LPAR. The default value is N. This parameter can be overridden at start time, in the start command, for specific cases.
• DIAG parameter allows different levels of information to be obtained for diagnostic purpose. 0 indicates no diagnostic messages, 3 is the maximum and provides more information about the communication with ZAC collector process. Default value is 0.
• PRMCTN parameter is available for container pricing feature, it's an optional parameter. This parameter member is necessary for container reporting. By default, this parameter is disable.

Observation:

In case of more than one TCPIP stack, it is necessary to add SYSTCPD DDname to ZCASC procedure pointing to the correct TCPIP.DATA dataset. Consult your Network system programmer.

Optional: History files

If you plan to use history files, allocate them using the ALLOHIST job of the SAMPLIB and uncomment the HISTA and HISTB DD cards.

Note: this feature is provided for compatibility reasons with previous versions of ZETALY Automated Capacity©. It is strongly recommended to use SMF records instead.

Define RACF authorizations

Authorize the ZCASC userid to use Open Edition Services. If required, please contact your security administrator. Below are recommended RACF commands. You can use the RACF job of the SAMPLIB. Also available ACF2 and TSS jobs.

AG ZCASCGRP OWNER(RACFADMUSER) OMVS(GID(NNN)) AU (ZCASC) NAME('MAIN STC AUTO SOFT CAPPING') +

OWNER(RACFADMUSER) NOPASSWORD + DFLTGRP(ZCASCGRP) OMVS(HOME(/u/asc/) UID(2221))

RDEFINE STARTED (ZCASC.*) UACC(READ) OWNER(RACFADMUSER) + STDATA(USER(=MEMBER))

SETROPTS GENERIC(STARTED) RACLIST(STARTED) REFRESH

Code sample 1 STCs RACF authorizations

If the RACF PROGRAM CLASS is activated on your site, you must run the job RACFWEB in the supplied

SAMPLIB to define the authorized programs for the ZAC web server.

Secure ZAC modify commands

As of version 3, ZAC checks whether modify commands issued by the current use Restoring ZAC distributed files are authorized or not. This feature is always active. ZAC will check the commands against security profiles defined in the security class you choose.

The profiles listed below may be set in generic form.

Table 2 List of ZAC commands security profiles (profiles in bold are new in V4.0)

These rules can be defined either in RACF, CA Top-secret or CA ACF2. Use one of the following procedures.

Using RACF

You may use the FACILITY class to define your security profiles. However, best practices encourage using the dynamic CDT class to declare your own classes. All commands to define your RACF ZAC class and your RACF resources are provided in job RACFCMD.

Review and submit RACFCMD job of the SAMPLIB. Also available ACF2CMD and TSSCMD jobs.

Using the dynamic CDT

If the dynamic CDT class is not used yet on your environment, issue the following command:

SETROPTS CLASSACT(CDT) RACLIST(CDT)

Code sample 2 CDT class activation

Then, declare your own class as a resource class of the dynamic CDT by issuing the following RACF command:

RDEFINE CDT $ZASCCMD CDTINFO(POSIT(nnn) MAXLENGTH(44) FIRST(ALPHA,NATIONAL) OTHER(ALPHA,NUMERIC,NATIONAL,SPECIAL) GENERIC(ALLOWED) GENLIST(ALLOWED) RACLIST(ALLOWED))

The POSIT number should be unique and in the range 0-1023 for this class. Numbers 0-18, 57-127, 528- 1023 are reserved for IBM use. The class name should start with a special or national character as recommended by IBM. In the command above, the $ZASCCMD class name given is a sample and may be adapted to your needs.

Then refresh the dynamic CDT:

SETROPTS RACLIST(CDT) REFRESH

It is also relevant to check that the chosen class is active, by using a SETROPTS LIST command. If it is not, use the following RACF command:

SETROPTS CLASSACT($ZASCCMD)

Then allow the class to hold generic resources and to accept generic commands:

SETROPTS GENCMD($ZASCCMD) SETROPTS GENERIC($ZASCCMD)

We recommend that you RACLIST your class prior to append resources:

SETROPTS RACLIST($ZASCCMD)

Resource definitions

Once you have an operational class to hold your resources, you must define these resources.

Use the profile names listed previously as your resource names, either strictly or in a generic form.

RDEFINE $ZASCCMD ASC.DISPLAY.HELP UACC(NONE) OWNER(owner) RDEFINE $ZASCCMD ASC.SET.* UACC(NONE) OWNER(owner)

…

You may use the job RACFCMD job of the SAMPLIB to define your RACF resources.

User associations

Finally, define the appropriate rights your users should have on the resources. Note that ZAC only checks against a READ access on the resource.

If you plan to use ZAC to send commands using the Alert process, you must authorize the Monitor STC to do this.

PERMIT ASC.DISPLAY.HELP CLASS($ZASCCMD) ACCESS(READ) ID(Stcuser) PERMIT ASC.SET.* CLASS($ZASCCMD) ACCESS(READ) ID(Stcuser) …

If necessary, refresh the RACLIST class as the previous commands results advised you to.

SETROPTS RACLIST($ZASCCMD) REFRESH

Using CA-Top Secret

First, add a class to the CA-Top Secret Resource Definition Table. The following $ASCCMD class name is given as an example and should be adapted to suit your needs. The RESCODE must be set to an HEX value between 101 and 13F.

TSS ADD(RDT) RESCLASS($ZASCCMD) RESCODE(xxx) ACLST(NONE,READ) DEFACC(NONE)

Then register the resource prefix to a resource owner you want:

TSS ADD(owner) $ZASCCMD(ASC.)

Then give access to resource or resource set to specific users:

TSS PER(user1) $ZASCCMD(ASC.DISPLAY.HELP) ACCESS(READ) TSS PER(user2) $ZASCCMD(ASC.SET.) ACCESS(READ)

You may use the job TSSCMD job of the SAMPLIB to define your resources.

Using CA ACF2

ACF2 requires a mapping to ensure compatibility between SAF classes and its own 3-character resource types. In the following excerpt of code $ZASCCMD and ASC are given as samples and should be adapted to suit your needs. Mapping is done by inserting a CLASMAP record as follows:

CLASMAP RESOURCE($ZASCCMD) RSRCTYPE(ASC) ENTITYLN(44)

Then define the access rules according to the profile table given earlier. Note in the following sample that the TYPE has necessarily the same value as the RSRCTYPE above. Here we want user1 and user2 to have access to resource ASC.HELP and ASC.SET respectively. ASC application needs to have a READ access.

$KEY(ASC) TYPE(ASC)

HELP UID(user1) SERVICE(READ) ALLOW SET UID(user2) SERVICE(READ) ALLOW

You may use the job ACF2CMD job of the SAMPLIB to define your resources.

Operations on ZFS

ZAC uses 3 ZFS files to store reports elements.

• The main ZFS file contains ZAC programs and elements requested to navigate in reports. It is provided.
• The Web ZFS file contains current web reports. It is not provided; you must create it.
• The Backup ZFS file contains archived reports. It is not provided; you must create it.

Creation of ZETALY Automated Capacity© ZFS Directories

Review and submit the ZFSMKDIR job of the SAMPLIB.

ZAC ZFS files mount

Mount the ZAC ZFS main files in the directory created in the previous step. Review and submit the ZFSMOUNT job of the SAMPLIB.

You may verify that the files are correctly mounted by using the ‘D OMVS,F’ command.

Populate ZFS Web file

Four pre-defined files are necessary to ZAC reports viewing.

• Doc.htm The online messages and codes manual.
• Index.htm The html definition of the business view;
• Prmasc.htm The Html page which format the parameters web view;
• Stclog.htm The Html page which format the web representation of the STC job log;

These files are delivered in binary format and are stored in the HTM library. You must copy these files to the allocated Web ZFS dataset.

Review and submit HTMMPUT job of the SAMPLIB.

Files owner update

To be accessed by the ZAC components, the defined OMVS files must have correct owners. Review and submit ZFSCHOWN job of the SAMPLIB.

Make ZAC file mounts permanent

Add the ZAC ZFS mount commands into the active BPXPRMxx member of your z/OS PARMLIB, to ensure that ZFS files remain mounted after an IPL. You can use the SAMPLIB member BPXPRMXX.

Customize HLQ1 to match your naming conventions and add the following entries. If you changed the default path, customize the MOUNTPOINT too.

MOUNT FILESYSTEM(‘HLQ1.ASCVnnnn.ZFS’)

TYPE(ZFS) (or HFS) MODE(RDWR)

MOUNTPOINT(‘/u/asc/’)

MOUNT FILESYSTEM(‘HLQ1.ASCVnnnn.WEB.ZFS’)

TYPE(ZFS) MODE(RDWR)

MOUNTPOINT(‘/u/ascweb/’)

Code sample 3 Make ASC ZFS mount points permanent

Optional: Create a zcost.resolve file.

If you are using HMC setting method, during the LPAR DEFCAP setting, ZETALY Automated Capacity© runs UNIX SERVICES processes. Usually, UNIX SERVICES processes perform TCP/IP prefix resolution using

/etc/resolv.conf OMVS file that contains TCPDATA parameters.

However, some sites do not allow the use of this file. In this case, define a file named zcost.resolve under your ZETALY Automated Capacity© /pgm path and copy the TCPDATA content to it. This file will be used during the LPAR DEFCAP setting process, instead of the standard /etc/resolv.conf file.

Update the Key in the ASCKEYxx member of ASC parmlib

You must update the license key in the ASCKEYxx member in the PARMLIB, with the software key provided by your product vendor. Starting in ZAC V4.4, the license can be read from any column and not necessarily from column 1

Note: An ASC0951W warning message will be sent to the ZAC STC log and a SYSLOG, 30 days before the ZAC key expires. This message is sent every day at 12:00 and at each start of the main STC. Once the available period is expired, the product continues to run until it is stopped. The ASC0951W message is still sent but the text is changed to alert that the key has expired. It can also be dynamically refreshed by console command F ZCASCSTC,REFRESHKEY.

Table 3 ZAC KEY file example

****** ************************ Top of Data *************************** 000001 * CPU KEY OBTAINED FROM ZETALY

000002 2KYGX-65DBZ-F5UV3-TJ75J CPC 0B62B EXPIRATION 20190131

****** *********************** Bottom of Data *************************

Installing ZETALY Automated Capacity© Reporting web server

The ZAC web reporting application can run either on DOMINO web server or APACHE web server. You must choose which one you plan to use. Your possible choices depend on the z/OS version you are running.

• If you are using a z/OS release prior z/OS V2.1 you must use DOMINO web server.
• if you are using z/OS V2.2 or above you must use Apache web server.
• Because with z/OS V2.1 APACHE web server is provided through "IBM ported tools", if you are using z/OS V2.1 you can choose either APACHE or DOMINO web server.

Refer to the appropriate installation process below.

Using DOMINO as web server

All installation jobs are in the customized SAMPLIB library.

Create Catalogued Procedure for the Web Reporter in a system PROCLIB

- e.g.: SYS1.PROCLIB(ZCASCW)

You can find a procedure sample in ZCASCW member of the SAMPLIB.

Customize the web reporter procedure.

//ZCASCW PROC ZCASCPRM='-R /u/asc/zcost.conf -P 2312’

Warning: Check the PORT in the ZCASCW procedure. Check the path in “zcost.conf” and “zcost.envvars” files.

Define RACF Authorizations

Authorize the ZCASCW userid to use Open Edition Services. If required, please contact your security administrator. Below are recommended RACF commands.

You can use the RACFW job of the SAMPLIB. Also available ACF2W and TSSW jobs.

Table 4 RACF authorizations definition for ZAC Web Reporter

AU (ZCASCW) NAME('WEB REPORT STC AUTO SOFT CAPPING') + OWNER(RACFADMUSER) NOPASSWORD + DFLTGRP(ZCASCGRP) OMVS(UID(2222))

PERMIT BPX.SERVER CLASS(FACILITY) ID(ZCASCW) ACCESS(UPDATE) RDEFINE STARTED (ZCASCW.*) UACC(READ) OWNER(RACFADMUSER) +

STDATA(USER(=MEMBER))

SETROPTS GENERIC(STARTED) RACLIST(STARTED) REFRESH SETROPTS GENERIC(FACILITY) RACLIST(FACILITY) REFRESH

If the RACF PROGRAM CLASS is activated on your site, run the job RACFWEB to define the authorized programs for the ZAC web server.

Create the www .browsable file

The www.browsable file is an empty file used by DOMINO HTTP server to obtain read authorization on the directory where archived reports are stored (DOMINO HTTP server only).

Review and submit the job ZFSBKWWW job of the SAMPLIB.

Create the DOMINO zcost.conf file.

This file contains the directives required for the web server on which ZAC reporting application will run. First, check ZFS ZAC program file is mounted.

Review and submit the JOB ZCOSTCNF job of the SAMPLIB.

Using APACHE as web server.

This installation process assumes an APACHE Server is already installed on your z/OS environment. The ZAC reporting web server will be regarded as a virtual web server and then declared as a "VirtualHost" in your APACHE instance.

All installation jobs are in the customized SAMPLIB library.

Create the APACHE zcost.conf file.

This file contains the directives required for the web server on which ZAC reporting application will run. First, check ZFS ZAC program file is mounted.

Review and submit the job APCHCONF job of the SAMPLIB.

Declare ZAC zcost.conf file in your existing APACHE configuration file.

To locate your APACHE configuration file, look at your APACHE STC JCL (HTTPDACS) and get DIR and CONF parameters values. Here is an example of APACHE procedure:

//HTTPDACS PROC ACTION='start'

// DIR='/ihsconfig/his/httpdacs',

// CONF='conf/httpd.conf'

//HIS EXEC PGM=BPXBATCH,

// PARM='SH &DIR/bin/apachectl -k &ACTION -f &CONF -DNO_DETACH',

// MEMLIMIT=512M

In this example, the APACHE configuration file is /ishconfig/ish/httpdacs/conf/httpd.conf

The directive you must add is: Include "/asc_path_name/zcost.conf"

To assist you, this directive has been generated in the SYSTSPRT file during zcost.file creation by the job

APCHCONF.

Edit your APACHE configuration file and add the directive at the end of it, as the sample below:

EDIT /ihsconfig/ihs/httpdacs/conf/httpd.conf Line 0000000895 Col 001 080 Command ===> Scroll ===> CSR

# The following example configuration can be activated by uncommenting # the LoadModule directive.

#LoadModule net_trace_module modules/debug/mod_net_trace.so

<IfModule mod_net_trace.c> NetTraceFile /tmp/nettrace

NetTrace client * dest file event senddata=65535 event recvdata=65535

</IfModule>

Include "/u/asc/zcost.conf"

******************************** Bottom of Data *************************

Validate APACHE configuration file by the following commands from OMVS (use TSO OMVS command): ZCUSR2:/u: >cd /ihsconfig/ihs/httpdacs/bin ZCUSR2:/ihsconfig/ihs/httpdacs/bin: >apachectl configtest

Syntax OK

ZCUSR2:/ihsconfig/ihs/httpdacs/bin: >

Enable Reporting SAF sign on.

By default, the connection to ZAC web reporting requires a SAF sign on.

In the APACHE configuration file verify that following modules are declared and uncommented (To uncomment a line, remove the hashtag in first column).

LoadModule auth_basic_module modules/mod_auth_basic.so LoadModule authz_user_module modules/mod_authz_user.so LoadModule authnz_saf_module modules/mod_authnz_saf.so LoadModule authz_default_module modules/mod_authz_default.so

If some module declarations are missing, add the declarations as above and verify in the APACHE modules directory that the modules are present. Based on the previous sample PROC, the path should be:

/ihsconfig/ihs/httpdacs/modules/

Optional: Disabled SAF sign on

This step is only required if you are using APACHE web server and you want to disable the sign on to access the ZAC web reporting.

Edit the zcost.conf configuration file, then remove or comment the following lines :

<Location />

AuthName "ZAC web reporting" AuthType Basic AuthBasicProvider saf Require valid-user

AuthSAFExpiration "EXPIRED! oldpw/newpw/newpw" AuthSAFReEnter "Enter new password one more time"

</Location>

#

# In case of Apache 9.0, the following lines

# should be added and uncommented, when SAF mode is inhibited #

# <Directory />

# Options FollowSymLinks # AllowOverride None

# FileETag All -INode # Require all granted # </Directory>

For /backup directory, comment the "Require all granted" statement as below:

<Directory "/u/your/asc/asc4500/backup/"> Options +Indexes +FollowSymLinks +MultiViews

IndexOptions HTMLTable FancyIndexing SuppressHTMLPreamble IndexStyleSheet "/css/archiv.css"

IndexOrderDefault Descending Date # Order deny,allow

# Allow from all

# Require all granted

Optional: enable HyperText Transfer Protocol Secure (https)

This step is only required if you plan to enable https protocol over TLS.

You can use your own existing root certificate signed by a certification authority (CA) as GlobalSign or others. In that case, you can directly jump to chapter 4.2.3.2.5.4

The process below applies only to RACF security server.

Define zCost certificate authority (root certificate)

This certificate (AUTH) will be used to sign the web reporting certificate (SITE). It's a root authority certificate

By default, all required parameters for RACDCERT utility are provided. You can update them if desired. If you modify one of them, ensure in next steps that all parameters are coherent.

Review and submit job APCHSSL1.

Optional: Export root certificate

The certificate authority public key can be exported in order to be imported in your browser to prevent security warning during web reporting connections. This feature applies only if the web reporting URL is managed thru a DNS. If you use an IP address a security warning will always be emitted.

Review and submit APCHSSL2

The public key is stored in your HLQ.AUTHORTY.CERT dataset.

Download this dataset on your computer (using ftp in ASCII mode) with name zcost.crt.

Depending on the browser you are using, import the zcost.crt certificate. Follow the appropriate process below:

Internet explorer

Double click on zcost.crt file, then accept importation (this process will update Windows registry). You could need administrator privileges.

Firefox

From Firefox menu:

Tools -> advanced -> Certificates -> display certificates.

Ensure that tabs "Authority" is selected. Click on import button then select zcost.crt file. Accept all confirmations.

Chrome

From Options:

Parameters -> Display advanced parameters -> managed certificates.

Select "Trusted Root Certification Authorities" tabs. Click on import button then select zcost.crt file. Accept all confirmations.

Create SITE certificate

If you are using a DNS, change DOMAIN name and URL as required. All other parameters can be stay as they are delivered except if you have updated them in first step.

Review and submit APCHSSL3

Create and connect KEYRING with SITE certificate

Review and submit APCHSSL4

Set RACF FACILITY access

Review and submit APCHSSL5

Create Apache configuration file for https support

Review and submit APCHSSL6 (ensure that the KEYRING name is correct)

Define BPX RACF Authorizations.

Authorize the HTTPDACS userid assigned to Apache HTTPDACS Stc to use BPX.SERVER resource. If required, please contact your security administrator. Below are recommended RACF commands. You can use the RACFWA job of the SAMPLIB. Also available ACF2WA and TSSWA jobs.

Table 5 RACF authorizations definition to permit APACHE STC to use BPX.SERVER resource.

PERMIT BPX.SERVER CLASS(FACILITY) + ID(HTTPDACS) +

ACCESS(UPDATE)

SETROPTS GENERIC(FACILITY) RACLIST(FACILITY) REFRESH

Installing ZETALY Automated Capacity© Collector

You must install one collector instance on each LPAR, which will be managed by the monitor.

Define the RESTART Dataset

ZETALY Automated Capacity© Collector is designed to allow for restarting in “WARM mode”. This feature requires storing the “restart” data into a file used at restart time.

Review and submit ALLORDSC job of the SAMPLIB.

Create the STC procedure in a system PROCLIB

- e.g.: SYS1.PROCLIB(ZCASCCOL)

You can find a procedure sample in the ZCASCCOL member of the SAMPLIB.

//ZCASCCOL PROC INTERVAL=120,PORT=2391,

// SECCLASS=$ZASCCMD,DUP=N,DIAG=0,START=WARM,PRMKEY=00

• INTERVAL parameter represents the interval (in seconds) between two collects. The collector will aggregate metrics along the interval and produces a set of measures at its end. The value must be chosen accordingly (same value) to INTERVAL general parameter. For more information, refer to ZETALY Automated Capacity© User's Guide.
• PORT is the IP port that will be used by the monitor to communicate with the collector. This is a port on which the collector is listen to. The value must be chosen accordingly to COLLIPPORT LPAR parameter. For more information, refer to ZETALY Automated Capacity© User's Guide.
• DUP parameter allows several Collectors to be started on the same LPAR. The default value is N. The purpose of this parameter is to be overridden at start time, in the start command, for specific cases.
• SECCLASS parameter is the security class you have chosen to define security profiles used to control collector commands. The value must be chosen accordingly to SECCLASS general parameter. You may use a specific class or use the existing FACILITY class. For more information, refer to ZETALY Automated Capacity© User's Guide.
• DIAG is the diagnostic level. The value can be 0 to 3, where 0 is “no diag” and 3 is the most detailed level. Diagnostic data is written into SYSPRINT dataset. 0 is the default.
• START parameter is provided with value WARM. In normal operation, the collector may always start in WARM mode. Code START=COLD if you exceptionally would use COLD mode when starting the STC (see chapter 4.6.1 “Starting the ZAC collector”). This parameter can be overridden at start time, in the start command.
• PRMKEY is the suffix used to build the name of the parmlib member, which contains the product key.

Observation:

In case of more than one TCPIP stack, it is necessary to add SYSTCPD DDname to ZCASCCOL procedure pointing to the correct TCPIP.DATA dataset. Consult your Network system programmer.

Define RACF Authorizations

Below are recommended RACF commands. You may use the RACFCOL job of the SAMPLIB. Also available

ACF2COL and TSSCOL jobs.

AG ZCASCGRP OWNER(RACFADMUSER) OMVS(GID(NNN)) AU (ZCASCCOL)NAME('ASC COLLECTOR') +

OWNER(RACFADMUSER) NOPASSWORD + DFLTGRP(ZCASCGRP))

RDEFINE STARTED (ZCASCCOL.*) UACC(READ) OWNER(RACFADMUSER) + STDATA(USER(=MEMBER))

SETROPTS GENERIC(STARTED) RACLIST(STARTED) REFRESH

Code sample 4 RACF authorizations definition for ZAC Collector

Secure ZAC Collector Modify Commands

As of version 3, ZAC checks whether modify commands issued by the current user are authorized or not. ZAC will check the commands against security profiles defined in the security class you chose. The profiles listed below may be set in generic form.

You may use the RACFCMDC/ACF2CMDC/TSSCMDC job of the SAMPLIB.

If you do not plan to create a new security class, you may set the SECCLASS general parameter to the

FACILITY value.

Migrating ZETALY Automated Capacity©

Dismount ZFS files

The ZFS files mounted at /asc/backup and /asc/web can be reused from V4.4 (after level L2212311), just necessary to unmount it and mount it in the new directory for version V4.5. It is also possible to generate a copy of those ZFS files using ADRDSSU COPY command like the example job ZFSCOPY of the SAMPLIB, or similar non-IBM utility.

We recommend this second approach for backup purposes.

After ZFS copy, job HTMPUT from SAMPLIB dataset must be executed to update .htm files present in

/asc/web of V4.5

OPUT 'ZCOST.ASCV4500.HTM(DOC)' -

'/asc/pgm/doc/doc.htm' BINARY OPUT 'ZCOST.ASCV4500.HTM(STCLOG)' -

'/asc/web/stclog.htm' BINARY OPUT 'ZCOST.ASCV4500.HTM(INDEX)' -

'/asc/web/index.htm' BINARY

OPUT 'ZCOST.ASCV4500.HTM(PRMASC)' -

'/asc/web/prmasc.htm' BINARY

Migrate ZAC parmlib members

Migrate ASCGENxx ZAC parmlib members

In V4.5 a new parameter and two new OPTIONS have been introduced

• WLMAUTO parameter which automatically sets the WLM Service Class to SYSSTC. The default is YES
• New OPTION 7th, which activates the last used PERIOD when a COLD START is done
• New OPTION 8th, which requests a response to a REPLY if RUNMODE is about to be modified by an ACTIVATE command.

Migrate ASCLPAxx ZAC parmlib members

V4.2, V4.3 and V4.5 members are compatible. No action required.

Migrate ASCALTxx ZAC parmlib members

A lot of new variables have been added in Alert process in V4.3 and V4.4. V4.4 and V4.3 members are compatible, but you may review new available variables (from ASCALT00 V4.5 provided sample) to code new alerts about new consumption metrics and new container rules.

Create a new ASCCTNxx parmlib member

If you plan to manage containers, you must define a new ASCCTNxx member in your parmlib. Refer to the provided ASCCTN00 member sample to define your containers.

Define new ZAC commands authorization profiles

ZETALY Automated Capacity© commands are checked against security profiles. Therefore, you must add new security profiles to be able to use new V4.5 ZAC commands. The new commands are:

New commands appeared in V4.1

• SET SECURITYMARGIN (ASC.SET.SECUM)
• SET REACTIVITY (ASC.SET.REACT)
• SET DISTLVL (ASC.SET.DISTLVL)
• INIT REPORT (ASC.SET.INIT.REPORT)
• INIT REPORT ALL (ASC.SET.INIT.REPORT.ALL)
• INIT REPORT BILLING (ASC.SET.INIT.REPORT.BILLING)

New commands appeared in V4.2

• SET MOBILE (ASC.SET.MOBILE)

New commands appeared in V4.4 and V4.5

• SET PRMCTN (ASC.SET.PRMCTN)
• CHECKKEY (ASC.CHECK.KEY)
• REFRESHKEY (ASC.REFR.KEY)
• SET TRACE (ASC.SET.TRACE)

Upgrading ZAC to a new level in the same version

From time-to-time ZETALY Automated Capacity© receives new corrections or enhancements and it is necessary to incorporate them into the product and send them to the customers. This topic will address how to receive a new level of ZAC product.

Load Modules update

Most cases involving corrections and new enhancements are addressed by replacement load modules. In these cases ZETALY sends to the customers a whole new LOADLIB in IBM XMIT format, which includes the identification of the level. For the installation of the new LOADLIB, the following steps are necessary:

1. Pre-allocate a sequential dataset with LRECL=80 and RECFM=FB.
2. Transfer the file sent by ZETALY to this dataset, using FTP or other file transfer tool, but specifying BINARY mode as transfer type.
3. Once the file has been transferred, issue TSO RECEIVE INDATASET('the.preallocated.dataset').

A prompt will be issued, which must be responded with the desired name of the new LOADLIB in the following format: DA('ZETALY.LOADLIB.new'). The name 'the.preallocated.dataset' must be replaced by the actual dataset name.

//$INSTALL JOB (),CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID

//********************************************************************

//* AUTO SOFT CAPPING V4.5.00 (ASC) *

//* #.COPYRIGHT (C) 2023 ZETALY *

//* INFO@ZETALY.IO ALL RIGHTS RESERVED. *

//********************************************************************

//* CHANGES MUST BE DONE: *

//* - volser: Change volser parameter according to your installation*

//********************************************************************

//RECEIVE EXEC PGM=IKJEFT01

//SYSPRINT DD SYSOUT=*

//SYSTSPRT DD SYSOUT=*

//SYSTSIN DD *

RECEIVE INDSN('THE.PREALLOCATED.DATASET') DATASET('ZETALY.LOADLIB.NEW') NEW VOL(volser)

1. When possible, stop ZAC collectors and monitor and replace the current LOADLIB by the new one, before restarting them.

Web Interface update

If the Web Interface needs an update, it is necessary to install it into ZFS sent by ZETALY using the following steps:

1. Save a backup of the ZFS dataset mounted at statement "path=" of ASCPATH member of ZAC Parmlib. path=/u/asc/pgm

pathweb=/u/asc/web pathbkp=/u/asc/backup

1. ZETALY will send a file containing a new HTM PDS dataset, in IBM XMIT format.
2. Execute steps 1 to 3 of topic 4.3.4.1, that will restore the new HTM dataset.
3. Execute job HTMPUT from ZAC SAMPLIB. ZETALY will give further instructions, indicating the modules that need to be replaced.
4. In your browser, delete the cache to reload the new code.

Starting / Stopping ZETALY Automated Capacity©

Starting the Monitor

Use the following MVS command:

S ZCASC

or

S ZCASC,START=COLD

or

S ZCASC,START=WARM

By default, (without overriding the start mode in the start command), ZETALY Automated Capacity© starts in the (COLD/WARM) mode defined in the JCL procedure. However, when starting for the first time the mode is always COLD (because the RDS file is empty).

Cold start: The context is initialized. All general and LPAR parameters are loaded from the selected parmlib members. Status of LPARs, last settings done, last activated periods and alerts status are re-initialized.

Warm start: The context is restored. General and LPAR parameters are reloaded from the restart dataset. Status of LPARs, last settings done, last activated periods and alerts status are loaded from the restart dataset.

Messages issued:

ASC0000I ZETALY AUTOMATED CAPACITY V4.5.00 MAIN TASK STARTED ASC0001I PRODUCT LEVEL IS 2404151

ASC0035I PATH IS /u/zcost/asc4500/pgm

ASC0002I LOADING GENERAL PARAMETERS USING MEMBER ASCGEN00 ASC0002I LOADING LPAR PARAMETERS USING MEMBER ASCLPA00 ASC0002I LOADING CONTAINER PARAMETERS USING MEMBER ASCCTN00 ASC0007I GENERAL PARAMETERS SUCCESSFULLY LOADED

ASC0006I PRODUCT IS RUNNING IN ACTIVE MODE ASC0031I CPC AFPS05SE CPCMIN=0,CPCMAX=0 ASC0031I CPC AFP053SE CPCMIN=0,CPCMAX=0 ASC0033I NO PERIOD DEFINED

ASC0007I LPAR PARAMETERS SUCCESSFULLY LOADED ASC0008I 6 LPARS DECLARED IN LPAR PARMS FILE ASC0015I NO LPAR GROUP DEFINED

ASC0007I CONTAINER PARAMETERS SUCCESSFULLY LOADED ASC0005I 2 CONTAINERS DECLARED IN CONTAINER PARMS FILE ASC0002I LOADING ALERT PARAMETERS USING MEMBER ASCALT00 ASC0007I ALERT PARAMETERS SUCCESSFULLY LOADED

ASC0025I 2 CPC ALERTS SET ASC0025I 1 LPAR ALERT SET ASC0025I 1 CONTAINER ALERT SET

ASC0016I COLLECT INTERVAL IS NOW SET TO 120 SECONDS ASC0051I COLD START COMPLETED

ASC0053I MONITOR IS NOW NON-SWAPPABLE ASC0050I ZETALY AUTOMATED CAPACITY IS READY

Figure 3 Examples of start messages in the system log

ZAC is ready to work from the ASC0050I message on.

Any SYSIN or DEFAULT parameters may be overridden with PRMxxx= - e.g.:

S ZCASC,PRMGEN=nn,PRMLPA=nn,PRMCTN=nn,PRMALT=nn,PRMKEY=nn

Or using a start command parameter

S ZCASC,RUNMODE=Message

Note: On the first time ZAC Monitor is activated, the following command must be issued:

F ZCASC,INIT REPORT ALL

Note: ZETALY Automated Capacity© is protected against duplicate occurrences. By default, to avoid production mistakes, you cannot simultaneously start two ZETALY Automated Capacity© monitor STCs on the same partition. However, in some cases (for example during the migration process), you may have to start two ZETALY Automated Capacity© monitor STCs. Use the DUP parameter to allow duplicate monitors.

S ZCASC,DUP=YES

Stopping the Monitor

Use the following MVS command:

P ZCASC

Messages issued:

ASC0999I ZETALY AUTOMATED CAPACITY MAIN TASK STOPPED

Starting /Stopping Web Reporter

Starting the Reporter using a Domino web server

Use the following MVS command:

S ZCASCW

Messages issued:

IMW3534I PID: 67174526 SERVER STARTING IMW3536I SA 67174526 0.0.0.0:2312 * * READY

Note: the STC main program is IMWHTTPD. This program is supplied by IBM. Verify that the

IMWHTTPD program is present in your LINKLIB (SYS1.LINKLIB).

Starting the Reporter using an APACHE web server

If the APACHE web server which support the ZAC Reporting is not active, you must start it. Use the following MVS command:

S HTTPDACS

Messages issued:

$HASP373 HTTPDACS STARTED

(HTTPDACS) IHS is active.

Verifying that web reporting is operational

ZETALY Automated Capacity report is a web application. To access it, you must use a browser. The supported browsers are:

• Microsoft Internet Explorer Version 11+
• Mozilla Firefox version 42+
• Google chrome version 30+

Connect your web browser to the HTTP server on which ZAC is installed.

Select http://xxx.xxx.xxx.xxx:pppp in your web browser.

You can pick up the IP address xxx.xxx.xxx.xxx from the LPAR on which the Web server runs, by using the command:

TSO NETSTAT HOME.

The port number pppp is the one you defined when customizing the installation parameters.

E.g.: http://10.44.22.23:2412

You will get the ZETALY Automated Capacity© home page.

Stopping the Reporter using a Domino web server

Use the following MVS command:

P ZCASCW

Messages issued:

BPXM023I (WASCZ301) IMW3540I SA 83951689 0.0.0.0:2301 * * STOPPING WORK BPXM023I (WASCZ301) IMW3541I SA 83951689 0.0.0.0:2301 * * TERMINATING NOW

Figure 4 ZAC Reporter stopping messages

Stopping the Reporter using the APACHE web server

Use the following MVS command:

P HTTPDACS

If your Apache STC name has less than 8 characters a message is displayed in the SYSLOG at start time, to provide the name to use for modifying and stop command.

Ex.

0.0.0.0:2401. Use jobname HTTPD16 for console commands.

P HTTPD16

Messages issued:

BPXM023I (HTTPDACS) IHS is stopping

$HASP395 HTTPDACS ENDED - RC=0000

Starting /Stopping ZAC Collector

Starting the ZAC Collector

From the V4.3.00 version, the collector retrieves LPARs MSU consumptions and stack them over the current billing month. The stacked consumptions are stored in the new collector Restart dataset. To preserve the monthly consumptions, the collector should always restart in "WARM" mode. However, to be able to reset the monthly cumulated consumptions in special cases, a "COLD" start is possible. In this case, all monthly consumptions will be reset to 0.

Use the following MVS command:

S ZCASCCOL

or

S ZCASCCOL,START=WARM

or

S ZCASCCOL,START=COLD

By default, (without overriding the start mode in the start command), the collector starts in the (COLD/WARM) mode defined in the JCL procedure. However, when starting for the first time (installation time) the mode is always COLD (because the Collector RDS file is empty).

COLD start: The monthly accumulated consumptions are initialized.

WARM start: The context is restored. All monthly accumulated consumptions are restored from the Restart Dataset.

Messages issued:

S ZCASCCOL

Messages issued:

ASC1000I ZETALY AUTOMATED CAPACITY V4.5.00 COLLECTOR TASK STARTED ASC1001I PRODUCT LEVEL IS 2404151

ASC1005I COLLECT INTERVAL IS 120 SECONDS ASC1006I IP PORT=2492

ASC1007I SERVER USES $ZASCCMD SECURITY CLASS ASC1009I DIAG LEVEL IS 0

ASC1051I ZETALY AUTOMATED CAPACITY COLLECTOR INITIALIZATION COMPLETE ASC1053I COLLECTOR IS NOW NON-SWAPPABLE

ASC1325I WARM START COMPLETED

ASC1050I ZETALY AUTOMATED CAPACITY COLLECTOR IS READY

Figure 5 Example of start messages in the system log

Stopping the ZAC Collector

Use the following MVS command:

P ZCASCCOL

Messages issued:

ASC1306I STOP COMMAND RECEIVED ASC1902I IP SERVER NOW STOPPED

ASC1999I ZETALY AUTOMATED CAPACITY COLLECTOR STOPPED

Figure 6 ZAC Collector stopping messages

Testing ZAC collector

You can use the TSTCOL job of the SAMPLIB to test the communication and response times between the

ZCASC and ASC collector's agents.

The output indicates if the communication is correct or not. You must populate the SYSIN with the LPARs you want to collect.

There are two outputs for this job:

• The first one is written into a file with DDNAME RESULT. It contains the collected metrics for all the objects defined into the SYSIN dataset
• The second one is written into a file with DDNAME SYSOUT. It contains the report of the collect, including return codes and response times of the TCP/IP requests performed

*LPARNAME CPCNAME LPAR_IP_ADR LPAR1 AC64B 10.22.42.30

COLLECTOR_IP_PORT 2391

Code sample 5 Example of SYSIN

*ColN Collect_Time CpcName CpcID Type Mdl Capty Cp Lpar Sysname .... 00001 20141015152400 AC64B 2097 704 0531 04 LPAR1 PROD01

*Srv_Cls Pe Workload Im Imsu BATMDM 01 BATCH 03 0000.00

STCLOM 01 STARTED 06 0242.57

STCMDM 01 STARTED 03 0000.00

TSO01 01 TSOOTHER 01 0000.00

TSO01 02 TSOOTHER 02 0000.00

SYSTEM 01 SYSTEM 00 0036.61

SYSSTC 01 SYSTEM 00 0078.71

SYSOTHER 01 SYSTEM 00 0000.00

Figure 7 Example of RESULT

ZETALY AUTOMATED CAPACITY COLLECTOR TEST PROGRAM STATUS OF COLLECTS

20141015152422 Collect LPAR1 10.22.42.30 :2391 RC=00000000 resp=235.61 ms

COLLECT 0000001 20141015152422-> 20141015152400 RC=0 DIAG_FLAGS=00 00 00 00 00

DIAG_CODES=00000000 00000000 00000000

Figure 8 Example of SYSOUT