GuangXingLiu

Back to top  

Back to top  

Back to top  

Back to top  

Back to top  

Back to top  

Back to top  

Back to top  

Back to top  

Back to top  

Back to top  

Back to top  

Back to top  

Newly introduced ESOTERICs WORK / TEMP / SORT not working as expected.

With this edition, three new esoterics WORK / TEMP / SORT have been   introduced in the IODF file. They have been mapped to devices in the   range 0600 to 060F.  However, this device range is wronlgy set in the   IODF file to be offline after IPL. In order to overcome this issue,   change the settings in IODF file for this device range, so that   they are online after IPL.

Also, one additional change is required to bring the esoterics   into effect. They need to be added to VATLSTxx member in the PARMLIB   library, as storage volumes. A sample statement is shown below, to   define volume serials WORK00 to WORK16 (on devices 0600 - 060F), as   storage. The VATLSTxx member is pointed to by the IEASYSxx member,   via statement VAL=xx.

   WORK* ,0,0,3390    ,Y    

IEBCOPY causing corruption during 'compress' function (OA38642).

A recent change in IEBCOPY code, is known to cause problems (APAR   OA38642) with compress function in a zPDT environment. A fix is being   worked at the moment. Please exercise caution while doing a compress   with IEBCOPY in zPDT environment. The 'z' line command used for   compressing PDS files in ISPF 3.4 option also uses IEBCOPY. Refer the   below APAR link for information on temporary circumvention     OA38642.  

GUNZIP results in "Unexpected end of file" error.

While using gunzip command to extract the zPDT volumes from gz   files, it throws an error message "Unexpected end of file". Though   this sounds like a serious error, we have tested the output and   could not find anything wrong. If you get this error message, just   ignore it and continue to use the extracted zPDT volume. Just make   sure the extracted file size is matching with value   (Uncompressed size in bytes) specified in the download website, for   that particular file.

Back to top  

SDRES1, SDRES2

SDRES1 is a 3390-3 volume that contains the base MVS system software   target, or run-time libraries, and other system data sets required to   IPL the system and use TSO/E and ISPF. This is the MVS IPL volume.

SDRES2 is a 3390-3 volumes that are an extension of the   SYSRES volume SDRES1. The volume is also required for IPL.   SDRES2 contains the usercatalog   USERCAT.Z113S.PRODS containing entries for z/OS related products.

SDSYS1

This 3390-3 volume contains data sets that you might change, either   through normal use of the system or user customization. All   USER.xxxxxx datasets are on this volume. System control data sets,   such as SYS1.IPLPARM, the RACF database, IODF (I/O Definition File),   and system's master catalog (CATALOG.Z113S.MASTER) reside on this   volume. This volume is required to IPL.

SDUSS1, SDUSS2

SDUSS1 is a 3390-3 volume that contains the ROOT and Version zFS   files for UNIX System Services of z/OS. This volume is required to   IPL.

SDUSS2 is a 3390-3 volume that contains the other HFS and zFS   files for UNIX System Services of z/OS. This volume is required to   IPL.

SDPRD1, SDPRD2, SDPRD3

SDPRD1 and SDPRD2 are 3390-3 volumes   that contains all z/OS products that are   not required to IPL basic z/OS   as delivered. If the products are customized at   some future date i.e. parmlib members updated, then these volumes may   be required for IPL.   SDPRD3 contains the language target libraries.   SDPRD3 contains the   HFS / zFS files for Java 6.0.0, Java 6.0.1 and Java 7.0.0.

SDDIS1, SDDIS2, SDDIS3, SDDIS4, SDDIS5, SDDIS6

These volumes contains the base MVS system software distribution   libraries. They contain the DLIB (Distribution Library) and zone   CSI's. These volumes need not be present to IPL, but are needed to   install service or products on the MVS system using SMP/E. These   volumes are all 3390-3.

SDPAGA, SDPAGB, SDPAGC, SDPAGD, SDPAGE, SDPAGF

These volumes contain page data sets. The SDPAGA volume has the PLPA,   Common and one Local page data set. Rest of the 5 volumes each have   one Local page data set. The loadparms that bring up DB2 or WAS   have been defined to use all the above 6 page volumes, all other   loadparms use only the first two volumes. If you do not want to use   all of these local page data sets, you can modify the PAGE parameter   on IEASYSnn member, accordingly.

SDDBA1, SDDBA2, SDDBA3 and SDDBAR

