 |
This is what you do:
- Check whether you are already using a LOGMODE table. If you are not,
you must create one with the MODETAB macro. It takes the form:
tabname MODETAB
where tabname is the name of the LOGMODE table.
If you do not create a logmode table, the VTAM default table,
ISTINCLM, is used, and this is not adequate for many of the operations
that can be done by GDDM.
- Check the MODEENT macros in the logmode table (or create them if you
do not already have a logmode table). Examples of MODEENT macros are
given in Table 6, and instructions on setting up the PSERVIC operand
are given in "The PSERVIC operand of the MODEENT macro" in
topic 2.2.3. You are strongly recommended to use the given values; if
you do not, your computer system may not work correctly.
When checking or writing your MODEENT macros, note these important
points:
- The examples are samples only. If the given PSERVIC values are
followed exactly, GDDM will work. However, you may have problems
if you change the values. In particular, note the RUSIZES (see
next point).
- The outgoing request unit (RU) size for SNA 3270 terminals (the
second byte in the RUSIZES operand) should be checked carefully.
- X'87' (indicating 1024 decimal) is suggested as an outgoing RU
size. This may be too large for some subsystems.
- For display terminals attached through a 3274-1A controller,
the outgoing RU size must not exceed X'C7' (indicating 1536
decimal).
- The SRCVPAC (secondary receive pacing) value must be specified for
the terminal, workstation, or multistation as follows (where n is
the SRCVPAC value, and m is the outgoing maximum RU size):
- For SNA 3179-G1, 3179-G2, 3192-G, or 3472-G terminals:
-
(2 n - 1) m 7680
- For SNA 3270-PC/G and /GX workstations, and 5550 multistations:
-
(2 n - 1) m 3584
- For SNA 3193 terminals:
- The fixed size of buffer (7680 bytes) is shared for the pacing
buffer by the two LTs that the 3193 supports.
The maximum RU length that the PLU can send is defined in byte 11
of the BIND, and the pacing count is specified in byte 9.
The 3193 accepts a maximum RU size and a pacing count within the
following limits:
- On nonqueriable printers, the GDDM TSO print utility uses the
existence of an alternate screen size to determine which APL
character set feature to assume.
If APL is to be used in the TSO print utility, you must specify an
alternate size on any nonqueriable printer on which this is valid,
even when it is the same as the primary size. The presence of an
alternate size is used by GDDM to differentiate between 3268 and
3287 printers.
For example, on a 3274-attached 3287 printer with a 2KB buffer
specification of 1920, an alternate size of 1920 should be given.
- On nonqueriable display terminals for TSO, GDDM relies on the
default and alternate screen sizes being different to establish
the type of APL character set that will be sent to the terminal.
If you use APL and need to have the default and alternate screen
size the same for nonqueriable display (non-printer) terminals,
see the sections on APL and GDDM in the GDDM System Customization
and Administration book.
- Check that the MODETAB and DLOGMOD operands have been included in your
system definition table and that they point to the correct logmode
tables and MODEENT entries for the terminals.
You should specifically ensure that the DLOGMOD operands are always
explicitly included, and not allowed to default.
The MODETAB and DLOGMOD operands may be coded for individual terminals
in the LU, LOCAL, or TERMINAL macros, or for many terminals in the
GROUP, LINE, or CLUSTER macros. Examples of the use of these macros
are shown in Table 7.
- For queriable non-SNA terminals, FEATUR2=EDATS must be included in the
TERMINAL macro for individual terminals, or at a higher level for many
terminals in the GROUP, LINE, or CLUSTER macros.
- Consider the use of VPACING to improve performance because of the
large data streams generated by GDDM.
- If non-SNA displays are going to be used, consider the size of the I/O
buffer pool as specified by the IOBUF parameter in VTAM. The large
size of the data streams generated by GDDM and the mode in which they
are sent by GDDM may require an increase in the value of this
parameter.
- You must define to the host computer as "queriable," all personal
computer systems you intend to use with GDDM-PCLK or GDDM-OS/2 Link to
enable file transfer between the host computer system and the personal
computer system to work.
|
| Table 6. Examples of MODEENT macros |
The MODEENT macro for non-SNA 3270 display terminals and printers:
MODEENT LOGMODE=modname, C
TYPE=1, C
FMPROF=X'02', C
TSPROF=X'02', C
PRIPROT=X'71', C
SECPROT=X'40', C
COMPROT=X'2000', C
PSERVIC=X'..... |
The MODEENT macro for SNA 3179-G, 3192-G1, 3192-G2, 3472-G, 3193
display terminals; 3270-PC/G, 3270-PC/GX, and PS/2 workstations; and
5550 multistations:
MODEENT LOGMODE=modname, C
TYPE=1, C
FMPROF=X'03', C
TSPROF=X'03', C
PRIPROT=X'B1', C
SECPROT=X'90', C
COMPROT=X'3080', C
RUSIZES=X'8687', C
PSNDPAC=X'01' C
SRCVPAC=X'01' C
PSERVIC=X'..... |
The MODEENT macro for SNA 3270 display terminals and printers excluded
from the above:
MODEENT LOGMODE=modname, C
TYPE=1, C
FMPROF=X'03', C
TSPROF=X'03', C
PRIPROT=X'B1', C
SECPROT=X'90', C
COMPROT=X'3080', C
RUSIZES=X'8587', C
PSERVIC=X'..... |
The MODEENT macro for SCS and IPDS printers with FMH-1 support
(queriable SCS printers):
MODEENT LOGMODE=modname, C
TYPE=1, C
FMPROF=X'03', C
TSPROF=X'03', C
PRIPROT=X'B1', C
SECPROT=X'90', C
COMPROT=X'7080', C
RUSIZES=X'86C7', C
PSNDPAC=X'01', C
SRCVPAC=X'01', C
PSERVIC=X'..... |
The MODEENT macro for SCS printers without FMH-1 support (nonqueriable
SCS printers):
MODEENT LOGMODE=modname, C
TYPE=1, C
FMPROF=X'03', C
TSPROF=X'03', C
PRIPROT=X'B1', C
SECPROT=X'90', C
COMPROT=X'3080', C
RUSIZES=X'8585', (3276-attached) C
or
RUSIZES=X'8587', (3174/3274-attached)C
PSNDPAC=X'01', C
SRCVPAC=X'01', C
PSERVIC=X'..... |
|
| Table 7. Examples of LU, TERMINAL, and LOCAL macros |
The LU macro for SNA 3270 devices:
LU LOCADDR=addr, C
MODETAB=tabname, C
DLOGMOD=modname, C
................
other parameters
The MODETAB and DLOGMOD operands can also be specified on the PU
macro.
The LOCAL macro for non-SNA 3270 devices:
LOCAL CUADDR=addr, C
MODETAB=tabname, C
DLOGMOD=modname, C
................
other parameters
;
The TERMINAL macro for non-SNA 3270 devices:
TERMINAL ADDR=addr, C
MODETAB=tabname, C
DLOGMOD=modname, C
FEATUR2=EDATS, C
................
other parameters
Notes:
1. Specify FEATUR2=EDATS only for queriable devices.
2. Verify that FEATUR2=MODEL1 is not implicitly specified for devices
that have a default buffer size larger than 480 bytes.
&nb
sp;
3. You can also specify the FEATUR2, MODETAB, and DLOGMOD operands on
the GROUP, LINE, and CLUSTER macros.
4. Always specify the DLOGMOD operand explicitly; you should not let
it default. |
|
GDDM V3R2 System Customization and Administration
Copyright IBM Corporation 1990, 2012