JES3 Datasets are not Cataloged

//S1      EXEC PGM=IDCAMS
//SYSPRINT  DD SYSOUT=*
//SYSIN     DD *
  DEFINE NVSAM (NAME( SYS1.JES3CKP1  ) DEVT(3390) VOL(S4RES2) )-
     CATALOG(CATALOG.OS390.MASTER)
  DEFINE NVSAM (NAME( SYS1.JES3CKP2  ) DEVT(3390) VOL(S4RES2) )-
     CATALOG(CATALOG.OS390.MASTER)
  DEFINE NVSAM (NAME( SYS1.JES3DRDS  ) DEVT(3390) VOL(S4RES2) )-
     CATALOG(CATALOG.OS390.MASTER)
  DEFINE NVSAM (NAME( SYS1.JES3JCT   ) DEVT(3390) VOL(S4RES2) )-
     CATALOG(CATALOG.OS390.MASTER)
  DEFINE NVSAM (NAME( SYS1.JES3OUT   ) DEVT(3390) VOL(S4RES2) )-
     CATALOG(CATALOG.OS390.MASTER)
  DEFINE NVSAM (NAME( SYS1.JES3SNAP  ) DEVT(3390) VOL(S4RES2) )-
     CATALOG(CATALOG.OS390.MASTER)

IMS801 Shutdown with OC1

Upon issue of /che freeze, the IMS system as delivered on the ADCD will end with an OC1. Continue to monitor this site. This problem is being researched and a solution will be forthcoming. During testing no data was damaged or lost and IMS would restart correctly despite the error.

02E Wait state using emulated IO on an MP3000.

At this time the only fix for this problem is to move volumes from emulated disk to physical internal disk, PID. Ref: Installing ADCD z/OS 1.4s on an MP3000. This problem has been reported when IPLing SARES1 in a standalone IPL. Also reported when IPLing using the basic four volumes, s4res1,s4res2,os39m1, and s4uss1.

SMP CSI Zones not Found for CSQ520 and CSQ531

SMP/E CSQ Zones not found

The CSQ CSI datasets for zones CSQ520T,CSQ520D, CSQ530T, and CSQ530D are no longer distributed with the ADCD. However, the zoneindexes are still defined within the MVS global zone. CSQ531 is distributed with the ADCD and is the only MQSeries release that is supported. To correct this problem run the following JCL:



//EDIT1    EXEC PGM=GIMSMP,REGION=48M
//STEPCAT   DD DISP=SHR,DSN=USERCAT.VS4RES2
//STEPLIB   DD DISP=SHR,UNIT=3390,VOL=SER=S4RES1,
//             DSN=SYS1.MIGLIB
//SMPCSI   DD DISP=SHR,DSN=MVS.GLOBAL.CSI
//SMPPTFIN DD DUMMY
//SMPHOLD  DD DUMMY
//SMPLOG   DD DUMMY
//SMPOUT   DD SYSOUT=*
//SMPRPT   DD SYSOUT=*
//SMPLOGA  DD DUMMY
//SMPCNTL  DD *
    SET BDY(GLOBAL).
    UCLIN .
    DEL GLOBALZONE
        ZONEINDEX(
        (CSQ520T)
        (CSQ520D)
        (CSQ530T)
        (CSQ530D) ) .
    ENDUCL  .

Product Libraries Commented Out in JES2 PROC.

The PROC00 DD statement in the JES2 proc was distributed as follows. Various product procedure (i.e. complier procedures) will fail with procedure not found conditions. It is suggested that the comments be removed followed by an IPL to pick up all the available procedures.

//PROC00    DD   DSN=USER.PROCLIB,DISP=SHR
//          DD   DSN=ADCD.ZOSV14S.PROCLIB,DISP=SHR
//          DD   DSN=CEE.SCEEPROC,DISP=SHR
//          DD   DSN=CSQ531.SCSQPROC,DISP=SHR
//          DD   DSN=EUV.SEUVPRC,DISP=SHR
//          DD   DSN=IOE.SIOEPROC,DISP=SHR
//          DD   DSN=EOY.SEOYPROC,DISP=SHR
//          DD   DSN=HLA.SASMSAM1,DISP=SHR
//          DD   DSN=CBC.SCBCPRC,DISP=SHR
//          DD   DSN=CBC.SCCNPRC,DISP=SHR
//          DD   DSN=IGY310.SVSC.PROCLIB,DISP=SHR
//          DD   DSN=IEL310.SVSC.PROCLIB,DISP=SHR
//          DD   DSN=FAN130.SVSC.PROCLIB,DISP=SHR
//          DD   DSN=SYS1.PROCLIB,DISP=SHR

Problems with Migration Utility

• In Job MGCATLG the following datasets are in error and should be removed from the job.
• Step 3
  SYS1.DDIR.D and SYS1.DDIR.I files will be created on first use of IPCS
• Step 4
  IBMUSER.SPFLOG1.LIST duplicate due to being logged on to IBMUSER
• In MGCATLG in STEP 6 SYS1.PARMLIB should be placed on volume (S4RES1) instead of &sysr1. At IPL SYS1.PARMLIB is referenced before the &sysr1 symbol is resolved. You may see message IGGN505A at IPL if this is not done. You can continue with the IPL by responding with an enter but it is best to correct the volume parameter in the master catalog.
• In job MGCATLG in STEP 7 the define alias for CSQ530 should be changed to CSQ531. Without this change, a subsequent IPL may have JCL error in JES2 startup and (abend=S023) in linklst look aside startup.
• In the optional job MGOPT2 step FORM (last step), change steplib to the following:

  //STEPLIB  DD  DSN=CSQ531.SCSQANLE,DISP=SHR,UNIT=3390,VOL=SER=S4RES1
  //         DD  DSN=CSQ531.SCSQAUTH,DISP=SHR,UNIT=3390,VOL=SER=S4RES1
  

RRS Abends Causing DB2 Connect to fail.

At RRS startup the following abend may occur. Especially true if migration was performed.

DUMPID=001 REQUESTED BY JOB (RRS     )
DUMP TITLE=COMPON=LOGGER,COMPID=5752SCLOG,ISSUER=IXGR1REC,MODUL
           E=IXGA1MM ,ABEND=S01C5,REASON=00000804
IXG063I LOGGER ABENDED AND REQUESTED AN SVC DUMP WHILE PROCESSING 644
LOGSTREAM: ATR.ADCDPL.RM.DATA
STRUCTURE: **UNKNOWN**
MODULE=IXGA1MM ,ABEND=S01C5,REASON=00000804
ATR203I RRS COULD NOT READ FROM THE RM DATA LOG.
ATR138I ATTEMPT TO BRING UP RRS FAILED, DIAG =00000008
ATR215I RRS ENCOUNTERED AN ERROR READING LOGSTREAM 645
ATR.ADCDPL.RM.DATA RETURN CODE: 00000008 REASON CODE: 80800000
DIAGNOSTIC INFORMATION: 00000000 00000000 04010020 00000000



As a result of the RRS abend, DB2 Connect will also abend as follows. IMS Connect will fail with a similar abend.



IWM034I PROCEDURE DSN1WLM1 STARTED FOR SUBSYSTEM DSN1 961
APPLICATION ENVIRONMENT WLMENV1
PARAMETERS DB2SSN=DSN1,NUMTCB=2,APPLENV='WLMENV1'
£HASP100 DSN1WLM1 ON STCINRDR
£HASP373 DSN1WLM1 STARTED
IEF403I DSN1WLM1 - STARTED - TIME=04.15.58
+DSNX982I  DSNX9WLM ATTEMPT TO PERFORM RRS ATTACH FUNCTION SPAS_ID 965
        FAILED WITH RRS RC = 00000008 RSN = 00F30091 SSN = DSN1
 PROC= DSN1WLM1 ASID = 0032 WLM_ENV = WLMENV1



To correct this error run the following jobs in order.
• SYS1.P390.CNTL(RRSDELLS) - Will delete the rrs logstream datasets
• SYS1.P390.CNTL(RRSLOGST) - Will build the rrs logstream datasets
• S RRS - Restart RRS

During SMP/E processing, various errors occur with datasets having vol=ser=Vxxxxx. Error in DDDEF info on SMP/E CSI's.

The base system used in creating the ADCD contained hard coded volume data in the SMP/E DDDEF entries. The ADCD build step to remove the entries was not run correctly before the final cd's were cut. Run the following JCL to remove the volser info.

//EDIT1    EXEC PGM=GIMSMP,REGION=48M
//STEPCAT   DD DISP=SHR,DSN=USERCAT.VS4RES2
//STEPLIB   DD DISP=SHR,UNIT=3390,VOL=SER=S4RES1,
//             DSN=SYS1.MIGLIB
//SMPCSI   DD DISP=SHR,DSN=JVA130.GLOBAL.CSI  .....point to the desired csi
//SMPPTFIN DD DUMMY
//SMPHOLD  DD DUMMY
//SMPLOG   DD DUMMY
//SMPOUT   DD SYSOUT=*
//SMPRPT   DD SYSOUT=*
//SMPLOGA  DD DUMMY
//SMPCNTL  DD *
//SMPCNTL  DD *
     SET BDY(GLOBAL) .
       ZONEEDIT DDDEF.
       CHANGE VOLUME(*,*) .
       CHANGE UNIT(*,*) .
     ENDZONEEDIT.
    RESETRC.
         SET BDY(JVA130T) .        /* CHANGE -zone name- */
           ZONEEDIT DDDEF.
           CHANGE PATH('/sysc/usr/'*,
                       '/usr/'*).
           CHANGE UNIT(*,*) .
           CHANGE VOLUME(*,*) .
         ENDZONEEDIT.
        RESETRC.
         SET BDY(JVA130D) .        /* CHANGE -zone name- */
          ZONEEDIT DDDEF.
          CHANGE UNIT(*,*) .
          CHANGE VOLUME(*,*) .
        ENDZONEEDIT.

Build Structure




S4RES1

This 3390-3 volume 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. This release uses the extended indirect catalog feature with &SYSR1 in the master catalog.

This volume is set up in the DEVMAP (Device Map) as address A80. When initially unzipped, the device appears as follows on the OS/2 emulated disk:

Table 1. File Size


S4RES1_1.A80		2,147,397,632 bytes
S4RES1_2.A80		699,034,112 bytes

S4RES2

This 3390-3 volume is an extension of the SYSRES volume S4RES1. It is also required for IPL. The release utilizes the extended indirect cataloging feature with &SYSR2 in the master catalog. The volume contains the usercatalog for z/OS and related products.

This volume is set up in the DEVMAP (Device Map) as address A81. When initially unzipped, the device appears as follows on the OS/2 emulated disk:


Table 2. File Size


S4RES2_1.A81		2,147,397,632 bytes
S4RES2_2.A81		699,034,112 bytes

S4DIS1, S4DIS2, S4DIS3, & S4DIS4

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

S4DIS1 volume is set up in the DEVMAP as address A85. This volume is a 3390-3.

S4DIS2 volume is set up in the DEVMAP as address A86. This volume is a 3390-3

S4DIS3 volume is set up in the DEVMAP as address A88. This volume is a 3390-3.

S4DIS4 volume is set up in the DEVMAP as address A8D. This volume is a 3390-3.

When initially unzipped, the devices appear as follows on the OS/2 emulated disk:


Table 3. File Size


S4DIS1_1.A85		2,147,397,632 bytes
S4DIS1_2.A85		699,034,112 bytes
S4DIS2_1.A86		2,147,397,632 bytes
S4DIS2_2.A86		699,034,112 bytes
S4DIS3_1.A88		2,147,397,632 bytes
S4DIS3_2.A88		699,034,112 bytes
S4DIS3_1.A8D		2,147,397,632 bytes
S4DIS4_2.A8D		699,034,112 bytes

S4USS1

This 3390-3 volume contains all HFS files for UNIX SYSTEM SERVICES of ZOS and other products. This volume is required to IPL.

This volume is set up in the DEVMAP as address A87. When initially unzipped, the device appears as follows on the OS/2 emulated disk:


Table 4. File Size


S4USS1_1.A87		2,147,397,632 bytes
S4USS1_2.A87		699,034,112 bytes

OS39M1

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.PARMLIB, the RACF database, the MVS IODF (I/O Definition File), and system's master catalog (CATALOG.OS390.MASTER) reside on this volume. This volume is required to IPL.

This volume is set up in the DEVMAP as address A82. When initially unzipped, the device appears as follows on the OS/2 emulated disk:


Table 5. File Size


OS39M1_1.A82		2,147,397,632 bytes
OS39M1_2.A82		699,034,112 bytes

S4DB21

This 3390-3 volume contains the DB2 system software target and distribution libraries. This volume also contains the SMP/E Target and DLIB zone CSIs for these products. The volume contains the usercatalog for DB2 and related products. This volume need not be present to IPL, but is needed to use DB2.

This volume is set up in the DEVMAP as address A83.
When initially unzipped, the device appears as follows on the OS/2 emulated disk:

Table 6. File Size


S4DB21_1.A83		2,147,397,632 bytes
S4DB21_2.A83		699,034,112 bytes

S4CIC1

This 3390-2 volume contains the target and distribution libraries for CICS. This volume also contains the SMP/E Target and DLIB zone CSIs for the CICS product. The volume contains the usercatalog for CICS and related products. This volume need not be present to IPL, but is needed to use the CICS product. When initially unzipped, the device appears as follows on the OS/2 emulated disk:

This volume is set up in the DEVMAP as address A84.


Table 7. File Size


S4CIC1.A84		1,897,620,992 bytes

S4IMS1

This 3390-2 volume contains the system software target and distribution libraries for IMS. This volume also contains the SMP/E Target a nd DLIB zone CSIs for the IMS product. The volume contains the usercatalog for IMS and related products. This volume need not be present to IPL, but is needed to use the IMS product.

This volume is set up in the DEVMAP as address A89. When initially unzipped, the device appears as follows on the OS/2 emulated disk:


