Communicate on a 3600 (3601) logical unit.
CONVERSE (3600-3601) >>-CONVERSE--FROM(data-area)--+-FROMLENGTH(data-value)--+-------> '-FROMFLENGTH(data-value)-' >--+-INTO(data-area)-+--+-TOLENGTH(data-area)--+----------------> '-SET(ptr-ref)----' '-TOFLENGTH(data-area)-' >--+-----------+--+---------+--+------------------------+-------> +-LDC(name)-+ '-DEFRESP-' +-MAXLENGTH(data-value)--+ '-FMH-------' '-MAXFLENGTH(data-value)-' >--+------------+---------------------------------------------->< '-NOTRUNCATE-'
Conditions: EOC, EODS, INBFMH, LENGERR, SIGNAL, TERMERR
CONVERSE communicates on a 3600 logical unit. This form of the CONVERSE command also applies to the 4700 and the 3630 plant communication system.
A logical device code (LDC) is a code that can be included in an outbound Function Management Header (FMH) to specify the disposition of the data (for example, to which subsystem terminal it should be sent). Each code can be represented by a unique LDC mnemonic.
The installation can specify up to 256 2-character mnemonics for each TCTTE, and two or more TCTTEs can share a list of these mnemonics. A numeric value (0 through 255) corresponds to each LDC mnemonic for each TCTTE.
A 3600 device and a logical page size are also associated with an LDC. “LDC” or “LDC value” is used in this book to refer to the code specified by the user; “LDC mnemonic” refers to the 2-character symbol that represents the LDC numeric value.
When the LDC option is specified in the CONVERSE command, the numeric value associated with the mnemonic for the particular TCTTE is inserted in the FMH. This value is chosen by the installation, and is interpreted by the 3601 application program.
On output, the FMH can be built by the application program or by CICS®. If your program supplies the FMH, you place it at the front of your output data and specify the FMH option on your CONVERSE command. If you omit the FMH option, CICS will provide an FMH but you must reserve the first three bytes of the message for CICS to fill in.
The use of FMH is optional and is not supported for all terminal types. If not supplied, CICS takes no action, except for 3600/4700 terminals, where an FMH is mandatory. In this case, if FMH is not specified, CICS supplies one and places it in the first 3 bytes of the message, which you must reserve for this purpose.
If the value specified is less than zero, zero is assumed.
If the length of data exceeds the value specified and the NOTRUNCATE option is not present, the data is truncated to that value and the LENGERR condition occurs. The data area specified in the TOLENGTH option is set to the original length of data.
If the length of data exceeds the value specified and the NOTRUNCATE option is present, CICS retains the remaining data and uses it to satisfy subsequent RECEIVE commands. The data area specified in the TOLENGTH option is set to the length of data returned.
If no argument is coded for MAXLENGTH, CICS defaults to TOLENGTH.
If DATALOCATION(ANY) is associated with the application program, the address of the data can be above or below the 16MB line.
If DATALOCATION(BELOW) is associated with the application program, and the data resides above the 16MB line, the data is copied below the 16MB line, and the address of this copy is returned.
If TASKDATAKEY(USER) is specified for the running task, and storage protection is active, the data returned is in a user-key. If TASKDATAKEY(CICS) is specified and storage protection is active, the data returned is in a CICS-key.
If the length of the data exceeds the value specified, but NOTRUNCATE is omitted, the data is truncated to that value, and the LENGERR condition occurs. When the data is received, the data area is set to the length of the data.
For a description of a safe upper limit, see LENGTH options in CICS commands.
Default action: ignore the condition.
Default action: terminate the task abnormally.
Default action: terminate the task abnormally.
Default action: terminate the task abnormally.
Default action: ignore the condition.
A CANCEL TASK request by a user node error program (NEP) may cause this condition if the task has an outstanding terminal control request active when the node abnormal condition program handles the session error.
Default action: terminate the task abnormally with abend code ATNI.