InterTest™ and SymDump ® 11.0
NOTE
More information:
CARS
Sign up for Hiper Notifications
Broadcom Support  is always alert to any known problems that could affect customers. We recommend that you sign up
for hiper notifications for all Broadcom   products on the Broadcom Support  website so that you receive notification of
potential problems as soon as possible. Select Hiper notifications and follow that dialog to receive notifications for your
products.
Business Value:
Early notification about the potential need to apply a required fix helps avoid unscheduled downtime and assists you in
proactively maintaining your software.
Apply IBM Maintenance
We recommend that you review the current list of IBM APARs for z/OS, especially related to hipers. Then apply the
APARs that are appropriate to your environment.
Business Value:
Missing APARs can affect the operation or performance of your product.
Product Requirements
This article describes the requirements needed to install and use the InterTest and SymDump  products.
Hardware Requirements
Storage Requirements
Ensure that you have the following storage available:
•For ESD installations, 915 cylinders for the downloaded files
•For installation and setup:
–Installation: 1,750 cylinders
–SMP/E temporary libraries: 60 cylinders
NOTE
Many installation library names have been updated with new naming conventions. Review existing CLISTs, JCL,
and procedures from prior product releases, and update the new data set names, if needed.
Data Monitoring
The data monitoring feature of InterTest for CICS requires a significant amount of storage over and above the
storage required by the programs being monitored. Compute the storage requirements as follows:
500 bytes times the number of transaction entries as defined by the STMTTRCE option plus the size of mirror area for


each program in the transaction for which data monitoring is active, where the mirror area is equal to the size of storage
for the monitored program.
If you encounter storage problems while using the data monitoring feature, perform one or more of the following actions:
 94


InterTest™ and SymDump ® 11.0
•Reduce the use of data monitoring in the region.
•Make the STMTTRCE value smaller in the default options table, IN25OPTS.
•Increase the EDSALIM for the CICS region.
Security Requirements
To complete the tasks in this section, you need the following security privileges:
•Read authority for all the SMP/E target data sets.
•Update authority for the PROTSYM, ALIB (optional), and INCLUDE file (optional).
•Superuser authority for installing and configuring the GUI. To mount a ZFS, you must have either superuser authority
or read access to the SUPERUSER.FILESYS.MOUNT resource (in the UNIXPRIV class).
Software Requirements
The following software is required:
•Supported release of the following IBM products and features:
–z/OS
–SMP/E
–COBOL, PL/I, and Assembler compilers
–LE Runtime
Eclipse User Interface
The Eclipse UI needs access to the Broadcom  Testing Tools server. The Broadcom  Testing Tools server requires IBM 32-
bit Java 5.0 (at or above SR5A) or IBM 32-bit Java 6.0 (at or above SR4).
UTF-16 Support for COBOL
The InterTest Batch mainframe ISPF user interface can display UTF-16 (Unicode) data in the Keep window and Display
panel when debugging a COBOL program. You must have z/OS Unicode Services installed to convert and display UTF-16
data. These services come standard with z/OS and are located in SYS1.CSSLIB.
PL/I Programs
When linking PL/I with Language Environment, CEESTART must be the first CSECT and the object module of the main


procedure must be included before any object modules of subroutines. The products assume that these procedures are
followed.
CICS Temporary Storage Model Restriction
The products use a temporary storage queue prefixed with a lower case "i" when starting. Because of this, you cannot
have a CICS-defined TSMODEL prefixed with a lower case "i" defined as recoverable. This will cause the start of the
product to wait endlessly for a syncpoint to be taken by the starting task.
Terminal Input/Output Area Compression Routine Users
Exclude the products' transactions and programs from any Terminal Input/Output Area (TIOA) compression packages
or routines, such as 3270 Super Optimizer/CICS and CTOP. Failure to do so produces unpredictable results because
InterTest for CICS uses saved TIOAs. In addition, the InterTest for CICS FILE facility does not work properly with data files
that have been put through data compression routines.
 95


InterTest™ and SymDump ® 11.0
TSO Logon Requirements for Foreground Debugging
The TSO logon requirements for foreground debugging in InterTest Batch are region size (when logging on) and the
number of DD statements that can be dynamically allocated at any one time during the session (DYNAMBR).
•The application uses about 1 MB of virtual storage, so you should log on with a region large enough for this product
and the program being debugged. A region of 4 MB is sufficient for most processing.
•The DYNAMBR number should be high, especially when running IMS/BTS applications in foreground. Allocation
checks to see if the number in DYNAMBR has been exceeded and has no other effect on the TSO session.
•Because the product has a dynamic STEPLIB facility, it is not necessary to allocate libraries containing dynamically
called modules at logon time.
ACF2
To use InterTest for CICS with ACF2 , add the transactions IPLX, ISER, VTAT, LIST, and VIRC to your ACF2 SAFELIST.
For additional information on these InterTest for CICS transactions, see IN25OPTS Keywords.
If InterTest global logging is turned on and the XDCT System Initialization parameter specifies a resource class profile,
ensure that it allows access to the CSSL transient data queue. Similarly, if the XPCT System Initialization parameter
specifies a resource class profile, ensure that it allows access to the CNTL transaction.
RACF Users
To use InterTest for CICS with RACF, define the InterTest for CICS transactions IPLX, ISER, VIRC, LIST, and VTAT to
CICS with CMDSEC(NO) and RESSEC(NO). All InterTest for CICS transactions and programs require UACC(READ) for


EXEC CICS INQUIRE commands to give all users RACF READ access. Using these settings makes the symbolics for a
source listing breakpoint display available to users.
If RACF file level security is in use, add the following statements to the xCICSFCT resource class:
PROTSYM, PROTHLF ...UACC(READ)
PROTCPF, PROTUHF, PROTMLOG ...UACC(UPDATE)
If InterTest global logging is turned on and the XDCT System Initialization parameter specifies a resource class profile,
ensure that it allows access to the CSSL transient data queue. Similarly, if the XPCT System Initialization parameter
specifies a resource class profile, ensure that it allows access to the CNTL transaction.
CICS Startup Parameter Considerations
If you are running SymDump  for CICS on a CICS Transaction Server release earlier than 5.1, you might need to increase
the value of your MAXOPENTCB SIT parameter.  For CICS regions which run small workloads, we recommend a
minimum value of 64. For CICS regions with large workloads, you might want to set MAXOPENTCB to the same value as
MXT.
CICS Global User Exits
This InterTest for CICS release requires the use of the following global user exits:
XPCFTCH and XPCTA
Required for the CNTL=START and CNTL=END commands to operate InterTest for CICS and control monitoring.
XDUREQ
Required for dump suppression and dump capture.
XMEOUT
Required for suppression of abend messages.
 96


InterTest™ and SymDump ® 11.0
XRMIOUT
Support for the CORE=LASTSQL command. Collects DB2-related call information for every DB2 call done in the
system. This can have significant performance implications in some DB2 shops. The parameter XRMIO=YES/NO
IN25OPTS controls the use of this exit. The default is XRMIO=YES.
XLDLOAD
Required for DWARF new copy support
When monitoring programs, observe the following rules:
•Do not disable the previous global user exits in any way. This action causes InterTest for CICS to stop functioning.
•The InterTest for CICS global user exits honor the return codes set by previous exits, which might have an impact on
whether InterTest for CICS successfully monitors a program. If you have problems caused by other CICS global user
exits setting a return code before InterTest for CICS exits receive control, you can ensure that the InterTest for CICS
exits are first to receive control by adding the program entry IN25PLTX to the CICS startup PLT. IN25PLTX is required
as the first program entry in Phase 1 (prior to the DFHDELIM entry) of the PLT.
•If you are installing SymDump  for CICS  with InterTest for CICS, always place the SymDump  for CICS IN25INST
program after the InterTest for CICS IN25PLT in the PLT.
NOTE
For more information, see the section Invoking more than one exit program at a single exit  in the IBM
Knowledge Centre at ibm.com  under Developing system programs  > Global user exit programs .
•If other exits receive control after InterTest for CICS, they must not change the return code or entry point fields in the
user exit parameter list.


user exit parameter list.
To disable SymDump  for CICS you must use the CNTL=END command.
Failure to observe these rules will cause monitoring to be disabled. For example, InterTest for CICS monitoring is not
performed if another exit receives control before InterTest for CICS and passes on a modified return code or entry point.
CICSplex Support
InterTest for CICS provides optional support for CICS regions participating in a CICSplex environment. When you install
InterTest for CICS with CICSplex support, participating CICS regions propagate InterTest for CICS commands and
breakpoints automatically to all regions in the CICSplex. This automatic propagation lets you easily debug dynamically
routed transactions and programs.
CICSplex command propagation is accomplished mainly through CAICCI for z/OS, a Common Components and Services
for z/OS. Other than installing CAICCI for z/OS and setting the following customization options, you do not need anything
else to obtain CICSplex support.
To install InterTest for CICS with CICSplex support, follow these steps:
1.Install CAICCI in all participating CICSplex regions as discussed in the section Common Components and Services  for
z/OS Requirements.
2.Follow the InterTest for CICS installation instructions. You can install using one of the following methods:
–CSM
–Pax-Enhanced Electronic Software Delivery
3.Use the following IN25OPTS customization options in each participating CICSplex region:
–CICSPLEX=YES
–CPLXFMID=a CICSplex family name
–CPLXCKPI=hhmm (a checkpoint interval)
For details on setting these options, see IN25OPTS Keywords.
NOTE
Obtain support for multiple CICSplex families within or across multiple z/OS regions by changing the CPLXFMID


family name that is associated with each region.
 97


InterTest™ and SymDump ® 11.0
Startup and Termination with CICSplex Support
InterTest for CICS regions that you installed with CICSPLEX=YES are affected during startup and termination in the
following ways:
•The CNTL=START and CNTL=RESTART commands automatically have InterTest for CICS resynchronize monitoring
with any active regions in the CICSplex upon startup.
•The CNTL=END, SCOPE=GLOBAL command can be issued to terminate concurrently all InterTest for CICS
processing in all connected regions in the CICSplex.
Dynamic Symbolic Support for Endevor
All InterTest and SymDump products provide optional support for Endevor  users to load dynamically the application
program symbolic information from Endevor  when the footprint option is in use. This feature allows debugging  or fault
analysis to proceed when application program symbolics are not found in the PROTSYM files.
To support this feature, the following products are required:
•A supported release of Endevor .
•Endevor  AUTHLIB, CONLIB, and the data set containing C1DEFLTS must be in the LNKLIST.
•C1DEFLTS. Add the keyword COMPLISTWD=.LIST to the C1DEFLTS TYPE=MAIN section. This keyword identifies
the text string that Endevor  looks for in an element's component list to identify the listing data set for the print element
listing function. The period (.) before the variable LIST is used as a wildcard to denote anywhere within the DSN
(LISTLIB, LISTING, COBLIST, for example). Change the variable LIST to conform to your DSN naming conventions for
compiler and assembler output files.
Note the following rules:
•Create the listings using an Endevor  generate process.


