ZD&T Survival Guide

z108251 ZD&T Survival Kit
Michael Erichsen
Xact Consulting A/S
Enterprise Modernization Specialist
2019 IBM Systems Technical University
20 – 24 May | Berlin, Germany

Xact Notices and Disclaimers
— The descriptions and recommendations are not official IBM material, but based on experiences
from several customer projects in various countries
• Any errors are ours, so please do not sue IBM, but make us wiser!
— Use them carefully and with common sense
— This is not a full ZD&T course, but should only be seen as a survival kit
— The bad news
• The system you break will be your own
— The good news
• The system you break will be your own
2 © Copyright Xact Consulting 2019

Speaker Introduction
— Michael Erichsen is not an IBM employee, but
a business partner employee
— About 35 years of experience of systems
programming, architecture, and a bit more
— 7 years of ZD&T support experience
— Is part of the Xact Enterprise Modernization
team, which specializes in supporting
customers with IBM products like
• ZD&T
• IBM Developer for z and I
• Rational Team Concert
— Xact Consulting is based in Denmark

Session Objectives
— Provide an overview over ZD&T
• Logical and physical views
— Explain how to run an implementation project
— And which challenges to handle
— Helpful commands and files to check and modify the system

What is ZD&T?
IBM Systems Technical University

What is ZD&T?
— ZD&T (currently) means IBM Z Development
and Test Environment
• zD&T
• RD&T
• RDzUT
• zPDT
— A z/OS or z/VM system running on emulated
z14 processors, hosted on Intel hardware
— Emulated hardware - real software
— Intended and licensed for test and
development, not production
— ZD&T
• PE: Personal Edition
• EE: Enterprise Edition
• PS: Parallel Sysplex

What is ZD&T? Logical View
z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Generic Configuration Volume
Instance Specific Configuration Volume
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume
— The hardware platform can be
• A physical Intel machine
• A VMWare Workstation on a Windows machine
• A VMWare instance
• Another supported virtualization product
• A virtual machine in a cloud service
— It must be 64-bit Intel hardware
— This is your own responsibility

z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume
— The Linux operating system is most often a
Red Hat Enterprise Linux (RHEL), which is
officially supported
— ZD&T is also officially supported on Ubuntu
and known to run on other Linux distributions
— It must be a 64 bit Linux
— This is also your own responsibility

z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume
— Z1090 (and its twin z1091) are Linux
programs, which emulate z Series hardware
— The latest version emulates z14
— This is supplied by IBM in North Carolina

z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume
— ADCD
• The z/OS operating system and subsystems are
supplied as a package called ADCD, Application
Developers Controlled Distribution
— It consists of disk images
— It can IPL out of the box
— It is supplied by IBM Dallas

z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume
— We like to add an instance specific
configuration volume
— Here we store members specific to an
instance (LPAR)
• TCP/IP
• System name related members
• Etc…
— This is created and mounted by yourself

z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume
— Host data and applications must be
downloaded from the Big Iron or created
synthetically
— We prefer to have download volumes and
active user volumes separated
— This is your own responsibility

What is ZD&T? Lasagna View

What is ZD&T? Physical View (“Classic” Style)
XA00
Master
Image
File
Share
License server
XA03
XA01
XA02

What is ZD&T? Physical View (Single-user System)
z1090
zVolumes
Host data and
applications
Linux
VMWare Workstation
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume
64-bit Windows
Intel Laptop

What is ZD&T? Physical View with ZD&T EE Tools
File
Share
License server
EE Tools Server XA03
XA01
XA02

What is ZD&T? VMWare View

Cloud view
2019 IBM Systems Technical University 18 O Copyright Xact Consulting 2019

What is ZD&T? Linux View

What is ZD&T? 3270 View

What is ZD&T? IDz View

What is ZD&T? License Server View

What is ZD&T? EE Tools View

What can you expect?

Expectations
— ZD&T is a complete and real z/OS (or z/VM)
system
• Almost everything is the same as on any other
z/OS system
• The functional answer to “Can you do this or
that” is almost always “Yes!”
— It is a great platform for development and
test
• You do not have to wait for Change Management
and RACF administrators
• You can easily restore a system to a previous
stage
• Can add zIIP and crypto-processors
— Very buzzword compliant
• A good platform for DevOps, “Shift Left”, agility
and flexibility

