ESO

14 Sep 2005

Contents - last update 14 Sep 2005.

ESO Overview

Expanded Service Option (ESO) Installation Instructions

z/OS RSU

S/390 Service Update Facility

Glossary

ESO Overview

Important changes to ESO announced July 2005, effective September 2006

SMP/E Version 3 Release 4 (included in z/OS Release 7 but will run on any z/OS or z/OS.e system at release 1.4 or later) provides improvements to electronic service delivery with SMP/E Internet Service Retrieval and improvements to ShopzSeries. Based on these changes to electronic distribution of service there are changes to ESO subscriptions.

• New ESO and Service Only CBPDO physical media service subscriptions will be accepted through March 2006. Existing physical media subscriptions will remain in effect until September 2006. Individual ESO orders will remain orderable through ServiceLink.

There are options available using the electronic service functions which can replace the physical ESO deliverable subscription which expires in September 2006:

• Use an SMP/E Internet Service Retrieval batch job as an ESO replacement. This batch job can be scheduled to run at whatever frequency you need. Using automation you can ensure the service you have available to install is as current as you want it to be.

• Use ShopzSeries and select the Internet delivery subscription option. You can choose the months and SRELs for which you want to receive service. See http://www.ibm.com/software/ShopzSeries.

• Use ShopzSeries to select e-mail notification of new monthly service and use the e-mail as a reminder to place an individual order for physical delivery See http://www.ibm.com/software/ShopzSeries.

Additional information on changes to ESO and other deliverables is available in 'z/OS Hot Topics' issue number 13, url http://www.ibm.com/servers/eserver/zseries/zos/bkserv/hot_topics.html.

Table of Contents

Introduction

Expanded Service Options (ESO) is one way IBM delivers PTFs for software running on the z/OS (OS/390, MVS) platform. ESO provides PTFs, also called service, that you can install to fix problems that have been found in IBM software. This service is called preventive service. (Service you order separately to solve a particular problem is called corrective service.) ESO allows you to order and receive preventive service on schedules that meet your needs.

The service included with ESO is based on the products licensed under the customer number used to order the ESO. Service for products licensed under other customer numbers must be ordered separately. For example, you can place different ESO orders or have different ESO subscriptions to receive service for the products licensed under each customer number.

ESOs have monthly service levels. A logical naming convention gives you an easy way to identify the characteristics of a PTF and to treat groups of PTFs the same way using SMP/E.

The important characteristics of ESO are:

• ESO can be ordered by request at any time
• ESO is also available via Basic or Tailored Subscriptions
• ESO has new service levels every month (12 per year)
• You specify ESO content and frequency of delivery
• ESO provides Enhanced HOLDDATA for z/OS and OS/390 current to the day prior to order production
• ESO assigns SOURCEIDs to help you manage PTF installation
• z/OS RSU SOURCEIDs are included in ++ASSIGN statements. See "SOURCEIDs" for more information.
• Enhanced HOLDDATA for z/OS and OS/390 is included. See "Enhanced HOLDDATA for z/OS and OS/390" for more information.

Table of Contents

Other IBM Preventive Service Deliverables

Other preventive service deliverables and packages include:

• Service-only Custom-Built Product Delivery Option (CBPDO)
• RefreshPac

Preventive service is also included in these packages:

• CBPDO
• ProductPac
• ServerPac
• SystemPac
• Preventive service applicable to a single product is also sometimes provided on a cumulative service tape shipped with the product

Preventive service can be ordered on-line at ShopzSeries, url http://www.ibm.com/software/ShopzSeries.

Table of Contents

Ordering ESO

ESO can be ordered "on request" or by using Tailored or Basic Subscriptions. ESO on request provides the greatest flexibility because it allows you to choose from all available options and you can order an ESO at any time.

If you use a Tailored Subscription, ESOs will be shipped at intervals you specify (from 1 to 12 months) and will contain the PTFs based on the selection criteria you specify.

If you use a Basic Subscription, ESOs will be shipped approximately once a month and will contain PTFs that have been available as corrective service for at least 90 days.

If you have access to the internet, you can click here to check the status of your order.

Table of Contents

ESO on Request

Obtaining service via ESO on Request will give you the most flexibility in controlling the content and the delivery of the ESO. An ESO on Request can be ordered by calling the IBM Support Center at 800-426-7378. You will need to have the following information to place the order:

