Page 1 of 1
IBM i Export / Import Save Files
Posted: Thu May 03, 2018 11:27 pm
by jyoung
When exporting to a save file, should you use a NEW save file every time?
We had an issue come up where I created a save file and exported an export list into the save file.
Before we deployed it (imported into production) I realized we missed something.
So I added the missing components to the export list and exported that list to the SAME save file. I checked the logs and it looked like all was ok, in the beginning of the log it said something like "file cleared".
When we ran the import, it failed with the message
Data area DC@EXTEXIM in QTEMP not found.
A bit further down we have
File DC@X02CC in library *LIBL not found or inline data file missing.
Then we get into
RNX1217 Information 99 05/02/18 19:00:07.305885 DC@P9007 DCXPGMLIB *STMT DC@P6207 DCXPGMLIB *STMT
From module . . . . . . . . : DC@P9007
From procedure . . . . . . : DC@P9007
Statement . . . . . . . . . : 229
To module . . . . . . . . . : DC@P6207
To procedure . . . . . . . : DC@P6207
Statement . . . . . . . . . : 5511
Message . . . . : Error message CPF4101 appeared during OPEN.
Cause . . . . . : RPG procedure DC@P6218 in program DCXPGMLIB/DC@P6218
received the message CPF4101 while performing an explicit OPEN operation on
file DC@X02CC. The actual file is DC@X02CC. Recovery . . . : Check the
job log for a complete description of message CPF4101, and contact the
person responsible for program maintenance.
DCM9998 Information 00 05/02/18 19:00:07.311960 DC@P9007 DCXPGMLIB *STMT DC@P6207 DCXPGMLIB *STMT
From module . . . . . . . . : DC@P9007
From procedure . . . . . . : DC@P9007
Statement . . . . . . . . . : 229
To module . . . . . . . . . : DC@P6207
To procedure . . . . . . . : DC@P6207
Statement . . . . . . . . . : 5511
Message . . . . : Program DC@P6218 encountered unexpected error - use HELP
for error details
Program =
DC@P6218.DCXPGMLIB, Error codes (refer chapter 14 in RPGIII manual)
were 00000 / 00000, Statement = 00000000, MI/ODT number = 0000, Routine =
*DETC, Number of parms = 008, Message number = , Message text = File
DC@X02CC in library *LIBL not found o
I have never had this happen before. I am going to create a NEW save file and see if that works.
Re: IBM i Export / Import Save Files
Posted: Fri May 04, 2018 12:44 am
by atostaine
They aren't related. I have the same save file that I use for all exports, never seen this.
Did you remove QTEMP from your library list?
Art
Re: IBM i Export / Import Save Files
Posted: Fri May 04, 2018 12:50 am
by jyoung
Not that I am aware of unless something happened with the user that does the import.
We actually schedule the import at night and use the REQUEST(IMPORT) command to execute it.
Code: Select all
DCXPGMLIB/LANSA REQUEST(IMPORT) PARM02('LIBRARY/SAVEFILE') PARM03(QSYSOPR) PARM04('AS/400') PARM06(N) PARM07(*ALL) PARM08(ENG) PARM09(YESYES) PARTITION(SYS)
Where PARM02 is the actual library and savefile.
Let me dig around and see if something happened to the user that this job uses.
Re: IBM i Export / Import Save Files
Posted: Fri May 04, 2018 11:42 pm
by jyoung
A few months back I had an issue with the Export / Import not working. It took a few hours on the phone with support to figure out what happened. Come to find out, we have a CL that has been around since '94 that gets run on our new servers that changes some of the default OS commands. One of the commands that gets changed is CRTPF. To fix the Export / Import issue then we had to restore the CRTPF command defaults.
It finally occurred to me that we just did an OS upgrade on the DEV server (7R1 to 7R3); did that CL get run again and change the commands back to their customized state?
Apparently it does, and the CRTPF command SHARE is *YES where it is normally *NO (if I recall correctly).
So to fix this issue we have to restore the CRTPF defaults.
Re: IBM i Export / Import Save Files
Posted: Sat May 05, 2018 12:41 am
by atostaine
It's usually considered best practice to make your own version of a command into another library, don't change QSYS. But you guys have been doing it that way a long time so that's not going to change.
There is also a thing called proxy commands that lets you create your own version of a command. CRTPRXCMD
Re: IBM i Export / Import Save Files
Posted: Sat May 05, 2018 1:04 am
by jyoung
I think they actually put them in another library but put that library on top of everything else in the library lists.
Its funny (not really I guess) because to me "not an IBM i guy" changing OS commands seems like a bad idea and should have a VERY GOOD reason for doing so. Whereas people that are "IBM guys" here think its LANSA's issue for relying on OS command defaults.
Neither one is going to change so its a royal PIA.
It does however now go into the new/update OS checklist.
Re: IBM i Export / Import Save Files
Posted: Tue May 08, 2018 3:16 am
by atostaine
You can change the job description that LANSA uses for the export/import so it doesn't have the custom library in it.
You are right the IBM i people will argue that forever. You should submit this, because if I was LANSA I would want to change my code so that default isn't assumed.
Re: IBM i Export / Import Save Files
Posted: Tue May 08, 2018 9:47 am
by MarkD
I agree with Joe.
Look at the changing the command parameter defaults from an ISVs perspective.
If you want to ship a CL program to your customers, say with a CPYF command in it, you would need to specify every single parameter to be absolutely sure it was going to do what you thought it would.
You'd also have to ship multiple versions of your CL program because the command parameters vary by IBM i OS version.
Re: IBM i Export / Import Save Files
Posted: Tue May 08, 2018 11:25 am
by KevinW
Hi Joe,
Was the save file you specified for the import one that contained an export? Messages about not finding datarea DC@EXTIM and file DC@X02CC would argue that the save file you tried to import from is either empty or was not used as the output of an export.
If this explanation is incorrect, I would recommend that you report this to local LANSA support.
Reusing a save file to re-export over should work.
Did using the new save file instead work?
Re: IBM i Export / Import Save Files
Posted: Wed May 09, 2018 12:27 am
by jyoung
Hey Kevin,
The save file was an export from our dev server. There seem to be no error messages in the export.
This is the EXPORT job log
Code: Select all
LANSA VERSION 14.1 = LANSA DEMONSTRATION SYSTEM = PAGE 1
PRINTED : 8/05/18 08:37:01 LANSA EXPORT RUN
PARTITION : SYS - Major System and Application Partition
LIST NAME : MEGS060
MSG MESSAGE
TYPE MSGID TEXT
C CPC3725 Save file MEGS060A in library DCXPGMLIB cleared.
C CPC0904 Data area DC@EXPINF created in library QTEMP.
C CPC7301 File DC@EXPINF created in library QTEMP.
C CPC7305 Member DC@EXPINF added to file DC@EXPINF in QTEMP.
C CPC7301 File DC@F51 created in library QTEMP.
C CPC7305 Member DC@F51 added to file DC@F51 in QTEMP.
C CPC7301 File DC@F51L created in library QTEMP.
C CPC7305 Member DC@F51L added to file DC@F51L in QTEMP.
C CPC7301 File DC@W02CE created in library QTEMP.
C CPC7305 Member DC@W02CE added to file DC@W02CE in QTEMP.
C CPC7301 File DC@X02CE created in library QTEMP.
C CPC7305 Member DC@X02CE added to file DC@X02CE in QTEMP.
C CPC7301 File DC@W06CE created in library QTEMP.
C CPC7305 Member DC@W06CE added to file DC@W06CE in QTEMP.
C CPC7301 File DC@W31CE created in library QTEMP.
C CPC7305 Member DC@W31CE added to file DC@W31CE in QTEMP.
C CPC7301 File DC@W32CE created in library QTEMP.
C CPC7305 Member DC@W32CE added to file DC@W32CE in QTEMP.
C CPF2105 Object DC@P6202 in QTEMP type *DTAQ not found.
C CPC9801 Object DC@P6202 type *DTAQ created in library QTEMP.
C CPC7301 File DC@F52 created in library QTEMP.
C CPC7305 Member DC@F52 added to file DC@F52 in QTEMP.
C CPC2955 1 records copied from member DC@F52V1.
C CPC2201 Object authority granted.
C CPC7301 File DC@F53 created in library QTEMP.
C CPC7305 Member DC@F53 added to file DC@F53 in QTEMP.
C CPC2201 Object authority granted.
C EIM0036 Exporting partition is multilingual
C EIM0037 Language ENG will be exported for all LANSA objects at user request
C EIM0037 Language FRA will be exported for all LANSA objects at user request
C EIM0037 Language JPN will be exported for all LANSA objects at user request
C EIM0002 Definition of field VLFCOMID successfully exported.
C EIM0002 Definition of field VLFCOMNME successfully exported.
C EIM0002 Definition of field VLFLOGAPP successfully exported.
C EIM0006 Object @CMGCBDS02 of type *SRVPGM from library DCXMODLIB successfully exported.
C CPI2101 Object @CMGCBDS02 in QTEMP type *SRVPGM created.
C CPC2130 1 objects duplicated.
C EIM0267 Definition of component CMGCBDS02 successfully exported.
C EIM0267 Definition of component LOGAPPE01 successfully exported.
C EIM0267 Definition of component VLFCOMC01 successfully exported.
C EIM0267 Definition of component VLFCOMC02 successfully exported.
C EIM0267 Definition of component VLFCOMD01 successfully exported.
C EIM0267 Definition of component VLFCOMF01 successfully exported.
C EIM0267 Definition of component VLFCOMI01 successfully exported.
C EIM0267 Definition of component VLFCOMM01 successfully exported.
C EIM0267 Definition of component VLFCOMP01 successfully exported.
C EIM0319 Definition of External Resource VLFDATA successfully exported.
C EIM0319 Definition of External Resource VLFDEFINI successfully exported.
C EIM0006 Object @VLFLOGS01 of type *SRVPGM from library DCXMODLIB successfully exported.
C CPI2101 Object @VLFLOGS01 in QTEMP type *SRVPGM created.
LANSA VERSION 14.1 = LANSA DEMONSTRATION SYSTEM = PAGE 2
PRINTED : 8/05/18 08:37:01 LANSA EXPORT RUN
PARTITION : SYS - Major System and Application Partition
LIST NAME : MEGS060
MSG MESSAGE
TYPE MSGID TEXT
C CPC2130 1 objects duplicated.
C EIM0267 Definition of component VLFLOGS01 successfully exported.
C EIM0267 Definition of component VLFPERU01 successfully exported.
C EIM0267 Definition of component VLFPIEG01 successfully exported.
C EIM0267 Definition of component VLFPIEP01 successfully exported.
C EIM0006 Object VLFCOM of type *FILE from library DCXMODLIB successfully exported.
C CPI2101 Object VLFCOM in LTMP651977 type *FILE created.
C CPC2130 1 objects duplicated.
C EIM0006 Object VLFCOM of type *SRVPGM from library DCXMODLIB successfully exported.
C CPI2101 Object VLFCOM in QTEMP type *SRVPGM created.
C CPC2130 1 objects duplicated.
C EIM0010 Definition of file VLFCOM in library DCXMODLIB successfully exported.
C CPC3722 1 objects saved from library LTMP651977.
C CPC2194 Library LTMP651977 deleted.
C CPC3722 19 objects saved from library QTEMP.
*** EIM9999 0 FATAL MESSAGES ISSUED DURING THIS EXPORT RUN
*** EIM9999 0 WARNING MESSAGES ISSUED DURING THIS EXPORT RUN
*** EIM9999 65 COMPLETION MESSAGES ISSUED DURING THIS EXPORT RUN
I am in contact with support, will update when I have a resolution.
Thanks,
Joe