Table 7. File Size


S4IMS1.A89		1,897,620,992 bytes

S4WAS1

This 3390-3 volume contains the product system software distribution libraries for Websphere. This volume also contains the SMP/E Target and DLIB zone CSIs for the product. This volume need not be present to IPL, but is needed to use Websphere 4.0.1 This volume is set up in the DEVMAP as address A8A. When initially unzipped, the device appears as follows on the OS/2 emulated disk:

Table 8. File Size


S4WAS1_1.A8A		2,147,397,632 bytes
S4WAS1_2.A8A		699,034,112 bytes

S4WAS2

This 3390-3 volume contains the product system software target libraries for Websphere. The volume contains the usercatalog for WAS and related products. This volume need not be present to IPL, but is needed to use Websphere 4.0. This volume is set up in the DEVMAP as address A8B. When initially unzipped, the device appears as follows on the OS/2 emulated disk:


Table 9. File Size


S4WAS2_1.A8B		2,147,397,632 bytes
S4WAS2_2.A8B		699,034,112 bytes

SARES1

This 3390-3 volume contains a complete 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, copy to physical internal disk (PID), 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: 03xx
Load Parms: 03xxSAM

Reply 0,sysp=sa



The load and loadparm address are the location of the SARES1 volume. On some MP3000 systems, a 02E abend occurs at IPL when using an emulated disk volume for IPL address. Thus SARES1 should be permanently resident on a physical internal disk on an MP3000.

This volume is set up in the DEVMAP as address A8C. When initially unzipped, the device appears as follows on the OS/2 emulated disk:


Table 10. File Size


SARES1_1.A8C		2,147,397,632 bytes
SARES1_2.A8C		699,034,112 bytes

---

SYSTEM 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 S4RES1, S4RES2, S4DIS1, S4DIS2, S4DIS3, S4DIS4, and S4USS1. These volumes are intended to be replaced. You should try to use alternatives to updating these volumes when possible.

  All changes to these volumes will be **LOST** when they are replaced. You should keep a record of any changes made to them, and back-up your system on a regular scheduled basis.

• When you get new levels of the system software, you may choose whether or not to replace OS39M1. We expect that most people will choose not to replace this volume. Jobs are provided for updating OS39M1 to reflect the new system in dataset ADCD.ZOSV14S.MIGRATE.

Standard Library Concatenation

The ADCD is distributed with a standard library concatenation of 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.ZOSV14S.LINKLIB

SYS1.LINKLIB

USER.xxxxx libraries have all been built on OS39M1 which is the only volume that is migrated ADCD Migration

USER.xxxxx will not be changed by ADCD or System processes; thus, user updates in USER.xxxxx will be retained between release levels. ADCD.ZOSV14S.xxxxxx libraries are allocated on S4RES1 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. In addition changes to ADCD.ZOSV14S.xxxxxxx libraries could be lost upon upgrade to the next release. SYS1.xxxxxxx libraries should NEVER be updated by users or ADCD development. System libraries should ONLY be updated through SMP/E install and maintenance processes.

PLEASE 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.

CD-ROM Installation on MP3000

Assumptions:

• A prior release to ADCD z/OS 1.4s is installed and running on the MP/3000 or use Stand-Alone res pack found on cd 13.



• The prior release is installed on the MP/3000 physical internal disk.



• The emulated disk storage has at least 12 GB of free storage. Note: The following process consist of four stages. If 12 GB of emulated disk are not available the number of stages could be increased with fewer disk loaded per stage.



• At least 14 physical internal disk are available for use. This process uses addresses 310-31D for installation of ADCD z/OS. Other addresses can be substituted if necessary.



• CD-ROM drive is H: and emulation disk access is G:



• Each of the following steps take from 10-20 minutes to execute depending on MP3000 model.



• Knowledge on use of TSO/ISPF editor and SDSF. This process requires the editing/submission of JCL, the checking of output via SDSF utility, and responding to console messages.



• Knowledge on use of SASE panels. This process requires the deactivation/activation of profiles, draging/droping operations, and IPL.

Stage 1:

Bring down any IPLed system. Deactivate the profile.

Insert disk 1 into the CD-ROM drive. From OS2 window on the SASE,

Enter H:

Enter cd1



Insert disk 2 into the CD-ROM drive. From OS2 window on the SASE

Enter cd2



Insert disk 3 into the CD-ROM drive. From OS2 window on the SASE

Enter cd3



Insert disk 4 into the CD-ROM drive. From OS2 window on the SASE

Enter cd4



Build Device Map

The device map can be loaded by the following two methods:



• Copy the distributed devmap from CD1
  
  From CD1 the file h:\devmap.dvm can be copied to the appropriate d:\iocp file. Select the device map in d:\iocp that matches the desired activation profile. For example if you are using PROFILEA1 then your will need to work with d:\iocp\awsmapa1.dvm. First copy the desired devmap to a backup i.e. copy d:\iocp\awsmapa1.dvm d:\iocp\awsmapa1.bak. Secondly copy from CD 1 h:\devmap.dvm to d:\iocp\awsmapa1.dvm. Using the EMIO icon on the SASE you can eliminate entries that you will not be using. For example, if you do not intend to install IMS (CD 10) you can remove the entry for S4IMS1.A89. You must now activate the profile to bring in the devmap changes.



• Manually update the devmap.
  
  From SASE console access the CPC Configuration panel. Drag /Drop CPC to Emulated IO. At the bottom of the panel is a note regarding which DEVMAP file was last copied to the active device map. Select that devmap file from the list i.e. D:\iocp\awsmapa1.dvm. Using F2 Update System Devices, make changes to the device map. If no previous device information exist or if you desire to delete the old entires and start over, it is recommended that you copy the devmap as described above. You can enter the following information on the first line of the panel but for volumes that have not been previously allocated (at this stage only A0-A3 have been allocated), the configurated will format an empty OS2 file that will have to be deleted before you unzip from the CD. The format process will also take 10-15 min for each volume; thus, entering new data on the first line of the configurator panel is not recommended. If you have existing definitions from a previous release, you can simply change the Fn/P information to point to the new file. If the file is allocated the remaining info will change to reflect the attributes of the new file.
  
  NOTE: Due to the size limitations of the MP3000 emulated disk, the devmap should be updated manually in stages. If you manually update the devmap, it is recommended that you build the necessary emulated files in stages to match the copy stages below. At the end of each stage the files can be deleted either via OS/2 erase or through the delete process of the devmap configurator. If the files are deleted via OS/2 erase the definitions will stay in the configurator but the OS/2 space will be available for other file allocations.
  
  




Addr	Device	Label	Atype	Size	Mgr	Fn/P
A0	3390	S4RES1	CKD	3339C	2	g:\zos14\S4RES1_1.a80





Addr	Device	Label	Atype	Size	Mgr	Fn/P
A1	3390	S4RES2	CKD	3339C	2	g:\zos14\S4RES2_1.a81





Addr	Device	Label	Atype	Size	Mgr	Fn/P
A2	3390	OS39M1	CKD	3339C	2	g:\zos14\os39M1_1.a82