Limitations
— Only use for development and test
— Do not use for performance test
• Emulated z14 hardware
• Many layers of virtualization
• No System Assistance Processors to handle I/O
— Do not run large Java workloads
— Some obscure crypto-instructions not
handled

Hurdles
— Each version of ADCD is different
• Which subsystems are configured and active?
• Which versions of z/OS and subsystems are
supplied
• How do the subsystems like CICS, IMS, DB2,
MQ, system logger etc. play together?
• ADCD provided both for ZD&T and for Big Iron
users
— Do you keep ZD&T versions in sync with
ADCD versions and/or your “Big Iron”?
— How do you keep data and applications in
sync with your “Big Iron”?

How to run an
implementation Project

Implementation Process Overview

An implementation Project
Preparations
— Identify a committed team
— Implement pilot hardware
— Install Linux operating system
— Establish connectivity and access
— Acquire and install license

An implementation Project
Preparations
— Identify a committed team
— Implement pilot hardware
— Install Linux operating system
— Establish connectivity and access
— Acquire and install license
▪ Single USB token on a single PC
▪ Software server license
▪ Hardware server license
Identify Requirements
— Business case, expectations, success
criteria
— Pilot workshop
— Requirements analysis report to state what
has been decided
— Refined pilot estimate
— Stop/Go decision for pilot

Install Pilot Baseline System
— Hardware (physical, virtual or cloud)
— License (server or local)
— Linux
— z109*
— ADCD
— Networking
z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume

Configure the system to look your way
— Naming standards
— Rename subsystem?
— Change codepage?
— Which subsystems to activate
— Which versions to use
— 3rd party software
z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume

Integrate Host Data, Applications and Configurations
— Distinguish between development and test
scenarios
— Describe test cases
— Identify host data, applications and
configurations for the pilot
— Create image on host
— Decide copying technologies
— Implement connectivity
— Configure ZD&T
— Define and load databases on ZD&T
— Configure applications
— System test
z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume

z/OS
— PROCLIB
— PARMLIB
— REXX EXEC’s and CLIST’s
— Physical and functional RACF user ids and
names

z/OS
— PROCLIB
— PARMLIB
— REXX EXEC’s and CLIST’s
— Physical and functional RACF user ids and
names
MQ
— MQ definition source
— Queue definitions
— Code page changes?
— References to remote queues should be
disabled by removing the IP addresses
— Archive jobs should point at existing disks
— Clean up the MVS SMP/E CSI for old MQ
versions, if you need to apply PTF’s

CICS
— CICS definitions source
▪ SIT, PLT, etc.
▪ Definitions in e.g. DEFINE, CREATE or CPSM
format
— CTG parameters
— CICS JCL
— Special customization of CICS start up or
logon

CICS
— CICS definitions source
▪ SIT, PLT, etc.
▪ Definitions in e.g. DEFINE, CREATE or CPSM
format
— CTG parameters
— CICS JCL
— Special customization of CICS start up or
logon
DB2
— DSNZPARM source
— List of SQLID’s and needed GRANT’s
— Archive jobs should be edited
— You might want to add the running version
of DB2 to the LINKLIST
— Change subsystem name?
— Change code page?

IMS
— Exit load modules
— MDA source or load modules
— DBRC DB and DBDS registration source
— DBD source
— PSB source
— SPOC offload or
program/transaction/database definitions
— RTT source

IMS
— Exit load modules
— MDA source or load modules
— DBRC DB and DBDS registration source
— DBD source
— PSB source
— SPOC offload or
program/transaction/database definitions
— RTT source
3rd party products
— SMP/E package or load libraries
— DBRMLIBs
— JCLLIBS, PROCLIBS, PARMLIBS etc.
— Including members in system libraries
— Installation instructions
— License or activation files

