Page 1 of 1

IDCAMS IMPORT

PostPosted: Mon Jun 13, 2011 4:28 pm
by Bad Man
Hi My colleague exported a file

/**************************************************/
/* VERIFY */
/**************************************************/
VERIFY DATASET(SYSU.$RGG.DB)
/**************************************************/
/* EXPORT */
/**************************************************/
EXPORT SYSU.$RGG.DB TEMP -
INFILE(KSDS) OUTFILE(TKSDS)
/**************************************************/
/* DEFINE - FORCE WITH REQVOL TO USE OUR VOLUME */

and then defined a new cluster and alter the name of the new file to current and then imported it

IMPORT INTOEMPTY -
INFILE(TKSDS) OUTFILE(KSDS)

and got these errors:

IMPORT INTOEMPTY -
INFILE(TKSDS) OUTFILE(KSDS)
IDC0604I DATA SET BEING IMPORTED WAS EXPORTED ON 06/12/11 AT 00:36:28
IGD17800I VOLUME VDR002 DEFINITION NOT FOUND
FOR DATA SET SYSU.$RGG.DB
IGD306I UNEXPECTED ERROR DURING IGDCNS01 PROCESSING
RETURN CODE 5002 REASON CODE 0
THE MODULE THAT DETECTED THE ERROR IS IGDVTSCH
SMS MODULE TRACE BACK - VTSCH VTSCF VTSCD VTSCC VTSCR SSIRT
SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00701
IGD17219I UNABLE TO CONTINUE DEFINE OF DATA SET
SYSU.$RGG.DB
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12

Now what I think we are doing wrong is we are importing it and we should use NOERASE and INTOEMPTY with this IMPORT. But the define has a comment saying use FORCE with REQVOL parameter now I saw the syntax and their is no such parameter like force or REQVOL in the IDCAMS define. Suggestions please.

Re: IDCAMS IMPORT

PostPosted: Mon Jun 13, 2011 8:56 pm
by steve-myers
You do not EXPORT or IMPORT a file, you EXPORT or IMPORT a VSAM dataset. You must use proper terminology. This is MVS, not Windoze, Unix or Linux.

EXPORT saves a number of dataset attributes with the exported data so it can restore the exported dataset with the exact same attributes. You can override some of these attributes with the IMPORT command. The command is pretty arcane. Study this link with care.

Re: IDCAMS IMPORT

PostPosted: Sun Jun 19, 2011 5:36 pm
by Bad Man
I looked at the older JCL and there I saw a parameter for defining VSAM file STORCLAS(REQVOL) which put the dataset on the correct volumes VDR*** and now I think when we test it next it should work....Also i made changes to ACS routines so that when STORCLAS REQVOL is choosen things land in the required pool..