Addr	Device	Label	Atype	Size	Mgr	Fn/P
A3	3390	S4DB21	CKD	3339C	2	g:\zos14\S4DB21_1.a83





Addr	Device	Label	Atype	Size	Mgr	Fn/P
A4	3390	S4CIC1	CKD	2226C	2	g:\zos14\S4CIC1.a84





Addr	Device	Label	Atype	Size	Mgr	Fn/P
A5	3390	S4DIS1	CKD	3339C	2	g:\zos14\S4DIS1_1.a85




Addr	Device	Label	Atype	Size	Mgr	Fn/P
A6	3390	S4DIS2	CKD	3339C	2	g:\zos14\S4DIS2_1.a86





Addr	Device	Label	Atype	Size	Mgr	Fn/P
A7	3390	S4USS1	CKD	3339C	2	g:\zos14\S4USS1_1.a87





Addr	Device	Label	Atype	Size	Mgr	Fn/P
A8	3390	S4DIS3	CKD	3339C	2	g:\zos14\S4DIS3_1.a88





Addr	Device	Label	Atype	Size	Mgr	Fn/P
A9	3390	S4IMS1	CKD	2226C	2	g:\zos14\S4IMS.a89





Addr	Device	Label	Atype	Size	Mgr	Fn/P
AA	3390	S4WAS1	CKD	3339C	2	g:\zos14\S4WAS1_1.a8A





Addr	Device	Label	Atype	Size	Mgr	Fn/P
AB	3390	S4WAS2	CKD	3339C	2	g:\zos14\S4WAS2_1.a8b





Addr	Device	Label	Atype	Size	Mgr	Fn/P
AC	3390	SARES1	CKD	3339C	2	g:\zos14\SARES1_1.a8c





Addr	Device	Label	Atype	Size	Mgr	Fn/P
AD	3390	S4DIS4	CKD	3339C	2	g:\zos14\S4DIS4_1.a8d

Use F10 and F6 keys to save above changes to the devmap.



Obtain the new devmap.

From SASE console access Daily panel. First deactivate the existing profile. Secondly activate the new profile. The devmap file must match the IOCDS in the profile i.e. if D:\iocp\awsmapa1.dvm is used, then A1 must be the active IOCDS file in the profile

IPL with new device map

IPL the previous release of z/OS with the new devmap in order to pick up the new definitions for emulated IO.

Note: If you are using stand alone res, bypass the following reformat step and change the copy statement below to OS39M1 from XS39M1. If you are not using stand alone res, OS39M1 will be a duplicate to the previous release and use the following procedure to reformat the new release OS39M1 volume. At IPL you need to respond in order to place A82 offline. A82 will be handled in the following step.

Reformat A82.

Reformat A82 label OS39M1 to XS39M1. This is necessary in order to vary the new OS39M1 online in order to copy the volume.

//REFMDSK JOB MSGLEVEL=(1,1),REGION=6000K,MSGCLASS=H,NOTIFY=&SYSUID
//********************************************************************
//*  REFORMAT OS39M1 device to XS39M1
//********************************************************************
//ICKDSF   EXEC PGM=ICKDSF,REGION=4096K
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
    REFORMAT UNITADDRESS(0A82) VERIFY(OS39M1) VOLID(XS39M1)

Vary A82,online

Initialize Volumes

Inspect unit addresses A80-A82 and A87. Should have volumes S4RES1, S4RES2, XS39M1, and S4USS1 respectively mounted. Vary 310-312,offline and vary 317,offline (or selected addresses for moving to physical internal drives).

Logon to TSO/ISPF. Use the following JCL to initialize the first set of internal disk.

//DSFINIT JOB  'INIT  L744',CLASS=A,MSGCLASS=H,MSGLEVEL=(1,1),
//        REGION=4M,TIME=1440,NOTIFY=&SYSUID
//**************************************************************
//* THIS IS AN EXAMPLE OF A JOB THAT WILL
//*  INITIALIZE AND LABEL A DASD VOLUME
//*
//**************************************************************
//ICKDSF  EXEC PGM=ICKDSF,REGION=4096K
//SYSPRINT  DD SYSOUT=*
//SYSIN     DD *
 INIT UNIT(310) NOVALIDATE NVFY VOLID(DSK310) PURGE -
     VTOC(0,1,30)
 INIT UNIT(311) NOVALIDATE NVFY VOLID(DSK311) PURGE -
     VTOC(0,1,30)
 INIT UNIT(312) NOVALIDATE NVFY VOLID(DSK312) PURGE -
     VTOC(0,1,30)
 INIT UNIT(317) NOVALIDATE NVFY VOLID(DSK317) PURGE -
     VTOC(0,1,30)
//

Respond to console messages with r xx,u to initialize the disk. Caution: be sure to validate that useful data is not being overwritten.

V 310-312,online and v 317,online

Copy Volumes.

Logon to TSO/ISPF. Use the following JCL to copy to internal disk.

//COPYDSK JOB MSGLEVEL=(1,1),REGION=6000K,MSGCLASS=H,NOTIFY=&SYSUID
//********************************************************************
//*  COPY JOB FROM TO
//********************************************************************
//STEP1       EXEC PGM=ADRDSSU,REGION=6000K
//SYSPRINT DD SYSOUT=*
//DASDIN   DD UNIT=3390,VOL=SER=S4RES1,DISP=SHR
//DASDOUT  DD UNIT=3390,VOL=SER=DSK310,DISP=SHR
//SYSIN    DD *
  COPY INDD(DASDIN) OUTDD(DASDOUT) -
  ADMIN COPYV
//STEP2  EXEC PGM=ADRDSSU,REGION=6000K
//SYSPRINT DD SYSOUT=*
//DASDIN   DD UNIT=3390,VOL=SER=S4RES2,DISP=SHR
//DASDOUT  DD UNIT=3390,VOL=SER=DSK311,DISP=SHR
//SYSIN    DD *
  COPY INDD(DASDIN) OUTDD(DASDOUT) -
  ADMIN COPYV
//STEP3             EXEC PGM=ADRDSSU,REGION=6000K                       ;          
//SYSPRINT DD       SYSOUT=*
//DASDIN   DD UNIT=3390,VOL=SER=XS39M1,DISP=SHR
//DASDOUT  DD UNIT=3390,VOL=SER=DSK312,DISP=SHR
//SYSIN    DD *
  COPY INDD(DASDIN) OUTDD(DASDOUT) -
  ADMIN COPYV
//STEP4  EXEC PGM=ADRDSSU,REGION=6000K
//SYSPRINT  DD SYSOUT=*
//DASDIN    DD UNIT=3390,VOL=SER=S4USS1,DISP=SHR
//DASDOUT   DD UNIT=3390,VOL=SER=DSK317,DISP=SHR
//SYSIN     DD *
  COPY INDD(DASDIN) OUTDD(DASDOUT) -
  ADMIN COPYV





Reformat 312.

Reformat 302 label XS39M1 to OS39M1.

