CICS Manual do Usuário - JOURNAL

JOURNAL

Creates a journal record.

Sintaxe:

JOURNAL
 
>>-JOURNAL--JFILEID(data-value)--JTYPEID(data-value)------------>
 
>--FROM(data-area)--+--------------------+---------------------->
                    '-LENGTH(data-value)-'
 
>--+------------------+----------------------------------------->
   '-REQID(data-area)-'
 
>--+---------------------------------------------+-------------->
   '-PREFIX(data-value)--+---------------------+-'
                         '-PFXLENG(data-value)-'
 
>--+---------+--+------+--+-----------+------------------------><
   '-STARTIO-'  '-WAIT-'  '-NOSUSPEND-'

Condição: IOERR, JIDERR, LENGERR, NOJBUFSP, NOTAUTH, NOTOPEN

Notas:

LENGTH is required in C or C++ programs.
When PREFIX is used, PFXLENG is mandatory in C or C++ programs. PFXLENG is mandatory in C programs.

Descrição:

JOURNAL creates a journal record.
The request can be for synchronous or asynchronous output; definitions of these terms, and detailed information regarding the synchronization of journal output, are given in the TXSeries for Multiplatforms Application Programming Guide.

For synchronous journal output, the WAIT option must be specified.
For asynchronous output (that is, the WAIT option is not specified), you can include the REQID option to provide an identifier for the journal record; this identifier can be used later in a WAIT JOURNAL command to synchronize the task with the creation of the journal record.

The STARTIO option is used, in a synchronous or asynchronous request, to specify that the journal output operation should start immediately.
STARTIO reduces absolute waiting time at the expense of general system performance and input and output load.

The following example shows how to request synchronous journal output and wait for the output operation to be completed:

     EXEC CICS JOURNAL
          JFILEID(2)
          JTYPEID('XX')
          FROM(KEYDATA)
          LENGTH(8)
          PREFIX(PROGNAME)
          PFXLENG(6)
          WAIT
     END-EXEC

In this example, STARTIO is not specified, so the task waits until the journal buffer is full or until output is initiated by a STARTIO request in another task.

The following example shows how to request deferred (asynchronous) journal output:

     EXEC CICS JOURNAL
          JFILEID(2)
          JTYPEID('SD')
          FROM(COMDATA)
          LENGTH(10)
          REQID(ENTRYID)
     END-EXEC

Opções:

FROM(data-area)

Specifies the user data that is to be built into the journal record.

JFILEID(data-value)

Specifies, as a 16-bit binary value in the range 1 through 99, the number that is to be taken as the journal identifier.
A Journal Definitions (JD) entry must exist for the number.
On other CICS systems, the value 1 is reserved for the system log; so you are advised to avoid using this number for regions.

JTYPEID(data-value)

Specifies the two-character identifier that is to be placed into the journal record to identify its origin.

LENGTH(data-value)

Specifies, as a 16-bit binary value, the length, in bytes, of the user data that is to be built into the journal record.
LENGTH cannot be greater than 32767 minus any value that is specified for PFXLENG and minus 20 bytes that are used for a prefix area.
The minimum value is 1 and the maximum value is 32747.
LENGTH is required in C or C++ programs. See LENGTH for more information about using this option.

NOSUSPEND

Specifies that the application program is not to be suspended for the NOJBUFSP condition; instead, control is to return immediately to the next instruction in the program.

PFXLENG(data-value)

Specifies, as a 16-bit binary value, the length, in bytes, of the user prefix data that is to be included in the journal record.
PFXLENG cannot be greater than 32767 minus any value that is specified for LENGTH and minus 20 bytes that are used for a prefix area.
The maximum value is 32747.

PREFIX(data-value)

Specifies the user prefix data that is to be included in the journal record.
A data area must be provided in COBOL programs.
When PREFIX is used, PFXLENG is mandatory in C or C++ programs.

REQID(data-area)

Specifies a 32-bit binary field that is to receive a number that identifies, by its position in the journal, the journal record that is being created. REQID applies to asynchronous output; that is, the WAIT option is not specified.

STARTIO

Specifies that the output of the journal request is to be initiated immediately. This option is ignored by TXSeries for Multiplatforms.

WAIT

Specifies that synchronous journal output is required.
The requesting task waits until the journal record has been written.
If the wait time exceeds the value of the DeadLockTimeout attribute in the Transaction Definitions (TD), an AKCS abend occurs.

Condições:

IOERR

Occurs if the physical output of a journal record was not accomplished because of an unrecoverable I/O error.
See Processing the IOERR condition for information about handling the IOERR condition.
Ação pré-definida: Terminates the task abnormally.

JIDERR

Occurs if the specified journal identifier does not exist in the Journal Definitions (JD).
Ação pré-definida: Terminates the task abnormally.

LENGERR

Occurs if either LENGTH or PFXLENG option has a negative or zero value.
Ação pré-definida: Terminates the task abnormally.

NOJBUFSP

Occurs if the journal storage does not have enough space to contain a journal record.
Ação pré-definida: Suspend task activity until space becomes available and the JOURNAL command is satisfied.
This default action can be overridden by the NOSUSPEND option.

NOTAUTH

Occurs if a resource security check has failed on JFILEID(data-value).
Ação pré-definida: Terminates the task abnormally.

NOTOPEN

Occurs if the JOURNAL command cannot be satisfied because thespecified journal is not open.
Ação pré-definida: Terminates the task abnormally.

Informações relacionadas: