Methods of Specifying and Updating Parameters
Related topics
This section describes the methods of specifying and updating parameters.
BMC PARMLIB
Code Debug CICS allows you to specify most configuration parameter values using BMC PARMLIB at product initialization.
Parameters are specified in BMC PARMLIB member XDGBxxxx.
Updating the CMSC with Your PARMLIB Members
If you have made changes to your PARMLIB members, you can use the z/OS MODIFY (F) command to update the CMSC with those changes.
Refreshing All PARMLIB Members
F cmscname,PARMLIB REFRESH
Refreshing a Single Parameter Member
F cmscname,PARMLIB REFRESH member_name
Updating the Code Debug CICS Parameters While CICS is Active
If you have made changes to your PARMLIB members while CICS is active, you can use transaction XSIT to update the active CICS region with those changes.
All parameter values can be updated by entering the transaction XSIT. XSIT directs CMSC to refresh the PARMLIB members for this CICS region. It then updates Code Debug in this CICS region with the parameters from CMSC.
If you execute XSIT while Code Debug is active, the following parameters will not be updated:
- ACTIVATE_CODE_COVERAGE_AT_INITIALIZATION
- CODE_COVERAGE_START_XPEDITER_NORMALLY
- DYNAMIC_TRANSACTION_ROUTING_SUPPORT
- ENABLE_DYNAMIC_FILE_DEF_FOR_SLS_FILES
- ENABLE_GLOBAL_USER_SIGN_OFF_EXIT
- ENABLE_UTILITIES_MODE
- ESD_CACHE_BUFFER_SIZE
- MAX_SUBTASKS_FOR_PDSE_SUPPORT
- MAXIMUM_SLS_FILES_TO_SEARCH
- MONITOR_MAX_STG_ABOVE_BAR
- NUMBER_CONCURRENT_PDSE_REQUESTS
- SERVICE_PROVIDER_SUBSYSTEM_NAME
- SLS_DDNAME_TEMPLATE
- SLS_DSN
- SLS_SHARED_DATABASE_TEMPLATE
- SUPPORT_CICS_OPEN_TRANSACTION_ENV
- TRANSID_XPFS
- USER_PROFILE_DDNAME.
Script Facility Parameters
The following parameters cannot be dynamically updated using XSIT while the Script Facility is active:
- SCRIPT_FACILITY_SYSTEM_SCRIPT_DDNAME
- SCRIPT_FACILITY_USER_SCRIPT_DDNAME
File Utility Audit Trail Parameters
The following parameters cannot be dynamically updated using XSIT while the File Utility Audit Trail is active:
- FILE_UTILITY_AUDIT_TRAIL_ALLOC_TYPE
- FILE_UTILITY_AUDIT_TRAIL_BASE_DSN
- FILE_UTILITY_AUDIT_TRAIL_BLKSIZE
- FILE_UTILITY_AUDIT_TRAIL_DDNAME
- FILE_UTILITY_AUDIT_TRAIL_DELETED_RECORDS
- FILE_UTILITY_AUDIT_TRAIL_ENABLE
- FILE_UTILITY_AUDIT_TRAIL_NEW_RECORDS
- FILE_UTILITY_AUDIT_TRAIL_NON_SMS_DSCB
- FILE_UTILITY_AUDIT_TRAIL_PRIMARY_ALLOC
- FILE_UTILITY_AUDIT_TRAIL_SECONDARY_ALLOC
- FILE_UTILITY_AUDIT_TRAIL_UNIT
- FILE_UTILITY_AUDIT_TRAIL_UPDATED_RECORDS
- FILE_UTILITY_AUDIT_TRAIL_VOLUME.
Assembling DBUGGBL
Assembling DBUGGBL is no longer supported. If your site previously assembled DBUGGBL to change transaction identifier for DBPA, XPED, XPRT, XPON, or XPSP, see Overriding-Session-Initialization-Transactions.