//REFMDSK JOB MSGLEVEL=(1,1),REGION=6000K,MSGCLASS=H,NOTIFY=&SYSUID
//********************************************************************
//*  REFORMAT OS39M1 device to XS39M1
//********************************************************************
//ICKDSF   EXEC PGM=ICKDSF,REGION=4096K
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
    REFORMAT UNITADDRESS(0312) VERIFY(XS39M1) VOLID(OS39M1)

This completes stage 1.

The basic ADCD z/OS 1.4 system can be ipled at this time using load address 310 and Loadparm 312csm.

Stage 2:

Bring down any IPLed system. Deactivate the profile.

Build DLIB volume, S4DIS1.

S4DIS1 is a distribution volume. If you do not apply SMP maintenance to your system, do not load this volume.

Insert disk 5 into the CD-ROM drive. From OS2 window on the SASE

Enter h:

Enter cd5



Build DLIB volume, S4DIS2

S4DIS2 is a distribution volume. If you do not apply SMP maintenance to your system, do not load this volume.

Insert disk 6 into the CD-ROM drive. From OS2 window on the SASE

Enter cd6



Build DLIB volume, S4DIS3.

S4DIS3 is a distribution volume. If you do not apply SMP maintenance to your system, do not load this volume.

Insert disk 7 into the CD-ROM drive. From OS2 window on the SASE

Enter cd7



Copy DB2 volume, S4DB21.

S4DB21 is a DB2 volume. If you are not using DB2, do not load this volume.

Insert disk 8 into the CD-ROM drive. From OS2 window on the SASE

Enter cd8

IPL with new device map

IPL the previous release of z/OS with the new devmap in order to pick up the new definitions for emulated IO.

Initialize Volumes

Inspect emulation IO disk. Addresses A83, A85, A86, and A88 should have volumes S4DB21, S4DIS1, S4DIS2, and S4DIS3 respectively mounted. Vary 313,offline, vary 315-316,offline, vary 318,offline (or selected addresses for moving to physical internal drives).

Logon to TSO/ISPF. Use the following JCL to initialize the disk volumes.

//DSFINIT JOB  'INIT   L744',CLASS=A,MSGCLASS=H,MSGLEVEL=(1,1),
//        REGION=4M,TIME=1440,NOTIFY=&SYSUID
//**************************************************************
//* THIS IS AN EXAMPLE OF A JOB THAT WILL:
//* INITIALIZE AND LABEL A DASD VOLUME
//**************************************************************
//ICKDSF  EXEC PGM=ICKDSF,REGION=4096K
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
 INIT UNIT(313) NOVALIDATE NVFY VOLID(DSK313) PURGE -
     VTOC(0,1,30)
 INIT UNIT(315) NOVALIDATE NVFY VOLID(DSK315) PURGE -
     VTOC(0,1,30)
 INIT UNIT(316) NOVALIDATE NVFY VOLID(DSK316) PURGE -
     VTOC(0,1,30)
 INIT UNIT(318) NOVALIDATE NVFY VOLID(DSK318) PURGE -
     VTOC(0,1,30)
//

Respond to console messages with r xx,u to initialize the disk. Caution: be sure to validate that useful data is not being overwritten.

V 313,online,V 315-316,online,v 318,online

Copy Volumes.

Logon to TSO/ISPF. Use the following JCL to copy the disk volumes.

//COPYDSK JOB MSGLEVEL=(1,1),REGION=6000K,MSGCLASS=H,NOTIFY=&SYSUID
//********************************************************************
//* COPY JOB FROM TO
//********************************************************************
//STEP1  EXEC PGM=ADRDSSU,REGION=6000K
//SYSPRINT DD SYSOUT=*
//DASDIN   DD UNIT=3390,VOL=SER=S4DIS1,DISP=SHR
//DASDOUT  DD UNIT=3390,VOL=SER=DSK315,DISP=SHR
//SYSIN    DD *
  COPY INDD(DASDIN) OUTDD(DASDOUT) -
  ADMIN COPYV
//STEP2  EXEC PGM=ADRDSSU,REGION=6000K
//SYSPRINT DD SYSOUT=*
//DASDIN   DD UNIT=3390,VOL=SER=S4DIS2,DISP=SHR
//DASDOUT  DD UNIT=3390,VOL=SER=DSK316,DISP=SHR
//SYSIN    DD *
  COPY INDD(DASDIN) OUTDD(DASDOUT) -
  ADMIN COPYV
//STEP3  EXEC PGM=ADRDSSU,REGION=6000K
//SYSPRINT DD SYSOUT=*
//DASDIN   DD UNIT=3390,VOL=SER=S4DIS3,DISP=SHR
//DASDOUT  DD UNIT=3390,VOL=SER=DSK318,DISP=SHR
//SYSIN    DD *
  COPY INDD(DASDIN) OUTDD(DASDOUT) -
  ADMIN COPYV
//STEP4  EXEC PGM=ADRDSSU,REGION=6000K
//SYSPRINT DD SYSOUT=*
//DASDIN   DD UNIT=3390,VOL=SER=S4DB21,DISP=SHR
//DASDOUT  DD UNIT=3390,VOL=SER=DSK313,DISP=SHR
//SYSIN    DD *
  COPY INDD(DASDIN) OUTDD(DASDOUT) -
  ADMIN COPYV

This completes stage 2.

Stage 3:

Bring down any IPLed system. Deactivate the profile.

Build CICS volume, S4CIC1.

S4CIC1 is a CICS volume. If you are not using CICS, you will not need to load this volume.

Insert disk 9 into the CD-ROM drive. From OS2 window on the SASE

Enter h:

Enter cd9

Build IMS volume, S4IMS1.

S4IMS1 is a IMS volume. If you are not using IMS, you will not need to load this volume.

Insert disk 10 into the CD-ROM drive. From OS2 window on the SASE

Enter cd10

Build WAS volume, S4WAS1

S4WAS1 is the distribution libraries of Websphere Application Server (WAS). If you are not using WAS, you will not need to load this volume

Insert disk 11 into the CD-ROM drive. From OS2 wind ow on the SASE

Enter cd11

Build WAS volume, S4WAS2.

S4WAS2 is Websphere Application Server (WAS). If you are not using WAS, you will not need to load this volume.

Insert disk 12 into the CD-ROM drive. From OS2 wind ow on the SASE

Enter cd12

IPL with new device map

IPL the previous release of z/OS with the new devmap in order to pick up the new definitions for emulated IO.

Initialize Volumes

Inspect unit addresses A84 and A89-A8b. Should have volumes S4CIC1, S4IMS1, S4WAS1, and S4WAS2 respectively mounted. Vary 314,offline, vary 319-31B ,offline (or selected addresses for moving to physical internal drives).

Logon to TSO/ISPF. Use the following JCL to initialize the disk volumes.

//DSFINIT JOB  'INIT   L744',CLASS=A,MSGCLASS=H,MSGLEVEL=(1,1),
//        REGION=4M,TIME=1440,NOTIFY=&SYSUID
//****************************************************************
//* THIS IS AN EXAMPLE OF A JOB THAT WILL:
//* INITIALIZE AND LABEL A DASD VOLUME
//****************************************************************
//ICKDSF EXEC PGM=ICKDSF,REGION=4096K
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
 INIT UNIT(318) NOVALIDATE NVFY VOLID(DSK318) PURGE -
     VTOC(0,1,30)
 INIT UNIT(319) NOVALIDATE NVFY VOLID(DSK319) PURGE -
     VTOC(0,1,30)
 INIT UNIT(31A) NOVALIDATE NVFY VOLID(DSK31A) PURGE -
     VTOC(0,1,30)
 INIT UNIT(31B) NOVALIDATE NVFY VOLID(DSK31B) PURGE -
     VTOC(0,1,30)
//

Respond to console messages with r xx,u to initialize the disk. Caution: be sure to validate that useful data is not being overwritten.

v 314,online and V 319-31B,online

Copy Volumes.

Logon to TSO/ISPF. Use the following JCL to copy the disk volumes.

//COPYDSK JOB MSGLEVEL=(1,1),REGION=6000K,MSGCLASS=H,NOTIFY=&SYSUID
//********************************************************************
//* COPY
//********************************************************************
//STEP1  EXEC PGM=ADRDSSU,REGION=6000K
//SYSPRINT DD SYSOUT=*
//DASDIN   DD UNIT=3390,VOL=SER=S4CIC1,DISP=SHR
//DASDOUT  DD UNIT=3390,VOL=SER=DSK314,DISP=SHR
//SYSIN    DD *
  COPY INDD(DASDIN) OUTDD(DASDOUT) -
  ADMIN COPYV
//STEP2  EXEC PGM=ADRDSSU,REGION=6000K
//SYSPRINT DD SYSOUT=*
//DASDIN   DD UNIT=3390,VOL=SER=S4IMS1,DISP=SHR
//DASDOUT  DD UNIT=3390,VOL=SER=DSK319,DISP=SHR
//SYSIN    D  *
  COPY INDD(DASDIN) OUTDD(DASDOUT) -
  ADMIN COPYV
//STEP3  EXEC PGM=ADRDSSU,REGION=6000K
//SYSPRINT DD SYSOUT=*
//DASDIN   DD UNIT=3390,VOL=SER=S4WAS1,DISP=SHR
//DASDOUT  DD UNIT=3390,VOL=SER=DSK31A,DISP=SHR
//SYSIN    D  *
  COPY INDD(DASDIN) OUTDD(DASDOUT) -
  ADMIN COPYV
//STEP2  EXEC PGM=ADRDSSU,REGION=6000K
//SYSPRINT DD SYSOUT=*
//DASDIN   DD UNIT=3390,VOL=SER=S4WAS2,DISP=SHR
//DASDOUT  DD UNIT=3390,VOL=SER=DSK31B,DISP=SHR
//SYSIN    D  *
  COPY INDD(DASDIN) OUTDD(DASDOUT) -
  ADMIN COPYV

This completes stage 3.

Bring down any IPLed system. Deactivate the profile.

Build Stand Alone Res volume, SARES1.

SARES1 is not a required volume. However, it is hightly recommended that you load this volume. The volume is necessary for correcting IPL problems with other systems or partitions.

Insert disk 13 into the CD-ROM drive. From OS2 window on the SASE

Enter h:

Enter cd13

1. Build DLIB Volume, S4DIS4.

   S4DIS4 is a distribution volume. If you do not apply SMP maintenance to your system, do not load this volume.

   Insert disk 14 into the CD-ROM drive. From OS2 window on the SASE

   Enter h:
   
   Enter cd14

   IPL with new device map

   IPL the previous release of z/OS with the new devmap in order to pick up the new definitions for emulated IO.

   Initialize Volume

   Inspect unit addresses A8C and A8D. Should have volume SARES1 and S4DIS1 mounted respectively. Vary 31C,offline (or selected addresse for moving to physical internal drives).

   Logon to TSO/ISPF. Use the following JCL to initialize the disk volumes.

   //DSFINIT JOB  'INIT   L744',CLASS=A,MSGCLASS=H,MSGLEVEL=(1,1),
   //        REGION=4M,TIME=1440,NOTIFY=&SYSUID
   //****************************************************************
   //* THIS IS AN EXAMPLE OF A JOB THAT WILL:
   //* INITIALIZE AND LABEL A DASD VOLUME
   //****************************************************************
   //ICKDSF EXEC PGM=ICKDSF,REGION=4096K
   //SYSPRINT DD SYSOUT=*
   //SYSIN    DD *
    INIT UNIT(31C) NOVALIDATE NVFY VOLID(DSK31C) PURGE -
        VTOC(0,1,30)
    INIT UNIT(31D) NOVALIDATE NVFY VOLID(DSK31D) PURGE -
        VTOC(0,1,30)
   //
   

   Respond to console messages with r xx,u to initialize the disk. Caution: be sure to validate that useful data is not being overwritten.

   v 31C-31D,online

   Copy Volumes.

   Logon to TSO/ISPF. Use the following JCL to copy the disk volumes.

   //COPYDSK JOB MSGLEVEL=(1,1),REGION=6000K,MSGCLASS=H,NOTIFY=&SYSUID
   //********************************************************************
   //* COPY
   //********************************************************************
   //STEP1  EXEC PGM=ADRDSSU,REGION=6000K
   //SYSPRINT DD SYSOUT=*
   //DASDIN   DD UNIT=3390,VOL=SER=SARES1,DISP=SHR
   //DASDOUT  DD UNIT=3390,VOL=SER=DSK31C,DISP=SHR
   //SYSIN    DD *
     COPY INDD(DASDIN) OUTDD(DASDOUT) -
     ADMIN COPYV
   //STEP2  EXEC PGM=ADRDSSU,REGION=6000K
   //SYSPRINT DD SYSOUT=*
   //DASDIN   DD UNIT=3390,VOL=SER=S4DIS4,DISP=SHR
   //DASDOUT  DD UNIT=3390,VOL=SER=DSK31D,DISP=SHR
   //SYSIN    DD *
     COPY INDD(DASDIN) OUTDD(DASDOUT) -
     ADMIN COPYV
   

   This completes stage 4.

CD-ROM Installation on Thinkpad or Netfinity using Flex-es

Please consult with your re-seller vendor for the latest instructions on installation in your environment. On cd1 in /flex directory are command files that may make installation easier. Since the cd were zipped a Window/OS2 environment, they will need to be unzipped and converted to flex-es format. The command files will assist in that process.

Migration from ADCD z/OS 1.4 Dec 2002