Note the following rules:
•Create the listings using an Endevor  generate process.
•Use Endevor  with the following DD statement coded to monitor the listing data set the Endevor  generate process that
is created:
MONITOR=COMPONENT,FOOTPRINT=CREATE
•The object and load module libraries must use the footprint feature with the following coded on their respective DD
statements:
FOOTPRINT=CREATE
If your installation has defined multiple C1DEFLTS, additional customization steps are necessary. For more information
about defining multiple C1DEFLTS, see Interfaces and Compatibility.
You might also need to install and customize CAICCI.
NOTE
The dynamic symbolic support for the Endevor  feature, hereafter referred to as the dynamic symbolic
support feature, cannot differentiate between multiple listing outputs created by a single Endevor  processor
for the same element. Therefore, dynamic symbolic support using listing outputs from multiple compiles
or assemblies from a single Endevor  GENERATE or MOVE action for the same element might produce
unpredictable results.
Common Services Requirements
InterTest and SymDump uses the following Common Components and Services  for z/OS components:
•CAI Resource Initialization Manager (CAIRIM)
•Broadcom  License Management Program ( LMP)
•CAI Common Communications Interface (CAICCI)
•Event Management
•Broadcom  Health Checker Common Service
 98


InterTest™ and SymDump ® 11.0
NOTE
•If other Broadcom  products are installed at your site, some of these services may already be installed. For
more information, see Common Components and Services  for z/OS
•We recommend that you stay current on Common Components and Services  maintenance.
Target Libraries
The following list contains target libraries used by InterTest and SymDump . These libraries must be allocated if they do not
already exist for some other Broadcom  product at your site:
CAI.CAVHAUTH
Target Authorized load library
CAI.CAVHCLS0
Target CLIST library
CAI.CAVHDBRM
Target DBRM library
CAI.CAVHDATV
Target GUI/server executables library
CAI.CAVHHELP
Target SymDump  Batch help library
CAI.CAVHHLF
Target CICS help library
CAI.CAVHJCL
Target sample JCL library
CAI.CAVHLOAD
Target load library
CAI.CAVHMAC
Target macro library
CAI.CAVHMSG0
Target ISPF message library
CAI.CAVHOPTN
Target common options library
CAI.CAVHPNL0
Target ISPF panel0 library
CAI.CAVHPNL1
Target InterTest Batch ISPF panel1 library
CAI.CAVHPROC
Target procedure library
CAI.CAVHRPF
Target InterTest Batch ROSCOE RPF library
CAI.CAVHSAMP
Target sample source library
CAI.CAVHSKL0
Target SymDump  Batch skeleton library
CAI.CAVHSRC
Target InterTest Batch source library
 99


InterTest™ and SymDump ® 11.0
CAI.CAVHSYM
Target sample CICS symbolic library
CAI.CAVHTBL0
Target SymDump  Batch table library
CAI.CAVHXML
Target installation XML
Distribution Libraries
The following list contains the distribution libraries used by InterTest and SymDump. These libraries must be allocated if
they do not already exist for some other Broadcom  product at your site:
CAI.AAVHCLS0
Sample REXX and CLIST
CAI.AAVHDBRM
Distribution DBRM library
CAI.AAVHDATV
Distribution GUI/Server executables library
CAI.AAVHHELP
Distribution SymDump  Batch help library
CAI.AAVHHLF
Distribution CICS help library
CAI.AAVHJCL
Distribution sample JCL library
CAI.AAVHMAC
Distribution macro library
CAI.AAVHMOD0
Distribution load library
CAI.AAVHMSG0
Distribution ISPF message library
CAI.AAVHOPTN
Distribution common options library
CAI.AAVHPNL0
Distribution panel0 library
CAI.AAVHPNL1
Distribution InterTest Batch panel1 library
CAI.AAVHPROC
Distribution procedure library
CAI.AAVHRPF
Distribution InterTest Batch ROSCOE RPF library
CAI.AAVHSAMP
Distribution sample library
CAI.AAVHSKL0
Distribution SymDump  Batch skeleton library
CAI.AAVHSRC
Distribution InterTest Batch source library
 100


InterTest™ and SymDump ® 11.0
CAI.AAVHSYM
Distribution CICS symbolic library
CAI.AAVHTBL0
Distribution SymDump  Batch table library
CAI.AAVHXML
Distribution installation XML
Concurrent Releases
This article describes concurrent release requirements.
You can install this release of your product and can continue to use an older release in another SMP/E environment. If you
plan to continue to run a previous release, consider the following points:
•When you install the product into an existing SMP/E environment, the new installation deletes previous releases in that
environment.
•If you acquired your product using SMP/E JCL, select different target and distribution zones for your new release from
where your current release is installed. The new zones use different libraries than your current release.
NOTE
CSM  installs a product into a new SMP/E environment by default. You can select an existing SMP/E
environment from your working set.
•Define DDDEF entries in your new zones to point SMP/E to the proper libraries for installation. Ensure that they point
to the new release libraries.
Install Products Using z/OSMF
Learn how to install product software using z/OSMF.
As a systems programmer, your responsibilities include acquiring, installing, maintaining, and configuring mainframe
products on your systems. z/OSMF lets you perform these tasks for Broadcom  mainframe products and mainframe
products from other vendors. z/OSMF lets you manage software on your z/OS systems through a browser at any time,
from any location. By streamlining some traditional tasks and automating others, z/OSMF can simplify some areas of
system management and also reduce the level of expertise that is required for managing system activities. Experienced
users can view, define, and update policies that affect system behavior, monitor system performance, and manage z/OS
software.


software.
As products and vendors adopt z/OSMF services, you can install and maintain all your mainframe products in a common
way according to industry best practices. After configuration is complete, you can execute the product and easily provision
new software instances for use on other systems throughout your environment.
Use the following topics to guide you through the installation process using z/OSMF:
Address z/OSMF Requirements
Provides information about z/OSMF general configuration and security requirements.
Acquire a z/OSMF Portable Software Instance
Provides the steps to acquire the product software from Broadcom Support  and register the portable software
instance in z/OSMF.
Install Product Software Using z/OSMF Deployments
Provides the steps to install (deploy) the portable software instance to an LPAR using z/OSMF Deployments. This
step creates the SMP/E environment and runs the RECEIVE, APPLY, and ACCEPT steps to prepare the software
instance for SMP/E operations. This step also:
 101


InterTest™ and SymDump ® 11.0
•Customizes the data set names that are defined to SMP/E.
•Mounts required USS files if necessary.
•Performs workflow execution to customize the deployed runtime environment for use on a specific z/OS
system.
Import Product Information into z/OSMF
Provides the steps to import the Broadcom  product information file so that z/OSMF has access to the latest
product release information. For a list of products using z/OSMF, see Mainframe Products using z/OSMF in the
Mainframe Common Maintenance Procedures documentation.
TIP
See our installation best practices article for a list of comprehensive z/OSMF video training from IBM.
When these tasks are completed, you are ready to install preventive maintenance. You can also configure software
instances using z/OSMF workflows.
Address z/OSMF Requirements
Before you install your Broadcom  mainframe products using the IBM ® z/OSMF Management Facility (z/OSMF), address
the installation and security requirements in the following table:
TIP
Your systems programmers and security administrators can complete these tasks in parallel.
Task Role
Apply required maintenance for CA Common Services for z/OS (CCS) Version 15.0
(SO12499)
The CCS PTF installs load module stubs for select IBM products into your installed
CCS library hlq.CAW0CALL. If prompted during installation for the data set name of
a load library for an IBM product that you do not have installed, specify your installed
hlq.CAW0CALL data set name.Systems programmer
Configure z/OSMF as described in the IBM Knowledge Center
The IBM z/OS Management Facility Configuration Guide   is your primary source of
information about how to install and configure z/OSMF. We also strongly recommend that


information about how to install and configure z/OSMF. We also strongly recommend that
you review the z/OSMF overview and use the installation checklists that are provided in
the IBM Knowledge Center. You can open the IBM documentation in a separate browser
tab for reference during installation of your products using z/OSMF Deployments.Systems programmer, security
administrator, domain administrator
Configure z/OSMF security for CA ACF2™ for z/OS , CA Top Secret® for z/OS , or IBM
RACF  as applicable to authorize users and resources.Security administrator
Confirm that the installer has read, create, update, and execute privileges in z/OS. Write
access is also required to the UNIX System Services (USS) directories that are used for
the installation process.Security administrator
Address the following USS requirements:
•Create a USS directory to receive the z/OSMF pax file and to perform the unpack
steps.
•Confirm that you have write authority to the USS directories that are used for the z/
OSMF pax installation process.
•Confirm that you have available USS file space.
To download and unpack the pax file, you need free space that is approximately 3.5
times the pax file size in the file system that contains the pax directories. For example, to
download and unpack a 14 MB pax file, you need approximately 49 MB of free space in
the file system hosting your pax directory. If you do not have sufficient free space, error
messages like EZA1490I Error writing to data set or EZA2606W File I/O error 133 can
occur.Systems programmer, security
administrator
 102


InterTest™ and SymDump ® 11.0
After these requirements have been addressed, you are ready to acquire a z/OSMF Portable Software Instance or
Configure a Software Instance using z/OSMF Workflows.
Acquire a z/OSMF Portable Software Instance
As a systems programmer, you can acquire an IBM z/OSMF portable package for your product from Broadcom Support
and then add the portable software instance to z/OSMF. The product SMP/E environments are pre-built at Broadcom ,
backed up, and made available for download as a z/OSMF portable software instance. After you acquire the portable
software instance, you can use z/OSMF Deployments to perform the installation and z/OSMF workflows to perform post-
install configuration.
The following diagram illustrates the acquisition process:
When you complete the acquisition process, the product software is ready for installation using z/OSMF Deployments.
Use the following topics to guide you through the z/OSMF product acquisition process:
1.Address all z/OSMF requirements.
2.Order the z/OSMF portable software instance .
NOTE
For a list of Broadcom  mainframe products that provide a z/OSMF package, see Mainframe Products using
z/OSMF for Software Maintenance .
3.Register the portable software instance in z/OSMF .
Order the z/OSMF Portable Software Instance
You can order the z/OSMF portable software instance from the Broadcom Support  and then download the package
to a local z/OSMF host as a single pax file. You can download directly to the mainframe or you can download to your
workstation and then transfer the pax file to the mainframe. A file transfer utility, such as FTP, is required to transfer data
to the mainframe.


