Graham,
If you are DB2 V10 then you need to keep in line with IBM's direction of SMS
management. I would look at the Share Presentation
http://www.bwdb2ug.org/PDF/SMS_is_Now_Mandatory_for_DB2_V10.pdf
Define the SMS environment for the DB2 catalog and directory data sets
(DSNTIJSS)
In DB2R Version 10, data sets that are defined for the DB2 catalog and
directory are managed by DB2 and must be SMS-managed.
Start of changeJob DSNTIJSS shows how to create a stand-alone SMS
environment for the DB2 catalog and directory data sets. Job DSNTIJSS is
designed for use on systems that do not already have a SMS environment, but
it can also be used as a reference for adapting an existing one. End of
change
Start of changeYou are not required to convert existing DB2 data sets to an
SMS environment before migrating to Version 10. These data sets can
indefinitely remain non-SMS-managed, but they will be converted to SMS
management when the related table space is reorganized.End of change
The SMS environment that you use for DB2 catalog and directory data sets
must be established before you begin migration to Version 10. The SMS
environment must include a data class for allocating the data sets in
extended format and using extended addressability. To define a data class
with this attribute, specify EXT in the DATA SET NAME TYPE field of the DATA
SET CLASS DEFINE panel of ISMF. Then, ensure that the automatic class
selection (ACS) routine associates the DB2 catalog and directory data sets
with this data class.
To create the stand-alone SMS environment for the DB2 catalog and directory:
Customize job DSNTIJSS according to the directions in the job prolog.
Run job DSNTIJSS.
To activate the SMS environment, use this z/OS command, where scds-name
is the name of the SMS source control data set that was specified by
DSNTIJSS:
SETSMS SCDS(scds-name)
Attention: This command will deactivate any existing SMS environment
that is defined from another SCDS.
Run the SMS CONVERTV tool with the TEST option to verify that all data
sets on target volumes can be placed under SMS management.
Example of running CONVERTV with the TEST option:
//CONVRTV EXEC PGM=ADRDSSU,REGION=5M
//SYSPRINT DD SYSOUT=*
//DD1 DD UNIT=SYSALLDA,VOL=SER=targvol1,DISP=OLD
//DD2 DD UNIT=SYSALLDA,VOL=SER=targvol2,DISP=OLD
//SYSIN DD *
CONVERTV DDNAME(DD1) SMS TEST CATALOG
CONVERTV DDNAME(DD2) SMS TEST CATALOG
/*
When CONVERTV TEST reports that all data sets on the target volumes can
be placed under SMS management, run CONVERTV without the TEST option to
convert the data sets. If any data sets cannot be converted, do not run
CONVERTV without the TEST option. You must either create additional ACS
routines to manage these data sets or move them to different (non-SMS)
volumes.
Related tasks:
Premigration checklist for migration to DB2 Version 10 conversion mode from
Version 8
Premigration checklist for migration to DB2 Version 10 conversion mode from
Version 9.1
That is why the DB2 Newsgroup can be so helpful. They focus on DB2 and can
keep you on the right track. There are good SHARE presentations on how DB2
and SMS management are working together.
Lizette
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Ron hesketh
Sent: Sunday, May 26, 2013 11:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DFHUTILB and DFHUPROC
Hi Graham,
DSNUPROC is aJCL procedure for executing DB2 utilities. DSNUTILB is the
DB2 utility program.
To create DB2 objetcts using DSNUTILB, you nees to use the EXEC SQL online
utility control statement.
To create your STOGROUP using DSNUPROC , your JCL woul;d be something like :
//STEP1 EXEC DSNUPROC,SYSTEM=ssid,UID='',UTPROC='' <==== ssid is
your DB2 subsystem id.
//DSNUPROC.SYSPRINT DD SYSOUT=(*)
//DSNUPROC.UTPRINT DD SYSOUT=(*)
//DSNUPROC.SYSIN DD *
EXEC SQL
CREATE STOGROUP CHELGRP
VOLUME VPWRKD
VCAT CHELCAT
ENDEXEC
/*
To do it using IKJEFT01, you need to use one of the IBM sample programs to
process the DDL.the TSO DSN command cannot execute SQL.
Heres an example from the DB2 IVP job DSNTEJ1 :
//PH01S01 EXEC PGM=IKJEFT01,DYNAMNBR=20,COND=(4,LT)
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
DSN SYSTEM(ssid)
RUN PROGRAM(DSNTIAD) PLAN(DSNTIAD) -
LIB('your.RUNLIB.LOAD')
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
CREATE STOGROUP CHELGRP
VOLUME VPWRKD
VCAT CHELCAT
;
/*
Regards,
Ron
From: Graham Hobbs <gho...@cdpwise.net>
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 27/05/2013 01:10 AM
Subject: DFHUTILB and DFHUPROC
Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
Wisdom sought please! I have tried to build a stogroup via batch job.
CREATE STOGROUP CHELGRP
VOLUME VPWRKD
VCAT CHELCAT
Seems DFHUPROC and DFHUTILB are options. Is one more common than the other?
Is it that the first calls the second (amongst others)?
Cheers,
Graham Hobbs
P.S. Secretly am looking for JCL that bl..dy works:-):-[
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