1. The Customer number under which the products for which you want service are licensed
2. The address to which the order should be shipped
3. The name and telephone number of a person to contact if there are any questions about your order
4. The starting service level that should be used to create the ESO
5. The ending service level that should be used to create the ESO
6. Whether look-ahead service should be included (see "Look-ahead Service")
7. Whether superseded PTFs should be excluded (see "Supersede Screenout")
8. If you only want service for some of the products licensed under the customer number you specify, a list of the FMIDs for which you want service

The planned turnaround time for ESO orders is five business days.

Table of Contents

ESO Tailored Subscription

You can get a subscription that meets your installation's needs using an ESO Tailored Subscription. Tailored Subscriptions are used to request from one to twelve automatic ESO shipments per year. You can also specify the age of the service to be included. (Zero months of aging delivers the most recently PER-closed service level.) PER-closed indicates the PTF is available as part of a Preventive Service package. You can also request:

• All available PTFs that resolve PEs, current to the day of order production
• All available service since the starting service level
• That superseded PTFs be excluded (see "Supersede Screenout")
• That the package be shipped to any address (if the address is not specified, it defaults to the address in your current profile)

Tailored Subscriptions must be renewed annually. You will be sent a renewal ("Recertification") notice in the last ESO package before your subscription expires.

Table of Contents

ESO Basic Subscription

ESO is available through a Basic Subscription. Basic Subscription ESOs are shipped six times a year, approximately once every two months. Each Basic Subscription ESO includes two months' PTF service. Also, Basic Subscription ESOs:

• Contain PTFs that have been available for 90 days or more
• Includes Enhanced HOLDDATA for z/OS and OS/390, current to the day prior to order production
• Include all available PTFs that resolve PTFs in error (PEs)
• Can exclude superseded PTFs (see "Supersede Screenout")

You can request that each package be shipped to any address (if the address is not specified, it defaults to the address in your current profile).

The yearly schedule for Basic Subscription ESO is shown below. If you use Basic Subscription ESO, you should get your ESO by the end of the "ship month" listed.

Service Levels	Ship Month
yy01 & yy02	June
yy03 & yy04	August
yy05 & yy06	October
yy07 & yy08	December
yy09 & yy10	February
yy11 & yy12	April

Notes:

1. "yy" is the last 2 digits of the year in which the service was identified as preventive service and assigned a SOURCEID. For example, ESO packages built in February have service for the months of September and October of the previous year.

Basic Subscriptions must be renewed annually. You will be sent a renewal ("Recertification") notice in the last ESO package before your subscription expires.

Look-ahead Service:  

(Look-ahead service is not available for basic subscription.)

You can also elect to receive all service approved for distribution (PTFs with a status of COR, in addition to PTFs with a status of PER) available on the day your order is produced. COR status of a PTF indicates is is available for Corrective Service, but is not yet included in a Preventive Service package.

For example, on 15 September 2003 the current service level was 0308. If you selected 0304 as the starting service level and selected look-ahead service, you would have gotten service levels 0304, 0305, 0306, 0307, 0308, and all PTFs approved for distribution as of 15 September.

The default for this option is "no."

Supersede Screenout:  

When you choose the supersede screenout option, PTFs superseded by other PTFs that are shipped with the order are excluded. This reduces the amount of service in the package.

The default for this option is "no."

Can be ordered by FMID:  

You can order an ESO for specific FMIDs.

Preventive Service Planning (PSP) Buckets:  

Preventive Service Planning (PSP) "buckets" are created on the first business day of each month and are updated daily. If you don't use electronic updates for Enhanced HOLDDATA for z/OS and OS/390, you should review these buckets to supplement the Enhanced HOLDDATA for z/OS and OS/390 from the ESO. They are named by SREL, using this naming convention:

PSP UPGRADE	Description
MVSPyymmX	For SREL Z038 (z/OS, OS/390, MVS)
CICSPyymmX	For SREL C150 (CICS)
IMSPyymmX	For SREL P115 (Database systems, including IMS and DB2)
NCPPyymmX	For SREL P004 (NCP)

Table of Contents

Expanded Service Option (ESO) Installation Instructions

Please refer to the chapter "Installing Preventive Service" in SMP/E Users Guide, SA22-7773 for information about how to install the service shipped with this order.

Note
Important changes have occurred to ESO, see "Important changes to ESO announced July 2005, effective September 2006" for more information.

Contents of an ESO

Data Set Attributes

