IEA602I ADDRESS SPACE CREATE FAILED. MAXUSERS WOULD HAVE BEEN EXCEEDED

Discussion of Co:Z sftp, a port of OpenSSH sftp for z/OS
Post Reply
D#H
Posts: 7
Joined: Mon Feb 22, 2016 4:00 pm

IEA602I ADDRESS SPACE CREATE FAILED. MAXUSERS WOULD HAVE BEEN EXCEEDED

Post by D#H »

System is operating on z/OS V2R4 at RSU2102.
A Redhat Linux data transfer client is migrating from FTP to openssh sftp, using the Co:Z Toolkit for MVS dataset allocation.
The client successfully makes a connection, authenticates, and attempts to store that data on the mainframe.
The /tmp/sftp-server log shows the following:
/WMD2/tmp/sftp-server.ftpnifi.244.131227.16909988.log *********************************************************** Top of Data
Co:Z SFTP Server version: 6.2.0 (7.6p1) 2020-10-30 Copyright (C) Dovetailed Technologies, LLC. 2008-2020. All rights reserved.
.13:12:27.868787. session opened for local user FTPNIFI from
.10.246.192.154.. Connection established, local_addr=172.26.250.71 local_port=2200 remote_addr=10.246.192.154 remote_port=41136
.13:12:27.885562. opendir "/+mode=text,blksize=27000,recfm=fb,lrecl=3000,space=cyl.100.80".
.13:12:27.888040. closedir "/+mode=text,blksize=27000,recfm=fb,lrecl=3000,space=cyl.100.80".
.13:12:27.890743. sent status No such file.
.13:12:27.893128. sent status No such file.
.13:12:27.893879. open "//N01.FH.WHS.FTP.DC4034.DATA(+1)" flags WRITE,CREATE,TRUNCATE mode 0666.
ZosSettings.I.:
Transfer options: blksize=27000,clientcp=ISO8859-1,lrecl=3000,mode=text,recfm=fb,servercp=IBM-1047,space=cyl.100.80,trim
ZosDataset.I.: Opening dataset N01.FH.WHS.FTP.DC4034.DATA(+1) for write with options: blksize(27000) lrecl(3000) recfm(f,b) cyl space(100,80) new catalog
IKJ56229I DATA SET N01.FH.WHS.FTP.DC4034.DATA NOT ALLOCATED, CATALOG ERROR+
IKJ56229I DATA SET NAME CONFLICTS WITH EXISTING DATA SET NAME OR USER IS NOT AUTHORIZED TO PERFORM THE OPERATION.
DatasetHandler.E.: BPXWDYN allocation failed S99ERROR=0x1708 S99INFO=0x0002
DatasetHandler.E.: BPXWDYN command was: "alloc fi(SYS00006) reuse msg(2) da('N01.FH.WHS.FTP.DC4034.DATA(+1)') blksize(27000) lrecl(3000) recfm(f,b) cyl space(100,80) new catalog"
DatasetHandler.E.: Dataset N01.FH.WHS.FTP.DC4034.DATA(+1) open error: EDC5000I No error occurred. (errno2=0xC4070044)
IKJ56247I FILE SYS00006 NOT UNALLOCATED, IS NOT ALLOCATED
.13:12:27.905494. sent status Failure.
.13:52:56.306571. session closed for local user FTPNIFI from .10.246.192.154..
********************************************************** Bottom of Data
-------------------------------------------
The connection is reset after 3 seconds, and the client tries again.
For some reason the actual connections is not closed for 40 seconds.
Eventually, enough address spaces are setup to the point of the IPL'd limit and message IEA602I ADDRESS SPACE CREATE FAILED. MAXUSERS WOULD HAVE BEEN EXCEEDED.
................................................................
This situation is a problem for the health of the z/OS system.
What could be wrong with the address space being left orphaned.
Kind regards,
Dan Hanschu, (417)850-2432, but prefer updates in this forum or email communications at dphansc@wal-mart.com
dovetail
Site Admin
Posts: 2022
Joined: Thu Jul 29, 2004 12:12 pm

Re: IEA602I ADDRESS SPACE CREATE FAILED. MAXUSERS WOULD HAVE BEEN EXCEEDED

Post by dovetail »

The last message in the Co:Z SFTP server session log ("session closed for local user...") means that the Co:Z SFTP server process ended.
It sounds like what you are saying is that the underlying SSH connection (managed by IBM z/OS SSHD) is not terminating.
I would suggest that you check the SSHD log (in SYSLOGD) for messages that should be present showing that sftp completed and
afterward that the SSH connection terminated.

One possibility is that the remote client just never closed the SSH connection, but just started another. This is sometimes a problem with user-written
applications that use an SSH/SFTP library.

It appears to us that Co:Z SFTP server is functioning correctly. The error in the CO:Z SFTP server log is a DYNALLOC error returned by z/OS when trying to allocate a new GDG member.

If you believe that there is a problem with SSHD connection termination, you might consider contacting IBM.
Post Reply