Other folks have pointed out that it looks like your sysprog didn't
complete the customization of the Program Prep part of Debug Tool to
tell it where your copy of the COBOL compiler is (which can be
LINKLIST). It appears your system doesn't have it in the default
IGY.SIGYCOMP location. Specifically EQAW.SEQATLIB(EQAZDFLT) variable
yc1clib.
You can temporarily override this by using option S and then 1 (S being
at the bottom of the Program Prep screen) if you know where the compiler
actually is.
Of course you don't have to use these panels. For the current
Enterprise COBOL for z/OS 4.2 compiler, what you can do is take the JCL
you are currently using to compile with and add the
TEST(NOHOOK,SEPARATE) compiler option, and a SYSDEBUG DD pointing to a
cataloged PDS(E) RECFM=FB LRECL=1024 that will contain the sysdebug file
(sometimes called a separate file).
If you look in the Debug Tool EQAW.SEQASAMP data set for member EQAWIVCP
there is an example of a COBOL compile and link for a CICS COBOL IVP
program (and instructions on how to start the debugger with it).
Your CICS region will also need to have been updated to have
EQAW.SEQAMOD in its STEPLIB and DFHRPL, and the Debug Tool CSD added.
Info on that is in the Debug Tool Customization Guide. Info on using
DTCN to start a debug session in CICS (from a user perspective) is in
the User's Guide. Both are at
www.ibm.com/software/awdtools/debugtool/library.
George
On 5/29/2013 2:11 PM, Graham Hobbs wrote:
Hello,
Long post - sorry!!
My first try at using the IBM Debug Tool for a COBOL/CICS pgm (no DB2
(that'll be next)), filled out the Program Prep screens (partial
groping), pressed Enter when told, finally got to this ..
Compile using 5655-S71 IBM Enterprise COBOL for z/OS
Input data set: 'IBMUSE2.QKVS(QKVSP04)'
Compiler options: TEST(NONE,SYM,SEPARATE) LIB CICS("COBOL3 CICS")
NODYNAM LIB RENT NOSEQ SIZE(4000K) CICS(''COBOL3'')
These data set names were generated using patterns that were specified
in the "Edit data set name patterns" panel. Override these names by
overtyping. These data sets will be created, if they do not exist
Compilation output data sets:
Listing . 'IBMUSE2.QKVS.LISTING(QKVSP04)'
Object. . 'IBMUSE2.QKVS.OBJECT(QKVSP04)'
SYSDEBUG. 'IBMUSE2.QKVS.SYSDEBUG(QKVSP04)'
SYSTERM . *
CICS Translator and DB2 SQL Processor options (Integrated and separate
Y CICS. . . COBOL3 CICS
N DB2 . . . HOST(COBOL)
N DB2 SQL output DBRM data set (Integrated and Separate):
DBRMLIB :
N Run Separate CICS Translator using these data set names:
Listing .
SYSTERM .
N Run Separate DB2 Precompiler using these data set names:
Listing .
SYSTERM .
.. Enter got me ..
EQAZ040I 5655-S71 IBM Enterprise COBOL for z/OS started for
'IBMUSE2.QKVS(QKVSP
04)' using 'IBMUSE2.QKVS(QKVSP04)'.
IKJ56228I DATA SET IGY.SIGYCOMP NOT IN CATALOG OR CATALOG CAN NOT BE
ACCESSED
IKJ56109I DATA SETS NOT CONCATENATED+
IKJ56109I FAILURE TO ALLOCATE DATA SET IGY.SIGYCOMP
***
..enter got me..
Allocation Error
Compile using 5655-S71 IBM Enterprise COBOL for z/OS
DB2 Precompiler return code = NOT RUN
CICS Translator return code = NOT RUN
COBOL Compiler return code = NOT RUN
The following data sets were used for this compilation.
Enter E to Edit, V to View, or B to Browse these data sets.
Input . : 'IBMUSE2.QKVS(QKVSP04)'
Compilation output data sets:
Listing : 'IBMUSE2.QKVS.LISTING(QKVSP04)'
Object. : 'IBMUSE2.QKVS.OBJECT(QKVSP04)'
SYSDEBUG: 'IBMUSE2.QKVS.SYSDEBUG(QKVSP04)'
SYSTERM : *
N DB2 SQL output DBRM data set:
DBRMLIB :
N CICS Translator data sets:
Listing :
SYSTERM :
N DB2 Precompiler data sets:
Listing :
SYSTERM :
.. boils down to an Allocation Error I think; looked for IKJ56228I in
z/OS V1R12.0 MVS System Messages Vol 9 (IGF - IWM) but isn't there,
googled but told me little, so possible someone might know where I
messed up?
As usual, please, thanks
Graham Hobbs
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