ESO tapes are not labeled (NL). All files have the same data set attributes:

     Record Format (RECFM).............FB
     Logical Record Length (LRECL).....80
     Block Size (BLKSIZE)..............27920

You can specify any volume serial or data set names to read the files on ESO tapes, because they are unlabeled tapes. For example, the VOL=SER JCL parameter can specify the external (printed) labels on the tape volumes in your order, or any other convenient names. The names used on the external labels are listed in the printed documentation shipped with each order.

The examples shown below use tape data set names that were chosen to indicate the content of the files being read. For example, PTFS is used as the data set name for File 1 because File 1 contains PTFs.

Table of Contents

Multi-Tape ESO Orders

ESO tape data sets are not multivolume files. Each file starts and ends on a single tape. If an attempt is made to process two or more ESO tape files as a multivolume data set that spans multiple tapes, SMP/E will issue these error messages:

     ----------++ PTF (UY84743)        /*
     GIM20311E ** THERE IS A SYNTAX ERROR IN THE CONTROL STATEMENT AT COLUMN 4
     GIM56704E ** THERE IS AN ERROR IN AN UNKNOWN MCS IN SMPHOLD.

To process two or more ESO tapes in a single jobstep, the DD statements should be concatenated in a manner similar to the example below:

     //SMPHOLD   DD DSN=HOLDDATA,VOL=SER=tape1,LABEL=(4,NL),
     //             DISP=SHR,DCB=(RECFM=FB,LRECL=80,BLKSIZE=7200),UNIT=tape
     //*
     //SMPPTFIN  DD DSN=PTFS,VOL=SER=tape1,LABEL=(1,NL),UNIT=AFF=SMPHOLD,
     //             DISP=SHR,DCB=(RECFM=FB,LRECL=80,BLKSIZE=7200)
     //          DD DSN=PTFS,VOL=SER=tape2,LABEL=(1,NL),UNIT=AFF=SMPHOLD,
     //             DISP=SHR,DCB=(RECFM=FB,LRECL=80,BLKSIZE=7200)
     //          DD DSN=PTFS,VOL=SER=tape3,LABEL=(1,NL),UNIT=AFF=SMPHOLD,
     //             DISP=SHR,DCB=(RECFM=FB,LRECL=80,BLKSIZE=7200)
     //*
     //SMPCNTL   DD *
       SET BOUNDARY(GLOBAL) .
         RECEIVE HOLDDATA .
         RECEIVE PTFS .
     /*

Note: All HOLDDATA is in File 4 of the first tape in any ESO order. This is why the example above does not concatenate File 4 on later tapes to File 4 on the first tape. For more information about the content of ESO tape files, see "File Structure".

Table of Contents

Receiving Large ESO Orders

1. Include File 1 from Tape 1 as the first tape processed in each SMP/E RECEIVE step. For example, if your ESO order contained 14 tapes, you could process tapes 1 through 7 in the first RECEIVE step and then tape 1 again, followed by tapes 8 through 14 in the second step.

2. Re-do the RECEIVE for the PTFs contained on tape 1 after you have RECEIVED all the service from all the tapes in your order. SMP/E will process the ++ASSIGNs and update any PTFs that have already been received.

Table of Contents

File Structure

There are five files on each ESO tape. Their content on a particular tape depends on whether it is the first tape in an ESO order or a second or subsequent tape in the same order. The files and their content are:

File	First ESO Tape	Additional ESO Tapes
1	PTFs that fall within requested starting and ending service levels PTFs available when the order was built that resolve PTFs in error (PEs) contained in the package ++ASSIGN statements for each PTF in the package (These statements assign SOURCEIDs to each PTF).	PTFs that met the selection criteria but would not fit on previous tapes.
2	Installation and usage instructions (this document in browsable, machine-readable form).	A ++NULL statement
3	A list of all PTFs included in the order.	A ++NULL statement
4	Enhanced HOLDDATA for z/OS and OS/390. (For a full description, see "Enhanced HOLDDATA for z/OS and OS/390".)	A ++NULL statement
5	All UCLIN applicable to all PTFs included in the order.	A ++NULL statement

Notes:

1. Corrective service tapes also have five files, and use the same structure shown above. Therefore, jobs used to process ESO tapes can also be used to process corrective service tapes.

2. CBPDO tapes have a different file format than ESO and corrective service tapes. For information about how to install service or products using CBPDO, refer to the CBPDO Memo to Users Extension shipped with the CBPDO tapes and to the topic "CBPDO Tapes" in SMP/E Users Guide, SA22-7773.

3. For electronic deliveries, files 3 and 4 are delivered together in a single *.txt file.

Table of Contents

Softcopy Packing List

A softcopy packing list is included in file 3. It includes:

1. Product numbers, associated FMIDs, and descriptions as listed in your customer profile. Information about which FMIDs had service shipped in this order is included.

2. A PTF list with associated FMID and SOURCEID assignments, cross-referenced with indicators for PE, UCLIN, HIPER, PE resolution, and system HOLDs. (System HOLDs include those for ACTION, AO, DELETE, DEP, DOC, EC, EXRF, FULLGEN, IOGEN, MSGSKEL, and MVSCP).

Unloading or Printing the List of PTFs

Unloading the List of PTFs:  

This sample job can be used to unload the list of PTFs from File 3 on the first ESO tape, and store it in a data set. Before submitting it:

• Change "tape" to a valid device name, generic name, esoteric name, or device number for a tape device on the SYSUT1 DD statement.
• Change "tape1" to whatever value you choose on the SYSUT1 DD statement. (The name printed on the external label is usually convenient.)
• Change "ESOnnnn" to the member name to be used.
• Change "vvvvvv" to the volume label for the DASD volume to be used on the SYSUT2 DD statement.
• If you want to run this job again later for another ESO tape, change the disposition on the SYSUT2 DD statement from "(NEW,CATLG)" to "SHR" and remove the SPACE parameter before doing so.

Lines that need to be changed are flagged with a '<===='.

     //JOB CARD
     //*
     //STEP1  EXEC PGM=IEBGENER
     //SYSPRINT DD SYSOUT=*
     //SYSIN    DD DUMMY
     //*
     //SYSUT1   DD DSN=PTFLIST,LABEL=(3,NL),VOL=SER=tape1,     <====
     //            UNIT=tape,DISP=OLD,                         <====
     //            DCB=(RECFM=FB,LRECL=80,BLKSIZE=7200)
     //*
     //SYSUT2   DD DSN=hlq.PTFLISTS(ESOnnnn),                  <====
     //            DISP=(NEW,CATLG),
     //            UNIT=SYSALLDA,VOL=SER=vvvvvv,               <====
     //            DCB=*.SYSUT1,SPACE=(TRK,(5,5,5))
     //*

Printing the List of PTFs:  

This sample job can be used to print the list of PTFs from File 3 on the first ESO tape. Before submitting this job:

• Change "tape" to a valid device name, generic name, esoteric name, or device number for a tape device on the SYSUT1 DD statement.
• Change "tape1" to whatever value you choose on the SYSUT1 DD statement. (The name printed on the external label is usually convenient.)
• If A is not a print output class at your installation, change the SYSOUT class on the SYSUT2 DD statement to specify a print output class.

Lines that need to be changed are flagged with a '<===='.

     //JOB CARD
     //*
     //STEP1  EXEC PGM=IEBGENER
     //SYSPRINT DD SYSOUT=*
     //SYSIN    DD DUMMY
     //*
     //SYSUT1   DD DSN=PTFLIST,LABEL=(3,NL),VOL=SER=tape1,     <====
     //         UNIT=tape,DISP=OLD,                            <====
     //         DCB=(RECFM=FB,LRECL=80,BLKSIZE=7200)
     //*
     //SYSUT2   DD SYSOUT=A
     /*

Table of Contents

SOURCEIDs

ESO identifies each PTF using SMP/E ++ASSIGN statements. The naming convention PUTyymm is used for PTFs that have been identified as preventive service, where yymm represents the year and month in which the PTF was so identified.

For example, PUT0310 identifies PTFs that were identified as preventive service during October 2003. These SOURCEIDs are assigned to eligible PTFs from the previous month starting on the 15th day of each month. Therefore, SOURCEID PUT0310 was assigned to PTFs that became available during the month of October 2003 in ESO orders built after 15 November 2003.

Other SOURCEIDs can also be assigned. All of the PTFs provided with ESO are assigned at least one of the SOURCEIDs listed below. (If you decide to assign additional SOURCEIDs, you can specify them using the SOURCEID parameter on the SMP/E RECEIVE command.) The IBM-assigned SOURCEIDs are:

PUTyymm	These SOURCEIDs identify PTFs that have been identified as preventive service. In PUTyymm, yymm identifies the year and month in which the PTF was marked as preventive service. All PTFs in ESO have SOURCEIDs of either PUTyymm or SMCCOR. (PTFs with a PUTyymm SOURCEID have PTF closure codes of "PER.")
SMCCOR	Identifies PTFs that have not yet been identified as preventive service. All PTFs in ESO have SOURCEIDs of either PUTyymm or SMCCOR. (Available PTFs that have not yet been marked as preventive service have PTF closure codes of "COR.")
HIPER	Identifies PTFs that resolve a High Impact / Critical APAR or supercede a PTF that does. PTFs assigned SOURCEIDs of HIPER will also be assigned either PUTyymm or SMCCOR SOURCEIDs.
PRP	Identifies PTFs that resolve PTFs in error. PTFs assigned SOURCEIDs of PRP will also be assigned either PUTyymm or SMCCOR SOURCEIDs.
RSUyymm	Identifies PTFs that have been identified by IBM as z/OS RSU based on APAR criteria. PTFs assigned SOURCEIDs of RSUyymm will also be assigned PUTyymm SOURCEIDs.
YR2000	Identifies PTFs that provide Year 2000 function, or fix a Year 2000-related problem.
EURO99	Identifies PTFs that provide Euro currency symbol function or fix a Euro currency symbol problem.

You can assign your own SOURCEID in addition to the ones IBM assigns. To assign an additional SOURCEID, use the SOURCEID operand of the RECEIVE command as shown below:

   SET BDY(GLOBAL) .
     RECEIVE
       SOURCEID(ESO0310) /* Assign SOURCEID of ESO0310  */ .

