A fix is available
APAR status
Closed as program error.
Error description
RESTRICTAPPL specification of a singular LU or LUG should allow this value to represent a range of LUNAMES or a range of PRTNAMES (or a single terminal LU, or a single printer LU). Currently, if the specification is, for example, an LUGROUP, and assignment for a Telnet printer is in progress, a database failure with rc 3005 will be issued because the CVB_Printer bit will be set but the TCL type will not match. A similar error would occur if lookup was for a terminal LU but the TCL type was not for a LU or LUGROUP.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: USERS AFFECTED: All users of Communications * * Server z/OS Version 1 Release 5 IP Telnet * * facilities. * **************************************************************** * PROBLEM DESCRIPTION: A terminal LU connection selects an * * Appl that is a Restrictappl with LUG * * prtgroupname. Because the Applmap for * * this is an object with subtype of * * Prtgroup, and CVB_Printer is off, * * error code 3005 is produced which * * denotes data base corruption. * **************************************************************** * RECOMMENDATION: * **************************************************************** Since PrtDefaultAppl and PRTMAP with Defappl was introduced in R140, there is no way to have an AllowAppl or RestrictAppl with a LUG that has both printer and terminal Lunames in it. The only way is to list every single Luname and Prtname. There needs to be a way for the user to build a group that has both terminal and printer Lunames in it. Also this will provide a more meaningful error return code when the Luname or Prtname of the connection is not in the Allow/Restrict Appl LUG. +-------------------------------------------------------------+ + Please check our Communications Server for OS/390 homepages + + for common networking tips and fixes. The URL for these + + homepages can be found in Informational APAR II11334. + +-------------------------------------------------------------+
Problem conclusion
This apar will allow either a PRTGROUP or an LUGROUP to be specified on the Allowappl APPL1 LUG grpname or the Restrictappl User User1 LUG grpname. This group can contain both printer and terminal LUNAMEs in it or ranges of both. Note that with R140, there are no duplicate rangelists built. Other Lugroups or PrtGroups that have the same ranges just point to the first one that was created. EZBTPGLP will allow the ApplMapgrp to be either PrtGroup or LuGroup. This must be done since now, when a BIND comes from an Appl for a Printer, the authorization is checked for the Printer to see if it is allowed to be used. If the LUNAME assigned to the connection is not in this group error code 3057 will be issued, which means that the LU/PRT MAP has a conflict with the ApplMapGrp. This will allow both printer and terminal LUNAMES to be specified for an AllowAppl or RestrictAppl statement. For instance Profile has the following: LUGROUP GRPLUA TCPM1141..TCPM1160 ENDLUGROUP PRTGROUP GRPPRTA TCPM1121..TCPM1140 ENDPRTGROUP LUGROUP GRPAPPL TCPM1121..TCPM1140 TCPM1141..TCPM1160 ENDLUGRP Allowappl Appl1 LUG GRPAPPL The rangelists for GRPLUA and GRPPRTA will be used by GRPAPPL. Now both printers and terminals can be on the same Allowappl or Restrictappl. Documentation change: SC31877602 V1R5 IBM Communications Server: IP Configuration Reference Under 2.6.3.2 for ALLOWAPPL under the description for LUG Change to read: LUG The name of a PRTGROUP or LUGROUP. This group can contain the names or rangelist names of both printer and terminal LUNAMEs. The same ranges or names may have been specified in prior PRTGROUPS or LUGROUPS and if so, will occupy the same storage. This will allow both printers and terminals to be on the same AllowAppl statement. Under 2.6.3.23 for RestrictAppl under the description for LUG Change to read: LUG The name of a PRTGROUP or LUGROUP. This group can contain the names or rangelist names of both printer and terminal LUNAMEs. The same ranges or names may have been specified in prior PRTGROUPs or LUGROUPs and if so, will occupy the same storage. This will allow both printers and terminals to be on the same Restrictappl statement. * Cross Reference between External and Internal Names
Temporary fix
Comments
APAR Information
APAR number
PQ78422
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
150
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2003-09-12
Closed date
2003-09-15
Last modified date
2003-11-02
APAR is sysrouted FROM one or more of the following:
PQ75705
APAR is sysrouted TO one or more of the following:
UQ80184
Modules/Macros
EZBTPGLP
| SC31877604 |
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
R150 PSY UQ80184
UP03/10/06 P F310
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"150","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"150","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 November 2003