APAR status
-
Closed as fixed if next.
Error description
-
Customer is FTPng a PDS from one system to another. In the process, FTP must allocate a temporay data set. This allocation failed and FTP issued the following 550 response: 550 Allocation of temporary data set failed: (rc=4, err=-26868, info=0) . FTP is converting the S99ERROR and S99INFO codes from the svc99 call into decimal and displaying the result. Output should be displayed in hex. . Even with a properly converted return code (-26868 converts to a 970c) we should be prefixing the message with a message number which would inform the user to look up the code in the 'Programming: Authorized Assembler Services Guide'. Even when given the correct code, customer did not know where to go to interpret it. . This error is only reported incorrectly by the server when a remote FTP client is putting a PDS to the server and the allocation fails. . KEYWORD: SVC99 allocate temporary data set failed negative error code
Local fix
-
Convert negative return code to hex equivalent. Right most 4 characters are the return code in hex. Example: -26860 -> FF970C -> 970C . Look up return code in 'Programming: Authorized Assembler Services Guide' for allocation errors.
Problem summary
-
**************************************************************** * USERS AFFECTED: All users of the Communications Server * * for OS/390 Release 10 IP * * and z/OS Version 1 Release 2 : FTP * **************************************************************** * PROBLEM DESCRIPTION: Reply "550 Allocation of temporary data * * set failed: (rc=4, err=-26868, info=0)" * * displays the error in decimal which, in * * this case, shows up as a negative * * number. This error should have been * * displayed in hex. * **************************************************************** * RECOMMENDATION: * **************************************************************** A FTP client is attempting to transfer a member of a loadlib. In this particular instance, the allocation of the required temporary data set that is needed at the server to restore the file. The server returned the error in the reply 550 but the error code is given as a negative decimal number which can not be found in the manual. The error code should be returned in hex, which is documented. +-------------------------------------------------------------+ + 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
-
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 MV24541 by Communications Server for OS/390 Development. PTR24541 PTR 24541
APAR Information
-
APAR number
PQ53468
-
Reported component name
TCP/IP V3 MVS
-
Reported component ID
5655HAL00
-
Reported release
50A
-
Status
CLOSED FIN
-
PE
NoPE
-
HIPER
NoHIPER
-
Special Attention
NoSpecatt / Xsystem
-
Submitted date
2001-10-15
-
Closed date
2001-10-18
-
Last modified date
2001-10-18
-
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
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"50A","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
28 March 2021