OS/390 DEMOpkg Installation Guide
The OS/390 DEMOpkg Installation Guide
describes the installation of the
OS/390 DEMOpkg System for the
PC Server S/390 platform (P/390 and R/390) and for the
CMOS S/390 platform.
The OS/390 DEMOpkg System resides on
twelve DASD volumes:
- The required Base Volumes contain:
| DASD Volume |
Description |
|---|
| DMTRES |
Base operating system products |
| DMTCAT |
Master catalog, page, spool, IODF |
| DMTOS1 |
Additional Base products |
| DMTOS2 |
Additional Base products |
| DMTOS3 |
Additional Base products |
- The optional Data Management Volumes contain:
| DASD Volume |
Description |
|---|
| DMTD01 |
Database, Transaction Processing, and Application Development
products |
| DMTD02 |
Additional Data Management products |
| DMTD03 |
Additional Data Management products |
| DMTD04 |
Additional Data Management products |
- The optional Tivoli Volumes contain:
| DASD Volume |
Description |
|---|
| DMTP01 |
Tivoli products |
| DMTP02 |
Additional Tivoli products |
| DMTP03 |
Additional Tivoli products |
The following publications contain helpful information on the PC Server/390:
- Connectivity on a PC Server System/390, SG24-4624
- MVS and the IBM PC Server 500 System/390, GG24-253
We are interested in your suggestions and comments. Access our DEMOcentral Web site and give us your
feedback.
| Important |
|---|
|
Make sure you have installed the required hardware and software
for the PC Server S/390 or RS/6000 S/390
machine according to the instructions that are delivered
with the machine. You may want to read the ITSO publication
P/390 and R/390 with OS/390: An Introduction (PDF).
|
P/390 and R/390 Requirements
- A PC Server 5xx S/390, a
RS/6000 with S/390 Server On Board, or
a CMOS S/390 CPU
- Server must have at least the PC Server
S/390 Release 2.1 programs or the RS/6000
S/390 Release 4.1.0.1 programs installed
- At least 24GB of disk storage, if
loading all products
When installing under AIX, the free disk space must be contained
on completely unused physical disk drives or a
RAID-5 array. The
install program automatically defines a new volume group and file
system to hold the OS/390 files.
- If you intend to run the OS/390 DEMOpkg system under VM/ESA,
refer to VM System Definitions
CMOS Requirements
- IBM S/390 processor running in ESA mode
- At least twelve 3390 Model 2 DASD devices
- Two 3490 tape drives
- A non-SNA 3270 device for the master console
- If you intend to run the OS/390 DEMOpkg system native in an LPAR,
refer to I/O Definition File Customization
- If you intend to run the OS/390 DEMOpkg system under VM/ESA,
refer to VM System Definitions
P/390 Requirements
- OS/2 Warp and Communications
Manager/2 (or Personal Communications) must be installed and operational before the
OS/390 DEMOpkg System can be installed
- The P/390
support programs and Licensed Internal Code must be installed before
running the DEMOpkg INSTALL command
R/390 Requirements
- AIX Version 4.1 (or later)
must be installed and operational before the
OS/390 DEMOpkg System can be installed
- A 3270 Terminal Emulator, such as the
Host Connection Program (HCON) facility or another 3270
terminal emulator product, must be installed to provide support
for 3270 terminal sessions
- The P/390
support programs and Licensed Internal Code must be installed before
performing the DEMOpkg installation
- Apply the latest patches and install images to the R/390 to
resolve an incompatibility between TCP/IP and the R/390
The patches and install images can be found at the following FTP site:
ftp://p390.ibm.com.
This is anonymous FTP site is for R/390 customers and service providers.
CMOS Requirements
- A driver OS/390 Version 2 or later system
must be installed and operational before the
OS/390 DEMOpkg System can be installed
- A stand-alone DFDSS restore environment must exist for first-time installations with
the proper CPU and I/O equipment installed and
correctly configured
The OS/390 DEMOpkg System is a complete replacement of previous
releases.
Before you
install this system,
any local customization and local data sets
that reside on your current DEMOpkg System must be preserved.
Some options for isolating local changes include:
- Keeping all local and user data sets on seperate volumes,
which includes a local usercatalog.
- Keeping all local tailoring and jobs in a
separate data set, which
is backed up before a new DEMOpkg System is installed.
For
information on backing up local changes and data sets, refer to
Migration Aids in the
OS/390 DEMOpkg Systems Reference Guide.
P/390 Requirements
Before you IPL the OS/390 System,
you need to
verify that the local
3270 sessions are correctly configured.
In order for a 3270
session to be used by the OS/390 System,
it must be configured as a local session.
The first five CM/2 3270
sessions should be configured for the OS/390,
unless the PC Server S/390 machine is also being used to
connect to other host machines.
To verify the current configuration, complete the following steps:
- To display the configuration of each CM/2 session,
Enter
from an OS/2 command prompt:
=> AWSCMLT
The 3270 non-SNA LT Options window appears.
- If the sessions are to be used for the OS/390 Master
Console or for TSO, make sure the
LT TYPE column value is LOCAL
- To activate any changes,
shutdown and restart CM/2
R/390 Requirements
Before you IPL the OS/390 System,
you need to
verify that the local
3270 sessions are correctly configured.
To verify the current configuration, complete the following steps:
- Ensure your 3270 emulation software is configured properly
There must be at least two sessions defined for the user root.
Sessions A and B should be configured
as TCP/IP sessions.
- To start the
configuration utility program (HCON), Enter:
=> smit hcon
- Add a unique R/390 port address
to the TCP/IP services for HCON
Add a service to TCP/IP with the
attributes:
|
Official Internet Service Name: |
hcon | |
Transport protocol: |
tcp | |
Socket Port Number: |
3046 |
CMOS Requirements
Before you IPL the OS/390 System,
you need to verify the following:
- Master Console Address: 463
- DASD Volumes: (1C0,16), (300,16), (600, 16)
- Tape Volumes: (350,16), (370,16), (A20,16)
| Important |
|---|
|
Before performing the installation, you need to terminate the
P/390 System. To terminate the system,
open the P/390 folder
and then double-click on the End P/390 icon.
The OS/390 DEMOpkg System installation procedure
verifies the P/390 has
been terminated before it performs the installation.
|
To install the OS/390 DEMOpkg System, complete the
following steps:
- Insert the DEMOpkg OS/390 Installation
Volume 1 CD-ROM into the CD-ROM drive
- Open an OS/2 full screen session
- At the C: prompt, Enter:
=> x:INSTALL
where x: is the drive letter of the
CD-ROM
drive.
The INSTALL command will:
- Copy the file from the installation
CD-ROMs to the MVS directory of the specified
disk.
The MVS directory
is created if it did not previously exist.
The file that is installed is a P/390 device map.
The device map contains all device
definitions and IPL parameters
required to operate the distributed
OS/390 System.
It will be the active P/390 device map after
the installation is complete.
- Automatically
adjust the OS/2 disk drive letter in the device map
file paths to match the disk being used for the DASD files.
- UNZIP simulated 3390 DASD
volumes from the CD-ROMs.
This process takes about two hours.
- When prompted, Enter the OS/2
drive letter
of the input CD-ROM and the output disk drive
The output disk drive contains
the simulated
DASD devices. The input
drive letter defaults to the drive containing the INSTALL
command
and the output drive defaults
to D:.
The installation of each CD-ROM takes about twenty-five minutes.
- Insert the DEMOpkg OS/390 Installation Volume 2
CD-ROM into the CD-ROM drive when requested
- Insert the DEMOpkg OS/390 Installation Volume 3
CD-ROM into the CD-ROM drive when requested
- Insert the DEMOpkg OS/390 Installation Volume 4
CD-ROM into the CD-ROM drive when requested
- Insert the DEMOpkg OS/390 Installation Volume 5
CD-ROM into the CD-ROM drive when requested
The messages, prompts, and responses of the
INSTALL command are
placed into the OS390.LOG file in the root directory of
the output disk. The file may be reviewed at any time to determine
what processing was performed by the INSTALL command.
Unzipping the Data Management Volumes
Note: These volumes are optional.
To unzip the volumes, do the following:
- Insert the Data Management CD
- Change to the directory where OS/390 resides (for example: D:\MVS)
- Enter the command:
=> x:unzip -j x:\mvs\fname.zip
where x is the drive letter of the CD-ROM drive and
fname is either DMTD01, DMTD02 DMTD03
or DMTD04.
- Make sure to update the device map to
reflect the new volumes
- Run the MVSCUST job to connect the
catalogs
Unzipping the Tivoli Volumes
Note: These volumes are optional.
To unzip the volumes, do the following:
- Insert the Tivoli CD
- Change to the directory where OS/390 resides (for example: D:\MVS)
- Enter the command:
=> x:unzip -j x:\mvs\fname.zip
where x is the drive letter of the CD-ROM drive and
fname is either DMTP01, DMTP02 or DMTP03.
- Make sure to update the device map to
reflect the new volumes
- Run the MVSCUST job to connect the
catalogs
|
Attention! |
To resolve a problem in the R/390 device map and this OS/390 DEMOpkg release, the latest
R/390 patches must be installed. Find the patches and install images at the following
FTP site:
ftp://p390.ibm.com. This anonymous FTP site is for R/390 customers and service providers. |
To install the OS/390 DEMOpkg System, complete the
following steps:
- Insert the DEMOpkg OS/390 Installation
Volume 1 CD-ROM into the CD-ROM drive
- Open an AIX window
- To copy the installation program from the first
CD-ROM into
the /tmp directory, Enter:
=> mount /cdrom
=> cp /cdrom/aix/insos390 /tmp
=> umount /cdrom
- To change to the /tmp directory, Enter:
=> cd /tmp
- To execute the installation program, Enter:
=> ./insos390
The insos390 command will:
- Create a Volume Group named OS390.
- Create a File System named MVS.
- Copy the file from the installation
CD-ROMs to the MVS directory of the
OS390 File System.
The file that is installed is a P/390 device map.
The device map contains all device
definitions and IPL parameters
required to operate the distributed
OS/390 System.
- UNZIP simulated 3390 DASD
volumes from the CD-ROMs.
This process takes about two hours.
- Follow the directions printed on the screen
- Insert the DEMOpkg OS/390 Installation Volume 2
through Volume 5 CD-ROMs when prompted
After the total disk space requirement has been determined
and verified, each CD-ROM is installed in reverse
sequence.
- Insert the DEMOpkg OS/390 Installation Volume 4
CD-ROM when prompted
- Insert the DEMOpkg OS/390 Installation Volume 3
CD-ROM when prompted
- Insert the DEMOpkg OS/390 Installation Volume 2
CD-ROM when prompted
- Insert the DEMOpkg OS/390 Installation Volume 1
CD-ROM when prompted
Each CD takes 20 minutes to install.
Unzipping the Data Management Volumes
Note: These volumes are optional.
To unzip the volumes, do the following:
- Enter mount /cdrom
- Switch to the directory that contains the volumes
For example, Enter: cd /os390/mvs
- Unzip the CD-ROM:
=> /usr/bin/r390/unzip -oj /cdrom/mvs/dmtd01.zip
=> /usr/bin/r390/unzip -oj /cdrom/mvs/dmtd02.zip
=> /usr/bin/r390/unzip -oj /cdrom/mvs/dmtd03.zip
=> /usr/bin/r390/unzip -oj /cdrom/mvs/dmtd04.zip
- Make sure to update the device map to
reflect the new volumes
- Run the MVSCUST job to connect the
catalogs
Unzipping the Tivoli Volumes
Note: These volumes are optional.
To unzip the volumes, do the following:
- Enter mount /cdrom
- Switch to the directory that contains the volumes
For example, Enter: cd /os390/mvs
- Unzip the CD-ROM:
=> /usr/bin/r390/unzip -oj /cdrom/mvs/dmtp01.zip
=> /usr/bin/r390/unzip -oj /cdrom/mvs/dmtp02.zip
=> /usr/bin/r390/unzip -oj /cdrom/mvs/dmtp03.zip
- Make sure to update the device map to
reflect the new volumes
- Run the MVSCUST job to connect the
catalogs
To install the OS/390 DEMOpkg System, do the following:
- Initialize the DASD volumes
Each of the DASD volumes must be pre-initialized
using ICKDSF and must be in a 3390-2 format.
- If restoring from a running system, use batch DFSMS-dss jobs to
restore the tapes to your selected volumes.
The CMOS tapes are delivered as standard label full volume dfdss dump tapes.
|
VOLUME |
VOLSER |
DATASET NAME |
|
DMTRES |
RES001 |
BACKUP.DMTRES |
|
DMTCAT |
CAT001 |
BACKUP.DMTCAT |
|
DMTOS1 |
OS1001 |
BACKUP.DMTOS1 |
|
DMTOS2 |
OS2001 |
BACKUP.DMTOS2 |
|
DMTOS3 |
OS3001 |
BACKUP.DMTOS3 |
|
DMTD01 |
D01001 |
BACKUP.DMTD01 |
|
DMTD02 |
D02001 |
BACKUP.DMTD02 |
|
DMTD03 |
D03001 |
BACKUP.DMTD03 |
|
DMTD04 |
D04001 |
BACKUP.DMTD04 |
|
DMTP01 |
P01001 |
BACKUP.DMTP01 |
|
DMTP02 |
P02001 |
BACKUP.DMTP02 |
|
DMTP03 |
P03001 |
BACKUP.DMTP03 |
The following is a sample job:
//RESTVOL JOB CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1),
// NOTIFY=&SYSUID
//***********************************************************
//* RESTORE OF PHYSICAL DUMP
//***********************************************************
//RESTORE EXEC PGM=ADRDSSU,REGION=0M
//SYSPRINT DD SYSOUT=*
//TAPE DD DISP=SHR,DSN=DMTRES.BACKUP,
// VOL=SER=(RES001),
// UNIT=/0366,
// LABEL=(1,SL)
//DASD DD DISP=SHR,UNIT=3390,VOL=SER=DMTRES
//SYSIN DD *
RESTORE INDD(TAPE) -
OUTDD(DASD) -
ADMIN
/*
- If restoring in stand-alone mode, you must IPL the DFSMS-dss IPL tape
to restore the tapes to your selected volumes
An EXTERNAL INTERRUPT
is required to switch to the second tape if one exists.
Under VM, a virtual EXT (#CP EXT) is required.
Each of the DASD volumes must be restored
using DFSMS-dss. The volumes are in FULL-DUMP format.
- Mount the DFSMSdss IPL tape on a tape drive
- Mount the first tape volume,
for the DASD volume being restored,
onto a second tape drive
- IPL the stand-alone DFSMSdss program
tape using either:
- The hardware console, or
- If under VM, Enter the #CP IPL command
After a few minutes the system enters a wait state by displaying
PSW:0000FFFF on the screen. At that time, the
program is waiting for an interrupt from a console device.
- On an attached 3270 terminal, press (Enter)
The terminal becomes the DFSMSdss console.
- Enter the following commands from the console:
All commands except for the first must be
entered in position two of the command line. This example is for
DFDSS-dss V1R4 and above:
=> console
=> console
=> restore fromdev(tape),fromaddr(ttt),toaddr(ccc),noverify
=> Y
where ttt is the device number of the input tape,
ccc is the output DASD device address
To start the P/390 System and IPL OS/390, do the following:
- Open the P/390 folder
- Double-click on the IPL P/390 icon
If all of the CM/2 sessions are
defined as local
sessions, the OS/390 Master Console
will appear in session D.
Otherwise, the Master Console is assigned to one of the
other sessions. The session name of the assigned window
will change to OS/390 Master Console.
The first response required is for JES2.
- Before using the Data Management or Tivoli products, you must IPL with the following parameters:
|
LOAD ADDRESS: |
01C0 | |
LOAD PARM: |
01C1DP.1 | |
|
- When the $HASP426 SPECIFY OPTIONS message appears,
Enter the following to cold start JES2:
=> xx COLD,NOREQ
where xx is the
reply ID of the console prompt.
Note: If the $HASP454 message appears, Enter
a response of Y.
No additional responses are required.
To start the R/390 System and IPL OS/390,
perform the following:
- To ensure the proper device map is used, Enter:
=> export CONFIG_FILE=/os390/mvs/devmap.mvs
- Change to the root directory and then Enter:
=> r390 &
The R/390 menu appears.
- Click on the IPL P/390 icon
Two 3270 sessions are started by the IPL process.
One will be used as the Master Console and the other may be used for TSO.
- Before using the Data Management or Tivoli products, you must IPL with the following parameters:
|
LOAD ADDRESS: |
01C0 | |
LOAD PARM: |
01C1DP.1 | |
|
- When the $HASP426 SPECIFY OPTIONS message appears,
Enter the following to cold start JES2:
=> xx COLD,NOREQ
where xx is the
reply ID of the console prompt.
Note: If the $HASP454 message appears, Enter
a response of Y.
No additional responses are required.
To IPL the OS/390 DEMOpkg System on a CMOS processor, do the following:
- Select the IPL option
- Before using the Data Management or Tivoli products, you must IPL with the following parameters:
|
LOAD ADDRESS: |
01C0 | |
LOAD PARM: |
01C1DP.1 | |
|
- When the $HASP426 SPECIFY OPTIONS message appears,
Enter the following to cold start JES2:
=> xx COLD,NOREQ
where xx is the
reply ID of the console prompt.
Note: If the $HASP454 message appears, Enter
a response of Y.
No additional responses are required.
To customize the OS/390 DEMOpkg System, complete the following steps:
- To logon to TSO, Enter:
=> TSO SYSPRG1 (password: sysprg1)
The ISPF Primary Option Menu appears.
- Enter the OS/390 Customization Dialog
command:
=> TSO MVSCUST
- Enter the values to be used for your location
For additional information about the fields, press (PF1).
- If you are installing the optional Data Management, Tivoli, or DLIB volumes, Enter Y
This will run the catalog connect jobs required to use them.
| Important |
|---|
|
If you wish to use the Data Management or Tivoli volumes, you need to verify that the catalog batch jobs have run and
completed with a return code of 0. These jobs impact the user catalogs and define the product aliases.
|
- When all information is correct, press
(Enter)
You will see several automatic updates being performed.
- Edit the TCP/IP configuration files:
- Edit the files with the
correct values for your IP network
- Verify several
initialization options
- Make changes to the files
if your address is a CLASS A/B/C account
Once you have completed the manual edit of the TCP/IP configuration
files, a batch job is submitted that completes the customization.
- To exit, press (PF3)
- Update the Web Server configuration file to
specify your HostName IP address:
- Enter oedit /etc/httpd.conf
- Update the HostName value to match your local IP address
- To exit, press (PF3)
The local customization values are not be effective until the
system is IPLed. To prepare for the IPL, you
need to
shutdown the OS/390
System.
To shutdown the system, do the following:
- From the
system console, Enter:
=> START SHUTDWN
After several minutes and many messages, the
ALL AVAILABLE FUNCTIONS COMPLETE message appears.
- To terminate JES2, Enter:
=> $PJES2
If JES2 does not terminate and ALL tasks are down, you can
issue the $PJES2,ABEND JES2 shutdown command and then
reply r xx,END.
- To terminate the P/390 or R390
open the P/390 folder and then double-click
on the End P/390 icon
To make the local customization values effective,
the customized OS/390 System needs to be
re-IPLed.
IPL Options
| If you run only the Base volumes, specify: | LOADPARM=01C1DP.1 |
| If you also run the Data Management volumes, specify: | LOADPARM=01C1DM.1 |
| If you also run the Tivoli volumes, specify: | LOADPARM=01C100.1 |
The TSO administration user IDs you can use are:
|
SYSPRG1 |
Systems programmer ID.
Fully authorized in RACF, SMS and others. Perform system programming tasks
that require a high level of authorization. | |
SYSADM1 | |
System administrator ID. | |
SYSOPR1 | |
System operator ID. | |
DB2ADM |
DB2 administrator ID. | |
DOMADM |
Lotus Domino/390 administrator ID. | |
BPXROOT |
OE administrator ID. | |
WEBADM |
Web Server administrator ID. | |
DCEADM |
DCE Server administrator ID. | |
SYSUSR1 |
End user ID. |
Note: The passwords are the same as the user ID. If not,
logon to SYSPRG1 and reset the passwords.
The logon procedures available to TSO users are:
|
SYSUSER |
provides access to the OS/390 BASE products. |
|
DBAUSER |
provides access to the OS/390 BASE products
plus the Data Management products. |
| TIVUSER |
provides access to the Tivoli products. |
| TSOUSER |
provides access to native TSO READY prompt. |
|
