Upgrade VSEESA263, Subset VTAM/FE6:
THIS SUBSET CONTAINS INSTALLATION INFORMATION FOR ACF/VTAM
VERSION 4, RELEASE 2, MODIFICATION 0.
Change Summary
DATE LAST
CHANGED SECTION
1. YY/MM/DD INSTALLATION INFORMATION NO ENTRIES
2. YY/MM/DD DOCUMENTATION CHANGES NO ENTRIES
3. 02/06/14 GENERAL INFORMATION
4. 06/04/24 SERVICE RECOMMENDATIONS
5. YY/MM/DD CROSS PRODUCT DEPENDENCIES NO ENTRIES
DATE APAR PTF VOLID COMMENTS
5 06/04/24 DY46553 UD53054 1000 HIPER VSE HARD WAIT DUE TO LOW
4 05/12/02 DY46463 UD52945 1000 HIPER VTAM INITIALIZATION HANGS
3 05/08/03 DY46402 UD52869 1000 HIPER ABEND - ABEND0C4 ISTLSC6G
2 05/08/03 DY46403 UD52870 1000 HIPER ABEND0A9 OR ABEND0C4 WITH
1 05/08/03 DY46404 UD52870 1000 HIPER ISTAPCPS+X'270' ABEND0C4
THIS SECTION CONTAINS CHANGES TO THE PRODUCT'S PROGRAM DIRECTORY.
1. YY/MM/DD NO ENTRIES
THIS SECTION OUTLINES MAJOR ERRORS IN THE PRODUCT'S PUBLISHED
DOCUMENTATION.
1. YY/MM/DD NO ENTRIES
THIS SECTION CONTAINS GENERAL INFORMATION, I.E. SYSGEN HINTS/TIPS.
2. 02/06/14 When you order VTAM V4R2 for VSE/ESA and/or VM/ESA,
you choose one of three packages:
* VTAM Client/Server
* VTAM MultiDomain
* VTAM InterEnterprise.
VTAM CLIENT/SERVER
The VTAM V4R2 Client/Server package is suited to an
entry-level networking environment. This environment is
typically smaller, like a single host, which does not
require the communications connectivity of larger
networks. Therefore, it does not require NCP ownership or
many of the other networking functions of larger networks.
CLIENT/SERVER RESTRICTIONS
In VTAM Client/Server, some keywords, definition
statements, start options, and operands on commands are
NOT supported. They are listed below.
Definition Statements
LOGAPPL, VRTG, VRTGCPCP, DLURNAME, SRCOUNT, SRTIMER,
CMPAPPLI, CMPAPPL0, LUGROUP, CDRM, NCP
Commands
DISCNTIM, SRCLEAR, SRCOUNT, SRTIMER, MODIFY USERVAR,
VARY LOGON, MODIFY COMPRESS, VARY ACT (LOGON and VRTGCPCP
not supported), MODIFY TRACE (SAVE=YES operand not
supported)
Start Options
AUTOTI, AUTORTRY, BN, BNDYN, BNORD, SNVC, CDSERVR, GWSSCP,
IOPURGE, VRTG, VRTGCPCP, SRCHRED, SRCOUNT, SRTIMER,
CMPVTAM, CMPMIPS, DISCNTIM
Persistent Session Support (not supported)
VTAM MULTIDOMAIN
MultiDomain is the package we recommend for our Version 3
customers. It provides the functional level of operation
needed for most of our VM and VSE environments. It
contains all of the functional capabilities of Client/
Server with additional APPN and subarea functions such as,
LOGAPPL and the capability to own an NCP.
MULTIDOMAIN RESTRICTIONS
In VTAM MultiDomain, some keywords, start options, and
operands on commands are NOT supported. They are listed
below.
Definition Statements
SRCOUNT, SRTIMER, MODIFY RESOURCE (SRCLEAR, SRCOUNT,
SRTIMER not supported)
Start Options
BN, BNDYN, BNORD, SNVC, CDSERVR, GWSSCP, SRCHRED, SRCOUNT,
SRTIMER
Persistent Session Support (not supported)
VTAM INTERENTERPRISE
InterEnterprise includes the functions available in
Client/Server and MultiDomain along with the APPN and
subarea functions that are required in an interconnected
network.
VM/ESA OPTIONAL FEATURE OF VSE/ESA
The VM/ESA Optional Feature is another item that we have
provided in response to our customers request for
lowering the cost of computing. If you currently have
VTAM for VSE and VM running on a single processor which
is eligible for MOSP pricing, or would like to have this
combination, but thought it was too expensive, then
the Version 4 VM/ESA Optional Feature is for you. To
order the optional feature, you must have VTAM V4R2 for
VSE/ESA either installed or on order.
For more detailed information, see the "VTAM Release
Guide for VM/ESA" (GC31-8089), or "VTAM Release Guide for
VSE/ESA" (GC31-8090).
ORDERING VTAM INITIALLY
After you place your initial order for the package you
have selected, you will receive a letter with the program
materials containing your package password. You need
this password to start VTAM. See "Starting VTAM" in the
"VTAM Network Implementation Guide" (SC31-6494).
If you cannot find this document, you can call the Key
Registration Center (1-800-446-8989) and they will give
you your current password either over the phone, by FAX,
or by mail.
CHANGING TO A DIFFERENT PACKAGE
After VTAM is installed, you may decide you need a
different package. You do not have to re-install VTAM.
However, you will need to order the new package and obtain
a password. When you place your order, you need the
following information:
* Your IBM customer number
* The VTAM Version 4 program number:
- VTAM Version 4 for VM/ESA: 5654-010
- VTAM Version 4 for VSE/ESA: 5686-065
- VTAM VM/ESA Feature for VSE/ESA: 5686-065
* The feature order number for the package you want.
(See the VTAM product announcement materials, your IBM
representative, or IBM Direct.)
Obtaining your new password depends on who places the
order
* Customer places the order through IBM Direct
- IBM Direct will enter your order for the new
package but do not currently provide password
information. The order must be processed before you
can call the Key Registration Center to obtain the
new password. This may take from three to five
working days. If you need the password immediately,
it is recommended that you contact an IBM
representative after placing your order. The IBM
representative must generate an "AEFORMS KEYORDER"
request which is described below. If you do not
currently have an IBM representative or you do not
know how to contact one, you can call 1-800-IBM-4YOU
and they will put you in touch with a representative
in your area.
* IBM representative places the order
- After the order has been placed, the IBM
representative should generate an "AEFORMS
KEYORDER" request. They need to indicate on the
request the medium for returning the password (i.e.
via PROFS NOTE, FAX, or mail). If the password
is needed immediately, the representative can call
the Key Registration Center at 1-800-446-8989.
They should inform the Key Center personnel that
they have submitted an "AEFORMS" so that they can
verify the order. The Key Center will provide the
password over the phone.
1. 02/06/14 Storage Requirements VTAM 4.2
=============================
A) SVA size
The size value of the SVA as shipped is
SVA PSIZE=(256K,2000K),SDL=300,GETVIS=768K
This value must be increased if private programs or OEM
programs are loaded into the SVA.
The above value covers all base products, especially
HLASM, REXX, CICS and VTAM.
B) Data Space Sizes
1. General
VTAM requires 1 MB for initialization, in addition, for
each partition running VTAM applications 1 MB.
This would be for example if POWER/PNET through a VTAM
line is used:
1 MB for VTAM, 1 MB for POWER and 1 MB for CICS
That is, in an environment with POWER/PNET 3 MB are
needed as minimum, without POWER/PNET, 2 MB is the
minimum since CICS always needs VTAM. The first data
space of 1 MB is created by VTAM itself, the second
data space is created when the ACB is opened to CICS.
If there are user applications of VTAM active, for each
partition running such applications, 1 MB has to be
added.
2. Maximum Value for VTAM Data Spaces
There is a maximum size for the VTAM data space which
may be specified either through the DFSIZE operand of
the SYSDEF statement or by the DSPACE parameter of the
EXEC job control statement. VTAM expands data spaces in
1 MB increments up to the specified limit.
The DFSIZE is a global value for all VTAM applications,
this value is only for VTAM applications, private usage
of data spaces is not affected. The value specified in
the EXEC JCL statement is only for the related
application and it overwrites the DFSIZE specification.
If DFSIZE is smaller than 1 MB VTAM will take 1 MB. The
IBM provided settings are: VTAM, CICS and POWER have a
DSPACE parameter of 2 MB. DFSIZE is not used. The
maximum of 2 MB will be sufficient for most cases, if
many different request unit sizes are used, we
recommend to change the maximum size to 3 MB.
The DSPACE parameter in the VTAM startup limits the
size for the VTAM data space that supports the VTAM
Control Point application. It does not set a maximum
for data spaces that VTAM gets for support of other
applications. It is the maximum allowed value of data
space VTAM can take from the VSE system data space pool
for itself. The DSPACE parameter in the applications
startup limits the value of data space which can be
used by VTAM to support this specific application.
3. How VTAM uses Data Spaces
The default size allocated is 1 MB for each partition.
From the first 1 MB data space, 1/4 MB is used for data
space management, the rest is also divided in 1/4 MB
pieces and is reclaimed as needed. There are two major
considerations when trying to estimate the size needed
for the VTAM data space:
1. The range of sizes of the request units (RU) being
received by applications in the partition.
2. The number of RUs that have to be queued because
the application does not have RECEIVE RPLs issued to
read incoming RUs.
There are 10 possible different RU size groups. Each
group will obtain a 1/4 MB piece when the first RU of
this size is queued. The groups have following size
limits (in hex):
Group 1 2 3 4 5 6 7 8 9 10
---------------------------------------------------------------
Size (upper limit) 78 F8 1F8 3F8 7F8 FF8 1FF8 7DF8 FBF8 10108
That means 3 MB of data space would allow to have RUs
of all 10 groups - 1/4 MB would be left. A 2 MB data
space would allow 7 groups, a 1 MB data space only
could have 3 different groups. If one quarter MB is
filled up with RUs not being processed, that means the
RUs are not received, the related section will be
extended by another 1/4 MB piece if further RUs need to
be stored for this group. The first quarter MB
reclaimed is not freed till VTAM is shut down,
additionally used quarters for a certain group are
freed if it is no longer used.
So the maximum size of the data space needed for VTAM
and its applications is variable and VTAM extends
dynamically.
4. Detailed Calculation
Minimum size used = 1 + N1 + N2 + N3 (MB)
where N1 is the number of VTAM applications using
RUs with sizes of 3 different groups
N2 is the number of VTAM applications using
RUs with sizes of 4 to 7 different groups
N3 is the number of VTAM applications using
RUs with sizes of 7 to 10 different groups
The above minimum size is the minimum value that should
be specified in the DSIZE operand of the SYSDEF
command.
5. How to verify the settings
The total amount of storage available for data spaces
is limited through the DSIZE parameter of the SYSDEF
command. The standard environments A and C have a DSIZE
value of 4 MB, environment B has 8 MB.
In case data compression is used, 2 MB of data space
are need for the compression logic. This data space may
extend by another 2 MB if needed. The DSIZE parameter
should be increased accordingly if data compression is
used.
The value of DSIZE should be the sum of all VTAM
related data spaces, virtual disks and private data
spaces used in the system.
We recommend to start with a higher DSIZE value than
calculated and adjust the value according to the used
space.
a) The QUERY DSPACE command will show the usage of
data spaces:
DSIZE MAX PARTMAX COMMAX VDISK DFSIZE
DEFINED: 8192K 256 16 5 1 960K
ACTUAL: 3072K 3 3 0 0
AREA DSPS AREA DSPS AREA DSPS AREA DSPS AREA DSPS AREA DSPS
F3 3
The ACTUAL: line shows the amount of space used
(3072K), the last line shows how many data spaces are
used by VTAM (F3).
b) The QUERY DSPACE,F3 command will show more details
about the data spaces of VTAM:
AREA DSPNAME SIZE MAXSIZE SCOPE OWNER DU-AL PASN-AL
F2 ISTA95B8 1024K 2048K ALL F3 X
F3 IST9A785 1024K 2048K ALL F3 X
F3 ISTFB726 1024K 2048K ALL F3 X
F3 ISTA95B8 1024K 2048K ALL F3 X
F4 ISTFB726 1024K 2048K ALL F3 X
6. In case a change is necessary:
If the maximum value of the data space size used by
VTAM should be changed, the related EXEC statement has
to be changed, f.e for VTAM:
// EXEC ISTINCVT,SIZE=ISTINCVT,PARM='CUSTNO=...',DSPACE=4M
This change is in the VTAMSTRT - use skeleton SKVTAM. For
the other VTAM applications proceed accordingly.
If the global value should be used, change the SYSDEF
command in the ALLOC procedure using the related
skeleton SKALLOCx where x is the environment character
A, B or C.
NOTE:
Do not add the SYSDEF command into your IPL procedure,
the subsequently called ALLOC procedure will deactivate
your specification. If you need it in the IPL procedure
f.e. if you use a virtual disk for the label area, be
sure that you have the same values specified in the
ALLOC procedure or that you have deleted the SYSDEF
command there.
IOBUF and LFBUF settings
There were some problems with the setting of LFBUF and
IOBUF. The result of the problem is garbage data is
transferred. This seems to be a real coding problem,
but as a circumvention we recommend that the IOBUF in
VTAM 4.2 should equal what the LFBUF value was in VTAM
3.4. Please refer to the actual information in Retain
for more details or a possible final solution. System
provided settings were.
LFBUF=(70,,,,11),
IOBUF=(70,288,,,11),
To verify the buffer definitions and storage
allocation, following commands are useful:
1.System information
- GETVIS F3
shows the usage of 24 and 31bit GETVIS in VTAM
partition F3.
- MAP F3
shows allocation information about VTAM partition F3.
2.VTAM information
- D NET,BFRUSE
shows information about all buffers and usage of
24 and 31bit system getvis area.
- D NET,vtamopts
shows information about all startup options.
- D NET,STATS,TYPE=VTAM
shows information about VTAM network.
- D NET,STORUSE,DSPNAME=*
shows information about all data spaces accessed
by VTAM.
- D NET,STORUSE,APPL=appl-name
shows information about the data space accessed by
VTAM for specific application appl-name.
- D NET,STORUSE,POOL=*
shows usage information about all VTAM storage
pools
5 06/04/24 PROBLEM: (DY46553) VSE HARD WAIT DUE TO LOW CORE OVERLAY BY
VTAM READ CCW FOR A LOCAL NON-SNA TERMINAL
USERS AFFECTED: All using IOBUF31=YES
RECOMMENDATION: INSTALL UD53054 ON VOLID 1000 (RFE6 )
4 05/12/02 PROBLEM: (DY46463) VTAM INITIALIZATION HANGS IN LARGE
PARTITION
USERS AFFECTED: All running VTAM in a very large z/VSE
partition. The VTAM partition is 2G.
RECOMMENDATION: INSTALL UD52945 ON VOLID 1000 (RFE6 )
3 05/08/03 PROBLEM: (DY46402) ABEND - ABEND0C4 ISTLSC6G TRYING TO SEND
AN NC_ER_OP ER_OP
USERS AFFECTED: All using XCA major nodes with leased
FID4 connections.
RECOMMENDATION: INSTALL UD52869 ON VOLID 1000 (RFE6 )
2 05/08/03 PROBLEM: (DY46403) ABEND0A9 OR ABEND0C4 WITH APPLICATIONS
DUE TO LUCB OVERLAY WITH X'01000000' BECAUSE
PREVIOUS LUCB POINTER PERCEIVED AS NCB .
USERS AFFECTED: All using VRs (Virtual Routes).
RECOMMENDATION: INSTALL UD52870 ON VOLID 1000 (RFE6 )
1 05/08/03 PROBLEM: (DY46404) ISTAPCPS+X'270' ABEND0C4 WITH REG3 ZERO
USERS AFFECTED: All using VRs (Virtual Routes)
RECOMMENDATION: INSTALL UD52870 ON VOLID 1000 (RFE6 )
This section contains information that is dependent upon another
product other than this subset ID. It also contains information
dealing with migration and product coexistance.
1. YY/MM/DD INTERDEPENDENT PRODUCT:
PROBLEM:
USERS AFFECTED:
RECOMMENDATION: INSTALL XXXXXXX ON VOLID XXXX
PTF Include List
UD52869 UD52870 UD52945 UD53054
PTF Exclude List
PE APAR List
End of Upgrade VSEESA263
, Subset VTAM/FE6
, as of 2020/04/09.
|