Menu principal                 [Fechar]


CICS Manual do Usuário - ENTER


Volta a página anterior

Volta ao Menu Principal


Desenvolvido por DORNELLES Carlos Alberto - Analista de Sistemas - Brasília DF. - cad_cobol@hotmail.com

ENTER

Writes a trace entry.

Sintaxe:



ENTER
 
>>-ENTER--TRACEID(data-value)--+-----------------+-------------->
                               '-FROM(data-area)-'
 
>--+----------------+--+-----------------+--+---------+--------->
   '-RESOURCE(name)-'  '-ENTRYNAME(name)-'  '-ACCOUNT-'
 
>--+---------+--+---------+------------------------------------><
   '-MONITOR-'  '-PERFORM-'
 

Condições: INVREQ

Descrição:

ENTER specifies a point within an application program at which a user trace entry, or a user Event Monitoring Point (EMP), or both, is to be produced.

A user trace entry is always constructed unless the MONITOR option is specified; whether the trace entry is written depends on whether user tracing is active for the task that is issuing the request (see the TRACE command).

The ACCOUNT, MONITOR, and PERFORM options relate to user EMPs; in the absence of these options, only a user trace entry is produced. Note that the ACCOUNT option has no significance for TXSeries for Multiplatforms and is therefore ignored if specified.

If the PERFORM option is specified, CICS constructs a user event monitoring structure from the remaining options and passes this to the EMP user exit (function CICS_EMP_EnterAPI()).
If the MONITOR option is also present, only the user Event Monitoring Point is constructed.
If MONITOR is not specified, a user trace entry is also constructed.
Note that specifying MONITOR without PERFORM causes nothing to happen.

A trace identifier in the range 0 through 199 must be provided in the TRACEID option.
Optionally, eight bytes of data can be supplied in the FROM option.
Also, an eight-byte name can be supplied in the RESOURCE option.
This data appears in the user trace entry.
Apart from the RESOURCE data, all these fields are also passed to the EMP user exit (where applicable).

User trace entries can be formatted by using the cicstfmt utility, as described in the TXSeries for Multiplatforms Administration Reference.

User event monitoring entries can be formatted byusing the cicsmfmt utility, if this has been upgraded by your system administrator.
CICS provides a sample version of this utility.
For further details, see the TXSeries for Multiplatforms Administration Reference.

The following example shows how to specify that a user trace entry should be produced:

    EXEC CICS 
         ENTER
         TRACEID(123)
         FROM(MSG)
    END-EXEC

Opções

    ACCOUNT
  • This option is retained for compatibility with IBM mainframe-based CICS, but has no significance for TXSeries for Multiplatforms and is therefore ignored.
    ENTRYNAME(name)
  • Specifies a qualifier for a user Event Monitoring Point. The name can be up to eight bytes long. If this option is omitted, a default entry name of USER is assumed.
    FROM(data-area)
  • Specifies an eight-byte data area whose contents are to be entered into the data field of the trace entry, or passed to the EMP user exit (where applicable).
  • If you omit the FROM option, eight-bytes of binary zeros are supplied.
    MONITOR
  • Specifies that a user Event Monitoring Point, rather than a trace entry point, is to be recorded.
    PERFORM
  • Specifies, for a User Event Monitoring Point, that user event information is to be collected in the performance class monitoring data records.
    RESOURCE(name)
  • Specifies an eight-byte name that is to be entered into the resource field of the trace entry.
    TRACEID(data-value)
  • Specifies, as a 16-bit binary value, the trace identifier for a user trace entry.
  • This identifier is also passed to the EMP user exit (where applicable). The value should be in the range 0 through 199.

Condições

    INVREQ

  • Occurs if TRACEID is outside the range 0 through 199.
  • Ação pré-definida: Terminates the task abnormally.

Related Information


© Copyright IBM Corp.