Hi Robin,
When debugging via CDF, XDC is actually running in the batch job,
not in the TSO session. Consequently, you need to add a JCL card to
the batch job pointing to your profile library. The ddname can be
either //XDCPROF or //ISPPROF. (It doesn't matter which.) The library
pointed to can be any FB-80 PDS[E], and the allocation should be DISP=SHR.
The profile library you use with the batch job can even be the same
library as is allocated to ISPPROF in your TSO session, provided that
the allocation in TSO is with DISP=SHR. (The risk of corruption is slight.)
You may also want to add //XDCTLIB pointing to the TLIB into which
your z/XDC installer placed the default profiles (from DBCOLE.XDCZ1D.XDCTLIB).
IHTH,
Dave Cole
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS: dbc...@colesoft.com
Home page: www.colesoft.com
Facebook: www.facebook.com/colesoftware
YouTube: www.youtube.com/user/colesoftware
At 8/27/2013 03:10 AM, Robin Atwood wrote:
I have noticed that when using option 3 of the XDC main panel
(XDC-CDF) I cannot then access the XDC ISPF profile and PK keys,
etc, are not restored. When I issue the PROFILE SAVE command I get a message
DBC770E saying XDCPROF and ISPPROF cannot be found. I assume this is
caused by the cross-domain environment or have we not set up things
correctly? Is there any way around this (searching find nothing)?
TIA
-Robin
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
