No mention of release was noted [that part of the joblog, along with the message identifiers were omitted], but the following describes the /same/ symptom string assuming my guess about the first MsgId is correct. The symptom string as I would have written it:

msgC2M3004 F/QC2IO FM/QC2RIOC1 FP/_Ropen stmt/28
T/QCPEXPRT TM/QCPEXPRT TP/Check_tofile_parameter stmt/1130

The V5R3M0 APAR SE23148 has the symptom string quoted from the following link:

More comments inline:

On 05 Apr 2013 21:17, Gary Kuznitz wrote:
** I changed the Callp to Call 'QCMDEXC'
And I am getting more info in the joblog now.

I don't know why the system is creating this file in QTEMP

File QACP173785 created in library QTEMP.

Given the spooled joblog showing the message identifier and the context, the reason for the file creation may be more obvious. Per only the copied text of the message being given, no context for why it was issued is possible other than a guess. However I recall in the old implementation of the export, that the feature first output to a temporary database file and then used CPYTOSTMF to effect the translation of the text data according to the requirements of the STMFCODPAG, and in that implementation, that the messages for the temporary files were visible. However in a quick test on v5r3, I saw no such messages. I do not recall if perhaps the v5r2 was the /old/ implementation.

Note: in newer releases, there are data area objects with naming QCP* that can be utilized to make the /old implementation/ of the database import and export facility be invoked instead of properly using the currently installed release-level of the features. Best to ensure no such data area is on the system causing an issue.

And then I get this error:
40 04/05/13 19:11:17 QC2IO QSYS *STMT QCPEXPRT QSYS
From module . . . . . . . . : QC2RIOC1
From procedure . . . . . . : _Ropen
Statement . . . . . . . . . : 28
To module . . . . . . . . . : QCPEXPRT
To procedure . . . . . . . : Check_tofile_parameter
Statement . . . . . . . . . : 1130 *PRCLT
Message . . . . : File is not opened.
Cause . . . . . : 1. You attempted to open a file for reading,
but the file does not exist. 2. You attempted to open a file for an
output operation, but the library does not exist. 3. You attempted to
close a file that is not open. 4. The open function ran out of
internal memory. Recovery . . . : 1. When you use fopen or freopen,
specific information on the exception message is contained in
_EXCP_MSGID declared in<stddef.h>. 2. When you use _Ropen, handle I/O
exceptions by specifying a signal handler for the SIGIO signal.
Technical description . : The value of errno is set to ENOTOPEN.

<<SNIP apparent completion message>>

I hope someone on the list will know why the error comes up. Maybe
that's why there aren't any records written to the Tmp folder.

I do expect that error is the origin for the issue, and that the export feature is failing to manifest that error it receives as an indication that the overall copy request failed; i.e. it sends a completion message [for its copy activity], even though it had failed to export any data [into a temporary file].

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page