Previous topic |
Next topic |
Contents |
Index |
Contact z/OS |
Library |
PDF
Tailoring the CLIST CBDCHCD z/OS HCD User's Guide SC34-2669-00 |
|
Tailoring the CLIST CBDCHCDA sample CLIST CBDCHCD (CBDCHCDJ for Kanji) is provided in SYS1.SCBDCLST to assist you in invoking HCD from the ISPF dialog. It allocates the HCD message log file (HCDMLOG), the trace data set (HCDTRACE), and the HCD term file (HCDTERM) with a default high-level qualifier of the userID (&SYSUID.). The CLIST also allocates the HCD data sets SYS1.SCBDPENU, SYS1.SCBDMENU, and SYS1.SCBDTENU (or SYS1.SCBDPJPN, SYS1.SCBDMJPN, and SYS1.SCBDTJPN for Kanji). In CBDCHCD and CBDCHCDJ, the ISPEXEC LIBDEF statement for ISPPLIB, ISPTLIB and ISPMLIB is done with the STACK option. This leaves existing LIBDEFs untouched, so that after exit, the existing HCD libraries ISPPLIB, ISPTLIB and ISPMLIB are freed again. If the prefixes for message, trace, and term data sets do not conform to the installation conventions, you may tailor the CLIST to match your installation defaults. If you want HCD to use your TSO prefix as the high level qualifier, you can call CBDCHCD with the parameter NOPREF(YES). This causes HCD to use the qualifiers &PREFIX..&SYSUID. CBDCHCD invokes another CLIST, CBDCHCD1. You may tailor this CLIST as well. In any case, use the application ID for HCD: NEWAPPL(CBD). The CLIST also tailors the ISPF environment by:
Note:
HCD can be invoked with the activated TRACE option,
when you have specified parameter TRACE(YES) in the default CLIST.
The size of the trace data set can be changed by modifying the CLIST.
In addition, you can delete the HCD provided trace data set and allocate
one according to your specific needs. |
Copyright IBM Corporation 1990, 2014
|