GuangXingLiu

一蓑一笠一孤舟,一丈丝纶一鱼钩,一曲高歌一樽酒,一人独钓一江秋.

ADCD z/OS V2R4 May Edition of 2020

What's New in ADCD z/OS V2R4 May      Edition of 2020

NOTE: As of ADCD z/OS V2R4 May      Edition of 2020, distribution via   DVDs has been discontinued and all future distribution of ADCD   Editions will only be available via download.

The      ADCD Release Guide z/OS V2R4 May      Edition of 2020,      also available on the download site, contains more information    about this edition. It also provides some additional notes and    tips to effectively manage the ADCD system.

The following products have been added:

The following products have been updated to PUT2003 / RSU2003

All of z/OS base, z/OS products and middleware volume size       has been increased to mod-9 (10,017 cylinders) to provide more       free space for expansion

Products contained in this release


Reported Problems, Fixes, Maintenance and Observations


Build Structure





Migration Guidelines

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   B4xxxx volumes   except for B4SYS1.   B4CFG1 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.Z24B.xxxxxx   The ADCD distributes these libraries empty. It is recommended that   the user place changes or overrides in these libraries. It is further   recommended that the   USER.Z24B.xxxxxx   libraries be backed up regularily.   When a new ADCD release is installed the   USER.Z24B.xxxxxx   libraries can   be copied from backups to the new   USER.Z24B.xxxxxx   libraries to provide   assistance in migration of programs and parameters.

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


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


USER.Z24B.xxxxxx   libraries have all been built on   B4CFG1   which is the only volume that should contain user data.

USER.Z24B.xxxxxx   will not be changed by ADCD or System processes; thus,   user updates in USER.Z24B.xxxxxx   will be retained between release levels.   ADCD.Z24B.xxxxxx libraries are allocated on   B4SYS1 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:


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

LOADPARMS Options

NOTE:   JES2 should be COLD started the FIRST time you bring up the   system.


Console PF Key Settings


USERIDS


Maintenance Service Levels

All the products on the ADCD consist of maintenance that is in a   closed status. A PTF that is still in open status or has other than a   document hold at the time the ADCD was built would not be added to   the ADCD. The following PUT levels may be minus PTFs that were open   at build time. Also some functions may be better than the PUT level   due to the addition of RSUs and individual PTFs. In general the   following is valid.


--------------------------------------------------------------------------------------------------------------------------------------


Table_01: Table_ z/OS 2.4 May 2020 Edition - PUT2003 / RSU2003 Volser
B4RES1     756,168,920       8,539,292,672     RES Volume 1 - Required for IPL
B4RES2     683,581,956       8,539,292,672     RES Volume 2 - Required for IPL
B4CFG1     21,740,948        8,539,292,672     Configuration Volume 1 - holds configuration files
B4SYS1     287,179,114       8,539,292,672     System Volume - Required for IPL
B4USS1     2,577,489,123     8,539,292,672     UNIX System Services - Required for IPL
B4USS2     1,035,650,126     8,539,292,672     UNIX System Services - Required for IPL
B4USR1     10,056,624        8,539,292,672     SMS Volume used for large data sets
B4PRD1     3,743,972,406     8,539,292,672     z/OS Products - Required to run individual products
B4PRD2     4,519,198,405     8,539,292,672     z/OS Products - Required to run individual products
B4PRD3     4,325,948,736     8,539,292,672     z/OS Products - Required to run individual products
B4PRD4     1,512,726,922     8,539,292,672     z/OS Products - Required to run individual products
B4DIS1     2,582,793,165     8,539,292,672     Distribution Volume 1
B4DIS2     789,508,250       8,539,292,672     Distribution Volume 2
B4DIS3     86,774,054        8,539,292,672     Distribution Volume 3
B4PAGA     578,375,144       8,539,292,672     Page Volume 1 (PLPA, Common and Local)
B4PAGB     545,124,940       8,539,292,672     Page Volume 2 (Local)
B4PAGC     443,992,902       8,539,292,672     Page Volume 3 (Local)
B4ZCX1     1,449,213,052     8,539,292,672     zCX Container Volume SMS Managed
SARES1     474,899,448       8,539,292,672     Stand Alone RES

Table_02: Table_ IMS V14.1.0 - PUT2003 / RSU2003 Volser
B4IME1     292,767,294       8,539,292,672     IBM Information Management System 14.1.0

Table_03: Table_ IMS V15.2.0 - PUT2003 / RSU2003 Volser
B4IMF1     699,989,184       8,539,292,672     IBM Information Management System 15.2.0

Table_04: Table_ DB2 V12 - PUT2003 / RSU2003 Volser
B4DBC1     1,525,659,145     8,539,292,672     DB2 for z/OS 12.1.506
B4DBC2     107,140,369       8,539,292,672     DB2 for z/OS 12.1.506
B4DBAR     10,157,845        8,539,292,672     Use to allocate DB2 Archive Logs, Only Download once for DB2 V11

Table_05: Table_ DB2 V11 - PUT2003 / RSU2003 Volser
B4DBB1     1,070,554,081     8,539,292,672     DB2 for z/OS 11.1.0
B4DBB2     213,263,384       8,539,292,672     DB2 for z/OS 11.1.0
B4DBAR     10,157,845        8,539,292,672     Use to allocate DB2 Archive Logs, Only Download once for DB2 V12

Table_06: Table_ CICS V5.4 - PUT2003 / RSU2003 Volser
B4C541     933,591,752       8,539,292,672     CICS Transaction Server for 5.4

Table_07: Table_ CICS V5.5 - PUT2003 / RSU2003 Volser
B4C551     907,285,765       8,539,292,672     CICS Transaction Server for 5.5

Table_08: Table_ WebSphere Application Server ND for z/OS V9.0 - PUT2003 / RSU2003 Volser
B4W901     4,709,212,604     8,539,292,672     WebSphere Application Server for z/OS 9.0.0
B4W902     1,201,344,542     8,539,292,672     WebSphere Application Server for z/OS 9.0.0

Table_09: Table_ Tivoli OMEGAMON v5.5.1 - PUT2003 / RSU2003 Volser
B4KAN1     616,487,860       8,539,292,672     Tivoli OMEGAMON for z/OS 5.5.1

Table_10: Table_ IBM engineering Workflow Management V7.0.0 - PUT2003 / RSU2003 Volser
B4BLZ1     1,481,626,014     8,539,292,672     IBM engineering Workflow Management V7.0.0

Table_11: Table_ IBM Installation Manager 1.8.9 - PUT2003 / RSU2003 Volser
B4INM1     3,790,368,588     8,539,292,672     IBM Installation Manager 1.8.9

Table_12: Table_ IBM z Distribution ZOWE V1.10.0 - PUT2003 / RSU2003 Volser
B4ZWE1     956,591,239       8,539,292,672     IBM z Distribution ZOWE V1.10.0



发表评论: