CRTE and uppercase translation
A description of how to initiate a CRTE session and the required input.
Initiate a CRTE session
CRTE SYSID(xxxx),TRPROF(yyyyyyyy)
Translation
to uppercase is dictated by the typeterm of the terminal at which
CRTE was entered and CRTE’s transaction profile definition as shown
in Table 1.| TYPETERM UCTRAN | CRTE PROFILE UCTRAN | INPUT TRANSLATED TO UPPERCASE |
|---|---|---|
| YES | YES/NO | ALL OF THE INPUT |
| NO | NO | NONE OF THE INPUT. See note. |
| NO | YES | ALL OF THE INPUT EXCEPT THE TRANSID. See note. |
| TRANID | YES | ALL OF THE INPUT |
| TRANID | NO | TRANSID ONLY |
| Note: If
the transid CRTE is not entered in uppercase, it will not be recognized
(unless there is a lower/mixed case alias), and message DFHAC2001
will be issued.
|
||
Input within the CRTE session
During the CRTE routing session, uppercase translation is dictated by the typeterm of the terminal at which CRTE was initiated and the transaction profile definition of the transaction being initiated (which has to be a valid transaction on the application owning region) as shown in Table 2.
| TYPETERM UCTRAN | TRANSACTION PROFILE (AOR) UCTRAN | INPUT TRANSLATED TO UPPERCASE |
|---|---|---|
| YES | YES/NO | ALL OF THE INPUT |
| NO | NO | NONE OF THE INPUT. See note. |
| NO | YES | ALL OF THE INPUT EXCEPT THE TRANSID. See note. |
| TRANID | YES | ALL OF THE INPUT |
| TRANID | NO | TRANSID ONLY |
| Note: If
the transid CRTE is not entered in uppercase, it will not be recognized
(unless there is a lower/mixed case alias defined on the AOR) and
message DFHAC2001 will be issued.
|
||
During a CRTE routing session, if the first six characters entered at a screen are CANCEL, CICS will recognize this input in upper, lower or mixed case and end the routing session.
Be aware that when transaction routing from CICS® Transaction Server for z/OS®, Version 5 Release 4 to an earlier release of CICS that does not support transaction based uppercase translation, uppercase translation only occurs if it is specified in the typeterm.