Note: ++ASSIGN statements, which are used by SMP/E to assign SOURCEIDs, are provided only for the PTFs shipped with your order. SMP/E will process them when you RECEIVE the PTFs from an ESO or Corrective service tape.

Table of Contents

Enhanced HOLDDATA for z/OS and OS/390

Enhanced HOLDDATA for z/OS and OS/390 is updated daily. The HOLDDATA shipped in File 4 will be one day old or less when your order is built. When you order an ESO or corrective service on tape, 2 years of Enhanced HOLDDATA for z/OS and OS/390 is shipped. When you order an ESO or corrective service to be delivered electronically, 90 days of Enhanced HOLDDATA for z/OS and OS/390 is sent.

You can bring your HOLDDATA up to date without ordering service by getting electronic updates of Enhanced HOLDDATA for z/OS and OS/390 via the Internet. Enhanced HOLDDATA for z/OS and OS/390 available from the Internet is updated daily. These very current electronic updates can help you prevent the inadvertent installation of PTFs in error and eliminate the need to research service before installing it. It also makes it unnecessary to review PUT PSP buckets. See "Enhanced HOLDDATA for z/OS and OS/390 from the Internet" for information about getting Enhanced HOLDDATA for z/OS and OS/390 from the Internet.

If much time has passed (more than a week or two) since your ESO was built, IBM recommends that you bring the ESO-supplied Enhanced HOLDDATA for z/OS and OS/390 up to date before installing service (see "Enhanced HOLDDATA for z/OS and OS/390 from the Internet").

