APAR status
Closed as fixed if next.
Error description
If a z/OS Communications Server IP Resolver Start Procedure has a //SETUP DD statement that points at an MVS data set that is less than 8 characters long the Resolver address space will not initialize. The start procedure is only used for cases where customization of the default resolver behavior is desired. When the resolver starts the following operator console messages will be issued: EZZ9296I UNABLE TO ACCESS FILE //DD:SETUP - RC 0008000C EZZ9299E RESOLVER INITIALIZATION FAILED - RC 8 RSN 000D0000 The Resolver will end and no TCPIP activity can be done.
Local fix
Two Bypasses are available 1. Just change the MVS data set name to be at least 8 characters long A more complex bypass is 2. Remove the RESOLVER_PROC statement from your BPXPRMxx parmlib member or modify the Resolver Start Procedure you have by removing or commenting out the //SETUP DD statement. Start the changed Resolver Start Procedure Issue a MODIFY <ResolverProcName>,REFRESH,SETUP=MvsDSname the MVSDSname can be the less than 8 character long name.
Problem summary
**************************************************************** * USERS AFFECTED: All users z/OS Version 1 Release 2 & 4 IP: * * RESOLVER * **************************************************************** * PROBLEM DESCRIPTION: Two error messages are issued * * when starting the Resolver. * * EZZ9296I UNABLE TO ACCESS FILE * * //DD:SETUP - RC 0008000C * * EZZ9299E RESOLVER INITIALIZATION * * FAILED - RC 8 RSN 000D0000 * * The Resolver ends and there is no * * TCP/IP activity. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Procedure or Job JCL has a setup DD and the the data set name is less then 8 characters long. //SETUP DD DSN=DSNAMEX(MEM-NAME),DISP=SHR,FREE=CLOSE The problem is that an invalid name is passed to dynamic allocation and the length is always set to 8 characters. When dynamic allocation is requested for this data set, the DD:NAME is passed but the move is done for 7 characters, the length of the dsn. Then Dynamic Allocation is told that the name is 8 characters long. The allocation fails, the error messages are issued, and the job terminates. The problem can be avoided by making the dataset name, in this case a PDS, 8 characters long. This way the DD:NAME will be padded out to 8 characters with blanks. +-------------------------------------------------------------+ + 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
Temporary fix
Comments
The Resolver will be changed to pass the correct name. This APAR is being closed FIN (Fixed If Next) with concurrence from the submitting customer. This means that a fix to this APAR is expected to be delivered from IBM in a release (if any) to be available within the next 18 months. This problem will be tracked as PTR MV28144 by Communications Server for OS/390 Development. PTR28144 PTR 28144
APAR Information
APAR number
PQ73066
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
120
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2003-04-10
Closed date
2003-04-21
Last modified date
2003-04-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R120 PSN
UP
R140 PSN
UP
[{"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":"120","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":"120","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
21 April 2003