Integrate Data
— DB2
• DDL
• Fieldprocs, Storage groups, Tablespaces, Databases, Tables, Indices, Plans, Bind processes, Views, Stored
procedures
• Unload datasets
• Punched LOAD statements
o Description of name correlation between unload and punch datasets,
• Bind information
• Tablespace partitioning
o What is the impact on disk space if we keep partitioning vs. how to remove it
• List of plans, package lists, collections and packages
— IMS
— Needed GDG and VSAM definitions
— QSAM

Integrate Applications
— For development
• Source, copybooks, JCL, support macros and REXX EXEC’s etc.
— For test
• Load libraries and DBRM libraries in test for batch, CICS, IMS, and external stored procedures
• Note that load modules and DBRM’s must have corresponding timestamps
— Native stored procedures source
— COBOL listings for debugging
— Exits

Pilot Test

After the Pilot Test
Design and build long-term System
— Implement server farm
— Create master image on a file share or using
ZD&T EE Tools
— Long term connectivity
— Security

After the Pilot Test
Design and build long-term System
— Implement server farm
— Create master image on a file share or using
ZD&T EE Tools
— Long term connectivity
— Security
Develop Processes and Tools
— Establish in-house support team
— Operating system and subsystem upgrades
— Source Control Management
— Test Data Management
— Host synchronization
— Deployment
— Scheduling
— Automation
— Security
— Quality assurance and reporting

Hand-over
— Describe operations procedures
— Training
— Coaching
— Final acceptance

Which Challenges have we
met?

Challenges: IBM-supplied ZD&T System is ready to run, but…
— The effort to adapt it to your environment is a big effort
• The organizational effort is much bigger than the technical effort!
— Customize the ZD&T z/OS system to your environment
— Identify, isolate, extract, copy and integrate applications, data and configurations from the Big Iron
to ZD&T
— Establish maintenance and operations and prepare for future system upgrades

Challenges: Application Dependencies on System and Subsystem Names
— Remove dependencies before copying to ZD&T?
— Rename while copying?
— Rename ZD&T default subsystem names?
• This would be a recurring activity for each new version of ADCD

Challenges: Data and Application upgrade Strategy
Development
— Deciding how to interact with existing SCM
and ALM systems
▪ Versioning
▪ Build
▪ Promotion

Challenges: Data and Application upgrade Strategy
Development
— Deciding how to interact with existing SCM
and ALM systems
▪ Versioning
▪ Build
▪ Promotion
Test
— Identifying a consistent set of test data
from the big iron
▪ Don't move everything
▪ If your SCM is in a mess, then don't rely on
this project to clean it up for you
— Extracting these data to a separate pool
▪ Initial, and recurring
— Agree with operations/service provider on
access to those data
▪ Picking the best tools
— Agree with 3rd party vendors on porting
data unload/reload tools to ZD&T
▪ Licenses?

Challenges: System Upgrade Strategy
— In sync with Big Iron?
— In sync with IBM deliveries of ADCD (Pre-packaged z/OS system)?
— Adding SMP/E work for selected subsystems?
— Swapping ADCD packages impacts DB2 and RACF
• Unload DB2 catalog and table spaces before swap using DB2ADM
• Reload after swap
• Unload RACF definitions and authorizations before swap using a REXX EXEC
• Reload after swap

Challenges: Security
— General principle
• Agility and flexibility requires more freedom than the Big Iron
— Suggested implementation
• Data and application copied to ZD&T must be cleansed before copying
• Separate RACF system and definitions on ZD&T
• Do not copy the Big Iron RACF database
— Data
• Anonymize and/or filter data
— Applications
• Confidential code
— Handle situations where team A must not see code or data from team B
— Difficult to agree with Big Iron staff on processes and tools for copying to ZD&T and for promoting
changes from ZD&T

How to survive the Journey

Cutting through the Lasagna

VMWare
— Use administration panels:
• Number of CPUs
• Memory
• Virtual file systems
• MAC address
z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume

Counting Processors
Standard Configuration Special Configuration

Counting Processors

