Pathway/iTS SCREEN COBOL Reference Manual (G06.24+, H06.03+, Pathway/iTS 1.0+)

Advisory Messages
Compaq NonStop™ Pathway/iTS SCREEN COBOL Reference Manual—426750-001
A-4
Modifying or Replacing the Advisory Message
Routine
18
Cause. Katakana data was entered on a device that has not been configured for
Katakana support.
19
Cause. Translation routines were unable to process the input character stream.
Modifying or Replacing the Advisory Message
Routine
You can modify the Pathway advisory message routine or replace it with a routine of
your own.
If you want to change the text of the messages or add error messages for use in
association with your own user conversion procedures, you can modify the existing
advisory-message routine, which is provided in TLIB. This routine is written in the
Portable Transaction Application Language (pTAL). A sample source listing (the actual
source in TLIB may differ somewhat) is given in Example A-1
.
To replace the routine, you must write a replacement procedure in pTAL. Whether you
modify or replace the routine, after compilation you must use the nld utility to link
your procedures in the native TCP user library object file, PATHTCPL.
The declaration for the advisory message procedure is as follows:
PROC ADVISORY^MESSAGE( MSGNUM, BUF, MESSLEN );
INT MSGNUM; ! THE ERROR NUMBER
STRING .BUF; ! PLACE MESSAGE HERE
INT .MESSLEN; ! RETURN MESSAGE LENGTH HERE (MAX 255)
The MSGNUM parameter is the internal message number as given in the list of advisory
messages in this appendix, or as returned by the user conversion procedure. If new
WRONG FORMAT: KATAKANA NOT ALLOWED
WRONG FORMAT: INVALID ASIAN CHARACTERS
Note. In releases prior to D40, advisory message routines were written in TAL. In D40 and
later releases (including all G-series releases), advisory message routines must be written in
pTAL. pTAL is based on TAL. The pTAL language excludes architecture-specific TAL
constructs and includes new constructs that replace the architecture-specific constructs. You
can write advisory message routines that can be compiled by both the TAL and the pTAL
compilers, thus enabling you to use the same source code for different releases of
Pathway/iTS.
If you are converting existing alternate advisory message routines to pTAL for use with a D40
or later version of Pathway/iTS, refer to the pTAL Conversion Guide and the pTAL Reference
Manual for further information. Many advisory message routines are simple enough that no
changes will be needed.