ETERNUS SF XL-DATA/MV V13 User's Guide

6.2 Messages Output by the Daemon or Service

The following are the messages output by the daemon and service of the UNIX/IA server.

---

 

KJU1000 mftfd completed successfully for device: #device

[Return Code]
0
[Definition]
mftfd completed successfully.
Or the register/delete event log procedure of XdmInsLog completed successfully.
[Parameter Definition]


#device

:

Device name

---

 

KJU1001 mftfd #vl started : #device

[Return Code]
0x01
[Definition]
mftfd started.
[Parameter Definition]


#vl	:	Version level
#device	:	Device name

---

 

KJU1002 invalid input command
             usage : mftfd [-t] [-m] -start device
                       mftfd -{ stop | kill } device
                       mftfd -{ h | v | stopall | killall }

[Return Code]
0x02
[Definition]
The input command is invalid.
[Solution]
Enter it correctly.

---

 

KJU1003 mftfd version #vl

[Return Code]
0x03
[Definition]
The version of mftfd is vl.
[Parameter Definition]


#vl

:

Version level

---

 

KJU1005 invalid path

[Return Code]
0x05
[Definition]
The specified path name of the device is invalid. The following are possible causes:

• The full path was not specified for the device.
• The path name is too long.

[Solution]
Specify the full path.
Specify the path name so that it does not exceed the maximum length (for Solaris/Linux: 1023 bytes; for HP-UX: 1022 bytes)

---

 

KJU1006 device check error : #device - #sysmsg

[Return Code]
0x06
[Definition]
Since an error occurred during the operation for checking whether or not the device is a raw device, the device was not checked.
[Parameter Definition]


#device	:	Device name
#sysmsg	:	System message

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1007 no such device or not raw device

[Return Code]
0x07
[Definition]
The device does not exist or it is not a raw device.
[Solution]
Specify the correct device.

---

 

KJU1008 not super user

[Return Code]
0x08
[Definition]
The user is not a super-user.
[Solution]
Only super-users can execute this command.

---

 

KJU1009 lock failed - #sysmsg

[Return Code]
0x09
[Definition]
Could not obtain the lock.
[Parameter Definition]


#sysmsg

:

System message

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1010 initialization needed : #device

[Return Code]
0x0a
[Definition]
The specified volume cannot be used for the data transfer.
The following things can be considered as a cause.

• The specified device has not been initialized properly as a data transfer volumes.
• The following information is not corresponding (For the operation of the XL-DATA/MV on the cluster system).
  • Set value of Environment Item (SERVERNAME) specified for the Data Transfer Environment Settings File.
  • Initialization configuration of the data transfer volume.

[Parameter Definition]

#device

:

Device name

[Solution]
Perform one of the following checks and try again.

• Check to see if the correct device is specified from both systems (the server system and the client system).
• Check the target data transfer volume by Initialization Contents Display Function (mftfdvlst command or Disk Utility).
• Check a set value of Environment Item (SERVERNAME) specified for the Data Transfer Environment Settings File (For the operation of the XL-DATA/MV on the cluster system).

---

 

KJU1011 no active daemon

[Return Code]
0x0b
[Definition]
mftfd is not running for the specified device.

---

 

KJU1012 already started : #device

[Return Code]
0x0c
[Definition]
mftfd is already running for the specified device.
[Parameter Definition]


#device

:

Device name

---

 

KJU1100 abnormally ended : #device #no.

[Return Code]
0x0d
[Definition]
mftfd ended abnormally or was forcibly terminated by the -kill option (or the service was stopped, for Windows) during the data transfer.
[Parameter Definition]


#device	:	Device name
#no.	:	The partition number used (the first partition is 0)

[Solution]
If processing ended abnormally, messages other than this one are output to indicate the cause of the error. Refer to those messages for the solution.

---

 