Please check Problems with Migration Utility prior to running the migration procedure.

  Application Developers -- z/OS Migration Instructions
  _______________________________________________________________

  WHEN TO USE THESE INSTRUCTIONS

  You should use these instructions if you have previously installed
  z/OS Release 4 Application Development System from CD,
  ADCD z/OS 1.4, or have migrated to z/OS Release 4 and do not wish
  want to replace your current OS39M1 volume (which contains most
  or all of your customization).  Note: the ADCD is design to migrate
  only between two consecutive releases.  The following describes
  migration from ADCD z/OS 1.4 to ADCD z/OS 1.4s.

  These instructions assume some basic knowledge of OS/2,
  MVS(z/OS), TSO/E, and ISPF.

  OVERVIEW

  This following structure applies to PROCLIB, PARMLIB,
  LPA, LINKLIB, ISPPLIB, VTAMLIB, VTAMLST, VTAM.SOURCE,
  and CLIST
  Libraries are concatenated with the following structure:
        User.xxxxx    -  Belong to the user, are located on OS39M1
                         and are not migrated between ADCD releases
        ADCD.ZOSxx    -  Belong to the ADCD developers. User changes
                         are not recommended since these libraries are
                         replaced between releases.  The libraries are
                         found on S4RES1.
        SYS1.xxxx     -  Belong to ZOS.  Generally are ZOS target
                         libraries and should be touch only by SMP
                         processing.  These libraries are replaced
                         between ZOS release levels.

  ADCD z/OS 1.4s will replace your current Release 4 volumes.
  OS39M1 is the only exception. S4RES1 and S4RES2 are the new
  Release 4s resident volumes and they are indirectly cataloged
  (S4RES2 uses symbolic &SYSR2 and S4RES1 uses symbolic &SYSR1 for
  SYS1 data sets).

  ADCD z/OS 1.4s consists of the following volumes:

                                          VOLUME   UCB   SIZE
     IPL resident volume ---------------- S4RES1   A80   2.8 GB
     Second resident volume ------------- S4RES2   A81   2.8 GB
     Master catalog, system data sets --- OS39M1   A82   2.8 GB
     DB2 UDB and related products ------- S4DB21   A83   2.8 GB
     CICS Transaction Server ------------ S4CIC1   A84   1.8 GB
     Maintenance Distribution Libraries - S4DIS1   A85   2.8 GB
     Maintenance Distribution Libraries - S4DIS2   A86   2.8 GB
     UNIX System Services files (HFS) --- S4USS1   A87   2.8 GB
     Maintenance Distribution Libraries - S4DIS3   A88   2.8 GB
     IMS/ESA Transaction and DB Server -- S4IMS1   A89   1.8 GB
     Websphere Volume 1 ----------------  S4WAS1   A8B   2.8 GB
     Websphere Volume 2 ----------------- S4WAS2   A8A   2.8 GB
     Standalone IPL Volume -------------- SARES1   A8C   2.8 GB
     Maintenance Distribution Libraries - S4DIS4   A8D   2.8 GB


  The volumes contain new levels of several products you already have
  plus some new products.  Your current copy of OS39M1 will not reflect
  these changes until you run the migration jobs to update it.
  See HTTP://dtsc.dal-ebis.ihost.com/adcd for information
  related to products contained in this release.

  NOTE:  In between restoring these volumes and running the migration
         jobs, some functions that were operational on the original
         z/OS R4  system will not work.    They will work on the new
         system after all the migration jobs have been successfully
         completed.

 The following migration jobs are located in ADCD.ZOSV14S.MIGRATE

  ***************************************************************
  *  READ ALL THE COMMENTS CAREFULLY TO MAKE SURE THE JOBS WILL *
  *  SERVE THEIR INTENDED PURPOSE WITHOUT CHANGING THINGS YOU   *
  *  HAVE ALTERED. Edit them as needed when they conflict with  *
  *  prior customization you have performed, or make necessary  *
  *  changes manually.                                          *
  ***************************************************************

  $README  - See ADCD.ZOSV14S.MIGRATE to JCL members below
  MGCTLG   - MASTER CATALOG required changes
  MGLOAD   - Update SYS1.IPLPARM to new load members
  MGRBACK  - RACF DB Backup
  MGRTEMP  - RACF DB template updates
  MGRACF   - RACF DB changes
  MG2OPT1  - Optional _ Unix System Services /u migration documentation
  MG2OPT2  - Optional _ Recreate MQSeries environment example


  INSTRUCTIONS

  To migrate your system to z/OS Release 4 without losing your data
  on the OS39M1 volume:

  1.  This procedure is designed to work with both release 4 and
      release 4s volume on physical internal disk (PID).  Emulated disk
      (EMIO), are only used for loading new volumes in this procedure.

    ******************************************************************
    * *  WARNING!!!!!!  WARNING!!!!!!  WARNING!!!!!!  WARNING!!!!!!* *
    * ****************************************************************
    * *             BACKUP YOUR CURRENT Release 4 SYSTEM           * *
    ******************************************************************
    * *  WARNING!!!!!!  WARNING!!!!!!  WARNING!!!!!!  WARNING!!!!!!* *
    ******************************************************************

  2. BACK UP your entire system. ESPECIALLY OS39M1, if you have made
     any changes to the other volumes.
     This assures you can recover from any problems that might occur
     during migration.

  3. Load the new system from the CD packet using the instructions in
      HTTP://dtsc.dal-ebis.ihost.com/adcd/load.html. You need to
      complete at lease stage 1 and update the devmap with the new
      volumes.

  4. IPL your Release 4 Dec 2002 system to bring in the new
     volumes you added to the devmap.

  5. From TSO =3.4 - Select dsname ADCD.ZOSV14S.MIGRATE
                     Select volume S4RES1
     Place 'C' in command column - to catalog ADCD.ZOSV14S.MIGRATE


  6. Run the following jobs ONE AT A TIME from userid IBMUSER, and check
     for successful completion codes.  Run the following order.  Some
     Jobs are dependent on the previous job.  Review each job
     before execution  to assure the job will not disturb
     any changes you have made, or local modifications, and
     for information about possible non-zero completion codes
     that are acceptable.


      MGCTLG  - MASTER CATALOG required changes
      MGLOAD  - SYS1.IPLPARM  updates
      MGRBACK - Backup current racfds
      MGRTEMP - Add new racf templates
      MGRACF  - Changes to racfdb
      MGOPT1  - Optional - migrate HFS.USER dataset
      MGOPT2  - Optional - rebuild MQseries datasets

 7.  Review the new SYS1.IPLPARM members.  Your environment
     may require IODF statement change.  System command 'D IOS,CONFIG'
     will provide the need information.

 8.  IPL the new release 4s system. Set the IPL ADDRESS to the new
     release 4s res volume S4RES1.  Set the load parm volume address
     for the old Release 4 OS39M1 volume.  Use IPLPARM value of 99.
     This value will allow access to both PID and EMIO.
     For example:
         Assume S4RES1 is loaded on PID address 300 and
         OS39M1 from Release 4 is loaded on PID 312
         IPL using load address 300 with loadparm 031299M

     At the IEA101A Specify System Parameters For z/OS 1.04.00 message,
     it is recommended to respond 0,sysp=cs upon the first time IPL.

 9.  Run MGRBACK job on the new system to sync the new racfdb and
     and backup dataset.

 10. Please review the
     pages on web site HTTP://dtsc.dal-ebis.ihost.com/adcd.
     They contain important information about your system,
     including products and software levels.

  This completes the migration procedure.

*****************************************

BACKOUT:
  Restore OS39M1 from backup.

IPLING Z/OS 1.4s

To IPL the MP3000 7060 use the following process from the SASE:

• Start at least two PCOM sessions prior to IPL. Failure to do this will invoke use of the SASE Operating System panels.
• Double click on group
• Click on image
• Select image you wish to IPL
• Click on page cycle icon at bottom right of the panel until you are on the CPC Recovery Panel
• Drag image to Load on the CPC recovery Panel. Note: you can select the image and double click on load in lieu of dragging.
• Enter load address of 0300 or desired address
• Enter loadparms of 030299M or desired parameters
• Respond to startup message
  

    r 00,SYSP=CS to cold start JES2 on the initial IPL.
  
  

LOADPARMS Options

The following table list the pre-configured distributed loadparms.

Table 11. LOADPARMS

LOADPARM		Description
CS		CLPA and cold start of JES2. Base z/OS system functions i.e. no CICS, DB2, IMS, WAS, etc.
00		Warm start of JES2. Base z/OS system functions i.e. no CICS, DB2, IMS, WAS, etc.
WS		Warm start of JES2. Base z/OS system functions i.e. no CICS, DB2, IMS, WAS, etc.
DC		CLPA, brings in CICS LPA modules, cold start of JES2, starts up DB2 and CICS.
DB		Warmstart of JES2 and starts the DB2 and CICS.
DI		CLPA and cold start of JES2 and loads the IMS Libraries. IMS must be manually started.
CC		CLPA and cold start of JES2, loads the CICS Libraries, starts up CICS, no DB2.
CW		Warm start of JES2, and starts up CICS.
2C		CLPA, cold start of JES2, starts up DB2, no CICS.
2W		Warm start of JES2, starts up DB2, no CICS.
IC		CLPA and cold start of JES2 and load the IMS Libraries, start IMS, no DB2 or CICS.
IW		Warm start of JES2 start IMS, no DB2 or CICS.
AC		CLPA and cold start of JES2 load IMS and CICS libraries, start IMS, DB/2, and CICS.
AW		Warmstart of JES2. start IMS, DB/2, and CICS.
BC		CLPA and cold start of JES2, load WAS libraries, WAS is manually started
BW		Warmstart of JES2. WAS is manually started.
99		Points to IODF99 for IPL on MP3000. Reply 00,SYSP=xx were xx is any of the above options i.e. for cics only xx=cc or cw.

NOTE: JES2 should be cold started the first time you bring up the system. LoadParm is preset to 0A82CS.

CONSOLE PF KEY SETTINGS

As the system is running, you may wish to do some of the following from t he Master Console:

Table 12. Master Console PF Keys

ACTION		COMMAND
Display Devices		PF 1
Display 3270 Devices		PF 2
Clear Top of Screen		PF 3
Create a 10-line Display Area		PF 4
Display Address Space Information		PF 5
Display Outstanding Reply Requests a nd Error Messages		PF 6
Display PF Keys		PF 7
Scroll Display Area		PF 8
Display TSO Users		PF 9
Display Active Address Spaces		PF 10
Display Active Jobs		PF 11
Clear Bottom Screen		PF 12

OUTSTANDING WTOR

     *02 ISTEXC200 - DYN COMMANDS MAY BE ENTERED

The following commands may be entered in reply to the outstanding WTOR (message ISTEXC200) issued by the Dynamic XID Exit. Please note that the command will not be processed and another WTOR will not be issued until the next tim e when the exit is called by VTAM.

• R XX,RELOAD

• - The current Dynamic XID mapping table is reloaded.

• R XX,DYNTAB=<table>

• - The Dynamic XID mapping table <table> becomes the current ltable.

  For further information see SYS1.README(VTAM).

USERIDS

The following TSO Userids and Passwords have already been set up on your system:

Table 13. Pre-Defined USERIDS

USERID		PASSWORD
P390 (RACF special authority)		SYS1 or P390
IBMUSER (RACF special authority)		SYS1 or IBMUSER
SYSADM (DB2 and RACF special auth)		SYS1 or SYSADM
SYSOPR (DB2 and RACF special auth)		SYS1 or SYSOPR
P390A - P390Z		TEST
WEBADM		WEBADM
OPEN1 - OPEN3		SYS1

Device Map Set-up for Emulated IO

The following list the device map as distributed with ADCD z/OS 1.4s. the

Table 14. DEVMAP

Device Type		Address		Description
2540		0C		emulated card reader
1403		0E		OS/2 printer
1403		0F		OS/2 printer
3088		10		CTC - network adapter
3088		11		CTC - network adapter
3088		12		CTC - network adapter
3088		13		CTC - network adapter
3490		19		SCSI-attached tape drive
3480		20		DAT Tape drive
3420		21		Emulated tape on disk
3278		70		MVS Master Console
3278		71		Local TSO Session 1
3278		72		Console 2
3278		73		IMS Master Terminal
3278		74		Console 3
3278		75		Local TSO Session 2
3278		76		Console 4
3278		77		Local TSO Session 3
3390-3		A0		S4RES1
3390-3		A1		S4RES2
3390-3		A2		OS39M1
3390-3		A3		S4DB21
3390-2		A4		S4CIC1
3390-3		A5		S4DIS1
3390-3		A6		S4DIS2
3390-3		A7		S4USS1
3390-3		A8		S4DIS3
3390-2		A9		S4IMS1
3390-3		AA		S4WAS1
3390-3		AB		S4WAS2
3390-3		AC		SARES1
3390-3		AD		S4DIS4

Network adapters installed in your MP3000 are generally shipped in an inactive state. You will need to activate these devices before use. The devices will appear in a dark blue color when on view the device map through the Configurator Panels.

To activate inactive devices, position the cursor on the first device and press ALT+F5. See the documentation or online help (F1) for additional details.

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.

• All functions of the base Z/OS 1.4s product are at PUT level 0303 and RSU level 0303
• All functions of the CICS TS2.2 are at PUT level 0303
• All functions of the DB2 UDB 7.1.0 are at PUT level 0303.
• All functions of the IMS 8.1.0 are at PUT level 0303.
• All functions of the WAS 4.0.1 are at PTF level 502

ADCD Survey

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
ADCD Customer Satisfaction Survey



Name:_________________________________________________
Company Name: ________________________________________
Address: _____________________________________________
         _____________________________________________



Date you received your ADCD __________________________

Are you a first time user   _____Yes     _____No


Did you have any installation problems: ______________
______________________________________________________
______________________________________________________
______________________________________________________

Please list products you would have liked to have been
included in this ADCD.

     ________________________     ____________________
     ________________________     ____________________
     ________________________     ____________________
     ________________________     _____________________
     ________________________     _____________________


Please list products contained on this CD that you will never
use.

     ________________________     _____________________
     ________________________     _____________________
     ________________________     _____________________
     ________________________     _____________________
     ________________________     _____________________

Please return this form to:

          [email protected]

If you have any feedback or questions, respond to [email protected]

Local Time is Sun Jul 25 2004 09:01:40 GMT+0200
This document was last modified on Sun, 25 Jul 2004 07:01:24 GMT