Re: Data not getting written to /tmp

I did a little searching and verified that messages in the form "File QACP###### created in library QTEMP" do seem to imply the v5r2 support is being used, plus that the v5r2 support is the /old implementation/ I had noted. I could not created the QCPTOIMPF data area to test the effects and further confirm, due to lack of authority.

So anyhow, it seems likely that the system being used to perform the CPYTOIMPF is using the deprecated support. If so, I would strongly suggest that those data areas be eliminated; that all import and export requests should be updated to use the new support [i.e. for the current release; whatever that is] in conjunction with the removal of any data areas forcing the features down their v5r2 code path.

Document Number: 553810605
Functional Area: DB2 for i5/OS
Subfunctional Area: CPYTOIMPF, CPYFRMIMPF, CPYTOSTMF, CPYFRMSTMF
Sub-Subfunctional Area: Copy To/From ImportFile or StreamFile
OS/400 Release: 5.4.5; 6.1; 6.1.1; 7.1; V5R3M0; V5R3M5; V5R4M0; V5R4M5; V6R1M0; V6R1M1; V7R1M0
http://www-912.ibm.com/s_dir/SLKBase.nsf/1ac66549a21402188625680b0002037e/f2e5bfd28245fbaa862576dc004e3d55?OpenDocument
"Document Title
Removal of CPYFRMIMPF and CPYTOIMPF 'CPV5R2' Behavior Data Areas

Document Description
This is a document to assist customers in moving away from using the CPYFRMIMPF and CPYTOIMPF data areas that cause V5R2 versions of the code to run. There was a major code rewrite for the CPYFRMIMPF and CPYTOIMPF commands at V5R3M0. This caused several changes to how the commands run and function. ..."

Document Number: 624264439
Functional Area: DB2 for i5/OS
Subfunctional Area: CPYTOIMPF, CPYFRMIMPF, CPYTOSTMF, CPYFRMSTMF
Sub-Subfunctional Area: Copy To/From ImportFile or StreamFile
OS/400 Release: 5.4.5; 6.1; 6.1.1; 7.1; V5R4M0; V5R4M5; V6R1M0; V6R1M1; V7R1M0
http://www-912.ibm.com/s_dir/slkbase.NSF/1ac66549a21402188625680b0002037e/46709df8f0c7a3ff8625799e006028e5?OpenDocument&ExpandSection=2%2C3#_Section2
"Document Title
CPYFRMIMPF and CPYTOIMPF Data Areas

Document Description
This document describes the different data areas that can be used for CPYFRMIMPF and CPYTOIMPF.

1. Data areas to force the V5R2 code paths

These two data areas force the CPYFRMIMPF/CPYTOIMPF to use the V5R2 code paths. ..."



On 05 Apr 2013 23:44, CRPence wrote:

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:
http://www.ibm.com/support/docview.wss?uid=nas2131452d21aaf08d5862570bb004215ad

"OSP-DB-MSGC2M3004-F/QC2IO-T/QCPIMPRT FILE NOT OPENED ..."

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.

<<SNIP>>