to the mainframe.
The portable software instance is a portable form of a software instance, including the SMP/E CSI data sets, all
associated SMP/E-managed target and distribution libraries, non-SMP/E-managed data sets, and meta-data that is
required to describe the product software instance.
 103


InterTest™ and SymDump ® 11.0
NOTE
To optimize downloads from Broadcom Support , configure the downloads.broadcom.com URL for HTTPS
and Secure FTP in your network security software, firewalls, or both. Sites that regulate access through an IP
address are required to allow network access to 141.202.253.110.
1.Go to Broadcom Support  at https://support.broadcom.com, and select Software , Mainframe Software , and My
Downloads.
2.Log in using your Broadcom Support  username and password.
The My Downloads  page appears.
3.Select a product from the list or enter the product name in the Search  field.
The product page appears with two tabs under the product name: Products  and Solutions .
4.Under Products , select the product that you want to download.
A list by release, service pack, and language appears.
5.Click the hypertext link to select a release.
The Primary Downloads  page appears. This page shows the available product-specific software packages that you
can select to download.
If an Additional Downloads  page is available, this page shows additional software packages that are related to your
product selection that you can download. These products may already be installed.
6.Review the packages that appear under Primary Downloads  and Additional Downloads  and complete the following
steps:
a.Select the zOSMF Package  (productid .VnnRn.ZOSMF.pax.Z) and other files that you want to include in the
product download.
If more than one package is available, you can only select one.
b.Select Download Selected , HTTPS Download , or Secure FTP Download . Secure FTP Download is the
preferred method. For download tips, see Product Download Help . For sample JCL and security requirements, see
Download Methods and Locations .
The product package is downloaded.


