Hints and tips to manage the z/OS 2.3 ADCD
Learn with the examples in this sections about page data sets available, starting IMS™ and running an IVP transaction, WLM configuration provided, ACS routines provided, recreating the coupling data sets, allocating DB2® archive logs into an esoteric, steps for dumping SMF data into GDG (Generation Data Group) data sets, using the esoteric devices, and how to start IBM® Healthchecker for z/OS®, IBM z/OS Management Facility (z/OSMF), and WebSphere® Application Server.
- Page data sets
This ADCD system provides you with three volumes that are dedicated for page data sets, D2PAGA through D2PAGC. - Starting IMS and running an IVP transaction
- WLM configuration provided on ADCD z/OS
The WLM configuration of application environments for DB2 Stored Procedures for DBBG are self-documented in the WLM application environment display. - ACS routines provided on ADCD
DB2 V11 requires that its Catalog and Directory are SMS managed. The ACS routines that are available on ADCD z/OS system were created to handle HLQ DSNCB10, which is the HLQ of the DB2 V11 Catalog and Directory. The logic is to use two qualifiers; the first is DSNCB10, and the second is DSNDBC or DSNDBD. The DSNDBC and DSNDBD indicate the cluster and data portion of the VSAM data set of a DB2 Tablespace. Other data sets for DB2 V11 have a HLQ of DSNB10, and these data sets are not SMS managed. A DB2 STOGROUP called SYSSMS was created for the Catalog and Directory Tablespace with a VCAT of DSNCB10 and VOL of (*). The (*) is for SMS managed STOGROUP. The DB2 STOGROUP, SYSDEFLT uses VCAT of DSNB10 and lists actual volumes, and it is not SMS managed. The installation is configured to use SYSSMS when it creates the Catalog and Directory Tablespaces. If you create and specify a STOGROUP of your own or default to SYSDEFLT STOGROUP, your Tablespace will fall into non-SMS managed volumes as specified in the STOGROUP. - Recreating the coupling data sets
The following coupling data sets are provided on ADCD. - Allocating DB2 archive logs into an esoteric device
Additional storage volume D2DBAR was defined and is pointed to by a new esoteric DBARCH for DB2 archive logs. You can find instructions for adding more volumes to this esoteric in this topic. Ensure to map this volume D2DBAR to device# 0AA3 in your devmap so that it is in sync with the IODF definition. - Steps for dumping SMF data into GDG data sets
The system is configured to clear SMF data by using the procedure SMFCLEAR. This procedure is triggered by the exit routine IEFU29, and the source code of which is available in ADCD.LIB.JCL. If you want to save the SMF data into GDG data sets, modify this exit routine to call procedure SMFDUMPS. Edit the exit routine IEFU29 to change occurrences of string SMFCLEAR to SMFDUMPS, and assemble or link edit the load module by using the JCL member IEFU29@, which is also available in ADCD.LIB.JCL. To take this change effect, you must re-IPL the system. As a GDG base SYS1.SMF.DATA was defined by using the JCL in ADCD.LIB.JCL(SMFGDG), the procedures SMFCLEAR and SMFDUMPS are available in ADCD.Z22C.PROCLIB. - Using the esoteric devices
Esoteric devices that are called WORK, TEMP, and SORT are defined and mapped to devices in the range 0600 – 060F. To use these esoterics, create emulated 3390 volumes in your zPDT® system, and map them to these device addresses by using the devmap file. - Steps for starting IBM Health Checker for z/OS
With this edition, IBM Health Checker is preconfigured to start automatically. - Steps for starting IBM z/OS Management Facility (z/OSMF)
A new load parm (IZ) is configured to start the z/OSMF product. These required commands to start z/OSMF are listed below for reference. However, these commands are included in the startup script member VTAMCI/DB/IM/IZ/WA/AL so that z/OSMF starts automatically. The first command starts the CIM (Common Information Model) server, and the second command starts z/OSMF. You must start the CIM server before starting the z/OSMF product. The WebSphere Application Server OEM provides a native application server runtime environment for z/OSMF. - LOADPARMS options
Lists available preconfigured distributed LOADPARMS. - Steps for starting WebSphere Application Server (WAS V8.5)
- Steps for starting WebSphere Application Server (WAS V9.0)
Parent topic: z/OS 2.3 ADCD reference