Table Of Contents
Editing Tools For Installation
Setting Up the SMP Environment
Making Global Changes with the ISPF Editor
Updating the TCPNAMES ISPF Edit Clist
Editing Tools For Installation
This appendix describes the some edits you must make before installing Cisco IOS for S/390Cisco IOS for S/390 and how to use the tools necessary for these editions.
It covers the following subjects:
•
Setting Up the SMP Environment
Describes how to allocate common load data sets.
•
Making Global Changes with the ISPF Editor
Describes how to use the ISPF editor to edit the ALLOCSMP job.
•
Updating the TCPNAMES ISPF Edit Clist
Describes how to edit the TCPNAMES member in the CNTL data set to globally change strings used by the ALLOCxxx job streams.
Setting Up the SMP Environment
The first time you install Cisco IOS for S/390, you must set up the SMP environment. To do this, you must edit some of the members to allocate common load data sets.
There are two ways to allocate the common data sets:
•
Use the OpenEdition change command in the ISPF editor
Globally edit the following symbols using values appropriate for your system configuration:
All Cisco IOS for S/390 software products require that a common environment be established for their installation. The process comprises these tasks:
•
Allocating and initializing the SMP and common data sets for Cisco IOS for S/390
•
Allocating product-dependent data sets for optional products
Making Global Changes with the ISPF Editor
This is the format of the global change command if you are using the ISPF editor to edit the ALLOCSMP job:
c `old_string' `new_string' all
To change the string SMPINDX to TCPACSS, enter this command:
c `SMPINDX' `TCPACSS' all
If you are changing the HOLDCL symbol to an asterisk in order to use the same SYSOUT class as specified on the JOB statement MSGCLASS parameter, make sure the asterisk is enclosed in single quotes in your global change command, as this command illustrates:
c `HOLDCL' `*' all
![]()
Caution![]()
Do not modify job ALLOCSMP to use a predefined Consolidated Software Inventory (CSI) in which other software products are installed. That is, Cisco IOS for S/390 software products must be installed in their own target and distribution zones.
![]()
Note
Expect return code 0 from each step of ALLOCSMP.
Updating the TCPNAMES ISPF Edit Clist
TCPNAMES is an ISPF Edit Clist in the CNTL data set. TCPNAMES globally changes all the strings used by the ALLOCxxx job streams. TCPNAMES inserts a jobcard and updates the job with your local variables.
The TCPNAMES Clist requires ISPF Version 2 or higher. If the TCPNAMES Clist is used as distributed, all data sets must have the same high-level qualifier except for the LINK data set, which is prefixed by SYS1. plus the high-level qualifier used for the other data sets.
1
Edit the JOBCARD member in the CNTL data set, changing the JOB statement to match your site's requirements.
2
Copy member TCPNAMES to a fixed length record format Clist data set that is in your TSO SYSPROC DD concatenation.
3
As you edit the ALLOCxxx and other installation members, update the variables in the ALLOCxxx job with the parameters passed through this TCPNAMES command:
The syntax is:
TCPNAMES high_level disk_vol disk_unit tape_vol tape_unit
Usage Notes:
Always run the Clist TCPNAMES from the command line of the member for every job prior to submitting the job.
If the high-level qualifier you are using is TCPACSS, the disk volume serial number is MVS001, the disk unit type is 3390, the tape volume serial number is TCPACSS, and the tape unit is TAPE, then use this primary line command to update variables:
TCPNAMES TCPACSS.Vxxx MVS001 3390 TAPE
This changes all the strings that need to be changed in the job and replaces the JOB statement with the one in the JOBCARD member.
![]()
Note
To run the ALLOCxxx jobs, it is not necessary to substitute variables for the tape_vol or tape_unit parameters. They are used in INSTSMPE.
![]()
Caution![]()
Whenever you make changes to any SYS1.PARMLIB member, make sure you can perform an IPL on your system using an alternate IPL volume or an alternate SYS1.PARMLIB member. Typographical errors can cause catastrophic errors during system initialization, leaving your MVS system in an unusable state.