KJU1101 data transfer timeout :{#device #no. | #filename #device #no.}

[Return Code]
0x0e
[Definition]
Timeout occurred due to lack of response from the client system.
The following things can be considered as a cause of the client system.

• The data transfer process(transfer command) was canceled.
• The system stopped.
• The volume (volume in which the source file or target file of data transfer exists) is a high loading state.
• CPU is a high loading state.

[Parameter Definition]

#device	:	Device name
#no.	:	The partition number used (the first partition is 0)
#filename	:	The name of the (input source or output target) file on the server

[Solution]
Please contact the system administrator and perform one of the following processes.

• Please rerun The data transfer process(transfer command).
• Please start the client system.
• When the load of volume is high, please reduce the load (multiprocessing level) of the volume.
• Please lower the load of CPU.

---

 

KJU1102 data transfer stopped unexpectedly : #device #no.

[Return Code]
0x0f
[Definition]
The data transfer prematurely terminated for some reason.
[Parameter Definition]


#device	:	Device name
#no.	:	The partition number used (the first partition is 0)

[Solution]
mftfd may have been forcibly terminated (e.g., by the kill command).
Contact the system administrator.

---

 

KJU1200 device open error : #device - #sysmsg

[Return Code]
0x10
[Definition]
Failed to open the intermediate file (shared disk).
[Parameter Definition]


#device	:	Device name
#sysmsg	:	System message

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1201 device seek error : #device [ - #sysmsg ] [ #no. ]

[Return Code]
0x11
[Definition]
The seek operation for the intermediate file (data transfer volume) failed.
[Parameter Definition]


#device	:	Device name
#sysmsg	:	System message
#no.	:	The partition number used (the first partition is 0)

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1202 device read error : #device [ - #sysmsg ] [ #no. ]

[Return Code]
0x12
[Definition]
The read operation for the intermediate file (data transfer volume) failed.
[Parameter Definition]


#device	:	Device name
#sysmsg	:	System message
#no.	:	The partition number used (the first partition is 0)

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1203 device write error : #device [ - #sysmsg ] [ #no. ]

[Return Code]
0x13
[Definition]
The write operation for the intermediate file (data transfer volume) failed.
[Parameter Definition]


#device	:	Device name
#sysmsg	:	System message
#no.	:	The partition number used (the first partition is 0)

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1300 file open error : { #filename [ - #sysmsg ] [ #device ] [ #no. ] | #filename [ #device ] [ - #sysmsg ] [ #no. ] }

[Return Code]
0x14
[Definition]
The open operation of the input source, output target, or .mftf file (mftf.ini for Windows) failed.
The following are possible reasons for the open failure:

• The specified path name is not the full path.
• The specified path does not exist.
• Access to the file is not authorized.

[Parameter Definition]

#filename	:	File name (input source or output target) on the UNIX/IA server
#sysmsg	:	System message
#device	:	Device name
#no.	:	The partition number used (the first partition is 0)

[Solution]
Check the specified file path or the .mftf file of the home directory of the specified account (or the mftf.ini file of the folder where the XL-DATA/MV is installed for Windows).

---

 

KJU1301 file read error : #filename [ - #sysmsg ] [ #device ] [ #no. ]

[Return Code]
0x15
[Definition]
The read operation of the input source file or .mftf file (mftf.ini for Windows) failed.
[Parameter Definition]


#filename	:	File name of the UNIX/IA server input source or .mftf file (mftf.ini file for Windows)
#sysmsg	:	System message
#device	:	Device name
#no.	:	The partition number used (the first partition is 0)

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1302 file write error : { #device [ - #sysmsg ] [ #no. ] | #filename [ - #sysmsg ] #device }

[Return Code]
0x16
[Definition]
The write operation of the output target file failed.
[Parameter Definition]


#device	:	Device name
#sysmsg	:	System message
#no.	:	The partition number used (the first partition is 0)
#filename	:	Temporary file

[Solution]
Proceed according to the contents of #sysmsg.
Insufficient space in the disk may be the cause; therefore, check the capacity.

---

 

KJU1400 insufficient memory - #sysmsg

[Return Code]
0x17
[Definition]
Insufficient memory.
[Solution]
Contact the system administrator, then try again after the problem is resolved.
[Parameter Definition]


#sysmsg

:

System message

---

 

KJU1401 cannot create child process : #device - #sysmsg

[Return Code]
0x18
[Definition]
The child process for the data transfer failed to create.
[Parameter Definition]


#device	:	Device name
#sysmsg	:	System message

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1402 cannot start daemon : #device - #sysmsg

[Return Code]
0x19
[Definition]
The daemon failed to start.
[Parameter Definition]


#device	:	Device name
#sysmsg	:	System message

Proceed according to the contents of #sysmsg.

---

 

KJU1403 cannot change to directory : #dirname - #sysmsg

[Return Code]
0x1a
[Definition]
Failed to change the current directory.
For Solaris: /var/opt/FJSVmftf
For HP-UX     : /var/opt/FHPmftf
For Linux     : /var/opt/FJSVmftf
[Parameter Definition]


#dirname	:	Directory name
#sysmsg	:	System message

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1404 cannot find directory : #dirname

[Return Code]
0x1b
[Definition]
Could not find the directory.
For Solaris: /var/opt/FJSVmftf
For HP-UX     : /var/opt/FHPmftf
For Linux     : /var/opt/FJSVmftf
[Parameter Definition]


#dirname

:

Directory name

[Solution]
Check the path name and re-enter it.

---

 

KJU1405 cannot open directory : #dirname - #sysmsg

[Return Code]
0x1c
[Definition]
Failed to open the directory.
[Parameter Definition]


#dirname	:	Directory name
#sysmsg	:	System message

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1500 access denied : #account #device [ #no. ]

[Return Code]
0x1d
[Definition]
The specified user account of the UNIX/IA server does not exist. For Windows systems, an account other than WINDOWS has been specified.
Or the specified user account of the UNIX/IA server is not authorized to execute the data transfer.
[Parameter Definition]


#account	:	The account name or the user identification If the server user name is invalid, server (server user name) If the client user name is invalid, client (client user name) is the output format. If the user ID cannot be determined, "unknown user" is output.
#device	:	Device name
#no.	:	The partition number used (the first partition is 0)

[Solution]
Specify an existing account and try again. For Windows systems, specify WINDOWS as the account.
If the account exists, register the user in the UNIX/IA server to permit data transfers.

---

 

KJU1501 invalid umask setting: #account #device [ #no. ]

[Return Code]
0x1e
[Definition]
The setting of umask is invalid.
[Parameter Definition]


#account	:	Account name
#device	:	Device name
#no.	:	The partition number used (the first partition is 0)

[Solution]
Specify a three-or-less-digit octal number.

---

 

KJU1600 cannot create pipe : #device [ - #sysmsg ] [ #no. ]

[Return Code]
0x1f
[Definition]
Could not create a pipe.
[Parameter Definition]


#device	:	Device name
#sysmsg	:	System message
#no.	:	The partition number used (the first partition is 0)

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1601 cannot dup open file : #device [ - #sysmsg ] [ #no. ]

[Return Code]
0x20
[Definition]
The dup failed.
[Parameter Definition]


#device	:	Device name
#sysmsg	:	System message
#no.	:	The partition number used (the first partition is 0)

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1602 cannot close file : #device [ - #sysmsg ] [ #no. ]

[Return Code]
0x21
[Definition]
Failed to close the file.
[Parameter Definition]


#device	:	Device name
#sysmsg	:	System message
#no.	:	The partition number used (the first partition is 0)

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1603 cannot execute filter command : #device [ - #sysmsg ] [ #no. ]

[Return Code]
0x22
[Definition]
The filter command could not be executed.
[Parameter Definition]


#device	:	Device name
#sysmsg	:	System message
#no.	:	The partition number used (the first partition is 0)

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1604 filter command stopped unexpectedly : #device [ #no. ]

[Return Code]
0x23
[Definition]
Due to an unexpected error, the filter command terminated prematurely.
[Parameter Definition]


#device	:	Device name
#no.	:	The partition number used (the first partition is 0)

[Solution]
The filter command process may have been forcibly terminated (e.g., by the kill command). Check the system status and try again.

---

 

KJU1605 filter command error : #device [ #no. ] [ - #errmsg ]

[Return Code]
0x24
[Definition]
The filter command ended with a completion code other than 0 or during a data transfer.
[Parameter Definition]


#device	:	Device name
#no.	:	The partition number used (the first partition is 0)
#errmsg	:	The system message that the filter command output to the standard error output.

[Solution]
Refer to the instructions of the filter command for a solution based on the #errmsg.

---

 

KJU1606 filter command timeout : #device [ #no. ]

[Return Code]
0x25
[Definition]
Timeout of the filter command occurred.
[Parameter Definition]


#device	:	Device name
#no.	:	The partition number used (the first partition is 0)

[Solution]
Specify a filter command for the environment variable(MFTF_COMMAND) as follows:

• Specify standard input or a file for input.
• Specify standard output or a file for output.
As for defails of filter command, refer to "Calling the Filter Command".
In addition, refer to the instructions regarding the filter command for a solution.

---

 

KJU1607 fork operation failed for filter command : #device [ - #sysmsg ] [ #no. ]

[Return Code]
0x26
[Definition]
The fork operation for starting the filter command failed.
[Parameter Definition]


#device	:	Device name
#sysmsg	:	System message
#no.	:	The partition number used (the first partition is 0)

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1700 cannot get filter command return code : #disknumber [ - #sysmsg ] #no.

[Return Code]
0x27
[Definition]
Failed to obtain the return code of the filter command.
[Parameter Definition]


#disknumber	:	Disk number
#sysmsg	:	System message
#no.	:	The partition number used (the first partition is 0)

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1701 child process aborted : #disknumber #no.

[Return Code]
0x28
[Definition]
Due to an unexpected error in the child process, the process was aborted.
[Parameter Definition]


#disknumber	:	Disk number
#no.	:	The partition number used (the first partition is 0)

[Solution]
The error information is output to the event data.
Contact a Fujitsu system engineer (SE) after collecting the information for investigation.

---

 

KJU1800 data transfer from logical unit to file : [ #filename ] completed successfully

[Return Code]
If the filter command is in use ....... 0x2A
If the filter command is not in use ... 0x00
[Definition]
The data transfer from the data transfer volume to the UNIX/IA server completed successfully.
[Parameter Definition]


#filename

:

The file name during the data transfer

---

 

KJU1801 data transfer from logical unit to file : [ #filename ] completed with a warning

[Return Code]
0x2A
[Definition]
The data transfer from the data transfer volume to the UNIX/IA server completed with a warning.
[Parameter Definition]


#filename

:

The file name during the data transfer

---

 

KJU1802 data transfer from file : [ #filename ] to logical unit completed successfully

[Return Code]
If the filter command is in use ....... 0x2A
If the filter command is not in use ... 0x00
[Definition]
The data transfer to the data transfer volume from the UNIX/IA server completed successfully.
[Parameter Definition]


#filename

:

The file name during the data transfer

---

 

KJU1803 data transfer from file : [ #filename ] to logical unit completed with a warning

[Return Code]
0x2A
[Definition]
The data transfer to the data transfer volume from the UNIX/IA server completed with a warning.
[Parameter Definition]


#filename

:

The file name during the data transfer

---

 

KJU1810 syntax error : [ #filename ] [: FILTER=#filtrtcode ]

[Return Code]
0x2B
[Definition]
The #filename file has a syntax error.
[Parameter Definition]

#filename	:	File name
#filtrtcode	:	Return code of the filter command

[Solution]
Check the syntax of the following files and correct them.

• Start Mode Specification File "startup.ini" (for Windows)
• Filter Command Return Code Conversion File ".filter_mftf" ("filter.ini" for Windows)
• User Registration File ".mftf" ("mftf.ini" for Windows)

---

 

KJU1811 function failed : #sysfunc [ - #sysmsg ]

[Return Code]
0x2C
[Definition]
Failed to call the function.
[Parameter Definition]


#sysfunc	:	Function name
#sysmsg	:	System message

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU1900 internal error(FUNC=#demdname,DETCODE=#detcode) : #device [ - #sysmsg ] #no.

[Return Code]
0x30
[Definition]
An internal error occurred during the data transfer.
[Parameter Definition]


#demdname	:	Request name
#detcode	:	Detail code (decimal)
#device	:	Device name
#sysmsg	:	System message * This may not be displayed, depending on the error contact.
#no.	:	Partition number

[Solution]
Refer to "Return Information of the XL-DATA/MV on the UNIX/IA Server" regarding the detail code.

---

 

KJU1901 device error(FUNC=#demdname DETCODE=#detcode) : #device [ - #sysmsg ] #no.

[Return Code]
0x31
[Definition]
An I/O error occurred in the data transfer volume.
[Parameter Definition]


#demdname	:	Request name
#detcode	:	Detail code (decimal)
#device	:	Device name
#sysmsg	:	System message * This may not be displayed, depending on the error contact.
#no.	:	Partition number

[Solution]
Refer to "Return Information of the XL-DATA/MV on the UNIX/IA Server" regarding the detail code.

---

 

KJU1902 parameter error in the communication area:#itemname

[Return Code]
0x32
[Definition]
A parameter error in the communication area.
[Parameter Definition]


#itemname

:

Item name

[Solution]
Contact a Fujitsu system engineer (SE) after collecting the information for investigation.

---

 

KJU1903 cannot execute filter command because it does not exist or access is denied [ : #command ]

[Return Code]
0x33
[Definition]
The filter command could not be executed.
The following are possible causes:

• The filter command does not exist.
• No execution authority.
• An invalid path was specified.
• The filter command string (including the options) is too long.

[Parameter Definition]

#command

:

Filter command

[Solution]
Make sure that the filter command exists, the user has the permission and others according to the causes if necessary.

---

 

KJU1904 transfer source file does not exist [ : #filename ]

[Return Code]
0x34
[Definition]
The transfer source file does not exist.
[Parameter Definition]


#filename

:

File name

[Solution]
Check the name of the transfer source file.

---

 

KJU1905 specified separator is invalid

[Return Code]
0x35
[Definition]
The specified separator is invalid.
[Solution]
Check the separator specification.

---

 

KJU1906 cannot create directory : DIR=#directory [ - #sysmsg ]

[Return Code]
0x36
[Definition]
Failed to create the directory.
[Parameter Definition]


#directory	:	Directory name
#sysmsg	:	System message

[Solution]
Proceed according to the contents of #sysmsg.

---

 

KJU1907 data transfer stopped due to client system error: #device #no.

[Return Code]
0x37
[Definition]
Due to an error detected in the client system, the transfer was aborted.
[Parameter Definition]


#device	:	Device name
#no.	:	Partition number

[Solution]
Check the message output to the client system.

---

 

KJU2000 installed XL-LINK/Datamover Service

[Definition]
The XL-DATA/MV has been registered as a service.

---

 

KJU2001 removed XL-LINK/Datamover Service

[Definition]
The XL-DATA/MV service has been removed.

---

 

KJU2002 XL-LINK/Datamover Service VxxLxx
             All Rights Reserved ,Copyright (c) Fujitsu Limited #yyyy [ -#yyyy ].
             Usage : mftfd.exe <-i> | <-r>
                   i - To install the service
                   r - To remove the service

[Definition]
An invalid option was specified.
[Parameter Definition]


#yyyy [ -#yyyy ]

:

Year

[Solution]
Enter the option correctly.

---

 

KJU2003 Unable to install XL-LINK/Datamover Service : #sysmsg

[Definition]
Failed to install the service.
[Parameter Definition]


#sysmsg

:

System message

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU2004 OpenSCManager failed : #sysmsg

[Definition]
Failed to open the SCM.
[Parameter Definition]


#sysmsg

:

System message

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU2005 CreateService failed : #sysmsg

[Definition]
Failed to create the service.
[Parameter Definition]


#sysmsg

:

System message

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU2006 OpenService failed : #sysmsg

[Definition]
Failed to open the service.
[Parameter Definition]


#sysmsg

:

System message

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU2007 DeleteService failed : #sysmsg

[Definition]
Failed to delete the service.
[Parameter Definition]


#sysmsg

:

System message

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU2008 Service failed - sysfunc : #sysmsg

[Definition]
Service processing failure.
[Parameter Definition]


#sysmsg

:

System message

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU2100 Detected internal contradiction
#sysmsg
error point : #errpoint

[Definition]
The Disk Utility encountered an unexpected error.
[Parameter Definition]


#sysmsg	:	System message
#errpoint	:	The code representing the location of the error

[Solution]
Contact a Fujitsu system engineer (SE) after collecting the information for investigation.

---

 

KJU2101 Application initialization error occurred
#sysmsg
error point : #errpoint

[Definition]
The initialization of the Disk Utility failed.
[Parameter Definition]


#sysmsg	:	System message
#errpoint	:	The code representing the location of the error

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU2102 Registry access error occurred
#sysmsg
error point : #errpoint

[Definition]
The Disk Utility failed to access the registry data.
[Parameter Definition]


#sysmsg	:	System message
#errpoint	:	The code representing the location of the error

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU2103 Device access error occurred
#sysmsg
error point : #errpoint

[Definition]
A disk access error occurred in the Disk Utility.
[Parameter Definition]


#sysmsg	:	System message
#errpoint	:	The code representing the location of the error

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU2104 Disk tree control error occurred
#sysmsg
error point : #errpoint

[Definition]
The Disk Utility failed to control the disk tree.
[Parameter Definition]


#sysmsg	:	System message
#errpoint	:	The code representing the location of the error

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU2105 Initialization information list control error occurred
#sysmsg
error point : #errpoint

[Definition]
The Disk Utility failed to control the initialization information list.
[Parameter Definition]


#sysmsg	:	System message
#errpoint	:	The code representing the location of the error

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU2106 Can't allocate memory
#sysmsg
error point : #errpoint

[Definition]
Insufficient memory for the Disk Utility.
[Parameter Definition]


#sysmsg	:	System message
#errpoint	:	The code representing the location of the error

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU2111 Disk access error occurred : Disk No. #disknumber
#sysmsg
error point : #errpoint

[Definition]
An access error occurred in the Disk Utility.
[Parameter Definition]


#disknumber	:	Disk number
#sysmsg	:	System message
#errpoint	:	The code representing the location of the error

[Solution]
Resolve the problem based on the content of #sysmsg, then try again.

---

 

KJU2300 installation failed - sysfunc : #sysmsg [ #filename ]

[Definition]
Failed to install this software.
[Parameter Definition]


#sysmsg	:	System message
#filename	:	Name of the file corresponding to the error message

[Solution]
Resolve the problem based on the content of #sysmsg, then try installing it again.