You must always receive HOLDDATA in sequence by date, which means receiving the most recent HOLDDATA last. Each ++HOLD is dated. You can list HOLDDATA from your global zone, examine saved SMP/E output from the last time HOLDDATA was received, or unload and examine the HOLDDATA file from the last service deliverable (ESO, CBPDO, RefreshPac, ProductPac, or ServerPac or SystemPac service tape) to find the last date specified on a ++HOLD statement. Also, the header in the Enhanced HOLDDATA for z/OS and OS/390 file contains ++NULL comments that indicate the time period covered by that specific file.

Important!

You should process more recent HOLDDATA only when it has a starting date that is either one day later than or is before the previous HOLDDATA ending date. If there are gaps in the HOLDDATA you process, PTFs marked in error during the missing period will not be held, and it is possible that one or more ++RELEASE statements could be missing from the data. This could result in some PTFs in error being installed, and others being held for ERROR when they would otherwise have been eligible for installation.

NOTE!

If there are multiple programmers in your organization that are independently ordering and installing service you should set up a process to ensure that only the latest Enhanced HOLDDATA for z/OS and OS/390 is RECEIVEd into SMP/E. The easiest method to achieve this is to consistently use the latest electronic Enhanced HOLDDATA for z/OS and OS/390 whenever installing any service, in addition to or instead of the HOLDDATA delivered with the service. This will prevent inadvertent downleveling of HOLDDATA.

Enhanced HOLDDATA for z/OS and OS/390 Hold Symptoms

Enhanced HOLDDATA for z/OS and OS/390 contains SMP/E ++HOLD and ++RELEASE statements for ERROR only. Both PTFs in error and FMIDs with outstanding HIPER APARs are held. The reason IDs for the holds are based on the APAR number that describes the error. PTFs that resolve an ERROR hold supersede the APAR number (the HOLD's reason ID) allowing the PTF or FMID held to be installed. (You can also use the BYPASS operand of the SMP/E APPLY command when installing products to bypass hold conditions you intend to resolve later. See "Using Enhanced HOLDDATA for z/OS and OS/390".)

Product FMIDs are held for APARs marked HIPER (High-Impact / Critical). When an FMID is held for a HIPER, any symptom flags from the HIPER APAR are included in addition to the reason ID. The HIPER symptom flags currently included are:

Flag	Keyword	Description
DAL	DATALOSS	Data is lost or corrupted.
IPL	SYSTEMOUTAGE	The system fails. Causes the customer to re-IPL, reboot, recycle or restart one or more systems or subsystems.
FUL	FUNCTIONLOSS	Causes a major loss of function on the customer's system.
PRF	PERFORMANCE	Severe impact to system performance/throughput.
PRV	PERVASIVE	May affect a large number of customers.
SYSPLXDS	SYSPLEXDS	Identifies HIPER fixes needed to support and implement SYSPLEX Data Sharing.
XSYSTEM	XSYSTEM	Identifies HIPER fixes which provide cross-system, migration, compatability or toleration support.
D/T2105	D/T2105	Identifies HIPER fixes which pertain to Hardware device 2105.
D/T2107	D/T2107	Identifies HIPER fixes which pertain to Hardware device 2107.
D/T1750	D/T1750	Identifies HIPER fixes which pertain to Hardware device 1750.

The current list of hold flags is at http://service.boulder.ibm.com/390holddata.html.

Enhanced HOLDDATA for z/OS and OS/390 and SMP/E Reporting

Enhanced HOLDDATA for z/OS and OS/390 delivers information about PE PTFs and HIPER APARs, and includes fixing PTF information when available.

After the HOLDDATA has been RECEIVEd, SMP/E can be used to list all HOLDDATA, or list HOLDDATA filtered using various criteria. The SMP/E REPORT ERRSYSMODS command can be used to report on unresolved hold conditions, including PTFs in error and unresolved HIPER APARs that apply to the products you have installed. The REPORT ERRSYSMODS command is included in all supported levels of SMP/E.

For more information about the SMP/E LIST and REPORT commands, see SMP/E Commands, SA22-7771.

Table of Contents

Enhanced HOLDDATA for z/OS and OS/390 from the Internet

Current Enhanced HOLDDATA for z/OS and OS/390 is available electronically at URL: http://service.boulder.ibm.com/390holddata.html.

You can request this data as needed, and the files are updated daily. You can download up to 3 years of Enhanced HOLDDATA for z/OS and OS/390. When requesting updated Enhanced HOLDDATA for z/OS and OS/390, always request a file that will have a starting date that is prior to the date of your most recently-received HOLDDATA (the available files are 30-day, 90-day, 1-year, 2-year and 3-year). You can check the production date of your last service deliverable that included Enhanced HOLDDATA for z/OS and OS/390, the date of your last electronic Enhanced HOLDDATA for z/OS and OS/390 update, the comments in the header of your last Enhanced HOLDDATA for z/OS and OS/390 file, or list your already-received HOLDDATA to determine which file you should request.

You can also use batch FTP on the host to automate the request and receipt of updated Enhanced HOLDDATA for z/OS and OS/390. Instructions and a sample job for this are on the web page.

Table of Contents

Using Enhanced HOLDDATA for z/OS and OS/390

Enhanced HOLDDATA for z/OS and OS/390 is processed the same way previously-provided HOLDDATA was processed. Use SMP/E's RECEIVE HOLDDATA command to receive Enhanced HOLDDATA for z/OS and OS/390 into the the Global zone.

Enhanced HOLDDATA for z/OS and OS/390 introduces ERROR holds against product FMIDs for HIPER APARs. This enables you to easily check whether all PE and HIPER recommended service in the product PSP bucket is installed when the FMID is being APPLYed. It also lets you use SMP/E's REPORT ERRSYSMODS to identify any uninstalled PE or HIPER fixes at any time.

You might want to change the parameters specified on the APPLY command when installing products. There are two ways to complete the installation of an FMID:

1. If you want to ensure that all critical service is installed at the same time as the FMID, add the SOURCEIDs of HIPER, PRP, and YR2000 to the APPLY command. There may be some HIPER APARs that do not have resolving PTFs available yet. You'll need to analyze any symptom flags to decide whether you should BYPASS specific ERROR HOLDs to continue the installation.

        APPLY S(fmid,fmid,...)
        FORFMID(fmid,fmid,...)
        SOURCEID(HIPER,PRP,YR2000,...)
        GROUPEXTEND .
   

   This method might take more initial research, but will make sure all critical service for which fixes are available (and not in a PE chain) is installed when the product is installed.

2. To install products as they would have been installed prior to Enhanced HOLDDATA for z/OS and OS/390, you can add a BYPASS(HOLDCLASS(HIPER,YR2000)) operand to the APPLY command. This will allow them to be installed even though there are unresolved ERROR HOLDs. Note that not all ERROR HOLDs will be bypassed, only the HIPER ERROR HOLDs. After the products are installed, the SMP/E REPORT ERRSYSMODS command should be run to identify any missing HIPER maintenance.

        APPLY S(fmid,fmid,...)
        BYPASS(HOLDCLASS(HIPER,YR2000))
        ...any other parameters documented in the program directory...
   

   This method gets the product installed more quickly, but requires work later, to investigate any uninstalled critical service.

One other procedural point about Enhanced HOLDDATA for z/OS and OS/390. Since it is likely (and advantageous) to receive updates to Enhanced HOLDDATA for z/OS and OS/390 between the APPLY and ACCEPT steps for a system, it is possible to encounter ++HOLDs on the ACCEPT that were not identified at the time of the APPLY. Reviewing the REPORT ERRSYSMODS before the ACCEPT will identify any outstanding PEs or HIPERs on the target system, which then may be reviewed for applicability.

Table of Contents

Printing Cover Letters for Selected PTFs

To print the PTF cover letters for selected FMIDs, you can use these SMP/E control statements after the PTFs have been received:

     SET BDY(GLOBAL).
     LIST FORFMID(fmid,
                  fmid)
          SOURCEID(PUTyymm)
          MCS
          .

To print the cover letters for selected PTFs, use the following SMP/E control statements.

     SET BDY(GLOBAL).
     LIST MCS(PTF_number,
              PTF_number)
          .

Table of Contents

Applying Selected Maintenance

ESO provides several SOURCEIDs. Using these SOURCEIDs, SMP/E provides wide flexibility in installing service using criteria you select. For example, if the latest ESO order you have included service for 9710 thru 9801, and you want to:

1. Install all PTFs from 9710, 9711, and 9712; and,
2. Install all earlier received PTFs; and,
3. Install other received HIPER PTFs; and,
4. Install other received PTFs for Year 2000; and,
5. Include PTFs that fix PEs and any needed to install the other PTFs specified, if they have been received.

You could to this with these SMP/E control statements:

     SET BDY(tgtzone) .
       APPLY
         SOURCEID(PUT*,HIPER,YR2000)
         EXSRCID(9801)
         GROUPEXTEND .

For more information about how to include or exclude service with different SOURCEIDs during APPLY and ACCEPT processing, see SMP/E Commands, SA22-7771.

Table of Contents

ESO Selective Install EXEC

Description

The MVS/ESO Selective Install EXEC is an example of how TSO/E REXX can be used to manipulate the data provided in the softcopy packing list in File 3 of an MVS/ESO order. Its use is not required to install the PTFs provided by ESO.

This file includes data in two sections. The first section contains data about products listed in your customer profile. Information on Product Number, FMID, Service, and Product Description is included. The Selective Install EXEC can be used to sort on any of these fields.

The second part of the softcopy packing list contains data about the PTFs included in this order. The PTF data includes PTF number, FMID, and Issue. There are also flag fields to identify PTFs that are unresolved PE (UPE), that have UCLIN (UCL), fix HIPER APARs, or contain System HOLD information. (System HOLDs include those for ACTION, AO, DELETE, DEP, DOC, EC, EXRF, FULLGEN, IOGEN, MSGSKEL, and MVSCP).

The last two fields of the softcopy packing list identify PE resolving PTFs (PRP) and the associated APAR. If the PRP field contains data, this indicates that the PTF listed in the PTF Number field has been marked PE. In this case, the PRP field lists the fixing PTF. The APAR FIXED field is provided as additional information to help determine the impact of the APAR. The Selective Install EXEC can be used to sort on any of these fields.

The Selective Install EXEC was originally designed to help installing selected service from an ESO order. It will generate SMP/E RECEIVE and EXCLUDE statements grouped by SOURCEID based on the selection criteria provided. For example, it can be used to create RECEIVE statements for all PTFs that are listed in File 3 as HIPER.

The EXEC can also be used to assist in locating necessary information about specific groups of PTFs. For example, it can be used to create a list of all PTFs held for ACTION. This output could be edited to provide a listing of the actual HOLDDATA or the PTF cover letters (which sould include the HOLDDATA).

Restrictions

The MVS/ESO Selective Install EXEC is provided only as a sample by IBM. It shows how TSO/E REXX can be used to manipulate the data provided in File 3 of an ESO order. While you may report problems with this sample EXEC to IBM if you choose, IBM will neither accept APARs for it nor commit to provide a solution or circumvention for any problem.

Downloading the ESO Selective Install Exec

Refer to "Downloading the ESO Sample Utilities" for download instructions.

The ESOUTIL Program, ZESO100

What is ESOUTIL?

ESOUTIL is a sample utility program you can download from the Internet. You can use it to copy selected PTFs and print selected PTF cover letters from ESO tapes using various selection criteria.

ESOUTIL can copy PTFs from an ESO tape to a data set on tape or DASD. It can copy all PTFs, PTFs selected be by SREL, FMID, COMPID or individual PTFs. All applicable ++ASSIGN statements (from the first ESO tape) are copied to the output data set with the PTFs.

ESOUTIL can also print the cover letters for all PTFs or selected PTFs from an ESO tape using the same selection criteria. Applicable ++ASSIGN statements are also included in the cover letter output.

Table of Contents

Support

This code is provided free of charge. The code is not warranted and is provided "as is". IBM is under no obligation to maintain, correct, update, change, modify, or otherwise support this program. IBM makes no representation and gives no warranty as to infringement of patents or copyrights relating to this material.

This code is copyrighted by IBM.

Table of Contents

Downloading the ESOUTIL Program

Refer to "Downloading the ESO Sample Utilities" for download instructions.

Table of Contents

Installation.

ESOUTIL is SMP/E-installable. Its FMID is ZESO100. Installation and usage instructions are included in the ZESO100 coverletter.

Downloading the ESO Sample Utilities

The ESO Selective Install Exec and ESOUTIL Program (ZESO100) can be downloaded from the IBM PCC BBS Miscellaneous File Area or via anonymous FTP at ftp.software.ibm.com. The path is s390/mvseso/tools (case sensitive).

For the ESO Selective Install Exec both a host version (FB 80) and a binary ZIP version are available.

To access the PCC BBS, the following minimum configuration is required.

• IBM PC or PS/2 or compatible
• 1200bps modem
• Communications software
• Telephone switched line.

To connect to the PCC BBS, dial (919) 517-0001, with your modem set for 8 data bits, 1 stop bit, and no parity bits. Or click here to link to the ftp site.

Once a connection to the PCC BBS is established, ESO files can be found under the "Miscellaneous Files" directory of the (L)ist Files command. Be sure to "unzip" any *.zip files before uploading to your host for execution. The utility used to "unzip" the files (PKUNZIP) is available from the PCC BBS.

z/OS RSU

z/OS Recommended Service Upgrade (z/OS RSU) and CST

z/OS RSU is a list of recommended MVS maintenance which reduces the total volume of maintenance a customer may choose to install.

Information on CST and RSU can be found at http://www.ibm.com/servers/eserver/zseries/zos/servicetst/.

Table of Contents

S/390 Service Update Facility

IBM S/390 SERVICE UPDATE FACILITY (SUF)

Effective January 15, 2006, the S/390 Service Update Facility will be discontinued.

An alternative to S/390 SUF is ShopzSeries. With ShopzSeries you can:

• order tailored product and service packages for z/OS, z/OS.e and OS/390

• order tailored product packages for z/VM, VM/ESA and VSE/ESA,

• review your software licenses in all of these environments, and

• plan for future upgrades.

Further information on ShopzSeries can be found at http://www.ibm.com/software/ShopzSeries.

Further information on SUF can be found at http://www.ibm.com/servers/eserver/zseries/zos/suf/.

Glossary

Table of Contents