A fix is available
APAR status
Closed as program error.
Error description
RSH fails when using RHOSTS on the server and requiring the local userid to be sent as part of the command string. If you are using RSH in batch and have an INPUT DD defined the local userid is not sent as part of the command string. The server will fail the login request if the local userid is required. Other possible symptoms: remshd: Login incorrect. EZA5051E The call to rcmd_af procedure failed: EDC8114I Address family not supported. rsn = 112B0000 EZA4994I Foreign host aborted the connection. VERIFICATION STEPS: A PKTTRACE of the failing connection will show only the remote USERID being sent prior to the actual command.
Local fix
Delete the INPUT DD. Steplib to RSH code prior to z/OS V1R5. It is in SEZALINK prior to z/OS V1R4. In SEZALOAD for V1R4 and above.
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Release 5, 6 & 7 IP * * RSH client TSO command * **************************************************************** * PROBLEM DESCRIPTION: TSO RSH client commands issued with * * an INPUT DD allocated will not send * * the local userid associated with * * the command to the remote shell * * server. * * This can cause LOGIN failures at the * * server host. * **************************************************************** * RECOMMENDATION: * **************************************************************** The TSO RSH client code did not send the local userid associated with the command to the remote shell server if an INPUT DD was allocated. +-------------------------------------------------------------+ + 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
The TSO RSH client will always send the local userid that issued the command to the remote shell server. The client's debug message, EZA5025I, is changed to display the local userid (locuser:) that is being sent to the remote shell server. **************************************************************** * FUNCTION AFFECTED: Communications Server TCP/IP (PK16976) * * RSH * **************************************************************** * DESCRIPTION : Documentation updates * **************************************************************** * TIMING : None * **************************************************************** z/OS Communications Server: IP Messages Volume 1 (EZA) Document Number: SC31-8783 --------------------------- Message Number: EZA5025I EZA5025I Calling function rcmd_af with: Host: AAA user BBB, cmd CCC, port DDD is changed to: EZA5025I Calling function rcmd_af with: Host: AAA locuser: BBB user: CCC cmd: DDD port: EEE Explanation: This message lists the host, local userid, remote userid, command, and port that are being passed to the local rcmd_af function which does the work of passing the information to the remote shell server. - AAA is the host that the command is being passed to - BBB is the userid of the local user issuing the RSH command - CCC is the logon ID of the user on the remote system - DDD is the command that is being passed to the host - EEE is the port number of the remote shell server **************************************************************** * FUNCTION AFFECTED: Communications Server TCP/IP (PK16976) * * RSH * **************************************************************** * DESCRIPTION : Other * **************************************************************** * TIMING : Pre-APPLY * **************************************************************** The RSH debug message EZA5025I has been changed to include the userid of the local userid (locuser:) that is issuing the RSH command. Any screen scrapers or applications currently using the text of the message should be reviewed to see what if any change may be necessary to process this new information. * Cross Reference between External and Internal Names EZATRSH (TSORSH ) EZATRSH (TSORSH ) EZATRSH (TSORSH )
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PK16976
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
160
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2005-12-19
Closed date
2006-01-17
Last modified date
2006-04-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK10872 UK10873 UK10874
Modules/Macros
EZATRSH
| SC31878306 | SC31878305 | SC31878304 | GC31878206 | GC31878205 |
| GC31878204 |
Fix information
Fixed component name
TCP/IP V3 MVS
Fixed component ID
5655HAL00
Applicable component levels
R150 PSY UK10872
UP06/03/03 P F603
R160 PSY UK10873
UP06/03/03 P F603
R170 PSY UK10874
UP06/03/03 P F603
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":"160","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":"160","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
05 April 2006