ASTYPE

GDDM V3R2 Base Application Programming Reference

ASTYPE

GDDM V3R2 Base Application Programming Reference
SC33-0868-02

Function

To override alphanumeric character-code assignments.

Note: Code page conversion functions are recommended in preference to the ASTYPE call. Support for the call is continued for compatibility reasons, and to support APL code page 293.


   ASTYPE      (type)

   APL code               111
   GDDM RCP code          X'0C081300' (201855744)

Parameters

type (specified by user) (fullword integer)
The new type number. Possible values are:

0

Translation from application code page to device code page.

1

No translation, except the removal of invalid characters.

2

EBCDIC: GDDM assumes the terminal is an EBCDIC terminal and finds a matching type number from the EBCDIC group.

3

Kanji/Hangeul: GDDM assumes the terminal is a Kanji/Hangeul terminal and finds a matching type number from the Kanji/Hangeul group.

n

Select type "n," where "n" is from the range supplied for your installation, overriding the default.

Description

Overrides alphanumeric character-code assignments by defining a type that is associated with a set of translation tables to be used on alphanumeric fields.

GDDM uses code conversion tables to ensure that a hexadecimal character code appears as the same character on all devices, thus giving programs a degree of device-independence. The meanings assumed for the hexadecimal values are shown in Figure 1, Figure 2, and Figure 3.

Figure 1. GDDM default EBCDIC character codes (code page 00351)






            




   Figure 2. Katakana character codes (Tables 32772, 32792, and 32793) (code
             page 00290)






            




   Figure 3. Japan (Latin) extended character codes (code page 01027)

The sets of translation tables are associated with type numbers that, in turn, are associated with device characteristics. It is the type number that is specified in the ASTYPE call.

At initialization, GDDM discovers the type of device in use and, by selecting a type number, specifies a set of translation tables. The ASTYPE call can be used either to specify a particular device type, or to specify the assumptions that GDDM uses to select a device type - for example, to assume that the device is a Kanji/Hangeul device.

The translation type you specify takes effect when data is transmitted to the device. To make it effective for data that was transmitted previously, call FSREST to cause retransmission of all the data to the device.

The ASTYPE call is a specialized call and should not be used in normal programming. A full description of the translation tables and associated type numbers is in the GDDM System Customization and Administration book.

ASTYPE is a tool for system programmers and special situations. Usually, ASTYPE should be left to the default. An example of the use of ASTYPE would be to allow a Kanji/Hangeul terminal to be used with APL. ASTYPE(2) would be specified before the use of APL and ASTYPE(3) before the use of Kanji/Hangeul.

The effect of a type value of 0, which is the default for the ASTYPE parameter, causes translation from the application code page to the device code page. However, the results, under Version 2 Release 2 of GDDM, will be the same as under earlier releases if ADMDATRN was not modified in the earlier releases and if no CECP application code page is explicitly specified.

Using an application code page of 00351 is equivalent to executing an ASTYPE call with a type value of 0 in an earlier release.

Using an application code page of 00290 or 1027 (GDDM Katakana) is equivalent to executing an ASTYPE call with a type value of 3 in an earlier release.

Executing an ASTYPE call with a type value of 293 will select an application code page of 293 (suitable for use with APL) on terminals that support it.

Principal errors

ADM0216 E: TYPE n IS INVALID

Notices | Terms of use | Support | Contact z/OS