Also, make sure you have done the following steps
http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=%2Fcom.ibm.d
b2z10.doc.inst%2Fsrc%2Ftpc%2Fdb2z_connect2tso.htm
Installation step 10: Connect DB2 to TSO
Although you can eventually connect DB2R to IMST, CICSR, or both, connecting
initially only to TSO is recommended for a first-time installation.
About this task
For a first-time installation, you can run the sample applications that do
not require CICS or IMS, allowing your database and system administrators to
gain familiarity with the administrative facilities of this version of DB2.
If you have previously installed DB2 and are performing that task again,
your database and system administrators are probably already familiar with
DB2. In this case, you can connect IMS, CICS, or both, at the same time that
you connect TSO. You can then run the sample applications that require CICS
and IMS at the same time that you run the sample applications for TSO and
batch.
Procedure
To attach DB2 to TSO:
Make DB2 load modules available to TSO and batch users.
Make DB2 CLISTs available to TSO and batch users.
Make PL/I options available (if applicable).
Make panels, messages, and load modules available to ISPF and TSO.
Connect the DB2I panels to the ISPF Main Panel.
Make DB2 load modules available to TSO and batch users
As part of installation, you must make DB2 load modules available to TSO
and batch users. If prefix.SDSNEXIT and prefix.SDSNLOAD are not included in
your LNKLSTxx, you can skip this step.
Make DB2 CLISTs available to TSO and batch users (DSNTIJVC)
To connect DB2 to TSO, you must make DB2 CLISTs available to TSO and
batch users by running the DSNTIJVC job.
Ensure that PL/I options are available
If you are using PL/I, ensure that the options that your DB2 programmers
use are included in the compiler.
Make DB2I panels, messages, and load modules available to ISPF and TSO
During installation, to connect the DB2 Interactive facility (DB2I) to
TSO, you must make panels, messages, and load modules available to ISPF and
TSO.
Connect DB2I panels to the ISPF main panel
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Lizette Koehler
Sent: Sunday, May 26, 2013 6:24 PM
To: [email protected]
Subject: Re: DFHUTILB and DFHUPROC
I forgot one other question.
Do you have the DB2 early code installed and running? At IPL time you
should see a message DSN something indicating that DB2 can be started. Also,
you may need a DB2 Subsystem actually running to do this.
I do not recall specifically - but that may be the case.
Lizette
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Lizette Koehler
Sent: Sunday, May 26, 2013 6:22 PM
To: [email protected]
Subject: Re: DFHUTILB and DFHUPROC
The DSN command name needs to be available to your TSO session, either Batch
or TSO Logon.
Do you have a STEPLIB for DSN Load Library (SDSNLOAD) IIRC - Do you have DSN
in the IKJTSOxx member for AUTHPGM or AUTHCMD?
The -DSN needs to be together no spaces.
This is documented in the DB2 manuals.
If your TSO logon proc has the DB2 load library in it, and you have SPUFI in
your TSO selections. Then I would use the SPUFI panels. It is easier to
enter DB2 commands and SQL from there.
Lizette
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Graham Hobbs
Sent: Sunday, May 26, 2013 6:14 PM
To: [email protected]
Subject: Re: DFHUTILB and DFHUPROC
Perry,
thanks but all the commands gave me this msg; READY
- DSN SYSTEM(DBAG)
IKJ56621I INVALID COMMAND NAME SYNTAX
READY
- CREATE STOGROUP CHELGRP
IKJ56621I INVALID COMMAND NAME SYNTAX
Does that imply IKJEFT01 can't do it, or, there is a there just a syntax
correction needed (besides the DD * :-). Seems a much simpler solution than
the DSNU's.
Graham
------
On 26/05/2013 7:32 PM, Perry Mayes wrote:
> Try running tso in batch. Something like below:
>
> //JOBLIB DD DISP=SHR,DSN=db2hlq.SDSNLOAD
> //STEP1 EXEC PGM=IKJEFT01,DYNAMNBR=20
> //SYSTSPRT DD SYSOUT=*
> //SYSPRINT DD SYSOUT=*
> //SYSUDUMP DD SYSOUT=*
> //SYSTSIN DD
> - DSN SYSTEM(ssid)
> - CREATE STOGROUP CHELGRP
> VOLUME VPWRKD
> VCAT CHELCAT
> Perry Mayes
> Sent from hand held device
>
>>>> Graham Hobbs <[email protected]> 26/05/2013 4:44:26 PM >>>
> Hi Lizette,
>
> Oiyoiyoi .. I meant DSNUTILB and DSNUPROC .. so sorry:-((.
>
> I sort of imagined that all the CICS and DB2 folk were here so didn't
> bother with CICS and DB2 groups. I do have a newsgroup list but it
> would have been interesting to see what other mainframe groups are
> useful except I couldn't read yours with Notepad or SPFPC60:-(.
>
> Yesterday I got my first CICS transaction working on Dallas's z/OS
> CICSTS42. It's accesses a VSAM KSDS file (built via IDCAMS). My next
> transaction is similiar but will access a DB2 table. Via reading it
> seems there are a) and b) preparatory one time steps to perform:
>
> a) create a stogroup
> b) create a database within the stogroup
> c) thereafter my software will add small tables to the database to be
> accessed by my CICS pgms.
>
> Thus the questions about using DSNUTILB or DSNUPROC for at least a)
> and
> b) above and which is best? .. and hopefully c).
>
> I have plunged in with both and failed miserably. My JCL knowledge
> used to be strong for batch prod jobstreams but dealing with these
> 'specialities' ten years later is a struggle. My baby start JCL is:
>
> //AU1 JOB (CONRAD),'GH', etc
> //* STOGROUP CREATE
> //DSNUPROC EXEC PGM=DSNUPROC,REGION=0M //STEPLIB DD
> DISP=SHR,DSN=DSNA10.PROCLIB
> //SYSIN DD *
> CREATE STOGROUP CHELGRP
> VOLUME VPWRKD
> VCAT CHELCAT
> //
>
> .. delivering ..
>
> IEW4007I FIND FOR MODULE DSNUPROC FAILED BECAUSE DIRECTORY ENTRY IS
> NOT VALID FOR A LOAD MODULE.
> CSV003I REQUESTED MODULE DSNUPROC NOT FOUND
> CSV028I ABEND806-04 JOBNAME=AU1 STEPNAME=DSNUPROC
>
> .. checked IEW4007I but both the steplib and proc exist .. yuk.
>
> Next, with the same JCL, will be
> CREATE DATABASE CHELBAS1
> STOGROUP CHELGRP
> CCSID EBCDIC
>
> Thanks for the quick answer!
> Graham
> ------
> On 26/05/2013 1:56 PM, Lizette Koehler wrote:
>> Graham,
>>
>> I am a little confused.
>>
>> Typically DFH is CICS functions, and a STOGROUP is either DB2 or DFSMS.
>>
>> So what are you trying to do? If you could post the complete Batch
>> Job that will help.
>>
>> Lizette
>>
>> PS. Yes there is a DB2 newsgroup and a CICS newsgroup which already
>> have this in their archives.
>>
>>
>>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List [mailto:[email protected]]
>> On Behalf Of Graham Hobbs
>> Sent: Sunday, May 26, 2013 10:10 AM
>> To: [email protected]
>> Subject: DFHUTILB and DFHUPROC
>>
>> 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 [email protected] with the message: INFO IBM-MAIN
