Write a trace entry.
ENTER TRACENUM >>-ENTER TRACENUM(data-value)-----------------------------------> >--+--------------------------------------------+---------------> '-FROM(data-area)--+-----------------------+-' '-FROMLENGTH(data-area)-' >--+----------------+--+-----------+--------------------------->< '-RESOURCE(name)-' '-EXCEPTION-'
Conditions: INVREQ, LENGERR
This command is threadsafe.
The ENTER TRACENUM command makes a trace entry in the currently active trace destinations. CICS® writes the trace entry only if the master and user trace flags are on, unless you specify the EXCEPTION option, in which case a user trace entry is always written, even if the master and user trace flags are off. Exception trace entries are always written to the internal trace table (even if internal tracing is set off), but they are written to other destinations only if they are active.
You can use the exception trace option in an application program to write a trace entry when the program detects an exception or abnormal condition. To do this, include an ENTER TRACENUM(data-value) EXCEPTION command in your program's exception or abnormal condition error-handling routine.
To write an exception trace entry in an error situation when an application program has given up control, you can issue an ENTER TRACENUM(data-value) EXCEPTION command from a user-written program error program (PEP). See the Writing a program error program for programming information about modifying the DFHPEP program.
Note ENTER TRACENUM replaces the earlier ENTER TRACEID command, which is still supported for compatibility with releases of CICS earlier than Version 3. You should use ENTER TRACENUM for all new programs, and whenever you apply maintenance to old programs.
For information about the trace entry format, see Using traces in problem determination .
Default action: terminate the task abnormally.
Default action: terminate the task abnormally.
EXEC CICS ENTER TRACENUM(123)
FROM(USER-TRACE-ENTRY)
END-EXEC.