Linux
— Get underlying hardware:
• less /proc/cpuinfo
• less /var/log/dmesg
• sudo dmidecode | less
• free -m
— Get Linux version:
• cat /etc/*-release
• uname -mrs
— Display filesystem:
• df –h
— Products (depending on Linux distro)
• yum install firefox
• yum install vsftpd
• yum in stall gedit
• yum install x3270
• yum install x3270-x11
z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume

Networking
— For DHCP:
• sudo dhclient –r
• sudo dhclient
— Files
• /etc/resolv.conf
• /etc/hosts
• /etc/sysconfig/network-scripts/ifcfg-*
— Commands
• /etc/init.d/network restart
• ip addr show
• ip route
• systemctl restart network
• ifconfig
• netstat –rn
• nm-connection-editor
• find_io
o ZD&T supplied

z1090/z1091
— rpm -qa | grep z109
— ZDT_Install_PE_V12.0.2.0.x86_64
— /usr/z1090/bin/aws_sysctl
— /usr/z1090/bin/aws_bashrc
— /usr/z1090/bin/z1090instcheck
— perl / zAppliance/scripts/create_devmap.pl
/zAppliance/z230 –h zos02.xact.dk >
/zAppliance/devmaps/XA02_devmap
• Note: If the ethernet device name is “new”, such
as ens-192, you might need to change it to
something like eth0
— /usr/z1090/bin/clientconfig
— runzpdt
• Edit DEVMAP and LOADPARM
z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume

Z1090/z1091
z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume
— Useful Linux commands for setup verification:
• ulimit -a
• ipcs -l
• /sbin/sysctl -a
• ifconfig
• gedit /etc/sysctl.conf
— pdsUtil
— awsckmap

Restoring a lost Master Console
z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume
— From Linux
• x3270 v700 &
— From SDSF
• V 700,offline
• V 700,online,uncond
• V 700,console
— Or from a Linux command line:
— oprmsg 'v cn(*),activate' oprmsg 'v
700,offline'
— oprmsg 'v 700,offline,force’ (optional)
— oprmsg 'v 700,online,uncond'
— oprmsg 'v 700,console'
— oprmsg 'v cn(*),deactivate' (optional)

z/OS
— At first IPL:
• Any console WTOR’s need response number 00,
e.g.
• IXC420D; Reply 00,I
— Tip:
• Use DDLIST (ISRDDN) to edit parmlib members,
so you do not overwrite IBM-supplied members,
but create new USER.Z23B.* members
• Do similarly for PROCLIB, CLIST etc.
— Console:
• F6 to see outstanding WTOR’s
• F10 to see what is running
• D O for options
• D IPLINFO
z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume

z/OS
— D IPLINFO:
• RESPONSE=XA02
• EE254I 10.56.40 IPLINFO DISPLAY 841
• SYSTEM IPLED AT 19.31.49 ON 04/16/2019
• RELEASE z/OS 02.03.00 LICENSE = z/OS
• USED LOADAX IN SYS1.IPLPARM ON 00A82
• ARCHLVL = 2 MTLSHARE = N
• IEASYM LIST = 00
• IEASYS LIST = AL (OP)
• IODF DEVICE: ORIGINAL(00A82)
CURRENT(00A82)
• IPL DEVICE: ORIGINAL(00A80)
CURRENT(00A80) VOLUME(B3RES1)
z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume

z/OS first Configuration
Run script runzpdt
(Linux)
Device map
(Linux)
IPLPARMS(LOADxx)
PARMLIB(IEASYSxx)
PARMLIB
Concatenation
PARMLIB
(COMMNDxx)
PARMLIB
(BPXPRMxx)
Master Catalog
PARMLIB(MSTJCLxx) PARMLIB(CLOCKxx) PARMLIB(PROGxx)

PARMLIB
(COMMNDxx)
PROCLIB(VTAMxx)
PARMLIB(VTAMxx)
PARMLIB
(BPXPRMxx)
PROCLIB(VTAM)PROCLIB(RESOLVER)
PROCLIB(TCPIP)
TCPPARMS
(TCPDATA)
VTAMLST
(ATCCONxx)
VTAMLST(OSATRLxx)
TCPPARMS(PROFILE)
PARMLIB(MSTJCLxx)
PROCLIB
Concatenation
VTAMLST
Concatenation

Understanding Catalogs
— Master catalog
• Specified in SYS1.IPLPARM
• SYSCAT B3SYS1113CCATALOG.Z23B.MASTER
• Is a VSAM file
• Limit to user catalogs and datasets needed at IPL time
— User catalog
• Also a VSAM file
• Contains ALIASes for data set high level qualifiers
• We like to have a user catalog on each user disk
o Then catalog information can be moved and copied with the disk
— Use IDCAMS IMPORT OBJECTS to import a user catalog into a master catalog

— USER.Z23B.PARMLIB(IEASYSAL)
— USER.Z23B.PARMLIB(IEFSSNDB)
— USER.Z23B.PARMLIB(CLOCK00)
— USER.Z23B.PARMLIB(BPXPRMBP)
— USER.Z23B.PARMLIB(BPXPRMDB)
— USER.Z23B.PARMLIB(BPXPRMIM)
— USER.Z23B.CLIST(ISPFCL)
— USER.Z23B.PROCLIB (ISPFPROC)
— USER.Z23B.PROCLIB(JES2)
— USER.Z23B.PARMLIB(JES2PARM)
— /etc/httpd.envvars
— SYS1.IPLPARM(LOADAX)
— ADCD.Z23B.PARMLIB(MSTJCL00)
— ADCD.Z23B.PARMLIB(COMMNDAL)
— ADCD.Z23B.PROCLIB(VTAM)
— USER.Z23B.PARMLIB(FTPSDATA)
— USER.Z23B.PROCLIB(FTPD)
— USER.Z23B.PROCLIB(TCPIP)
— USER.Z23B.PROCLIB(VTAMALL)
— USER.Z23B.PROCLIB(SHUTALL)
— USER.Z23B.PARMLIB(VTAMALL)
— USER.Z23B.PARMLIB(SHUTALL)

TASID (https://www-01.ibm.com/support/docview.wss?uid=swg24009131 )

Our Advice: Create an LPAR-specific Configuration Disk
— Separate what is in common for all your ZD&T
instances (LPAR’s) from what is specific to
each
— Will make cloning and maintenance easier
— A model 3 disk is sufficient
— Add to device map
— Add LPAR-specific PARMLIB, PROCLIB etc
• PROCLIB must not be a PDSE
— Concatenate them at the top in IPLPARM,
JES2, MSTJCL*, ISPFPROC etc.
— Create a local user catalog on this and any
other user disk, so you can copy them around
z1090
zVolumes
Host data and
applications
Linux
Hardware Platform
Local User
Volume
Local User
Volume
Local User
Volume
Local User
Volume

Renaming the LPAR
— USER.VTAM.SOURCE(USSN) and (USSNJCL)
• Copy from ADCD.Z23B.VTAM.SOURCE and edit
— USER.Z23B.PROCLIB(TN3270)
— USER.Z23B.CLIST(IMSCOLD)
— USER.Z23B.CLIST(IMSSTOP)
— USER.Z23B.CLIST(IMSWARM)
— USER.Z23B.PARMLIB(BPXPRM01)
— USER.Z23B.PARMLIB(BPXPRMRT)
— USER.Z23B.PARMLIB(COMMNDAL)
— USER.Z23B.PARMLIB(GRSRNL00)
— USER.Z23B.PARMLIB(IEASYM00)
— USER.Z23B.PARMLIB(IEASYM00)
— USER.Z23B.PARMLIB(IEASYSAL)
— USER.Z23B.PARMLIB(IGDSMS00)
— USER.Z23B.PARMLIB(IZUPRM01)
— USER.Z23B.PARMLIB(JES2PARM)
— USER.Z23B.PARMLIB(SMFPRM00)
— USER.Z23B.PARMLIB(VTAM00)
— USER.Z23B.PARMLIB(VTAMALL)
— USER.Z23B.PROCLIB(JES2)
— USER.Z23B.PROCLIB(TCPIP)
— USER.Z23B.TCPPARMS(IPNODES)
— USER.Z23B.TCPPARMS(PROFILE)
— USER.Z23B.TCPPARMS(TCPDATA)

Renaming the LPAR
— JES2 console command:
• $T NODE(S0W1),NAME=XA02
— SMS name is changed using the ISMF panels (ISPF option M.2)
• Read the manual and be very careful!
— A change in IEASYM00 to a new SYSNAME impacts USS file systems
• Mount tables must be handled
• Symbolic links needs to be changed (Can be quite tricky)
— The system you break will be your own!
— Back up the configuration disks at the Linux level, before you try any of this
• B3CFG1
• B3SYS1
• Others…
— The emergency exit:
• Do a stand-alone IPL (Consult the Redbook)

SYSLOG and LOGREC
— To avoid SYSLOG and the JES SPOOL running full we add a started task called
USER.Z23B.PROCLIB(SPINSYSL) and added it to USER.Z23B.PARMLIB(VTAMALL) containing these
commands:
• /*$TA WLOG,T=23.58,I=86400,’$VS,''W L'''
• /*$TA WLOG,T=23.59,I=86400,’$P JQ,A>1,Q=PPU,PROTECT’
— If you do not need LOGREC, you can avoid LOGREC messages by changing PARMLIB member
IEASYS** to
• LOGREC=IGNORE,
— Some other SPOOL commands:
• $P JQ,A>1,Q=PPU,PROTECT
• $tbufdef,extbuf=(LIMIT=100)
• $dbufdef
• K Q
• K C,A,123,456 (Deletes within the interval 123-456)
• $PQ
• $DSPL
• $D JQ,SPOOL=(%>5)
• W L

Time
— Twice a year you might want to change time. This is done by updating
• USER.Z23B.PARMLIB(CLOCK00)
— To standard or daylight saving time after IPL
— You can change it immediately from the console or SDSF using
• SET CLOCK=HH.MM.SS
— Set time from Linux
— Unix time zone suggestion for Berlin:
• TZ=CET-1CEST-2,M3.5.0/2,M10.5.0/3
• Handles DST (Until we get rid of it!)
#!/bin/sh
oprmsg 'VARY CN(*),ACTIVATE'
cur_date=`date +"%Y.%j"`
cur_time=`date +"%H.%M.%S"`
oprmsg "SET DATE=$cur_date"
oprmsg "SET CLOCK=$cur_time"

Understanding the USS File System
— zFS
• z/OS File System
— Seen from z/OS
• A linear VSAM file
— Seen from USS
• A hierarchy of directories and files
— Use TSO ISH to display the mount table, to create zFS datasets, and to mount them dynamically
— Save definitions to a PARMLIB(BPXPRM**) member
— Give administrators READ access in RACF to class FACILITY, profile BPX.SUPERUSER

— /u : user home directories (optional). /bin : Essential user command binaries. /usr: Secondary
hierarchy for read-only user data; contains the majority of (multi-)user utilities and applications.
/usr/llp: Repository for installed files. /lib : Essential shared libraries and kernel modules. /opt :
Add-on application software packages. /SYSTEM (e.g. XA02) LPAR-specific. /dev : Device files. /tmp
: Temporary files. /var: Variable files—files whose content is expected to continually change during
normal operation of the system—such as logs, spool files, and temporary e-mail files. /etc : Host-
specific system configuration. /global: Sysplex-wide.
USS File System Hierarchy Standard

JES3
— To use JES3 as the primary job entry subsystem, you must specify JES3 in member IEFSSNxx of
USER.Z23B.PARMLIB
— Modify
• SYS1.IPLPARM(LOADJ3)
• USER.Z23B.PARMLIB(IEASYSJ3)
• USER.Z23B.PARMLIB(IEFSSNJ3)
• USER.Z23B.PROCLIB(JES3)
• USER.Z23B.PARMLIB(JES3INFT)
• USER.Z23B.PARMLIB(JES3IN00)

DB2
— To rename a DB2 subsystem
• Install a separate subsystem and use that instead of the IBM-supplied one
• This includes SMS definitions
— To change code page on a DB2 subsystem
• Change DSNZPARM members DSNHDECM and DSNHMCIM
• DELETE CCSIDS using utility DSNJU003
• Cold start DB2

CICS
— CICS is supplied without log definitions
• You must create them to be able to warm start
• Why?
o Probably because the ADCD distribution is used in many ways
o IBM cannot know whether you will have a coupling facility or use dataset logging
— You need to add RACF security if you need it
— CICSPlex SM is installed, but not configured and activated
— Ports etc. Must be defined for CICS Explorer, if you need them
— Interregion communication requires an entry for CICS in PARMLIB member IEFSSNxx

IMS
— IMS Connect and ODBC are not defined and
not activated
— IMS catalog is not configured
— For IMS SPOC you need to do some work
— To rename an IMS subsystem you must
modify:
• DFSE10.PROCLIB(DFSMPR)
• DFSE10.PROCLIB(IVP1DBCG)
• USER.IMS.JCL(IMSMSG )
• USER.&SYSVER.ISPPLIB(XACTMAIN)
• USER.Z23B.PARMLIB(HWSCFG00)
• USER.Z23B.PARMLIB(PROGAI)
• USER.Z23B.PARMLIB(SHUTALL)
• USER.Z23B.PARMLIB(VTAMALL)
• USER.Z23B.PROCLIB(BCECFGHT)
• USER.Z23B.PROCLIB(CSLDI001)
• USER.Z23B.PROCLIB(CSLOI000)
• USER.Z23B.PROCLIB(DFSDF000)
• USER.Z23B.PROCLIB(DFSMPR)
• USER.Z23B.PROCLIB(HWSEXIT0)
• USER.Z23B.PROCLIB(IMS14CR1 )
• USER.Z23B.PROCLIB(IMS14HWS)
• USER.Z23B.PROCLIB(IMS14ODB)
• USER.Z23B.PROCLIB(IMS14OM1)
• USER.Z23B.PROCLIB(IMS14SCI)
• USER.Z23B.PROCLIB(IMS14RD1)
• USER.Z23B.TCPPARMS(PORTS)

IDz
— You need to change JAVA_HOME in /etc/zexpl/rse.env to an existing Java version, e.g.
/usr/lpp/java/J8.0_64
— Debugger is not configured
— PD Tools are subject to your license conditions
• Consequently not configured, but present in ADCD
— SMP/E environment is incomplete
• Some SMPLOG, SMPPTS and other empty datasets are missing
• Must be defined to apply PTF’s

z/OS MF
— z/OS MF is a Java Liberty application and very CPU-hungry
— Start-up was changed to start at IPL-time at z/OS 2.3
— You might want to move it back again to COMMND** or VTAMALL to start after everything else on
ZD&T
— Change AUTOSTART parameter
— Also remove load at start-up time for some z/OS MF plug-ins to help it start faster
• As kindly adviced by Marna Walle

Don’t Worry – Be Happy!

Where to find more
— Knowledge Center
• https://www.ibm.com/support/knowledgecenter/en/SSTQBD_12.0.2/com.ibm.zdt.overview.gs.doc/topics/c
_product_overview.html
— zPDT Guide and Reference
• http://www.redbooks.ibm.com/redbooks/pdfs/sg248205.pdf
— Mailing list
• z1090@yahoogroups.com
— IBM Z Development and Test Environment Forum
• https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-
000000002283&ps=25

Session Summary
— Provide an overview over ZD&T
• Logical and physical views
— Explain how to run an implementation project
— And which challenges to handle
— Helpful commands and files to check and modify the system
— Any more questions?

Any more Questions for follow-up? Please ask them on the App!
94

Thank you!
Michael Erichsen
Enterprise Modernization Specialist
Xact Consulting, Denmark
Michael.Erichsen@xact.dk
+45 70 23 01 00
www.xact.dk
Linkedin: https://www.linkedin.com/in/michaelerichsen/
Slideshare: https://www.slideshare.net/dsmer/
Youtube: https://www.youtube.com/user/MichaelErichsen
Please complete the Session
Evaluation!
© Copyright Xact Consulting 201995

ZD&T Survival Guide

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie ZD&T Survival Guide

Ähnlich wie ZD&T Survival Guide (20)

Mehr von Michael Erichsen

Mehr von Michael Erichsen (15)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

ZD&T Survival Guide