IBM Support

ACOP041I error on session restart from remote side when DISP=MOD is used in a process copy step.

Technote (troubleshooting)


Situation where a Connect:Direct z/OS system starts a session to Connect:Direct i5/OS:
On first copy attempt the mainframe is getting a SDE0210I allocation error because the destination file on i5/OS is locked.
Error SDE0210I will be handled on mainframe side as retryable
according to the in the initparms.

On a retry of this process during session initiation a restart flag will be forwarded.

In the copy step this restart flag will cause the i5/OS side to deny
such a a copy when DISP=MOD is used with error ACOP041I.

Reason: existing data in the destination file may get lost!

There would be no such a problem for a restart of a copy step where DISP=RPL or DISP=SHR was coded.

When mainframe will get back error ACOP041I the process will be set to hold.
Such a process can't be released again, because still the restart flag will be used.

The process must be submitted again to get this working.

Doing a view process in the process queue on mainframe side should show you how the failing process was coded.
These information then can be used to submit a new process.

This is working as designed.


On a copy restart when using DISP=MOD existing data in the destination file may get lost

Resolving the problem

The process must be submitted again to get this working.

Cross reference information
Segment Product Component Platform Version Edition
Commerce Sterling Connect:Direct for z/OS z/OS 5.1, 5.0, 4.8

Document information

More support for: Sterling Connect:Direct for i5/OS

Software version: 3.6, 3.7

Operating system(s): IBM i

Reference #: 1624075

Modified date: 31 January 2013

Translate this page: