CPYTOIMPF with QNTC (formerly Help with SWAPUSRPRF)

Further results:

Executing the same exact CPYTOIMPF CMD from our test machine works fine
(many times)

Looking at the joblog of the failing job on the Prod machine shows that
although a
CPC2958 "All records copied from file CRDSNDF in AVLIB" MSG was received
it was preceded by quite a few (20) MCH6903 "The heap space has reached its
maximum allowable size" MSGs

I guess this is the culprit

Any ideas, anyone?

TIA
Gad




Hello Rob, Alan , Scott

Further testing has proved me partially wrong .

Occasionally the CL PGM does manage to create a non-empty target text file
although partially (not the entire file).
most of the times though, an empty file is created.

executing the CPYTOIMPF part directly from the command line (using the
WINUSER profile) is less erratic but still most of the times an empty file
is created.

I conclude then that the problem does not lie with SWAPUSRPRFF

While debugging I changed the target directory to an
NFS-mounted-Windows-directory
(no need to swap user) and with this target directory the CPYTOIMPF
succeeded every time
(much slower though )
The A/M NFS mount bypass the Windows permission mechanism, perhaps
that's why it succeeds .

Our Windows domain administrator re-checked permissions on the file server
side and said
they are correct.

I'm at a loss

Any idea, anyone?

Gad

date: Wed, 21 Oct 2020 10:36:09 -0500
from: Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
subject: Re: Help with SWAPUSRPRF

Gad,

What is SWAPUSRPRF??? Is this a utility that you (or someone in your
shop) wrote?? Can you tell us more about how it works and how error
handling with this program is intended to work?

My guess is that this SWAPUSRPRF program uses either the profile handle
or profile token APIs to change the userid of the job.? If this is the
case, then it wouldn't be related to activation groups, since these
tools work at the job level, not the activation group level.

Have you tried calling the profile handle APIs directly from your CL
program?? Does that have the same problem?? If so, it would tell you
that the problem is in those APIs.? If not, you'd know the problem is in
the SWAPUSRPRF program and you could troubleshoot it accordingly.

-SK