Download Methods and Locations .
The product package is downloaded.
7.Execute JCL to unpack the installation file and restore the individual pax files. Sample JCL follows:
//USSBATCH EXEC PGM=BPXBATCH
//STDOUT   DD SYSOUT=*
//STDERR   DD SYSOUT=*
//STDPARM  DD *
sh cd /yourUSSpaxdirectory /;
pax -rvf yourpaxfilename.ZOSMF.pax.Z
/*
Customize the sample JCL as follows and then submit for execution:
a.Add a JOB statement.
b.Update the USS directory ( yourUSSpaxdirectory ) with the path name where you want to copy the pax file.
c.Update yourpaxfilename  with the name of the pax file that you want to copy to the mainframe.
USSBATCH can take several minutes to execute. A return code of zero is expected. Any other return code indicates a
problem.
After successful execution, the individual pax files have been restored and are ready for use. Go to Register Portable
Software Instance in z/OSMF .
Register Portable Software Instance in z/OSMF
After you have acquired and downloaded the portable software instance to a local z/OSMF host system, you must log
in to z/OSMF to register the product software and define the portable software instance to z/OSMF as shown in the
 104


InterTest™ and SymDump ® 11.0
following procedure. When you complete these steps, the portable software instance is registered in z/OSMF and ready
for installation (deployment).
1.Log in to the z/OSMF web interface and select your user ID in the top or bottom right-hand corner to switch between
the Desktop Interface and Classic Interface.
2.Complete either  of the following steps to display the Software Management page:
a.In the Desktop Interface, select Software Management .
b.In the Classic Interface, select Software , Software Management .
3.Select Portable Software Instances  to define your portable software instance to z/OSMF.
4.Select Add from the Actions menu and select From z/OSMF System .
The Add Portable Software Instance page displays.
5.Complete the following steps:
a.Select or type the system name (destination LPAR) and UNIX directory (destination USS directory) where the
portable software instance files reside and select Retrieve .
b.Enter a name for the new portable software instance. You can also enter an optional description and assign one or
more categories that display existing packages.
c.Select OK.
The new portable software instance is now defined to z/OSMF.
The portable software instance is now registered in z/OSMF and ready to install (deploy). Go to Install Product Software
using z/OSMF Deployments.
Install Product Software Using z/OSMF Deployments
As a systems programmer, your responsibilities include installing product software in your z/OS environment. After
the portable software instance or software instance is registered in z/OSMF, you can use z/OSMF Deployments to
install the product software and create the product data sets (global, CSI, target libraries, and distribution libraries) for
the new software instance. The deployment jobs create a copy of the source product data sets to create the product


target runtime environment. Creating a copy of the SMP/E target data sets keeps the SMP/E environment clean and it
also isolates the product runtime environment for maintenance activities. You can also perform z/OSMF workflows to
customize the SMP/E data sets, mount UNIX System Services (USS) files if necessary, and configure the new software
instance on the target system.
To install Broadcom  mainframe products using z/OSMF and make the product software available for use on a system
by users and other programs, define a new deployment. This step defines the SMP/E environment name and the prefix
of the CSI data set in z/OSMF. You also specify data set allocation parameters for all SMP/E data sets, target libraries,
and distribution libraries. To define a new deployment, complete the deployment checklist (specify the USS path, DSN,
VOLSERs), and submit the deployment jobs through the z/OSMF user interface. When the deployment is complete, you
have a source and target copy of the software.
NOTE
For more information about these tasks, see Deploying software  in the IBM documentation.
Subsequent maintenance activities for the product update the SMP/E environment without affecting your active product
runtime environments. You decide when to redeploy the maintenance-updated SMP/E target data sets to each of the
product runtime environments.
Before you begin this process, review the installation best practices and verify the installation requirements in Prepare for
Installation.
NOTE
The installer requires read, create, update, and execute privileges in z/OS. Write access is also required to the
USS directories that are used for the installation process. To deploy a product that has USS components, the
installer's user ID must have access to the appropriate resource profiles in the UNIXPRIV class, access to the
 105


InterTest™ and SymDump ® 11.0
BPX.SUPERUSER resource profile in the FACILITY class, or UID(0). For UNIXPRIV, read access is required to
SUPERUSER.FILESYS.CHOWN, SUPERUSER.FILESYS.CHGRP, and SUPERUSER.FILESYS.MOUNT.
1.Display the Deployments table in z/OSMF ( Software Management, Deployments ).
2.Define a new deployment by selecting New from the Actions menu.
The deployment checklist displays. You can also modify, view, copy, cancel, or remove existing deployments.
3.Complete the deployment checklist items as described in Defining new deployments  in the IBM documentation.
As you complete the deployment checklist, be sure to make the following selections:
a.Specify the properties for this deployment (name, description, and optional category).
b.Select the software to deploy.
For this step, select the Portable Software Instance  button and select your package.
c.Select the objective for this deployment to indicate where and how you want to install the selected portable
software instance.
For this step, indicate that you want to create a software instance and specify the global zone CSI and the system
where the target software instance will reside.
d.Check for missing SYSMODs and view missing SYSMOD reports.
For this step, deselect the following report options:
•Requisite SYSMODs and Fix Categories reports
•Regressed SYSMODs and HOLDDATA Delta reports
e.Configure this deployment to define the target software instance.
•For DLIBs , specify Yes to copy the distribution zones and libraries that are associated with the source software.
You can customize the names and the storage class or volumes of the new data sets.
•For Model , indicate The source software  to use as a model. z/OSMF uses the data sets, volumes, mount


points, catalogs, and SMP/E zones that are associated with the model to specify default values for the target
software instance.
•For SMP/E Zones , the DLIB and TLIB names do not typically need to be changed.
•For Data sets , change the target data set name prefix to the one that you want to use for your deployment.
Specify a volume or storage class to identify where to create the target data sets.
•For Catalogs , no action is required assuming that your target data set prefix is defined in a user catalog.
•For Volumes and Storage Classes, no action is required. A summary is presented of the target data sets to be
created and how much space is required.
•For Mount Points , review the mount points for the UNIX file system data sets that are included in the target
software instance. When specifying a new target mount point, retain the static path extension in the path name
to prevent failures in the configuration workflow. For example, targetpathname .
NOTE
If your product does not include USS directories, ignore this instruction.
f.Define the job settings to generate JCL to install the software and view the deployment summary. For this step,
update the JOB statement as needed.
NOTE
If the target system for the deployment is in a JES Multi-Access Spool (MAS) and the mount point is only
accessible from the target system, add a System Affinity (SYSAFF) to the job card to ensure execution
on the system where the zFS resides.
g.Submit the deployment jobs in sequential order, wait for each job to complete, and then select Refresh  to register
job completion in z/OSMF.
A return code of zero is expected.
When all deployment jobs have executed successfully, you have unzipped and renamed the product data sets, and


updated the CSI data sets. The product data sets have also been successfully copied and the properties for the
target software instance have been specified.
h.Execute workflows if any exist for the software being deployed. Most products have at least one of the following
workflows:
 106


InterTest™ and SymDump ® 11.0
Post SMP/E Workflow
Updates the CSI with site-specific external data sets, relinks load modules, and optionally mounts USS
directories.
NOTE
If prompted for the data set name of a load library for an IBM product that is not installed, specify your
installed Common Components and Services  for z/OS CCS_hlq .CAW0CALL data set name.
Base installation Workflow
Configures a new software instance for your product software.
Upgrade Workflow
Updates an existing software instance for your product to a new product release.
NOTE
For a list of products with workflows to complete post-install configuration, see Mainframe Products using
z/OSMF for Software Management  in the Mainframe Common Maintenance Procedures documentation.
i.Specify a name and description for the new target software instance.
The deployment process is complete. The new software instance is defined to z/OSMF. You are now ready to Import
Product Information into z/OSMF before you install product maintenance.
Import Product Information into z/OSMF
As a systems programmer, your responsibilities include maintaining a current repository of acquired product packages
that are ready for installation in your mainframe environment. z/OSMF lets you view a consolidated list of the products and
maintenance packages that are included in each software instance or portable software instance. You can import product
information for the Broadcom  mainframe products that you have installed on z/OS into z/OSMF. After retrieving the
information, you can use the Products page in the z/OSMF Software Management task to obtain a list of products that are
contained in your software instances. This information helps you to determine which products are nearing or have reached
end of service (EOS) or end of life (EOL) support. This information is useful when planning for future installations and


upgrades. You can also use this information to identify software instances that will be affected by changes to a product.
The product information file for Broadcom  mainframe products is stored on the following FTP directory:
https://ftpdocs.broadcom.com/WebInterface/phpdocs/0/MSPSaccount/COMPAT/BroadcomProdInfo.txt
Enable Secure Downloads
To prevent SSL handshake failures when importing product information into z/OSMF, use the following procedure to
enable secure downloads:
1.Download the certificate from the following URL:
https://ftpdocs.broadcom.com/WebInterface/redirectFTPDocs.html?path=/cadocs/0/certs/digicert-old/Digi-
Intermediate.crt
Note the location on your workstation where the certificate was downloaded.
2.Upload the certificate as text data to your z/OS system in RECFM=VB and LRECL=84 format.
If you use FTP, use the following FTP commands to avoid truncation:
ASCII
QUOTE SITE WRAP LRECL=84 RECFM=VB
PUT your_PC_file_name  'your.mvs.dataset.name ' (REPLACE
quit
3.Add the certificate to the existing z/OSMF IZUSVR keyring.
For ACF2 , specify SET PROFILE(USER) DIV(CERTDATA)
INSERT CERTAUTH. yourcertname  DSN('your.zos.dataset.name ') -
  LABEL( yourlabeldescription )
 107


InterTest™ and SymDump ® 11.0
CONNECT CERTDATA(CERTAUTH. yourDigicertCAcertname ) KEYRING(IZUSVR.keyr01)
 RINGNAME(IZUKeyring.IZUDFLT) USAGE(CERTAUTH)
For Top Secret, specify TSS ADD(CERTAUTH) DIGICERT( yourDigicertCAcertname ) LABLCERT( yourlabelname ) -
DCDSN('your.zos.dataset.name ') TRUST

TSS ADD(IZUSVR) KEYRING( zosmfringname ) RINGDATA(CERTAUTH, yourDigicertCAcertname ) -
USAGE(CERTAUTH)
For IBM RACF, specifyRACDCERT CERTAUTH ADD(' your.zos.dataset.name ') WITHLABEL(' yourlabelname ') TRUST
RACDCERT ID(IZUSVR) CONNECT(CERTAUTH LABEL('your_digicertCA_label') +
RING(keyringname ) USAGE(CERTAUTH))
To load the contents of this file into z/OSMF, you can:
•Load the file from the Broadcom  URL
•Load the file from your local workstation
•Load the file from a z/OS data set or UNIX file
After the file is loaded, you can then retrieve the product information in z/OSMF from the Products  view in the Software
Management task (see Displaying a list of your products in the IBM documentation).
NOTE
If you create software instances or portable software instances in z/OSMF, import the product information file
again so that you have current information that is displayed about your installed products. We recommend that
you repeat the following procedures on a regular schedule or at least monthly to ensure that you have current
Broadcom  product information available in z/OSMF. This process ensures that you have access to all product


packages as they become available. For more information, see Retrieving product information from product
information files  in the IBM documentation.
Load the File from the Broadcom  URL
Use the following procedure to load the contents of the Broadcom  product information file into z/OSMF directly from the
Broadcom  FTP directory.
1.Log in to the z/OSMF web interface.
2.Complete either  of the following steps:
–In the Desktop Interface, select Software Management.
–In the Classic Interface, select Software , Software Management .
The Software Management  dashboard displays.
3.Select Products .
The Products table list  is displayed.
4.Select Retrieve End of Service Information  from the Actions menu or select the Retrieve End of Service Information
button if available.
The Select Product Information File  page displays.
5.Complete the following steps:
a.Select the option to Select files that reside on or can be accessed by primary system  and select Add from the
Actions drop-down menu under Product Information Files.
The Add Product Information File  page is displayed.
b.Select URL and then specify the following URL in the URL field.
https://ftpdocs.broadcom.com/WebInterface/phpdocs/0/MSPSaccount/COMPAT/BroadcomProdInfo.txt
c.Specify a description in the Description  field.
d.Select OK.
The product information file table is updated with the new URL.
 108


InterTest™ and SymDump ® 11.0
6.Select the new URL and select Retrieve .
The contents of the file are loaded into z/OSMF.
You can now view the Broadcom  product information that has been retrieved from the Software Management dashboard.
Load the File from Your Local Workstation
Use the following procedure to load the contents of the Broadcom  product information file into z/OSMF from your local
workstation.
1.Download the product information file from the following Broadcom  FTP directory to your local workstation using your
Web Browser or an FTP client:
https://ftpdocs.broadcom.com/WebInterface/phpdocs/0/MSPSaccount/COMPAT/BroadcomProdInfo.txt
2.Log in to the z/OSMF web interface.
3.Complete either  of the following steps:
–In the Desktop Interface, select Software Management.
–In the Classic Interface, select Software , Software Management .
The Software Management  dashboard displays.
4.Select Products .
The Products table list  displays.
5.Select Retrieve End of Service Information  from the Actions menu.
The Select Product Information File  page displays.
6.Select the option to Select a file that resides on your local workstation , enter your file name and description, and
select Retrieve .
The contents of the file are loaded into z/OSMF.
You can now view the Broadcom  product information that has been retrieved from the Software Management dashboard.
Load the File from a z/OS Data Set or UNIX File
Use the following procedure to load the contents of the Broadcom  product information file into z/OSMF from a z/OS data
set or UNIX file that the primary z/OSMF host can access.
1.Use FTP to download the product information file directly to the mainframe.
NOTE


1.Use FTP to download the product information file directly to the mainframe.
NOTE
Upload the file with binary in the FTP JCL so that the file is not converted to the EBCDIC character set.
Sample JCL follows that you can customize and execute:
//FTPSTEP  EXEC PGM=FTP,PARM='(EXIT=08'
//SYSTCPD  DD DSN= your_TCP/IP_data_set_name ,DISP=SHR
//SYSPRINT DD SYSOUT=*
//OUTPUT   DD SYSOUT=*
//INPUT    DD *
ftp.broadcom.com 21
anonymous email_address
cd /pub/MSPSaccount/JSON/
dir
asc
locsite LR=80 REC=FB BLOCKSI=0
locsite PRI=20 SEC=10 CY
get BroadcomProdInfo.txt ' z/OS_data_set ' (REPLACE
your_TCP/IP_data_set_name
Specify the TCP/IP stack for an external network.
 109


InterTest™ and SymDump ® 11.0
email_address
Specify your valid email address.
z/OS_data_set
Specify the z/OS data set name where you want to save the product information file. If the specified data set does
not exist, it is created during the download process.
2.Log in to the z/OSMF web interface.
3.Complete either  of the following steps:
–In the Desktop Interface, select Software Management.
–In the Classic Interface, select Software , Software Management .
The Software Management  dashboard displays.
4.Select Products .
The Products table list  displays.
5.Select Retrieve End of Service Information  from the Actions menu or select the Retrieve End of Service Information
button if available.
The Select Product Information File  page displays.
6.Complete the following fields:
a.Select the option to Select files that reside on or can be accessed by primary system  and select Add from the
Actions drop-down menu under Product Information Files.
The Add Product Information File  page displays.
b.Select Primary z/OSMF system  and specify the z/OS_data_set_name  in the Data set or UNIX file  field.
The primary z/OSMF host system must be able to access the specified data set or UNIX file.
c.Specify a description in the Description  field and select OK.
The product information file table is updated with the new URL.
7.Select the new URL and select Retrieve .
The contents of the file are loaded into z/OSMF.
You can now view the Broadcom  product information that has been retrieved from the Software Management  dashboard.
Install Products Using CSM
Review the following high-level process for installing product software using CSM .
As a systems programmer, you can acquire, install, and deploy your mainframe product software on z/OS systems using


CSM . CSM  simplifies and unifies the management of your Broadcom  mainframe products on z/OS systems. You can use
CSM  to manage your product software in a common way according to industry best practices. You can also obtain and
apply corrective and recommended maintenance easier. A web-based interface lets you install and maintain your products
faster and with less chance of error.
WARNING
As part of our ongoing commitment to customer success and to help our customer base achieve their
strategic business initiatives, we are investing our resources in z/OSMF for software management. We will
be discontinuing technical support for CSM . In accordance with the terms and conditions, guidelines, and
parameters of Broadcom’s support program, which is documented in the Broadcom Software Maintenance
Policy Handbook , this announcement provides written notification of End of Life for CSM . This notification means
that CSM  will no longer be enhanced and maintenance and technical support, including self-service support, will
be discontinued effective June 30, 2023 . For full details, see the End of Life Announcement.
If you do not have CSM  installed, download it from Broadcom Support .
WARNING
To install a product using CSM , you must  modify the SYSPRINT size. The default allocation of 30 cylinders is
insufficient to complete the installation. Increase the allocation parameters of the SYSPRINT data set to at least
120 cylinders.
 110


InterTest™ and SymDump ® 11.0
Use the following topics to guide you through the product installation process using CSM :
•Acquire Your Products Using CSM
•Install Your Products Using CSM
NOTE
Before you begin this process, review the installation best practices and verify that the installation requirements
in Prepare for Installation have been met.
When these steps are completed, you are ready to install preventive maintenance.
Acquire Your Product Using CSM
As a systems programmer, your responsibilities include maintaining an up-to-date repository of acquired product
packages that are ready for installation in your mainframe environment. CSM  provides a product list that lets you display
the list of licensed product installation and maintenance packages and to download these packages. Also, you can update
the product list to add external product packages that you acquired outside of CSM  so that they are ready for installation
using CSM .
The following diagram shows the product acquisition process:
1.Configure CSM .
2.Download the product package from Broadcom Support  or add an external product package:
–Download from Broadcom Support :
a.Update the product list .
b.Download product packages .
–Add external product package:
a.Add external product installation packages .
 111


InterTest™ and SymDump ® 11.0
b.Add external product maintenance packages .
After you complete this process, the product packages are ready for installation with CSM .
Configure CSM
Before you start acquiring product packages, configure a Broadcom Support  Online account, a CSM  account, and the
required download settings. If you have previously configured these settings, update the product list .
1.Start your Web browser, and enter the CSM  access URL, which you can get from your system administrator.
NOTE
If the Notice and Consent Banner appears, read and confirm the provided information.
2.Enter your z/OS login user name and password, and log in.
The initial page appears. You are prompted to perform configuration.
3.Configure the following settings:
–Proxies that CSM  uses to communicate with Broadcom Support  Online.
If proxies are not used, the following port numbers are used: HTTPS Port Number 443 and FTP Port Number 21.
WARNING
If your site uses proxies, review your proxy credentials on the User Settings , Software Acquisition
page.
–The USS path to the temporary directory for downloaded software packages
If you do not specify the directory, default settings are used that you can change later.
NOTE
These settings are also available on the System Settings , Software Acquisition  page.
Select Next .
You are prompted to define your Broadcom Support  account.
4.Select New.
You are prompted for the credentials to use on Broadcom Support .
5.Specify the credentials, select OK, and then Next .
You are prompted to review your user settings. These settings are available on the User Settings  page.
6.Change the settings or keep the defaults, and then select Finish .
A dialog opens, which shows the progress of the configuration task.
7.Select the Settings  tab, and review other settings, as needed.


7.Select the Settings  tab, and review other settings, as needed.
You have configured CSM  to acquire products.
Update the Product List
The product list displays a list of downloadable licensed product packages. To see the current list of available product
packages for download, update the Available Products tree.
1.Log in to CSM  using your credentials.
2.Select the Products  tab.
3.(Optional) Update the product list only with packages that belong to specific site IDs.
a.Select the Edit button in the Filter  section and associate one or more site IDs to a filter in the Edit Filter  window.
b.Select the filter in the Filter  section.
c.Right-click the Products  link at the top of the product tree and select Update Product List .
4.Select the Update Product List  link in the Actions  section on the left side.
Updating of the product list with all products for all site IDs starts.
 112


InterTest™ and SymDump ® 11.0
NOTE
If you updated the product list only for a selected filter, skip this step.
5.Confirm the update.
A dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress
tab to close this dialog. The task output browser opens, and you can view the action details. Select Close  to close the
task output browser.
NOTE
While a task is in progress, you can perform other work. Select Hide  to exit the dialog and view the task
status later on the Tasks tab.
The product list is updated.
Download Product Packages
You can download product installation and maintenance packages from the updated product catalog so they are ready for
installation.
1.Log in to CSM  using your credentials.
2.Select the Products  tab.
3.Select the product name on the Available Products tree.
The product releases are listed in the Releases  table on the right.
4.Download product packages by selecting one of the following options:
–To download product packages for all product releases, right-click the product name in the list, and select Update
Product .
–To download packages only for specific releases, select one or more releases in the Releases  table on the right
and select the Update Product Releases  link.
5.View the downloaded packages using either of the following options:
–To display the downloaded maintenance packages, select the product release icon
in the product list.
–To display the downloaded base installation package, select the product gen level icon
below the product release in the product list.
The product packages are downloaded and ready for installation.
Add External Product Installation Packages
Sometimes you have product installation packages that you downloaded outside of CSM . For example, you do not
have an HTTP or an FTP access in your mainframe environment, or the required packages are not available from the


Broadcom Support  website. You can use CSM  to install these external packages according to your organization policy. If
you are using this installation option, first add the external packages to the CSM  software catalog.
1.Log in to CSM  using your credentials.
2.Select the Products  tab.
3.Select the Add Product  link in the Actions  section.
4.Specify the name, release, and gen level of the product, and select OK.
The product is added to the product list.
5.Select the gen level of the product that you want to download on the product tree.
The Base Install Packages  section appears on the right.
6.Select the Add External Package  button.
 113


InterTest™ and SymDump ® 11.0
7.Specify one of the following package types and package details, and select OK.
UNIX File
Adds an installation package that is located in a USS directory in binary mode.
FTP File
Adds a product package that is not published on Broadcom Support . For example, a beta version of a product.
Specify the FTP host, FTP port, FTP path, package name, and the user name and password to access the FTP
location.
8.Refresh the page to see the added product package.
The product installation package is now listed in the product list and is available for installation with CSM .
Add External Product Maintenance Packages
Sometimes you have maintenance packages, for example, unpublished maintenance or a program temporary fix (PTF),
that you downloaded outside of CSM . You can use CSM  to install these external maintenance packages per your
organization policy. For this installation option, first add the packages to the CSM  software catalog.
Usually, the maintenance is placed as a single package. However, some Broadcom  products have older aggregated
maintenance packages that were released before December 31, 2013. An aggregated package  is a file that comprises
several single maintenance packages (nested packages). When you add an aggregated package, CSM  inserts all the
nested packages and the aggregated package itself. In the list of maintenance packages, the aggregated package is
marked with the CUMULATIVE type.
1.Log in to CSM  using your credentials.
2.Select the Products  tab.
3.Select the product release for which the maintenance applies.
The maintenance packages for the release are listed.
4.Select the Add External Maintenance  button.
You are prompted to specify the package.
5.Specify one of the following package types and package details:
Data Set


5.Specify one of the following package types and package details:
Data Set
Adds a maintenance package that is located in a z/OS data set with a logical record length of 80 and with a record
format of fixed blocks.
UNIX File
Adds a maintenance package that is located in a USS directory in binary mode.
FTP File
Adds a maintenance package that is not published on Broadcom Support . This option is intended for downloading
a PTF to validate it. Specify the FTP host, FTP port, FTP path, maintenance package name, and the user name
and password to access the FTP location.
Solution
Adds a published solution from Broadcom Support .
6.Refresh the page to see the added maintenance package.
The product maintenance package is now listed in the product catalog and is available for installation with CSM .
You completed the acquisition process. The product packages are ready for installation with CSM .
Install Your Product Using CSM
As a systems programmer, your responsibilities include installing products in your z/OS environment using CSM . This step
of the installation process creates or updates the SMP/E environment (global, target, and distribution zones).
The following diagram shows the major steps to install your product using CSM .
 114


InterTest™ and SymDump ® 11.0
1.(Optional) Configure base installation settings .
2.(Optional) Configure a working set of SMP/E environments .
3.Initiate product installation  and review product information .
4.Select an installation type .
5.Review installation prerequisites  if any are presented.
6.Take one of the following steps to select an SMP/E environment :
–Create an SMP/E environment :
a.Set up the global zone .
b.Create a target zone .
c.Create a distribution zone .
–Use an existing SMP/E environment from your working set:
a.Update the global zone .
b.Set up the target zone: Either create a target zone  or use an existing target zone .
c.Set up the distribution zone: Either create a distribution zone  or use an existing distribution zone .
NOTE
If you install a product or its components into an existing target or distribution zone, older versions are
deleted from the zone and associated data sets. Use new target and distribution zones for this installation.
Doing so means that you can apply maintenance to your current version, if necessary.
 115


InterTest™ and SymDump ® 11.0
7.Review the installation summary and start the installation .
Configure Base Installation Settings
You can configure base installation settings on the System Settings, Software Installation page.
1.Select the Settings  tab, and select the Software Installation link under System Settings in the Settings section on the
left side.
2.In the SIS Base Install - File System  section, select the file system type that is used when installing a product that
allocates file systems. If you select Product Specific File System , the file system that is used for installing a product
is defined according to the product metadata. Otherwise, the product metadata is overwritten.
3.In the Execute Checks During Base Installation  section, configure the following settings by selecting or clearing
corresponding checkboxes:
Execute Apply Check During Base Installation
Verifies that all requirements for the Apply step are satisfied before the Apply step executes. If the Apply Check
step fails, installation stops and all the previous steps are undone.
Suspend Base Installation After Apply Check
Suspends the base installation process after Apply Check is completed and generates pending installation actions
for the SMP/E environment where the product is being installed. This check box is enabled if you enable the
Execute Apply Check During Base Installation  checkbox.
Execute Accept Check During Base Installation
Verifies that all requirements for the Accept step are satisfied before the Accept step executes. If the Accept
Check step fails, installation stops and all the previous steps are undone.
Suspend Base Installation After Accept Check
Suspends the base installation process after Accept Check is completed and generates pending installation
actions for the SMP/E environment where the product is being installed. This check box is enabled if you enable
the Execute Accept Check During Base Installation  checkbox.
4.Select Apply .
A dialog that shows the progress of the task opens. When the task completes, select Show Results  on the Progress


tab to close this dialog. The task output browser opens, and you can view the action details.
While a task is in progress, you can perform other work. Select Hide  to exit the dialog and view the task status later on
the Tasks tab.
The base installation settings are configured.
NOTE
If you configure the base installation settings to execute checks during base installation, CSM  creates a pending
installation for the SMP/E environment. For more information about the pending installation, see the CSM  online
help.
Configure a Working Set of SMP/E Environments
If you plan to install a product in an existing SMP/E environment, add this SMP/E environment to your working set. A
working set  is a selected group of SMP/E environments with which you want to work. Although you can have only one
working set, you can have as many SMP/E environments in it as you need.
CSM  does not have a default working set.
If you do not have the SMP/E environment in your working set, you can only create a new SMP/E environment during
product installation. In this case, exit the installation wizard, configure your working set and then restart the wizard.
1.Select the SMP/E Environments  tab, and select the SMP/E environments that you want to include in a working set.
An information text area under the list of SMP/E environments displays the number of environments you selected.
 116


InterTest™ and SymDump ® 11.0
2.Select Use as Working Set.
3.Select OK.
The working set is configured.
The new working set replaces a previously defined working set.
You can display only those SMP/E environments that are in your working set by selecting Show Working Set Only.
Initiate Product Installation
You can install a downloaded product from the Products  tab. The process starts a wizard that guides you through the
installation. At the end of the wizard, a task dynamically invokes the SMP/E and other utilities that are required to install
the product.
1.Select the Products  tab.
2.Perform one of the following steps:
–If the package was acquired using CSM :
From the product list on the left side, select the required product gen level (the innermost level in the product list
under the release level of a product; for example, SP0 or 0110). Locate the product package that you want to install,
select Actions  to the right of the package, and select Install.
–If the package was acquired outside of CSM :
In the Actions section in the left pane, select the Install External Package link. Enter the location of the package.
Select OK.
The Introduction step of the wizard appears where you can Review Product Information .
Review Product Information
Review the information about the product that you are installing.
1.On the Introduction  step, review the information about the installation.
If the product license agreement appears, review it. If you agree, accept it. If you do not accept the license agreement,
you cannot proceed with the installation.
2.Select Next .
You are prompted to select the type of installation .
An information text area can appear at the bottom of the wizard. The area provides information that helps you progress


through the wizard. For example, if a field is highlighted (indicating an error), the information text area identifies the
error.
Select an Installation Type
When you install a product, you select an installation type. There can be one or more installation types, according to the
product.
When you select the custom installation type, you are prompted to select the features that you want to install. If your
selected features require installation of other features, the installation wizard includes the required features to the
installation process. If your selected features are mutually exclusive, the installation wizard excludes any features
conflicting with the features you selected last from the installation process. For example, you select feature 1 and select
feature 2 that is mutually exclusive with feature 1. The wizard automatically excludes feature 1.
1.On the Features  step, select the type of installation, and select Next .
2.(Optional) If you select the custom installation type, select the features to install, and select Next .
A summary of the features to install appears, with prerequisites .
 117


InterTest™ and SymDump ® 11.0
Review Installation Prerequisites
Some products require an installation of other products first.
Review the summary of installation prerequisites to verify that all prerequisites are satisfied on the Prerequisites  step.
•If no prerequisites exist, select Next .
You are prompted to select an SMP/E environment for the installation .
•If all prerequisites exist and are satisfied, you are prompted to locate the installed prerequisites.
Install the product to the same SMP/E environment and the target zone where the product prerequisites are installed.
a.From the SMP/E environment  drop-down list, select an SMP/E environment with the installed prerequisites. This
drop-down list represents all CSM -managed SMP/E environments where the prerequisites are installed.
A list of target zones for the selected SMP/E environment where the prerequisites are installed is populated.
b.From the target zone  drop-down list, select a target zone within the selected SMP/E environment where the
prerequisites are installed.
c.Select Next .
You are prompted to confirm the selected SMP/E environment for the installation .
•If prerequisites are not satisfied, perform one of the following actions:
–Select Cancel  to exit the wizard. Install the prerequisites or migrate an SMP/E environment to CSM  where the
prerequisites are installed. Restart the installation.
–Open CSM  in another browser window and install the prerequisites, or migrate an SMP/E environment to CSM
where the prerequisites are installed. When done, select Refresh  on the Prerequisites  step of the wizard. Then,
select the SMP/E environment and a target zone where the prerequisites are installed. Select Next  to continue the
product installation.
You are prompted to confirm the selected SMP/E environment for the installation .
Select an SMP/E Environment
You select the SMP/E environment where you want to install your product in. You can create an SMP/E environment, or


you can select an existing SMP/E environment from your working set. You can configure your working set  from the SMP/E
Environments tab.
While you work with an SMP/E environment, the environment is locked and other CSM  users cannot perform any action
against it. When the task finishes, logging out from CSM , or a CSM  session is inactive for more than 10 minutes, the lock
releases.
If you select an SMP/E environment being used in CSM  by another user, a notification message appears. You are
prevented from performing any actions on the SMP/E environment. You can wait until the notification message disappears
and the SMP/E environment becomes available or can select Cancel to select another SMP/E environment.
1.On the SMP/E Environment  step, substep 1, take one of the following steps:
–Select Create a New SMP/E Environment  to create an SMP/E environment.
–Select an existing SMP/E environment from your working set.
•If no existing SMP/E environment appears, exit the wizard, configure your working set , and restart the wizard .
•If your product has the installed prerequisites , the SMP/E environment with the installed prerequisites that
you selected at the Prerequisites  step of the wizard is preselected for you. You cannot select another SMP/E
environment. You cannot create a SMP/E environment.
NOTE
When you install a product in an existing SMP/E environment where HOLDDATA is received, the
product installation may fail.
2.Select Next .
You are prompted to complete one of the following tasks:
 118


InterTest™ and SymDump ® 11.0
•Create an SMP/E environment
•Review parameters of an existing SMP/E environment .
Create an SMP/E Environment
You can create an SMP/E environment while you are installing a product. During the process, you are asked to specify the
following information:
•The SMP/E environment name and the prefix of the CSI data set in CSM
•Data set allocation parameters
You can specify data set allocation parameters collectively for all SMP/E data sets, target libraries, and distribution
libraries that are allocated during product installation. You allocate data sets using one of the following methods:
•Allocate data sets using SMS parameters.
•Allocate cataloged data sets using UNIT and optionally VOLSER.
•Allocate uncataloged data sets using UNIT and VOLSER.
If you allocate uncataloged data sets, specify a VOLSER. Based on the value that you enter, CSM  performs the following
validations to ensure integrity of the installation:
•The value of VOLSER must specify a mounted volume.
•You must have ALTER permissions for the data sets with the entered high-level qualifier (HLQ) on the volume that
VOLSER defines.
•To test allocation, CSM  temporarily allocates one of the uncataloged data sets that are allocated during the installation.
a.The data set is allocated with one track for both primary and secondary space.
b.CSM  verifies that the data set has been allocated on the specified volume.
c.The data set is deleted.
If the data set allocation fails or the data set cannot be found on the specified volume, you cannot proceed with the
product installation wizard.
1.On the SMP/E Environment  step, substep 2, review and specify the following parameters as applicable:
SMP/E Environment Name
Defines the SMP/E environment name.
Data Set Name Prefix


SMP/E Environment Name
Defines the SMP/E environment name.
Data Set Name Prefix
Defines the prefix for the name of the CSI VSAM data set.
Catalog
Defines the name of the SMP/E CSI catalog.
Cross-Region
Identifies the cross-region sharing option for SMP/E data sets. This parameter is set to its default value. You
cannot edit it.
Cross-System
Identifies the cross-system sharing option for SMP/E data sets. This parameter is set to its default value. You
cannot edit it.
High-Level Qualifier
Specifies the high-level qualifier (HLQ) for all SMP/E data sets that are allocated during installation. Product
packaging defines the low-level qualifiers (LLQ). The low-level qualifiers cannot be changed.
DSN Type
Specifies the DSN type for allocating SMP/E data sets.
 119


InterTest™ and SymDump ® 11.0
SMS Parameters / Data Set Parameters
Specifies if this SMP/E environment is using SMS parameters (Storage Class, Management Class, Data Class) or
data set parameters (VOLSER, Unit, Catalog).
An information text area can appear at the bottom of the wizard. The area provides information that helps you progress
through the wizard. For example, if a field is highlighted (indicating an error), the information text area identifies the
error.
2.Select Next.
Work DDDEF allocation parameters and a list of the data sets to be created for the SMP/E environment appear.
Review Parameters of an Existing SMP/E Environment
When you use an existing SMP/E environment to install your product, you review the SMP/E environment parameters.
If applicable, you also specify parameters for any new data sets to be allocated while installing a product. During the
process, you are asked to review allocation parameters for new data sets, which you can customize for each data set. The
existing data sets remain intact.
The Software Installation Service (SIS) determines which data sets exist and which must be allocated for the installation
using an existing SMP/E environment. If the SIS determines that new data sets must be allocated, you are prompted to
specify the data set allocation parameters. The data set allocation parameters are prepopulated with the values from the
existing data set that was found first.
1.On the SMP/E Environment  step, substep 2, review the current SMP/E environment parameters and allocation
parameters for data sets that must be added to the SMP/E environment. Update the information as applicable.
2.Select Next .
Work DDDEF allocation parameters and a list of the data sets to be created for the SMP/E environment, if any,
appear .
Set Up SMP/E Environment Parameters
When creating an SMP/E environment for your product installation, you specify SMP/E environment parameters.


When creating an SMP/E environment for your product installation, you specify SMP/E environment parameters.
When using an existing SMP/E environment for installing your product, you review and, if necessary, update its SMP/E
environment parameters.
You can assign different prefixes to each newly allocated data set during the installation process.
1.On the SMP/E Environment step, substep 3, specify whether to use SMS parameters (Storage Class, Management
Class, Data Class) or Unit parameters for allocating work DDDEFs for the SMP/E environment. Complete the
appropriate fields.
The allocation parameters that you specify for work DDDEFs are applied only to new work DDDEFs that are created
during the installation. The existing work DDDEFs, if any, remain intact.
NOTE
The settings for allocating work DDDEFs are globally defined on the System Settings, Software
Installation  tab. You must have the appropriate access rights to be able to modify these settings.
2.Review the data set names if any appear. Select the Override link to change the high-level qualifier of the data set
name and the allocation parameters. Select OK.
3.(Optional) If any additional parameters appear, review the parameters that have the default values assigned. Edit the
parameters if necessary and specify any missing parameters.
4.Select Next .
You are prompted to select a target zone to use .
 120


InterTest™ and SymDump ® 11.0
Select a Target Zone
You select a target zone in the SMP/E environment where you want to install your product. You create a target zone or
select an existing target zone in the SMP/E environment (if you use an existing SMP/E environment).
1.On the Target Zone step, substep 1, perform one of the following actions:
–Select Create a New Target Zone to create a target zone.
–Select an existing target zone in the SMP/E environment.
This option is available only if you selected to use an existing SMP/E environment.
WARNING
•If you install a product or its components into an existing target or distribution zone, older versions are
deleted  from the zone and associated data sets. Use new target and distribution zones for this installation
so that you can apply maintenance to your current version, if necessary.
•If your product has the installed prerequisites , the target zone of the SMP/E environment with the installed
prerequisites that you selected at the Prerequisites  step of the wizard is preselected for you. You cannot
select another target zone. You cannot create a target zone.
2.Select Next .
You are prompted to create a target zone  or use an existing target zone .
Create a Target Zone
You can create a target zone in a new or an existing SMP/E environment where you install your product. The target zone
parameters are prepopulated with the values that are entered for the SMP/E environment. You can change data set
allocation parameters.
You can specify a different SMP/E environment data set to be used for a new target zone.
1.On the Target Zone step, substep 2, review and specify the target zone SMP/E parameters as applicable.
Target Zone Name
Defines the name for the target zone.
Create New CSI Data Set
Specifies that a new CSI data set will be created for the target zone.


Specifies that a new CSI data set will be created for the target zone.
Data Set Name Prefix
Defines the prefix for the name of the target zone data set. This field is only enabled when you have selected the
Create New CSI Data Set  check box.
Catalog
Defines the name of the SMP/E target zone catalog. This field is only enabled when you have selected the Create
New CSI Data Set  check box.
Cross-Region
Identifies the cross-region sharing option for SMP/E data sets. This parameter is set to its default value. You
cannot edit it.
Cross-System
Identifies the cross-system sharing option for SMP/E data sets. This parameter is set to its default value. You
cannot edit it.
High-Level Qualifier
Specifies the high-level qualifier (HLQ) for all target zone data sets that are allocated during installation. Product
packaging defines the low-level qualifiers (LLQ) and they cannot be changed.
DSN Type
Specifies the DSN type for allocating target zone data sets.
 121


InterTest™ and SymDump ® 11.0
SMS Parameters / Data Set Parameters
Specifies if this target zone uses SMS parameters (Storage Class, Management Class, Data Class) or data set
parameters (VOLSER, Unit, Catalog).
An information text area can appear at the bottom of the wizard. The area provides information that helps you progress
through the wizard. For example, if a field is highlighted (indicating an error), the information text area identifies the
error.
2.Select Next .
A list of the data sets to be created for the target zone appears .
Use an Existing Target Zone
When using an existing target zone for installing your product, you review and, if necessary, update its parameters.
1.On the Target Zone step, substep 2, review the current target zone parameters and allocation parameters for data
sets that must be added. Update as applicable.
NOTE
You cannot change the current SMP/E environment parameters.
2.Select Next .
If there are any data sets to be created for the target zone, a list of data sets appears . If the list is empty, no new data
sets are going to be allocated.
Set Up Target Zone Parameters
When creating a target zone in the SMP/E environment for your product installation, specify target zone parameters.
1.On the Target Zone step, substep 3, review the data set names if any appear. Select the Override  link to change the
high-level qualifier of the data set name and the allocation parameters. Select OK.
2.(Optional) If more parameters appear, review the parameters that have the default values assigned. Edit the
parameters if necessary and specify any missing parameters.
3.Select Next .
You are prompted to confirm the distribution zone .
Confirm a Distribution Zone
You must confirm a distribution zone of the SMP/E environment where you want to install your product. Depending on


whether you created a target zone or you selected an existing target zone, create a distribution zone or select an existing
distribution zone in the SMP/E environment.
1.On the Distribution Zone  step, substep 1, review the selected option for the distribution zone.
–If you are using an existing target zone, the related distribution zone is automatically selected. You cannot select
other distribution zones or cannot create one.
NOTE
If you install a product or its components into an existing target or distribution zone, older versions are
deleted from the zone and associated data sets. Use new target and distribution zones for this installation
so that you can apply maintenance to your current version, if necessary.
–If you are creating a target zone, you can create a distribution zone or you can select an existing distribution zone.
NOTE
Using an existing distribution zone with a new target zone relates the existing distribution zone to the
new target zone. This action breaks the relationship from the previous target zone that was related to
 122


InterTest™ and SymDump ® 11.0
this distribution zone. You cannot accept maintenance packages from the previous target zone to this
distribution zone using CSM .
2.Select Next .
You are prompted to set up the distribution zone.
Create a Distribution Zone
You can create a distribution zone that is related to the newly created target zone. The distribution zone parameters are
prepopulated with the values that are entered for the SMP/E environment. You can change data set allocation parameters.
You can specify a different SMP/E environment data set to be used for the new distribution zone.
You can also specify the same SMP/E environment data set as the one that you specified for the target zone. In that case,
the target and distribution zones share the SMP/E environment data set. The SMP/E environment data set is allocated
using the parameters that you have defined when specifying the target zone.
1.On the Distribution Zone  step, substep 2, review and specify the following parameters as applicable:
Distribution Zone Name
Defines the name for the distribution zone.
Create New CSI Data Set
Specifies that a new CSI data set is created for the distribution zone.
Data Set Name Prefix
Defines the prefix for the name of the distribution zone data set. This field is only enabled when you have selected
the Create New CSI Data Set  check box.
Catalog
Defines the name of the SMP/E distribution zone catalog. This field is only enabled when you have selected the
Create New CSI Data Set  check box.
Cross-Region
Identifies the cross-region sharing option for SMP/E data sets. This parameter is set to its default value. You
cannot edit it.
Cross-System
Identifies the cross-system sharing option for SMP/E data sets. This parameter is set to its default value. You
cannot edit it.
High-Level Qualifier


cannot edit it.
High-Level Qualifier
Specifies the high-level qualifier (HLQ) for all distribution zone data sets that are allocated during installation.
Product packaging defines the low-level qualifiers (LLQ) that cannot be changed.
DSN Type
Specifies the DSN type for allocating distribution zone data sets.
SMS Parameters / Data Set Parameters
Specify if this distribution zone is to use SMS parameters (Storage Class, Management Class, Data Class) or
data set parameters (VOLSER, Unit, Catalog). Complete the applicable fields.
An information text area can appear at the bottom of the wizard. The area provides information that helps you progress
through the wizard. For example, if a field is highlighted (indicating an error), the information text area identifies the
error.
2.Select Next .
A list of the data sets to be created for the distribution zone appears .
 123


InterTest™ and SymDump ® 11.0
Use an Existing Distribution Zone
You can use an existing distribution zone that is related to the existing target zone you selected, or with a new target zone.
The distribution zone parameters are prepopulated with the values that are entered for the SMP/E environment. You can
change data set allocation parameters.
NOTE
Using an existing distribution zone with a new target zone relates the existing distribution zone to the new target
zone. This action breaks the relationship from the previous target zone that was related to this distribution zone.
You cannot accept maintenance packages from the previous target zone to this distribution zone using CSM .
1.On the Distribution Zone  step, substep 2, review the current distribution zone parameters and allocation parameters
for data sets that you want to add. Update as applicable.
NOTE
You cannot change the current SMP/E environment parameters.
2.Select Next .
If there are any data sets to be created for the distribution zone, a list of data sets appears . If the list is empty, no new
data sets are going to be allocated.
Set Up Distribution Zone Parameters
When creating a distribution zone in the SMP/E environment where you want to install your product, specify distribution
zone parameters.
1.On the Distribution Zone  step, substep 3, review the data set names if any appear. Select the Override  link to
change the high-level qualifier of the data set name and the allocation parameters. Select OK.
2.(Optional) If any additional parameters appear, review the parameters that have the default values assigned. Edit the
parameters if necessary and specify any missing parameters.
3.Select Next .
You see a summary of the installation task .
Start the Installation
After you complete setting up the SMP/E environment and its zones, you are ready to start the installation.


To start the installation, review the summary on the Summary  step, and select Install .
A dialog that shows the progress of the task opens. When the task completes, Select Show Results  on the Progress  tab
to close this dialog. The task output browser opens, and you can view the action details.
While a task is in progress, you can perform other work. Select Hide  to exit the dialog and view the task status later on the
Tasks tab.
You completed the product installation. You can now start maintaining the installed products.
Install Products Using SMP/E JCL
As a systems programmer, your responsibilities include installing products on your mainframe system. With this option,
you acquire a product pax file and the latest product updates from Broadcom Support  and then install, maintain,
deploy, and configure the products on your systems. Batch jobs are provided to create the SMP/E environment. A basic
understanding of UNIX System Services (USS) is required.
NOTE
Before you begin this process, review the installation best practices and verify that the installation requirements
in Prepare for Installation have been met.
 124


InterTest™ and SymDump ® 11.0
You perform the following tasks to install a product with a pax file:
When these steps are completed, you are ready to install preventive maintenance.
UNIX System Services Environment
You need a UNIX System Services (USS) directory and a file system with adequate space to perform the following tasks:
•Receive product pax files from Broadcom Support .
•Perform utility functions to unpack the pax file into z/OS data sets that you can use to complete the product installation.
We recommend that you allocate and mount a dedicated file system for this process. The amount of space that you need
for the file system depends on the following variables:
•The size of the pax files that you intend to download.
•Whether you plan to keep the pax files after unpacking them. We do not recommend this practice.
We recommend that you use one directory for downloading and unpacking pax files. Reusing the same directory
minimizes USS setup. Complete the USS setup only one time. You reuse the same directory for subsequent downloads.
Alternatively, you can create a directory for each pax download.
WARNING
Downloading pax files for the SMP/E installation requires write authority to the USS directories that are used
for the native SMP/E JCL installation process. In the file system that contains the pax directories, you also
need free space approximately 3.5 times the pax file size to download the pax file and unpack its contents. For
example, to download and unpack a 14-MB pax file, you need approximately 49 MB of free space in the file
system hosting your pax directory.
 125


InterTest™ and SymDump ® 11.0
Allocate and Mount a File System
The product installation process requires a UNIX System Services (USS) directory to receive the pax file and to perform
the unpack steps. We recommend that you allocate and mount a file system that is dedicated to the product acquisition.
We also recommend that you create a directory in this file system where the pax file will be located. This directory
(yourUSSpaxdirectory) is used later in the installation process when acquiring and unpacking the product pax file.
NOTE
To issue the USS mount command for the file system, read access is required to the SAF resource name
SUPERUSER.FILESYS.USERMOUNT in the UNIXPRIV class.
1.Allocate the zFS by customizing the following sample JCL to your site requirements:
//DEFINE   EXEC PGM=IDCAMS
//SYSPRINT DD   SYSOUT=*
//SYSUDUMP DD   SYSOUT=*
//AMSDUMP  DD   SYSOUT=*
//SYSIN    DD *
  DEFINE CLUSTER ( +
  NAME(YOUR_ZFS_DATA_SET_NAME ) +
  STORAGECLASS( class) +
  LINEAR +
  CYL(primary secondary ) +
  SHAREOPTIONS(3 3) +
  )
/*
//FORMAT   EXEC PGM=IOEAGFMT,REGION=0M,
// PARM=('-aggregate YOUR_ZFS_DATA_SET_NAME  -compat')
//SYSPRINT DD   SYSOUT=*
//SYSUDUMP DD   SYSOUT=*
//STDOUT   DD   SYSOUT=*
//STDERR   DD   SYSOUT=*
//CEEDUMP  DD   SYSOUT=*
//*
–Add a JOB card.
–Issue the NUM ON  command followed by UNNUM to edit the JCL with number off (no sequence numbers in columns


73 through 80).
–Issue the CAPS OFF  command. However, where needed, use uppercase and lowercase values. For example,
YOUR_ZFS_DATA_SET_NAME  must be uppercase and aggregate  and compat  must be lowercase.
–Ensure the the zFS data set name that you use conforms to your data set naming conventions for USS file
systems.
If the allocation of the file system data set fails, it is because of environmental settings now allowing for the
allocation.
–Ensure that the SYSIN DD is indented at least one space.
When these edits are complete, the zFS is allocated.
2.Create a mount point for the file system. This example shows how to create your USS pax directory named
yourdirectory /PAX in the existing /u/maint directory. From the TSO OMVS shell, enter the following commands:
cd /u/maint/
mkdir yourdirectory
cd yourdirectory
mkdir PAX
Further references to this mount point appear as yourUSSpaxdirectory . You can reuse the same directory for all
product acquisitions to minimize USS setup. Alternatively, you can create a directory for each pax download.
 126


InterTest™ and SymDump ® 11.0
The mount point is created.
3.Mount the file system by customizing the following sample:
//MOUNT    EXEC PGM=IKJEFT01,REGION=0M
//SYSTSPRT DD SYSOUT=*
//SYSTSOUT DD SYSOUT=*
//SYSTSIN  DD *
MOUNT FILESYSTEM(' your_zFS_data_set_name ') +
MOUNTPOINT(' yourUSSpaxdirectory ') +
TYPE(ZFS) MODE(RDWR) +
PARM('AGGRGROW')
/*
The file system is mounted.
4.(Optional) Set security permissions for the directory. You can permit write access to anyone in the same group as the
person who created the directory. For example, to allow write access to the USS pax directory for other users in your
USS group, enter the following command from the TSO OMVS shell or the Telnet or SSH client of choice at your site:
NOTE
USS commands are case-sensitive.
chmod -R 770 / yourUSSpaxdirectory /
Write access is granted. Other users can access the USS pax directory and its files.
5.Verify that the file system is mounted. To do so, enter the following commands from the Telnet or SSH client:
cd {yourUSSpaxdirectory}
df - k .
The file system is mounted. The output shows the mount point and the mount data set. Resolve errors before
continuing.
Acquire the Product Pax Files
To begin the product installation procedure, copy the product pax file into the USS directory that you set up.
NOTE
To optimize downloads from Broadcom Support , configure the downloads.broadcom.com URL for HTTPS
and Secure FTP in your network security software, firewalls, or both. Sites that regulate access through an IP


address are required to allow network access to 141.202.253.110.
This procedure explains how to transfer a product pax file from Broadcom Support  online to the mainframe.
1.Confirm that you have addressed the following UNIX System Services (USS) requirements:
–Write authority to the USS directories that are used for the pax installation process.
–Available USS file space.
NOTE
In the file system that contains the pax directories, you also need free space approximately 3.5 times the
pax file size to download the pax file and unpack its contents. For example, to download and unpack a 14-
MB pax file, you need approximately 49 MB of free space in the file system hosting your pax directory.
If you do not have sufficient free space, error messages similar to the following appear:
EZA1490I Error writing to data set
EZA2606W File I/O error 133
2.Go to Broadcom Support  at https://support.broadcom.com, and select Software , Mainframe Software , and My
Downloads.
3.Log in using your Broadcom Support  username and password.
The My Downloads  page appears.
4.Select a product from the list or enter the product name in the Search  field.
 127


InterTest™ and SymDump ® 11.0
The product page appears with two tabs under the product name: Products  and Solutions .
5.Under Products , select the product that you want to download.
A list by release, service pack, and language appears.
6.Click the hypertext link to select a release.
The Primary Downloads  page appears. This page shows the available product-specific software packages that you
can select to download.
If an Additional Downloads  page is available, this page shows additional software packages that are related to your
product selection that you can download. These products may already be installed.
7.Review the packages that appear under Primary Downloads  and Additional Downloads  and complete the following
steps:
a.Select the SMP/E JCL Package  (classic pax) and other files that you want to include in the product download.
If more than one package is available, you can only select one.
b.Select Download Selected , HTTPS Download , or Secure FTP Download . Secure FTP Download is the
preferred method. For download tips, see Product Download Help . For sample JCL and security requirements, see
Download Methods and Locations .
The product package is downloaded.
You are now ready to extract the contents of the product package into a product directory that you create.
Create a Product Directory from the Pax File
After you acquire and download the product package (pax file), you are ready to create a product directory in which to
extract the contents of the package. You can do so using the pax command or the ESDUNPAX sample JCL.
Use the pax Command
To use the pax command to create a product directory, enter:
cd /yourUSSpaxdirectory/
pax -rvf pax-filename
These commands set the current working directory in your USS directory to the directory containing the pax file and


These commands set the current working directory in your USS directory to the directory containing the pax file and
then performs the following actions:
•Extracts the files and directories that are packaged within the pax file.
•Creates a USS directory in the same directory structure where the pax file resides.
•Automatically generates a product and level-specific directory name.
The product directory is created. You are now ready to copy the sample installation JCL to a z/OS data set.
Use the ESDUNPAX Sample JCL
To use the ESDUNPAX sample JCL to create a product directory, review the following JCL sample and edit it as shown in
the procedure that follows:
//ESDUNPAX JOB ( ACCOUNTNO ),'UNPAX PAX FILE',
// MSGCLASS=X,CLASS=A,NOTIFY=&SYSUID
//*********************************************************************
//* This sample job can be used to invoke the pax command to create   *
//* the product-specific installation directory.                      *
//*                                                                   *
//* This job must be customized as follows:                           *
//* 1. Supply a valid JOB statement.                                  *
//* 2. Replace "yourUSSpaxdirectory" with the name of the USS         *
//*    directory used on your system for Pax ESD downloads.           *
 128


InterTest™ and SymDump ® 11.0
//* 3. Replace "paxfile.pax.Z" with the name of the pax file.         *
//* NOTE: If you continue the PARM= statement on a second line,       *
//*       start entering characters in column 16 and make sure        *
//*       the 'X' continuation character is in column 72.     *
//*********************************************************************
//UNPAXDIR EXEC PGM=BPXBATCH,
// PARM='sh cd / yourUSSpaxdirectory /; pax -rvf paxfile.pax.Z '
//*UNPAXDIR EXEC PGM=BPXBATCH,
//* PARM='sh cd / yourUSSpaxdirectory /; pax                              X
//*             -rvf paxfile.pax.Z '
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
Edit the sample JCL as described in the following steps:
1.Replace ACCOUNTNO with a valid JOB statement.
2.Replace yourUSSpaxdirectory  with the name of the USS directory that you use for product downloads.
The job points to your specific directory.
3.Replace paxfile.pax.Z  with the name of the pax file.
The job points to your specific pax file.
4.Submit the job.
The job creates the product directory.
NOTE
If the PARM= statement exceeds 71 characters, comment out the first UNPAXDIR. Then uncomment and
use the second form of UNPAXDIR instead. This sample job uses an X in column 72 to continue the PARM=
parameters to a second line.
The product directory is created. You are now ready to copy the sample installation JCL to a z/OS data set.
Copy Installation Files to z/OS Data Sets


Copy Installation Files to z/OS Data Sets
Use this procedure to invoke the SMP/E GIMUNZIP utility to create the SAMPJCL z/OS data set.
The file UNZIPJCL in the product directory contains a sample job to extract the installation package. You edit and submit
the UNZIPJCL job to copy the sample installation JCL to a z/OS data set.
1.Locate and read the product readme file or installation notes, if applicable, which resides in the product-specific
directory that the pax command created. This file contains the product-specific details that you require to complete the
installation procedure.
You have identified the product-specific installation details.
2.Use ISPF EDIT or TSO ISHELL to edit the UNZIPJCL sample job. You can perform this step in one of the following
ways:
Use ISPF EDIT Specify the full path name of the UNZIPJCL file.
Use TSO ISHELL Navigate to the UNZIPJCL file and use the E line command to edit the file.
The job is edited.
3.Change the SMPDIR DD PATH to the product-specific directory created by the pax command.
Your view is of the product-specific directory.
4.If ICSF is not active, perform the following steps:
a.Change the SMPJHOME DD PATH to your Java runtime directory. This directory varies from system to system.
b.Perform one of the following steps:
 129


InterTest™ and SymDump ® 11.0
•Change the SMPCPATH DD PATH to your SMP/E Java application classes directory, typically /usr/lpp/smp/
classes/.
•Change HASH=YES to HASH=NO on the GIMUNZIP parameter.
One of the following outcomes occurs: ICSF is active or you are using Java.
5.Change yourHLQ  to the high-level qualifier (HLQ) for z/OS SAMPJCL data set.  We suggest that you use a unique
HLQ for each expanded pax file to identify uniquely the package.
6.Submit the UNZIPJCL job.
The UNZIPJCL job completes with a zero return code. Messages GIM69158I and GIM48101I in the output and
IKJ56228I in the JES log are acceptable. The SAMPJCL data set is created with the HLQ that you specified in the
UNZIP job. You use this data set to perform the product installation.
Prepare the SMP/E Environment for a Pax Installation
The members in the following procedure are used to prepare the product data sets, initialize the SMP/E zones, and create
the DDDEFs for your product. These steps include:
•Allocating product and SMP/E data sets, and product USS data sets and directories
•Creating and customizing the SMP/E CSI
•(Optional) Customizing the SMP/E CSI for USS
For information about the members, see the JCL comments.
1.Customize the macro AVHSEDIT as follows with your site-specific information:
a.Replace the rightmost parameters for each ISREDIT CHANGE command.
b.Set the PRODHLQ to the same value specified for yourHLQ  within the JCL that is used to unzip the pax file.


c.(Optional) Set the NULLFILE HLQ if applicable and use it for the IMS, HSSR, and CICS DDDEF specifications
when valid system libraries do not exist in your environment. This setting does not apply to every product.
d.Save your changes and then copy the macro to your SYSPROC location.
The macro is ready to customize the yourHLQ .SAMPJCL members.
When you edit an installation member, type AVHSEDIT on the command line, and press Enter to replace the defaults
with your specifications.
NOTE
The following steps include instructions to execute the AVHSEDIT macro each time you open a new
SAMPJCL member. To edit all SAMPJCL members simultaneously, read and follow the instructions in the
AVHAREAD member, and submit the AVHEDALL member.
2.Open the SAMPJCL member AVH00ALL in an edit session and execute the AVHSEDIT macro from the command
line.
AVH00ALL is customized.
3.Submit AVH00ALL.
This job produces the following results:
–Creates the target and distribution data sets for your product.
–Creates unique SMPLTS, SMPMTS, SMPSCDS, and SMPSTS data sets for this target zone.
4.Complete the following steps if your product requires a zFS file system or if you want to install a feature of the product
that requires a zFS file system:
WARNING
If the following members do not exist in SAMPJCL, ignore this step. This step does not apply to your product.
Go to Step 5.
a.Open the SAMPJCL member AVH03ALU in an edit session and execute the AVHSEDIT macro from the command
line.
AVH03ALU is customized.
b.Submit AVH03ALU.
 130