| Introduction |
 |
SMS/Debug is a real-time debugging tool for IBM DF/SMS. Trace facilities are available for the production ACS rules language, the DF/SMS volume selection routines and the DADSM pre and post processing exits.
| Description |
|
SMS/Debug is a real-time
trace facility for DF/SMS. Trace facilities are available for:
- the production ACS rules language
- the DF/SMS volume selection routines
- the DADSM pre and post processing exits
Simple User Interface - When SMS/Debug is started,
the product dynamically adds a JCL and TSO command extension to the system.
The SMSDEBUG keyword parameter can then be used to activate the debug
facilities on both batch and TSO data set allocations. For example, the
following batch job uses the SMSDEBUG keyword to activate tracing.
//JOBNAME JOB...
// EXEC PGM=IEFBR14
//DD1 DD DSN=TEST.DATASET,SPACE=(TRK,1),
// STORCLAS=STC1,SMSDEBUG=YES
Trace Output Returned to User - The trace output is
returned directly to the user. For batch jobs, the trace messages are
included in the JES output message log. If a TSO trace is requested, the
messages are returned directly to the TSO user. For VSAM IDCAMS defines,
output is returned to the SYSPRINT DD statement.
No Rules Language - Unlike most of the other DTS Software
products, SMS/Debug does not require any installation setup or product
configuration.
| Benefits |
|
Maximizes utilization of the SMS environment
Provides Tracing facility for:
- ACS Routines
- SMS Volumes
- DADSM Exits
Ease-of-Use
- Installs from CD or web download
- Trace facilities initiated using JCL extensions
- Component of ACC
| History |
|
SMS/Debug is actually a feature that’s been available in ACC for many years. Not all companies need the power and sophistication of ACC, but many SMS installations are still struggling to debug ACS rules and figure out “Why did SMS pick THAT volume?”
In early 2003, DTS cloned the SMS debugging features from ACC and wrote a very short manual for a very simple product – SMS/Debug.
|