IO execution not allowed at session initialization

Hello!

I installed on ZOS 2.5 the Natural 9.2.3 and the NDV 9.2.3 + CICS TP 6.2, but I have the following problem when I try to MAP any system entry point via NaturalOne:

This error came out only if I try to send STACK=(LOGON LIB) parameter.

Got new connection
Client USERID arrived
Worker task active, SID=SYSTEMID, client: USERID
ClientDir: Client USERID already stored in Client Directory.
Session runtime connect successful, Lib:
PrintError: IO execution not allowed at session initialization
Cancel IO, A(IO-Buffer)=1E7CC268
Cancel IO done, A(IO-Buffer)=00000000
Connection error, cancel session SYSTEMID
Worker task disconnect, client: USERID
Free LTCB…and finish

Without STACK parameter I got this message:

Got new connection
Client USERID arrived
Worker task active, SID=SYSTEMID, client: USERID
ClientDir: Client USERID already stored in Client Directory.
Session runtime connect successful, Lib:
Exec IO, bufflen:2443

Later when the NDV try to cancel the connected sessions the following messages are arrives:

02 15:29:53 00000013 PrintError: PAL Error, RC:-18, the connection has been gracefully closed
ErrClass:0, Reason:0
02 15:29:53 00000013 Cancel IO, A(IO-Buffer)=1E7B2028
02 15:29:53 00000007 PrintError: PAL Error, RC:-18, the connection has been gracefully closed
ErrClass:0, Reason:0
02 15:29:53 00000007 Cancel IO, A(IO-Buffer)=1E61A028
02 15:29:53 00000013 Cancel IO done, A(IO-Buffer)=FFFFFFFF
02 15:29:53 00000013 Client connection reset, cancel session
02 15:29:53 00000013 PrintError: Error at:CancelSession: Session termination failed
NATURAL session terminated with RC=12
NATURAL FrontEnd error. Function=20, RC=9939/12
NAT9939 Internal: Connection handle missing
02 15:29:53 00000013 Execute IO/NATSOC failed, cancel session
02 15:29:53 00000013 Security LOGON successful, Lib:
02 15:29:53 00000013 PrintError: Error at:LTCB post initialization failed
NATURAL session terminated with RC=12
NATURAL FrontEnd error. Function=20, RC=9939/12
NAT9939 Internal: Connection handle missing
02 15:29:53 00000013 Worker task disconnect, client: USERID
02 15:29:53 0000000D PrintError: PAL Error, RC:-18, the connection has been gracefully closed
ErrClass:0, Reason:0
02 15:29:53 0000000D Cancel IO, A(IO-Buffer)=1E711028
02 15:29:53 00000009 PrintError: PAL Error, RC:-18, the connection has been gracefully closed
ErrClass:0, Reason:0
02 15:29:53 00000009 Cancel IO, A(IO-Buffer)=1E670028
02 15:29:53 00000007 Cancel IO done, A(IO-Buffer)=FFFFFFFF
02 15:29:53 00000007 Client connection reset, cancel session
02 15:29:53 00000007 PrintError: Error at:CancelSession: Session termination failed
NATURAL session terminated with RC=12
NATURAL FrontEnd error. Function=20, RC=9939/12
NAT9939 Internal: Connection handle missing
02 15:29:53 00000007 Execute IO/NATSOC failed, cancel session
02 15:29:53 00000007 Security LOGON successful, Lib:

02 15:29:53 00000007 PrintError: Error at:LTCB post initialization failed
NATURAL session terminated with RC=12
NATURAL FrontEnd error. Function=20, RC=9939/12
NAT9939 Internal: Connection handle missing

I using the following control setup on the NDV STC:

DEFAULT_PROFILE = STARGATE:

INITIAL_USERID = STARGATE:

DBG_CODEPAGE = USER:
FRONTEND_NAME = NATCSRFE:
FRONTEND_OPTIONS = 0X01:
FORCE_IPV4 = YES:
PORT_NUMBER = 7070:
RFE_CICS_TA_NAME = NRFE:
RFE_CICS_FE_NAME = ND923RE:
RFE_CICS_KEEP_TA = YES:
RFE_CICS_TA_PORT = 3014:
RFE_CICS_TA_INIT_TOUT= 20:
HTPMON_PORT = 1235:
THREAD_NUMBER = 5:
THREAD_SIZE = 4096:
TRACE_LEVEL = 15+31:
SECURITY_MODE = IMPERSONATE_LOCAL:
SECURITY_SYSLOG = YES:
SECURITY_CACHING = YES:
SECURITY_TIMEOUT = 360,480:

SESSION_PARAMETER = ‘PROFILE=(STARGATE)’:

TERMINAL_EMULATION = 3270:

I’m new in ADABAS/Natural system programming.

Thank you for your help in advance!

Do you have Natural Security? It’s liklely something is running at startup that is trying to do I/O - PRINT, INPUT,WRITE,DISPLAY,etc. Check the user and library profiles to see what the startup program is set to.

The Idea is good, but the problem is that if I start the server without CICS TP, so I start the NDV server together with BATCH then this logon problem not exist at all.

The problem was that we not defined properly the Natural Security for the CICS started task. :frowning: