Skip to Content
Jun 11, 2006 at 10:45 AM

LODRUN command is failing to extract files


I am preparing to upgrade our BW 3.5 (NW04) to NW2004S and have downloaded all relavent SR1 CD's from the marketplace.

The Upgrade master is 51031683 and I understand that this has to burned to a CD as it cannot be run from the IFS, but using the command below does not work.


The file is failing because it cannot find the files to extract. See errors below.

Message . . . . : File not selected. File label or file name mismatch for file /UMU_OS400_PPC64/UPGRADE/QTEMP.

Cause . . . . . : The file on volume was not restored because of a mismatch of file names. One of the following


-- If a label name was specified for the LABEL parameter, the file label on the volume does not match the file label on the command.

-- If the LABEL(*SAVLIB) parameter was used on the command, the file label does not match the library name for the SAVLIB parameter specified on the command, or the diskette file name qualifier is not valid.

-- If the LABEL parameter was not specified, the volume mounted does not contain the data to be restored.

-- If an optical file name was specified for the OPTFILE parameter, the file name on the volume does not match the file name on the command.

Recovery . . . : Replace the mounted volume with one that contains the file that is needed or change the specified label name for the LABEL parameter or optical file name for the OPTFILE parameter and try the request again.

<b>From WRKLNK '/QOPT' the file has the path


Looking at the CD in windows the file has the full path name but when it is put in the i-series it chops off anything over 8 characters.

I then changed the LODRUN command to the follwoing


but get the following mesage

Message . . . . : Object not found. Object



Cause . . . . . :

Object /QOPT/D51031683/UMU_OS400_PPC64/UPGRADE/LODINST, or a directory in the object path, could not be found, or its type cannot be resolved by this function.

Recovery . . . : Correct the name or specify an object of the correct type.

To determine if the object exists, use the Work with Object Links


command. If the name exists, check the type of the object. If the name contains symbolic link objects, ensure the path names they resolve to exist.

Retry the operation.

Any assistance on how to overcome this issue would be gratefully appreciated, we had planned to start the

upgrade today but cannot proceed until we get past this.

Many thanks,