Landmark Lighting D20R2-06/99 - Manual (Page 80)

Step 6 Set up network requirements for non-SNA terminals.
This section primarily applies if you intend to log onto the
Landmark PerformanceWorks MVS product from a non-SNA
terminal that either is remote or will be in cross-domain session
with the product. It also may apply to SNA sessions if the
outbound RUSIZE in the BIND is very large or is not specified. If
none of these conditions apply to your use of the product, you can
skip this section.
Landmark PerformanceWorks MVS products sometimes transmit
very large outbound data streams, especially if the terminal is a
color terminal with a large screen (a 3270 model 3, 4, or 5). Since
non-SNA terminals do not support chaining, the entire screen must
be sent in one transmission. In some networks, the large size of
these transmissions can be a problem for the network.
To support the largest possible transmission, the MAXDATA
parameter on any Network Control Program (NCP) between the
terminal and the host in which the product is running should be set
to at least 14,000 bytes. MAXDATA is the maximum message size
the NCP will accept. Most screens are much smaller than 14,000,
but this is a safe value for MAXDATA that no product screen
should ever exceed. If none of your terminals use color, you may
be able to run with a smaller value.
MAXDATA should not exceed
the product of MAXBFRU
and UNITSZ. If you change MAXDATA, be aware that its value is constrained by
the values of the MAXBFRU parameter (the number of host buffers
VTAM uses to communicate with NCP) and the UNITSZ parameter
(the size of each host buffer). The MAXDATA value should not
exceed the product of MAXBFRU and UNITSZ.
Step 7 Identify the applid of the primary session of each product.
Identify the applid of the primary session for each product using
Landmark product communication on your system. Primary
sessions are the product sessions accessed when you enter the JUMP
command to explicitly access another product. Each unique
Landmark PerformanceWorks MVS product on your system should
have at least one primary session. More than one primary session
can be defined for each. When more than one primary session is
defined and a JUMP command is issued, the first primary session
found active is used to satisfy the JUMP request.
Primary sessions are actually defined on the Remote Session
Definition screen in Step 8, but you should know what the applid
of the primary session is for each product before you start Step 8. If
an address space is not the primary session, it is called a secondary
session.
If no primary session is active when the JUMP command is issued,
the first secondary session found active is used to satisfy the JUMP
request.
Setting Up Landmark Product Communication Chapter 3: Landmark Product Communication
3-8