AD-CD installation
The z System Personal Development Tool program provides z System functionality and associated utility programs. It does not include any z System software. z System software, including operating systems, utilities, middleware, applications, and so forth, must be obtained separately. In practice, the IBM offerings for ISVs (zPDT) or commercial customers (zD&T) might include the z/OS AD-CD package although it is not part of the zPDT program.
For software licensing purposes, a zPDT system is a z System machine and all software licensing requirements that apply to a larger z System installation also apply to a zPDT installation. This statement applies to all z System software from IBM and, we assume, applies to all z System software available from other vendors.
The discussions in this chapter assume that proper licenses have been obtained for the z System software. Licensing arrangements (and associated costs) can be complex topics and are not further addressed in this document.
|
Important: The discussions in the remainder of this document assume the reader has a general familiarity with z/OS systems programming and understands how to access various control data sets. We highlight specific details that might be relevant to zPDT usage and the current AD-CD releases. This is not intended as an introduction to z/OS administration.
Furthermore, we assume basic familiarity with the AD-CD z/OS package. You can find update information about the AD-CD packages at the following website:
|
6.1 General principles
All current IBM z System Operating Systems (assuming proper licenses exist) are supported for zPDT usage, subject to architecture constraints described in “z System characteristics” on page 8. This includes current versions of z/OS, z/VM, and z/VSE. Linux distributions intended for z System use may be used, but all possible functions and configurations have not been extensively tested. Older version might work correctly if they are configured to work with the current z System architecture, which is z14 in the case of zPDT GA9.
6.2 z System operating systems
There are limitations for installing IBM operating systems. These limitations are related to the use of the software media and packaging techniques involved and are not limitations on the use of the operating systems after they are installed.
The most common limitation is for any software that is distributed on tape. To install this software, your zPDT system must have a tape drive, and these are not commonly available for PC machines. Another limitation is related to any z System software that is packaged in such a way that installation requires specific z System HMC functions.
6.2.1 Media
In most cases (when a tape drive is not available) installation media is limited to CD, DVD, and LAN connections. (We can consider FTP as media in this context.) Distributed files must be in formats that can be processed for zPDT. There are two meaningful formats:
•A Linux image of an emulated 3390 drive1 that can be restored in the 3390 format used by zPDT. The image might be compressed (using gzip, for example) and would need to be uncompressed before use with zPDT. Likewise, the image might be in .tar files and would need to be extracted (and possibly uncompressed) before being used with zPDT.
The 3390 drive image format must be produced by another zPDT system, because no other product uses the same 3390 image format that is used by zPDT. Whatever preliminary unpacking or uncompression is needed must be done by Linux utilities before the 3390 image can be used by a z System operating system.
•A tape image in awstape format. Such images appear as “real” tape volumes to z System Operating Systems operating on zPDT, and can be processed as such by using emulated tape drives. The tape might contain product installation material (in SMP/E format, for example), an ADRDSSU dump of a disk volume, or any other tape data usable by z System programs.
Another media option is to FTP a product (or other data) directly to z/OS. Some z System software is distributed in this format. zPDT must have a running z/OS and LAN connection to use this method. (Most of our discussion is for z/OS, but z/VM, z/VSE, or Linux for z Systems might be used in the same way. The point is that a working z System operating system must be installed before additional software can be sent directly to it through FTP.)
Differentiating the handling of these methods is important:
•CDs and DVDs must be processed by Linux programs (unless they contain awstape files).
•awstape files must be processed by z/OS (or another z System operating system), although the transport of awstape files can be managed by Linux through CD/DVDs, USB memory keys, or FTP.
•Direct FTPs to z/OS might be in other formats, for example in formats suitable for processing by SMP/E or the TSO XMIT command. In any event, these are z System formats and not Linux formats.
•An emulated 3390 volume (after decompression, if necessary) is a large Linux file that is meaningful only to z System software.
6.3 Installing a z/OS AD-CD system
The following examples use volsers (volume serial numbers) corresponding to the z/OS 2.3 (May 2018) release of the AD-CD system. These volsers tend to change in a standard pattern for new releases.
The IPL volume(s) in recent z/OS AD-CD releases are encrypted. The two “IPLable” volumes are usually xxRES1 and SARES1, where “xx” changes with each z/OS AD-CD update. These must be installed using the Z1090_ADCD_install or the Z1091_ADCD_install command. These commands decrypt the volumes and assist in implementing a signature technique that identifies the customer installing the volume.2
6.3.1 Specific installation instructions
There are multiple download files for current z/OS AD-CD releases, one file for each emulated 3390 volume. Documentation with each AD-CD release contains specific information about the volumes needed for that release.
Volumes other than IPL volumes are all in simple gzip format. AD-CD system installation might be as follows, assuming our target directory for emulated 3390 volumes is /z:
(We assume you are working as userid ibmsys1)
$ cd /tmp (or wherever you stored the downloads)
$ Z1090_ADCD_install c3res1.zPDT /z/C3RES1 (decrypt IPL volume)
$ gunzip -c c3res2.gz > /z/C3RES2 (unzip other volumes)
$ gunzip -c c3uss1.gz > /z/C3USS1
$ gunzip -c c3sys1.gz > /z/C3SYS1
And so forth for all the volumes to be installed.
Use the Z1091_ADCD_install command instead of Z1090_ADCD_install if appropriate.
Notice that the suffix of the file name for a distributed IPL volume is now .zPDT or .ZPDT instead of .gz. The distributed file is encrypted and compressed; it is automatically expanded as part of the Z1090_ADCD_install processing.
The files containing emulated volumes (and the directory containing these files) must have read and write permissions for the userid running zPDT. Assuming use of the ibmsys1 userid, we suggest that all such files and their directories (/z, in our examples) be owned by ibmsys1.
File name considerations
An emulated 3390 volume exists in a single Linux file. For example, a 3390-9 volume exists as a 8.5 GB Linux file. A 3390 volume has a volser that is written in the first track of the 3390 volume.3 The Linux file holding the (emulated) 3390 volume has a Linux file name, which is specified in a devmap. There is no required relationship between the volser and the Linux file name. For example, volser WORK02 might be in /tmp/mysys/ckd001.
In all our examples, we elected to use the volser of the 3390 volume as the Linux file name that holds the volume. We use uppercase letters simply to make these emulated volume file names more distinctive. There is no requirement to use the volser as the Linux file name, and there is no requirement to use uppercase names.
We strongly suggest that you make the Linux file name reflect the volser, if at all possible. For example, volser WORK02 might be in /z/mysys/WORK02 or /z/mysys/WORK02.ckd. A Linux naming convention that reflects the volser can avoid wasted debugging time.
6.3.2 IODF device numbers
We must know the device numbers (commonly known as addresses) used by the z/OS system. (These may be changed after the z/OS system is installed. Changing involves creating a new IODF data set, new IPLPARM member or members, and IPL of z/OS again.) Most users of the AD-CD system accept the device numbers in the IODF supplied with the AD-CD system. These are listed here:
ADDRESS DEVICE Purpose
00C 2540R Card reader. Useful as an emulated device.
00E -00F 1403-N1 Line printers. Useful as an emulated device.
120-15F 3380 Disks . (Control units defined for 120-127)
300-318 3390 3390 disks
400-40F OSA OSA
550-55F 3420 Round tape drives
560-56F 3480 Without COMPACT feature
580-58F 3490 Tape drives
590-59F 3590 Tape drives
600-60F 3990 Disks
700 3270 Terminal. AD-CD systems use as NIP & z/OS master console
701-73F 3277 Terminal. Normally for VTAM (TSO, CICS, etc)
900-910 3277 Terminal. Normally for VTAM (TSO, CICS, etc)
908 3270 Could be used as a z/OS console
909-91F 3277 Terminal. Normally for VTAM (TSO, CICS, etc)
A80-AFF 3390 Disks
E20-E23 CTC 3172s or CTC devices
E40-E43 CTC 3172s or CTC devices
1A00-1AFF 3390 Disks
2A00-2AFF 3390 Disks
3A00-3AFF 3390 Disks
Most of the addresses are three hex digits, due to historical reasons. Both the AD-CD z/OS system and zPDT system can work with four-digit addresses. These addresses have been stable for many releases of the z/OS AD-CD system; however, it is possible they might change in future releases.
In principle the 3390 IPL volume, for example, could be mounted at any address defined as a 3390. By AD-CD convention, the IPL volume and the volume containing the IODF and other key data sets are usually mounted at addresses A80 and A82:
VOLSER ADDRESS Purpose
C3RES1 A80 IPL volume and key z/OS libraries
C3SYS1 A82 Spool space, LOGGER data sets, VSAM, etc
The A80 and A82 addresses are used in AD-CD documentation examples, but there is no requirement to use specific addresses. The other volumes can be mounted at any convenient address that is defined in the IODF as a 3390. In practice, many users simply start at address A80 and increment it sequentially for each additional volume.
6.3.3 zPDT control files
Before the AD-CD system can be used, an appropriate devmap must be created. A basic example is shown here:
$ cd /home/ibmsys1
$ gedit aprof2 3 (this is an arbitrary file name)
[system]
memory 9000m # define 9000 MB z System
processors 1 # use 2 or 3, if appropriate
3270port 3270 # port number for TN3270 connections
[manager]
name aws3274 0002 # define a few 3270 terminals
device 0700 3279 3274
device 0701 3279 3274
device 0702 3279 3274
device 0703 3279 3274
device 0704 3279 3274
[manager]
name awsckd 0001
device 0a80 3390 3990 /z/C3RES1 # (The “C3” prefix is for the
device 0a81 3390 3990 /z/C3RES2 # z/OS AD-CD released in December
device 0a82 3390 3990 /z/C3SYS1 # 2018. Later releases will have a
device 0a83 3390 3990 /z/C3CFG1 # different prefix)
device 0a84 3390 3990 /z/C3USS1
device 0a85 3390 3990 /z/C3USS2
device 0a86 3390 3990 /z/C3PRD1
device 0a87 3390 3990 /z/C3PRD2
device 0a88 3390 3990 /z/C3PRD3
device 0a89 3390 3990 /z/C3PAGA
device 0a8a 3390 3990 /z/C3PAGB
device 0a8b 3390 3990 /z/C3PAGC
device 0a8c 3390 3990 /z/C3USR1
#(continue with whatever additional volumes you installed.)
Gaps in the assigned address numbers do not create a problem. The devmap can have any name and be placed in any directory. It is best if it is in the directory you will use when starting zPDT so that you do not need to enter a full path name when using it.
We suggest you do not define OSA devices for your initial z/OS startup. The OSA definitions can be a little more complex and we suggest you verify that your basic z/OS system is operational first.
6.3.4 IPL and operation
Start zPDT with an awsstart command. Among other functions this starts the zPDT device manager that emulates local, channel-attached 3270 terminals. Using the awsstart command creates a z1090 subdirectory in the current home directory (if it does not already exist) and several zPDT-related directories below it.
$ cd /home/ibmsys1
$ awsstart aprof2 (use your devmap name)
(wait for messages. Press Enter to regain the $ prompt.)
AWSSTA014I Map file name specified: aprof22
0 Snapdump incident(s), RAS trace and RAS log files occupy 657046 bytes
in /home/ibmsys1/z1090/logs.
Associated files, logs, and core files occupy 10364 bytes in
/home/ibmsys1/z1090/logs
Using the same Linux window (or a different window, if you prefer), start at least two local 3270 sessions:4
$ x3270 -port 3270 localhost &
$ x3270 -port 3270 localhost &
$ x3270 localhost:3270 & (another way to specify a port number)
Consider the following information:
•x3270 is the name of the program.
•In the devmap we assigned Linux TCP/IP port 3270 for this function. The port number is arbitrary, but should not be used for any other purpose in your system. Port 3270 is usually a good choice and is easy to remember.
•We want to connect to our own Linux system; this is indicated by the localhost operand.
•The ampersand (&) causes the x3270 program to execute in the background, leaving the Linux window free for additional commands. We can recall and execute the x3270 command repeatedly to create multiple 3270 sessions.
The 3270 window displays identification lines if there has been no data sent to it by the z System software. These lines indicate the terminal identity by address and LUname or IP address. A number of options are available for working with these LUnames and these are discussed in 3.3.3, “The aws3274 device manager” on page 46. The File and Options menus at the top of the x3270 window can be used for a variety of functions. Changing the font size (using the Options menu) has the effect of changing the 3270 window size.
The 3270 session for the z/OS console (address 700 for the AD-CD system) should be ready before z/OS IPL. Next, issue the appropriate IPL command in the Linux window:5
$ ipl a80 parm 0a82cs
After a few seconds, the initial z/OS messages appear on the 3270 session at address 700. During the first IPL of the AD-CD system (or an IPL after a long period of non-use, or a changed z System serial number) you might see messages similar to this one:
IXC420D REPLY I TO INITIALIZE SYSPLEX ADCDPL, OR R TO REINITIALIZE XCF
If this message is issued, go to the 3270 session displaying the message and enter the following command:
r 00,i
After VTAM is started, the VTAM logo should display on the other 3270 sessions.6
There is usually some documentation for each AD-CD release that provides details about different IPL parameters and TSO logon procedures. A brief summary for a recent z/OS AD-CD system is shown here:
IPLparm LogonProcedure Purpose
0A82CS ISPFPROC Basic IPL without DB2, etc. Cold start JES2.
0A8200 ISPFPROC Subsequent basic IPLs. Warm start JES2
0A82DC DBSPROCB Initial IPL for DB2 V12, etc
User IBMUSER is always present on z/OS and is typically used for initial TSO logons. The initial password for IBMUSER should be published with the AD-CD documentation. It is typically SYS1 or IBMUSER. If there are security concerns about your system, change this initial password as soon as possible.
The distributed logon procedures change with various AD-CD releases. The procedures are in the ADCD PROCLIB data set.
The Linux command window that was used for the awsstart command should be kept open, if possible. Asynchronous messages from zPDT are sent to this window. You can enter zPDT commands from other windows, but it is possible that you might miss significant messages that are sent to the original window.
6.3.5 Shutting down
z/OS should be shut down cleanly, if possible. Enter the s shutdown7 command at the z/OS console and reply to any messages produced. The message ALL FUNCTIONS COMPLETE indicates that JES2 can now be stopped with the command $PJES2. After JES2 ends, System z operation can be stopped. The zPDT system is stopped with this command in the Linux window:
$ awsstop
This produces several messages. It might be necessary to press Enter to obtain the Linux prompt. Any 3270 windows may be closed at this point.
6.3.6 Startup messages
Messages such as the following are produced by the awsstart command:
AWSSTA014I Map file name specified: aprofa2
0 Snapdump incident(s), RAS trace and RAS log files occupy 657046 bytes
in /home/ibmsys1/z1090/logs
Associated files, logs, and core files occupy 10364 bytes in
/home/ibmsys1/z1090/logs
Glance at these messages, because SNAP dump incidents are indications of an internal zPDT error, and if you want to work with your zPDT support, you will need this data. The number of bytes used for various logs and dumps is usually not significant unless it becomes too large. In general, zPDT manages these files automatically. However, if the numbers displayed become too large (many megabytes) and if you are not actively working on a problem with your zPDT support organization, you might want to clean up these files. To do this, add the --clean option the next time you issue an awsstart command:
$ awsstart aprof11 --clean
You can get the --clean behavior every time by setting a Linux shell environment variable Z1090_CLEAN=YES; however, we do not suggest doing this because it might easily result in the removal of important debugging information in the event of a zPDT failure.
6.3.7 Local volumes
For our examples, we created a Linux partition mounted at /z. The process for adding your own 3390 volumes is outlined here:
1. Create the emulated 3390 volume using a zPDT utility:
$ alcckd /z/WORK01 -d3390-3 (assuming you want a 3390-3 volume)
2. Update the devmap to include the new volume. (Assume address AA0 for this example.)
[manager]
name awsckd 0001
...
device AA0 3390 3990 /z/WORK01
3. Restart zPDT with the updated devmap.
4. IPL z/OS with the new volume present. z/OS will detect an uninitialized volume and vary it offline.
5. Create and run an ICKDSF job to initialize the volume:
//BILLX JOB 1,OGDEN,MSGCLASS=X
// EXEC PGM=ICKDSF,REGION=1M
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
INIT UNIT(AA0) NOVERIFY VOLID(WORK01) VTOC(0,1,14)
/*
6. Vary the new volume online and begin using it:
VARY AA0,ONLINE (on the z/OS console)
6.4 Multiple operating systems
We can install multiple z System Operating Systems, limited only by the disk space we have available. Every emulated 3390-3 volume uses approximately 2.8 GB of disk space and 3390-9 volumes use about 8.6 GB.
It is important to distinguish between installing additional emulated 3390 volumes (perhaps with a variety of operating systems), and using the volumes. We can, of course, only IPL a single system at any one time in a zPDT instance.8 The volumes that might be “seen” by that system depend on several factors:
•Does the current devmap contain all the desired volumes?
You can have multiple devmaps, each with a different selection of emulated volumes and assigned addresses, but we can have only one devmap specified when we start a zPDT instance. You cannot change the active devmap while zPDT is running.9 (You can change the devmap file after zPDT is started, but this file change has no effect on the running zPDT.)
•Do the device addresses in the devmap match suitable addresses in the IODF of the z/OS system?
For example, if one of the emulated 3390 volumes is assigned address 190 (in the devmap), then the default z/OS AD-CD IODF would not “see” the volume because this address is not in the IODF. (z/VM does not have predefined addresses for various device types, making this aspect of z/VM easier to use.)
•Duplicate disk volsers may not be present.
You may have duplicate volsers for emulated volumes on your PC disk, but the duplicates should not be present in a given devmap.
•It might not be possible to use the common addresses typically associated with an operating system.
For example, all the AD-CD documentation uses A80 as the IPL address for a z/OS AD-CD system. We can have two (or more) AD-CD systems represented in the devmap at the same time, but only one volume can have address A80 during any single execution of zPDT. This does not prevent us from IPLing any of the (multiple) AD-CD systems present, but we need to specify the correct address. An example might make this clearer:
Address VOLSER Purpose
A80 ZCRES1 IPL volume for z/OS 1.12 AD-CD system
A81 ZCRES2 Libraries for z/OS 1.12 AD-CD system
A82 ZCSYS1 Paging, spooling, VSAM for 1.12 AD-CD system
...
A90 SBRES1 IPL volume for z/OS 1.11S AD-CD system
A91 SBRES2 Libraries for z/OS 1.11S AD-CD system
A92 SBSYS1 Paging, spooling, VSAM for 1.11S AD-CD system
...
Assuming our devmap is configured for these addresses, we can ipl A80 parm 0A82CS to run the 1.12 system or we can ipl A90 parm 0A92CS to run the 1.11S system.10 In either case, the running z/OS system can access all the volumes of both z/OS systems. This is convenient for migration purposes. The volumes are readdressed by simply changing the addresses in the devmap.
We can run multiple z System Operating Systems at the same time by starting multiple zPDT instances, but this requires more resources (especially PC memory).
1 3380 images could also be used, but we ignore these here.
2 z/OS AD-CD releases prior to z/OS 2.1 were not encrypted. z/OS AD-CD releases starting with z/OS 2.1 have encrypted IPL volumes. To decrypt these you must have zPDT release GA5 or later and you must have a token license file that contains the proper license to enable decryption. The proper license files are distributed in .zip format. If you have earlier software (before z/OS 2.1 or before zPDT GA5) you should refer to earlier editions of this document.
3 The volser is written by the ICKDSF utility program (for a new volume), or is already present in a volume that was downloaded or taken from a DVD.
4 These instructions assume you have x3270 installed and are using it on the same PC that is running zPDT.
5 This example assumes you have mounted the IPL volume at address A80 and the volume containing the IODF and IPL parameters at address A82. By AD-CD convention, the “cs” IPL parameter causes a JES2 cold start.
6 If the 3270 session displays a message Unsupported Function, simply use the 3270 Clear key to obtain the initial VTAM display. Some TN3270e emulators encounter this initial message and others do not.
7 This shutdown command is not a standard z/OS function; additional command names might be present. These trigger VTAMAPPL scripts to issue various commands involved in stopping z/OS.
8 This statement ignores the possibility of running multiple z/OS guests under z/VM.
9 This is not completely true. We can change the volume mounted on an emulated disk drive or tape drive with the awsmount command.
10 Yes, we know these levels of z/OS are ancient and do not work on current zPDT system, but they illustrate the point being made.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.