MustGather: CPYTOIMPF/CPYFRMIMPF Issues

Troubleshooting

Problem

This document describes the necessary information that needs to be collected to aid in quicker resolution of CPYTOIMPF or CPYFRMIMPF issues.

Resolving The Problem

For issues concerning CPYFRMIMPF and CPYTOIMPF this document includes the recommended data collection for debug.

This is by no means all inclusive; however, it is meant as a starting point for document collection.

If you encounter a CPYTOIMPF or CPYFRMIMPF issue collect the following information using either method A or method B as it is related to the issue:

Method A - QMGTOOLS

The below steps assume you have the latest version of QMGTOOLS.

Re-create Information, if possible:

1. CPYTOIMPF -> FROMFILE

CPYFRMIMPF -> TOFILE

saved to an IBM i savefile using SAVOBJ.

2. CPYTOIMPF -> TOFILE

CPYFRMIMPF -> FROMFILE

saved to an IBM i savefile using SAV.

3. Complete command with all parameters.

Note: For cases requiring file data to be sent in, the debug will be easier if the number of records can be limited but still cause the issue.

**Send in Save files generated by above steps (this is not sent by QMGTOOLS).**

Data collection:

1. Issue CHGJOB (-jobnumber-/-jobuser-/-jobname-) LOG(4 00 *SECLVL) LOGCLPGM(*YES).

2. Run the CPYFRMIMPF/CPYTOIMPF to reproduce problem. Locate the fully qualified Job information. This information is used in step 8.

3. If incorrect output - explanation / screen captures / resulting output files needed.

4. ADDLIBLE QMGTOOLS

5. GO MG

6. 5 - Database menu

7. 10 - CPYTOIMPF/CPYFRMIMPF

8. Put in job information from step 2 ( Leave Job name of * if the current job re-created the problem)

9. Put in full Case number and specify FTP option.

NOTE: If *NO is used for FTP then you must manually send to IBM via:

MustGather: Instructions for Sending Data to IBM i Support

Method B - Manual Collection

PTF information:

1. Version, release, and modification level of system (for example IBM i 7.3, IBM i 7.4)

2. Issue WRKPTFGRP and F6 to get a QSYSPRT spool file

3. Issue DSPPTF OUTPUT(*PRINT)

4. Issue DSPOBJD OBJ(QSYS/QCPIMPRT) OBJTYPE(*PGM) DETAIL(*SERVICE) OUTPUT(*PRINT)

5. Issue DSPOBJD OBJ(QSYS/QCPEXPRT) OBJTYPE(*PGM) DETAIL(*SERVICE) OUTPUT(*PRINT)

6. Issue DSPOBJD OBJ(QSYS/QCPEXPRT2) OBJTYPE(*PGM) DETAIL(*SERVICE) OUTPUT(*PRINT)

7. Issue DSPOBJD OBJ(QSYS/QSQCLI) OBJTYPE(*SRVPGM) DETAIL(*SERVICE) OUTPUT(*PRINT)

8. Issue DSPOBJD OBJ(QSYS/QSQRUN1) OBJTYPE(*SRVPGM) DETAIL(*SERVICE) OUTPUT(*PRINT)

Data Area information:

Results of the following SQL statement:

(this will show what data areas are being used and with what values)

SELECT 

       DATA_AREA_LIBRARY, 

       DATA_AREA_NAME, 

       DATA_AREA_VALUE 

FROM QSYS2.DATA_AREA_INFO 

WHERE DATA_AREA_TYPE = '*CHAR'

  and DATA_AREA_LIBRARY = 'QSYS'

  and DATA_AREA_NAME in ('QCPFRMIMPF', 'QCPTOIMPF', 'QCPENFSCSD', 'QCPNONEEOF', 'QCPEFSINGL', 'QCPZEROLEN', 'QCPCPYTSMP', 'QCPZEROSTG', 'QCPNOBLANK', 'QCPUSEPATH', 'CPTOFLDDLM');

JOB Information / collection

1. Issue CHGJOB (-jobnumber-/-jobuser-/-jobname-) LOG(4 00 *SECLVL) LOGCLPGM(*YES).

2. Run the CPYFRMIMPF/CPYTOIMPF to reproduce problem.

3. Issue DSPJOBLOG JOB(-jobnumber-/-jobuser-/-jobname-) OUTPUT(*PRINT).

4. WRKJOB JOB(-jobnumber-/-jobuser-/-jobname-) OUTPUT(*PRINT).

5. *If incorrect output - Explanation / Screen Shots / Resulting output files needed *

Re-create Information, if possible:

1. From File saved to SAVF.

2. To File saved to SAVF.

3. Command to run, and any additional recreate instructions, files, programs and/or steps.

4. Issue DSPSYSVAL SYSVAL(QLANGID) OUTPUT(*PRINT)

Note: For cases requiring file data to be sent in, the debug will be easier if the number of records can be limited but still cause the issue.

File Information if re-creates not possible:

1. Issue DSPFD and DSPFFD of database fromfile / tofile (gives database file attributes).

2. WRKLNK Option 8 of stream fromfile / tofile (gives stream file attributes).

3. If DTAFMT(*FIXED) is used, DSPFFD of the FDF file used.

4. If the command is invoked inside a program, send the source of the program.

** All spool files and save file generated from above steps needs to be sent to IBM. **

 
Direction for transferring files to IBM if QMGTOOLS was NOT used

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CQ3AAM","label":"IBM i Db2->CPYTOIMPF \/ CPYFRMIMPF"},{"code":"a8m0z0000000CHbAAM","label":"IBM i Db2->MustGather Database"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Historical Number

560722126

Was this topic helpful?

Document Information

Modified date:
22 April 2022

UID

nas8N1012288

Tips