SDDBA1 is a 3390-3 volume that contains DB2 V10 related data. SDDBA1   contains the DB2 usercatlog, USERCAT.Z113S.DB2VA. Also SDDBA1   contains all DB2 target libs.   This volume is not required to IPL   but is required to bring up DB2 V10.

SDDBA2 is a 3390-3 volume that contains DB2 V10 DLIB and CSI's. Also   contained are Target and DLIB for various DB2 V10 utility products.   The volume is not required for IPL but is needed to apply DB2   maintenance and run DB2 utilities and products. i.e. QMF,   Administration tool.

SDDBA3 is a 3390-3 volume that contains DB2 catalog and directories   with HLQ DSNCA10, which are SMS managed. The volume is not required   for IPL but is needed to bring up DB2.   DB2.

SDDBAR is a 3390-3 volume defined in a new esoteric called DBARCH.   This esoteric has been defined in DB2, for allocating the archive   logs into this storage volume. This volume is required, if you want   to bring up DB2 V10.

SDDB91, SDDB92, SDDB93 and SDDBAR

SDDB91 is a 3390-3 volume that contains DB2 V9 related data. SDDB91   contains the DB2 usercatlog, USERCAT.Z113S.DB2V9. Also SDDB91   contains all DB2 target libs.   This volume is not required to IPL   but is required to bring up DB2 V9.

SDDB92 is a 3390-3 volume that contains DB2 V9 DLIB and CSI's. Also   contained are Target and DLIB for various DB2 V9 utility products.   The volume is not required for IPL but is needed to apply DB2   maintenance and run DB2 utilities and products. i.e. QMF,   Administration tool.

SDDB93 is a 3390-3 volume that contains DB2 catalog and databases.   The volume contains basic customization for bringing up DB2 on the   ADCD. The volume is not required for IPL but is needed to bring up   DB2.

SDDBAR is a 3390-3 volume defined in a new esoteric called DBARCH.   This esoteric has been defined in DB2, for allocating the archive   logs into this storage volume. This volume is required, if you want   to bring up DB2 V9.

SDC421

SDC421 is a 3390-3 volume that contains CICS 4.2 Target, DLIB and all   related data for CICS 4.2. USERCAT.Z113S.CICS420 resides on this volume.   This volume is not required to IPL but is required to bring up CICS 4.2   and apply CICS maintenance.

SDC411

SDC411 is a 3390-3 volume that contains CICS 4.1 Target, DLIB and all   related data for CICS 4.1. USERCAT.Z113S.CICS410 resides on this volume.   This volume is not required to IPL but is required to bring up CICS 4.1   and apply CICS maintenance.

SDWA81, SDWA82, SDWA83, SDWA84, SDWA85 and SDWA86

SDWA81 is a 3390-3 volume that contains   target libraries for Websphere Application Services.

SDWA82 is a 3390-3 volume that contains distribution libraries   for Websphere Application Services.   SDWA82 is required to perform maintenance on   Websphere Application Services,

SDWA83 and SDWA84 are 3390 volumes that contain target zFS files   that are very large. Though SDWA83 is a standard 3339 cylinder   mod-3 volume, SDWA84 is a non-standard volume with 3600 cylinders.   These volumes are not required to IPL but are required to bring   up Websphere Application Services.

SDWA85 and SDWA86 are 3390-3 volumes that contain pre-configured   zFS files required for manually starting WAS.

SDWA71, SDWA72, SDWA73, SDWA74 and SDWA75

SDWA71 is a 3390-3 volume that contains   target libraries for  Websphere Application Services.

SDWA72 is a 3390-3 volume that contains distribution libraries   for Websphere Application Services.   SDWA72 is required to perform maintenance on   Websphere Application Services,

SDWA73 is a   3390-3 volume that contains one Websphere Application Services   target zFS file that is very large.   These volumes are not required to IPL but are required to bring   up Websphere Application Services.

SDWA74 and SDWA75 are 3390-3 volumes that contain pre-configured   zFS files required for manually starting WAS.

SDIMC1, SDIMC2, SDIMU1 and SDIMU2

SDIMC1 is a 3390-3 volume that contains IMS Target, DLIB and all   related data for IMS 12.   USERCAT.Z113S.IMS12 resides on this volume. This volume is not required   to IPL but is required to bring up IMS and perform maintenance on   IMS.

SDIMB1 is a 3390-3 volume that contains IMS Target, DLIB and all   related data for IMS 11.   USERCAT.Z113S.IMS11 resides on this volume. This volume is not required   to IPL but is required to bring up IMS and perform maintenance on   IMS.

SDIMU1 and SDIMU2 are 3390 volumes that contain   IMS Utilities. SDIMU2 is a non-standard volume with 3600   cylinders, to accomodate the large zFS file.   These volumes are not required to IPL but is required to bring up IMS   and perform maintenance on IMS Enterprise Suite.

SDBBN1, SDBBN2

SDBBN1 is a 3390-3 volume that contains Target libraries for   z/OS Management Facility, zOSMF.   This volume is not required to IPL but is required to bring up zOSMF.

SDBBN2 is a 3390-3 volume that contains distributions libraries for   z/OS Management Facility, zosmf.   This volume is not required to IPL but is required to perform  maintenance on zOSMF.

SDKAN1

SDKAN1 is a 3390-3 volume that contains Target and DLIB libraries for   Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS 5.1.0.   This volume is not required to IPL but is required to bring up DB2   PE.

SARES1

This 3390-3 volume contains a single volume stand alone system. This   volume can be used to IPL and logon to a TSO/ISPF session.

The disk volume can assist in building LPAR environments and correct   errors that prevent system IPL.

Recommended use of this volume is to install the volume and leave   accessible. The volume should not be altered. The volume should stay   in a background mode and be available for emergency type of   situations. If other z/OS, OS/390, or LPAR partitions contain errors,   the SARES1 volume could be used to solve the problem.

The stand alone system does not contain TCPIP or Unix system service   support. The system cannot be used to install products or apply   maintenance via SMP/E.

To IPL the standalone res volume:  

Load Address: 0Axx  

Load Parms: 0AxxSAM  

Back to top  

The following guidelines will make it easier for you to replace   this level of system software with new levels built the same way.

Only IBM-supplied system software should reside on SDxxxx volumes   except for SDSYS1. SDSYS1 contains RACF, IPL, and catalog datasets   that are user dependent.

The ADCD does not contain a generalized migration utility or process.   Each user   has unique requirements. It is recommended that you build a migration   plan based on your unique needs.  The ADCD does have some assistance.   The ADCD uses a system of concatenated libraries (see below)   The highest   level of concatenation is USER.xxxxxxxx.  The ADCD distributes these   libraries empty.   It is recommended that the user place changes or   overrides is these libraries.  It is further recommended that the   USER.xxxxxxxx libraries be backed up regularily.  When a new ADCD   release is installed the USER.xxxxxxxx libraries can be copied from   backups to the new USER.xxxxxxxx libraries to provide instance   migration of programs and parameters.

The ADCD is distributed with a standard library   concatenation for the following:

• LINKLST

• PROCLIB (including TSO procedures)

• CLIST

• ISPPLIB (TSO panels)

• LPALIB

• PARMLIB

• VTAMLST

• VTAMLIB

• VTAM source

The configured order of concatenation is user,   ADCD developers, and z/OS system   datasets.   For example, the LINKLST concatenation would be as   follows:

• USER.LINKLIB

• ADCD.Z113S.LINKLIB

• SYS1.LINKLIB

USER.xxxxx libraries have all been   built on SDSYS1 which is the only volume that should contain user   data.

USER.xxxxx will not be changed by ADCD or System processes; thus,   user updates in USER.xxxxx will be retained between release levels.   ADCD.Z113S.xxxxxx libraries are allocated on SDRES1 and are the   libraries that are used by ADCD developers.  No RACF rules exist on   these libraries; however, changes to these libraries could destroy   customization necessary to bring up many products.   SYS1.xxxxxxx libraries should NEVER be updated   by users or ADCD development.  System libraries should ONLY be updated   through SMP/E install, maintenance processes, or like processes.

NOTE:   Changes to System libraries or ADCD pre-customization may corrupt   your system and prevent or delay IBM support activites.

The correct procedure for a user update to system data is to:

• Copy the system data from SYS1.xxxxx or ADCD.xxxx to USER.xxxxx

• Edit, compile, or run user program against the USER.xxxx item

• Re-ipl, recycle system service, or re-logon to TSO

Removing a user update would be the reverse of the above procedure.

Back to top  

NOTE:   JES2 should be cold started the first time you bring up the   system.

Back to top  

Back to top  

Back to top