HiRDB Dataextractor Version 8 Description, User's Guide and Operator's Guide

[Contents][Index][Back][Next]

8.2 Details of messages


JXU7000E

INSUFFICIENT MEMORY

Memory shortage occurred.
S: Terminates processing after disconnecting.
P: Re-execute when sufficient memory becomes available.

JXU7001E

LOGICAL ERROR OCCURRED CODE=Uaaa, bbb[, c...c]

Error occurred during internal processing.
aaa: Maintenance code
bbb: Detail code
c...c: Maintenance information
S: Terminates processing after disconnecting.
P: Contact the customer engineer.

JXU7002E

SYSTEM CALL ERROR, FUNC=a...a, ERRCODE=bbb
{NAME=c...c|SIZE=d...d|[e...e]}

System call shown as a...a resulted in an error.
a...a: System call resulting in the error
bbb: Error code
c...c: Filename or service name
d...d: Size of area to be allocated
e...e: Maintenance information
S: Terminates processing after disconnecting.
P: Check the reference manual for the indicated error code and function, eliminate the cause of the error, and then re-execute.
  • When FUNC=getservebyname
    Confirm that the service name in the services file matches the service name in HiRDB Dataextractor's environment variable information setup file (hirdbxt.ini).
  • When FUNC=connect and errno=239 or 10061 (target system is a Windows version)
    Confirm that the service has been started.
  • When FUNC=LoadLibraryEx, errno=1114, and NAME=%PDDIR%\bin\pdsingle.dll (target system is a Windows version)
    If the target HiRDB system was installed with a setup identifier, confirm that the following environment variables are specified in hirdbxt.ini:
    - PDDIR
    - PDCONFPATH
    - PDUXPLDIR
  • When FUNC=CodeCnvOpen and ERRCODE=-4
    If a mapping table for character code conversion that was created with version 07-03 or an earlier version was used, re-create the mapping table.

JXU7003E

ROW LENGTH EXCEEDS 4294967295

HiRDB Dataextractor cannot continue processing because the length of a row exceeded 4 GB.
S: Terminates processing.
P: Check the row lengths in the applicable table and re-execute. If the table contains BLOB or SGMLTEXT columns, make sure the XTLOBBUFSIZE environment variable is specified, and then re-execute.

JXU7005I

END OF a...a RETURN CODE IS bb

HiRDB Dataextractor terminated with return code bb.
a...a: Program name:
PXTCNTL: HiRDB Dataextractor on the data target system (TCP/IP)
PXTOSIL: HiRDB Dataextractor on the data target system (OSI)
xtrep: HiRDB Dataextractor on the data source system (extraction from HiRDB)
xtrepO: HiRDB Dataextractor on the data source system (extraction from ORACLE)
bb: Return code:
0: Normal termination
4: HiRDB's database load utility resulted in an error; overflow or truncation may have occurred.
8: Parameter error
12: Unresumable error occurred.
16: Processing terminated abnormally or internal conflict was detected.
S: Terminates processing.
P: Take one of the following actions:
  • Return code: 12
    Eliminate the cause of the error on the basis of the message output to the error log file or standard output, and re-execute.
  • Return code: 16
    Contact the customer engineer.

JXU7006E

a...a TERMINATED BY SIGNAL, NO=b...b

Program was terminated by a signal.
a...a: Program name:
PXTCNTL: HiRDB Dataextractor's entry program
PXTLOAD: Program started by PXTCNTL
PDLOAD: HiRDB database load utility
PXTMOCT: OSI daemon program
b...b: Number of signal causing program termination
S: Terminates processing.
P: Check other messages, if any, for the cause of the error, and then re-execute. If there are no other messages, contact the customer engineer.

JXU7007I

HiRDB Dataextractor SYSTEM STARTED
{PID=a...a|SYSLOG=b...b}

HiRDB Dataextractor has started.
a...a: HiRDB Dataextractor's process ID
b...b: HiRDB Dataextractor's error log file
S: Starts processing.

JXU7008I

HiRDB Dataextractor SYSTEM
TERMINATED PID=a...a

HiRDB Dataextractor has terminated.
a...a: HiRDB Dataextractor's process ID
S: Terminates processing.

JXU7009I

HiRDB Dataextractor LOAD PROCESS
a STARTED PARTNER JOB NAME=b...b

HiRDB Dataextractor has started data import processing.
a: One of the following:
M: Control processing
F: Input file creation processing
b...b: Name of the XDM/XT job that connected with this processing
S: Starts import processing.

JXU7010E

a...a ERROR OCCURRED, CODE=bb

Error occurred in another program.
a...a: Program name:
PXTCNTL: HiRDB Dataextractor on the data target system
SHELL SCRIPT: User-specified shell script
bb: Error code:
When a...a is PXTCNTL:
4: HiRDB database load utility resulted in an error.
12: Unresumable error occurred while accessing HiRDB Dataextractor, HiRDB, or user-specified shell command.
16: HiRDB Dataextractor terminated abnormally.
When a...a is SHELL SCRIPT:
bb indicates the exit status that is returned by the user-specified shell script.
S: Takes one of the following actions:
When a...a is PXTCNTL:
  • Error code: 4
    Resumes processing.
  • Error code: Other than 4
    Terminates processing.
When a...a is SHELL SCRIPT:
Terminates processing.
P: Take one of the following actions:
When a...a is PXTCNTL:
  • Error code: 4
    Check the execution results listing from the program shown as a...a for errors.
  • Error code: Other than 4
    Eliminate the cause of the error on the basis of the execution results listing from the program shown as a...a, and then re-execute the job.
When a...a is SHELL SCRIPT:
Check the execution results listing from the user-specified shell script for errors.

JXU7011I

a...a ROWS EXTRACT [SUCCESSFULLY]

a...a rows have been extracted.
a...a: Number of rows extracted
SUCCESSFULLY: Displayed with the final number of rows that were output
S: Resumes processing.

JXU7012I

{FILE|DIRECTORY} CREATED NAME=a...a
[COUNT=b...b]

File or directory creation processing has terminated.
a...a: Filename or directory name
b...b: Number of data items
S: Resumes processing.

JXU7013E

{FILE|DIRECTORY} EXIST NAME=a...a

Specified file or directory already exists.
a...a: Filename or directory name
S: Terminates processing.
P: Take one of the following actions, and then re-execute:
  • Change the name of the file or directory to be created.
  • Change the appropriate specification so that the existing file or directory can be overwritten.

JXU7014I

EXEC a...a IS b...b

a...a is being executed.
a...a: Event being executed:
pdload ARG: pdload is being executed.
SHELL SCRIPT: Shell script is being executed.
b...b: One of the following is displayed:
a...a: pdload ARG
pdload's execution options
a...a: SHELL SCRIPT
Absolute pathname of the shell script
S: Waits for termination of a...a.

JXU7017E

THIS FUNCTION IS NOT SUPPORT, KIND=a...a b...b

Facility to be executed is not supported by the version in use at the destination. The following this message, HiRDB Dataextractor outputs maintenance information in dump format.
Destination: XDM/XT or HiRDB Dataextractor
a...a: Maintenance information
b...b: Maintenance information (dump format)
S: Terminates processing.
P: Verify that the function being executed is supported by the combination of the versions used with the target system. If this is not applicable, contact the customer engineer.

JXU7018I

FILE CREATED COUNT=aa SUCCESSFULLY

File creation processing has been completed.
aa: Number of data items
S: Resumes processing.

JXU7019I

INVALID ADDRESS MODE,
HiRDB Dataextractor a...a b...b=c...c

HiRDB Dataextractor accessed a program with a different addressing mode.
a...a: HiRDB Dataextractor's addressing mode:
32bit: 32-bit mode
64bit: 64-bit mode
b...b: Target program:
  • HiRDB
c...c: Target program's addressing mode:
32bit: 32-bit mode
64bit: 64-bit mode
S: Terminates processing.
P: Use the target program's addressing mode, and re-execute.

JXU7020E

MODULE TRACE FILE CREATED NAME=a...a

Module trace file was output.
a...a: Name of the module trace file
S: Terminates processing.

JXU7021E

NOT EXEC a...a

HiRDB Dataextractor was unable to execute the indicated processing.
a...a: Processing whose execution was attempted:
MODULE TRACE: Module trace collection processing
S: Resumes processing.

JXU7022E

CORE FILE IN a...a

The core file storage directory is a...a.
a...a: Name of the core file storage directory
S: Resumes processing.

JXU7100E

COMMUNICATION ERROR OCCURRED
CODE=(aaa, bbbb)[PARTNER=d...d]
[HOSTNAME=e...e]

Error occurred with respect to communication with the target system.
aaa: Processing code:
2: setsockopt socket library
6: Receiving
7: Sending
bbbb: Error code:
TCP/IP used: Socket library's errno
OSI used: TLI function's t_errno
d...d: JOBID or process ID:
XDM/XT: JOBID
HiRDB Dataextractor: PXTCNTL's process ID
e...e: Remote system's host name
This information is displayed only when the remote system is a HiRDB Dataextractor.
PARTNER and HOSTNAME portions are displayed only when OSI is used.
S: Disconnects and terminates processing.
P: Eliminate the cause of the error and re-execute.
TCP/IP used:
  • Check the Hitachi CSMA/CD Network CD105 (TCP/IP) manual for the socket library's reason code corresponding to the processing code. In the case of a network error, eliminate the cause of the error and re-execute.
  • For other errors, contact the customer engineer.
OSI used:
  • Process ID displayed with PARTNER
    Take appropriate action according to the HiRDB Dataextractor error file located at the host indicated by HOSTNAME. This error file contains the process ID displayed at the beginning of this message.
  • Process ID not displayed with PARTNER
    Take appropriate action according to the HiRDB Dataextractor error file located at the host that contains the HiRDB3 system manager. This error file contains the process ID displayed at the beginning of this message.

JXU7101E

a...a CANNOT CONNECT
[PARTNER=d...d] [HOSTNAME=e...e]

Connection establishment with the remote system failed.
a...a: Load name:
PXTCNTL: Load name when TCP/IP is used
PXTOSIL: Load name when OSI is used
d...d: Job ID or process ID:
XDM/XT: Job ID
HiRDB Dataextractor: PXTCNTL's process ID
e...e: Remote system's host name
This information is displayed only when the remote system is HiRDB Dataextractor.
PARTNER and HOSTNAME portions are displayed only when OSI is used.
S: Disconnects and terminates processing.
P: Eliminate the cause of the error and re-execute.
TCP/IP used:
  • Check the specified port number for an error.
  • Re-evaluate the combination of HiRDB Dataextractor versions between local and remote systems.
  • Check; if necessary, revise the value of the XTPCHKTIME environment variable.
OSI used:
  • Process ID displayed with PARTNER
    Take appropriate action according to the HiRDB Dataextractor error file located at the host indicated by HOSTNAME. This error file contains the process ID displayed at the beginning of this message.
  • Process ID not displayed with PARTNER
    Take appropriate action according to the HiRDB Dataextractor error file located at the host that contains the HiRDB system manager. This error file contains the process ID displayed at the beginning of this message.
  • Check; if necessary, revise the value of the XTPCHKTIME environment variable.

JXU7102E

CONNECTION CLOSED{CODE= (aaa, bbbb)
|FUNC=c...c CODE=d...d}[PARTNER=e...e]
[HOSTNAME=f...f]

Connection with the remote system was interrupted because of an error.
aaa: Processing code (maintenance code):
6: Receiving
7: Sending
bbbb: Error code (maintenance code):
TCP/IP used: Socket library's errno
OSI used: TLI function's t_errno
c...c: Name of the TLI function resulting in the error
d...d: Error code (maintenance code):
TLI function's t_errno
e...e: Job ID or process ID:
XDM/XT: Job ID
HiRDB Dataextractor: PXTCNTL's process ID
f...f: Remote system's host name
This information is displayed only when the remote system is a HiRDB Dataextractor.
PARTNER and HOSTNAME portions are displayed only when OSI is used.
S: Terminates processing.
P: An error may have occurred on XDM/XT or HiRDB Dataextractor. Correct the error and re-execute.
  • Process ID displayed with PARTNER
    Take appropriate action according to the HiRDB Dataextractor error file located at the host indicated by HOSTNAME. This error file contains the process ID displayed at the beginning of this message.
  • Process ID not displayed with PARTNER
    Take appropriate action according to the HiRDB Dataextractor error file located at the host that contains the HiRDB system manager. This error file contains the process ID displayed at the beginning of this message.

JXU7103E

CANNOT CONNECT WITH a...a, (b...b)
[PARTNER=c...c]

Could not establish connection with the HiRDB Dataextractor located at the host where data is to be stored.
a...a: Name of the host at the data storage destination
b...b: IP address of the host at the data storage destination
xxx.xxx.xxx.xxx format (xxx: decimal number)
c...c: Job ID or process ID:
XDM/XT: Job ID
HiRDB Dataextractor: PXTCNTL's process ID
PARTNER portion is displayed only when OSI is used.
S: Terminates processing.
P: Eliminate the cause of the error and re-execute.
TCP/IP used:
Check the specified port number for an error.
If the FQDN was specified instead of the host name when HiRDB Dataextractor was executed, use b...b instead of a...a to identify the host that could not be connected.
OSI used:
  • Process ID displayed with PARTNER
    Take appropriate action according to the HiRDB Dataextractor error file located at the host indicated by HOSTNAME. This error file contains the process ID displayed at the beginning of this message.
  • Process ID not displayed with PARTNER
    Take appropriate action according to the HiRDB Dataextractor error file located at the host that contains the HiRDB system manager. This error file contains the process ID displayed at the beginning of this message.

JXU7104E

COMMUNICATION ERROR OCCURRED,
LOADNAME=a...a HOSTNAME=b...b
[PARTNER=c...c]

Error occurred during communication with another HiRDB Dataextractor.
a...a: Load name of the remote HiRDB Dataextractor
b...b: Name of the host at which a...a is located
c...c: Job ID or process ID:
XDM/XT: Job ID
HiRDB Dataextractor: PXTCNTL's process ID
PARTNER portion is displayed only when OSI is used.
S: Terminates processing.
P: Take appropriate action according to the message issued before this message and the message output by the remote load.
  • When using OSI, process ID displayed with PARTNER
    Take appropriate action according to the HiRDB Dataextractor error file located at the host indicated by HOSTNAME. This error file contains the process ID displayed at the beginning of this message.
  • When using OSI, process ID not displayed with PARTNER
    Take appropriate action according to the HiRDB Dataextractor error file located at the host that contains the HiRDB system manager. This error file contains the process ID displayed at the beginning of this message.

JXU7106I

OSI COMMUNICATION PROGRAM IS NOT ACTIVE

HiRDB Dataextractor will retry the requested operation because the program required for OSI communication is not active.
S: Resumes processing.
P: Start the program required for OSI communication (XNF).

JXU7200E

ERROR OCCURRED DURING
DATABASE ACCESS STATUS=aaag
OPERATION CODE=b...b [c...c]

An unresumable error occurred while accessing HiRDB or ORACLE. This message may be followed by a HiRDB or ORACLE message.
aaa: HiRDB SQLCODE or ORACLE error code
b...b: Operation code (internal information)
c...c: HiRDB or ORACLE message
S: Disconnects and terminates processing.
P:
HiRDB
Eliminate the cause of the error on the basis of the HiRDB SQLCODE or HiRDB message, and re-execute. For details about the HiRDB SQLCODE and HiRDB messages, see the HiRDB Messages manual.
ORACLE
Eliminate the cause of the error on the basis of the ORACLE error code or message, and re-execute. In the case of an SQL analysis error, check the values specified in the column name specification file, table expression specification file, and lock information file. For details about the ORACLE error codes and messages, see the ORACLE manual.

JXU7201E

ERROR OCCURRED DURING ENVIRONMENT
SET FUNCTION=a...a [CODE=bbb]

An unresumable error occurred while setting up the HiRDB Dataextractor operating environment.
a...a: Name of environment setup function (internal information), name of environment variable, or section name
If PDUSER is displayed, you must have specified a user ID and password in advance.
bbb: Environment setup function's return value (internal information)
S: Disconnects and terminates processing.
P: Check the HiRDB and HiRDB Dataextractor environment (variables) and re-execute. Also, check that HiRDB has started. If FUNCTION=SECTION NUMBER is displayed, HiRDB Dataextractor's environment variable information setup file (hirdbxt.ini) contains too many sections, in which case correct the file and re-execute.

JXU7203E

a...a IS NOT DEFINED IN ENVIRONMENT
FILE

Error detected in HiRDB Dataextractor's environment variable information setup file.
a...a: Name of the environment variable
S: Disconnects and terminates processing.
P: Check HiRDB Dataextractor's environment variable or HiRDB's environment variables, and re-execute.

JXU7204E

TIMEOUT OCCURRED DURING a...a

Timeout occurred during processing.
a...a: Processing type:
INPUT FILE I/O: Write to input file
RECEIVE DATA: Message receive from remote system
SEND DATA: Message send to remote system
S: Terminates processing.
P: Correct the error on the basis of the messages in the error log or HiRDB database load utility's error file, and re-execute.
INPUT FILE I/O displayed as the type of processing:
  • Storage table locked
    Re-execute after the processing that locks the storage table has terminated.
    If necessary, also revise the job schedule so that no more than one import process occurs on a table at the same time.
  • Storage table not locked
    Specify an input file write monitoring time (XTOPNWTIME environment variable) and re-execute. If it has already been specified, increase the value and re-execute.
RECEIVE DATA or SEND DATA displayed as the type of processing:
Check the communication line for problems. If there are no problems with the communication line, increase the communication function's response monitoring time (XTTCPWTIME or XTOSIWTIME environment variable), and re-execute.

JXU7205E

VALUE OF a...a PARAMETER IS INVALID

Parameter value is invalid.
a...a: Name of parameter
S: Terminates processing.
P: Eliminate the cause of the error and re-execute.

JXU7206E

SPECIFIED TABLE a...a.b...b IS NOT
DEFINED IN c...c DICTIONARY

Specified table a...a.b...b is not defined in the dictionary.
a...a: Authorization identifier on the source or target system
b...b: Table identifier on the source or target system
c...c: Type of database
S: Terminates processing.
P: Correct the table name or define the table, and re-execute.

JXU7207E

SPECIFIED LOAD COLUMN NUMBER IS
NOT EQUAL EXTRACT COLUMN NUMBER
IN TABLE a...a.b...b

Number of columns in the import table does not match the number of columns in the extraction table.
a...a: Authorization identifier on the target system
b...b: Table identifier on the target system
S: Terminates processing.
P: Correct the table name or HiRDB definitions, and re-execute.

JXU7208E

DATA CONVERT ERROR CODE=aa COUNT=bb

Data truncation or overflow occurred.
aa: Error code:
01: Data truncation
02: Overflow
bb: Number of errors
S: Terminates processing.
P: Correct the column length on the target system or increase the value of the XTLOBBUFSIZE environment variable, and then re-execute.

JXU7208I

DATA CONVERT ERROR CODE=aa

Data truncation or overflow occurred.
aa: Error code:
01: Character truncation
02: Overflow
S: Resumes processing.

JXU7209E

ERROR OCCURRED DURING DATA PUT
CODE=aa COUNT=b...b [SIZE=c...c]

Write error occurred in the extracted data.
aa: Error code:
01: Size of the output file is invalid
02: There is no more file to be output
b...b: Number of data items
c...c: Data length per line
S: Terminates processing.
P: Take one of the following actions:
Error code: 01
Increase the value of the XTFILESIZE environment variable and re-execute.
Error code: 02
Take one of the following actions and re-execute:
  • Increase the value of the XTFILESIZE environment variable.
  • Provide more space in the directory for storing output files.
  • Add a filename in the -o option.

JXU7210I

DIFFERENCE MAY BE INCLUDE IN a...a.
b...b.c...c

Data truncation, overflow, or rounding error may occur.
a...a: Authorization identifier on the source or target system
b...b: Table identifier on the source or target system
c...c: Name of column to be extracted or imported or the value set in SQLNAMEC in the Column Name Descriptor Area (SQLCNDA). (For details about the Column Name Descriptor Area, see the HiRDB SQL Reference manual.)
S: Resumes processing.

JXU7211E

DATA TYPE OF {a...a.b...b.c...c|ROW|#n...n}
CANNOT CONVERT

Data type cannot be converted due to an invalid data attribute.
a...a: Authorization identifier on the target system
b...b: Table identifier on the target system
c...c: Column name on the target system
n...n: Serial number of the extracted field
S: Terminates processing.
P: Correct the table name or HiRDB definitions, and re-execute.
If ROW is specified in the column name specification file and a storage column contains variable-length data, either remove the specification of ROW or re-define the target data as fixed-length data, and then re-execute.
If ROW is specified in the column name specification file and the import information file is specified, remove either the specification of ROW or the specification of the import information file, and then re-execute.

JXU7212E

DATA LENGTH OF {a...a.b...b.c...c|ROW}
CANNOT CONVERT

Data type cannot be converted due to invalid data length, precision, or scale.
a...a: Authorization identifier on the target system
b...b: Table identifier on the target system
c...c: Column name on the target system
ROW: When ROW is specified in the column name specification file, the total length of columns does not match between the source and target systems.
S: Terminates processing.
P: Correct the table name or HiRDB definitions, and re-execute.

JXU7213E

SPECIFIED RDAREA a...a IS INVALID BECAUSE
TABLE b...b.c...c IS NOT FOUND IN RDAREA

Specified RDAREA a...a does not contain a table.
a...a: Name of RDAREA on the target system
b...b: Authorization identifier on the target system
c...c: Table identifier on the target system
S: Terminates processing.
P: Correct the table name or RDAREA name or define it in HiRDB, and then re-execute.

JXU7214E

PARTITIONING OF SPECIFIED TABLE a...a.b...b IS
NOT SUPPORTED

Specified table partitioning method is not supported.
a...a: Authorization identifier on the target system
b...b: Table identifier on the target system
S: Terminates processing.
P: Correct the table name and re-execute.

JXU7215E

DATA TYPE OF a...a.b...b.c...c NOT
SUPPORT

Conversion of specified combination of attributes is not supported.
a...a: Authorization identifier on the source or target system
b...b: Table identifier on the source or target system
c...c: Column name on the source or target system
S: Terminates processing.
P: Correct the table name or HiRDB definitions, and re-execute.

JXU7216E

NULL DATA CANNOT BE SPECIFIED IN
a...a.b...b.c...c

The column specified in the null value information file has the NOT NULL constraint.
a...a: Authorization identifier on the source or target system
b...b: Storage table identifier on the source or target system
c...c: Column name on the source or target system
S: Terminates processing.
P: Correct the null value information file or HiRDB definitions, and re-execute.

JXU7217E

ARRAY NUMBER INVALID IN
a...a.b...b.c...c

Invalid combination of number of repetition column elements between source system and target system.
a...a: Authorization identifier on the target system
b...b: Table identifier on the target system
c...c: Column name on the target system
S: Terminates processing.
P: Check the number of elements defined in the columns on the source and target systems, correct any errors, and then re-execute.

JXU7218E

DATA VALUE OF a...a.b...b.c...c CANNOT CONVERT
ERROR CODE=dd COUNT=e...e

Data cannot be converted due to an invalid data type.
a...a: Authorization identifier on the source system
b...b: Table identifier on the source system
c...c: Column name on the source system
dd: Error code:
01: Value of DATE-type data is a B.C. year.
02: Value of numeric data resulted in overflow.
e...e: Number of erroneous lines
S: Terminates processing.
P: Use a convertible attribute on the target system or specify extraction conditions to avoid extracting invalid data, and then re-execute.

JXU7220E

a...a IS INVALID IN b...b LINE=c...c

Specification a...a in line c...c in file b...b is invalid.
a...a: Specified information
b...b: Filename
c...c: Line number
S: Terminates processing.
P: Correct the specification in the file and re-execute.

JXU7221E

FES OR BES IS NOT FOUND IN a...a

There is no front-end server or back-end server on the HiRDB unit at host a...a.
a...a: Name of host on the data target system
S: Terminates processing.
P: Change the client settings so that connection is established with a target host where a front-end server or back-end server is located, and then re-execute; or, check and make sure that the HiRDB environment variables specified in the environment variable information setup file are correct for the corresponding server unit, and then re-execute.

JXU7222E

{ENVIRONMENT FILE NAME IN /etc/
inetd.conf|INPUT DATA FILE NAME}
NOT SET UP

ENVIRONMENT FILE NAME IN /etc/inetd.conf displayed:
HiRDB Dataextractor's environment variable information setup filename is missing in the /etc/inetd.conf configuration file.
S: Terminates processing.
P: Check the value of the server program arguments field in the /etc/inetd.conf configuration file, and re-execute.
INPUT DATA FILE NAME displayed:
The input data file to be passed to pdload is not specified.
S: Terminates processing.
P: Take one of the following actions:
  • Data extraction or import between HiRDBs
    Specify the -o or -O option in the xtrep command and re-execute.
  • Linked to XDM/XT
    Specify the TRANSFER JXUMCTL control statement and re-execute.

JXU7223E

TABLE NAME a...a.b...b IS INVALID
ERROR CODE=c...c

Specified table name is invalid.
a...a: Authorization identifier on the target system
b...b: Table identifier on the target system
c...c: Error code:
004: Specified table has the view attribute.
005: Specified table has the FIX attribute.
If 2 is specified in the XTNLDFLT environment variable, data cannot be imported into a FIX table.
S: Terminates processing.
P: Take one of the following actions:
  • Correct the table name or HiRDB definitions, and re-execute.
  • If the error code is 005, change the value of the XTNLDFLT environment variable and then re-execute.

JXU7224E

a...a NOT FOUND

a...a was not found.
a...a: Absolute pathname
S: Disconnects and terminates processing.
P: Check if there is a file or directory with the absolute pathname shown as a...a, eliminate the cause of the error, and then re-execute.
When a...a is $PDDIR*/lib/libscomon.sl, $PDDIR*/client/lib/libzclt.sl, $PDDIR*/lib/libssol.so, or $PDDIR*/client/lib/libzclt.so:
  • Correct the directory path specified in PDDIR in HiRDB Dataextractor's environment variable information setup file, and then re-execute.
  • HiRDB may have not been installed correctly. Reinstall HiRDB and re-execute.
* $PDDIR is replaced with the actual directory path specified in PDDIR in HiRDB Dataextractor's environment variable information setup file.

JXU7230I

DATA CONVERT ERROR CODE=aa (b...b, c...c-d...d, e...e) [f...f]

An error occurred during character code conversion processing.
This message is output if the number of conversion error detections has not reached the cutoff number specified by the XTUNDEF environment variable.
aa: Error code
01: Data truncation occurred.
03: Column data ends with only a portion of a 2-byte or 3-byte code.
04: Some other code conversion error occurred.
b...b: Indicates one of the following:
- column-number[[subscript]]: Serial number from the beginning of the columns subject to extraction
- Maintenance information
c...c: Start location of the erroneous column (offset from the top of the row)
d...d: End location of the erroneous column (offset from the top of the row)
e...e: Offset of the erroneous data from the top of the row
f...f: Row data (dump format)
Displays the data before conversion.
If multiple messages are displayed for conversion of one row, this information is displayed after the last message. Note that no row data is output to the message log file.
S: Resumes processing.

JXU7230E

DATA CONVERT ERROR CODE=aa (b...b, c...c-d...d, e...e) [f...f]

An error occurred during character code conversion processing.
This message is output if the number of conversion error detections has reached the cutoff number specified by the XTUNDEF environment variable.
aa: Error code
01: Data truncation occurred.
03: Column data ends with only a portion of a 2-byte or 3-byte code.
04: Some other code conversion error occurred.
b...b: Indicates one of the following:
- column-number[[subscript]]: Serial number from the beginning of the columns subject to extraction
- Maintenance information
c...c: Start location of the erroneous column (offset from the top of the row)
d...d: End location of the erroneous column (offset from the top of the row)
e...e: Offset of the erroneous data from the top of the row
f...f: Row data (dump format)
Displays the data before conversion.
If multiple messages are displayed for conversion of one row, this information is displayed after the last message. Note that no row data is output to the message log file.
S: Terminates processing.
P:
When the error code is 01:
Correct the column length at the target system and then re-execute.
When the error code is 03 or 04:
Correct the extracted data and then re-execute.

JXU7300E

ERROR EXIST IN COMMAND LINE USAGE
: a...a

Specified command line is invalid.
a...a: Command line specification:
xtrep: HiRDB extraction command
xtrepO: ORACLE extraction command
S: Terminates processing.
P: Specify the correct command on the command line.

JXU7301E

LITERAL LENGTH OF PARAMETER IN
a...a OPTION EXCEEDS b...b

Length of value for option a...a exceeds b...b.
a...a: Option specification item:
EXTRACT TABLE: Name of extraction table
EXTRACT FILE NAME: Name of table expression specification file
FILE NAME: Name combining the value of the XTTMPDIR environment variable and the value of the -o, -O, or -q option
DIRECTORY NAME: Name combining the value of the XTTMPDIR environment variable and the value of the -b option
b...b: Maximum possible number of characters
S: Terminates processing.
P: Reduce the number of specified characters to no more than bb, and re-execute.
  • FILE NAME displayed as a...a
    Reduce the total length of the values specified in the XTTMPDIR environment variable and the -o, -O, or -q option to no more than bb, and then re-execute.
  • DIRECTORY NAME displayed as a...a
    Reduce the total length of the values specified in the XTTMPDIR environment variable and the -b option to no more than bb, and then re-execute.

JXU7302E

PARAMETER a...a IN b...b OPTION IS
INCORRECT

Value a...a specified in option b...b is invalid.
a...a: Specified value
b...b: Option specification item:
EXTRACT TABLE: Name of extraction table
S: Terminates processing.
P: Correct the specified value and re-execute.

JXU7303E

PARAMETER a...a IN b...b OPTION IS
OUT OF VALUE RANGE

Value a...a specified in option b...b is outside the valid range of values.
a...a: Specified value
b...b: Name of option
S: Terminates processing.
P: Correct the specified value and re-execute.

JXU7305E

a...a OPTION MISSING

Required option a...a is missing.
a...a: Name of option
S: Terminates processing.
P: Specify option a...a and re-execute.

JXU7306E

a...a OPTION CANNOT BE SPECIFIED
WITH b...b OPTION

a...a and b...b are mutually exclusive.
a...a: Name of option or environment variable
b...b: Name of option or environment variable
S: Terminates processing.
P: Specify either a...a or b...b and re-execute.

JXU7307E

a...a OPTION CANNOT BE SPECIFIED
WITHOUT b...b OPTION

Option a...a must accompany option b...b.
a...a: Name of an option or environment variable
b...b: Name of an option or environment variable
S: Terminates processing.
P: Either specify option b...b or omit option a...a, and then re-execute.

JXU7308E

DUPLICATE PARAMETER a...a IN b...b
OPTION

Value a...a is duplicated in option b...b.
a...a: Specified value
If b...b is the -o or -O option value, the message displays the name that combines the values of the XTTMPDIR environment variable and the -o or -O option.
b...b: Name of option
S: Terminates processing.
P: Correct value a...a so that it is not duplicated, and then re-execute.

JXU7309E

a...a [OPTION] CONFLICTS WITH b...b [OPTION]

A combination of options, or of specified values, or of an option and a specified value is invalid.
a...a: Option name or specified value
b...b: Option name or specified value
S: Terminates processing.
P: Check; if necessary, revise the option or specified value and then re-execute.

JXU7311E

INVALID OPTION SPECIFIED, OPTION NAME=a...a

An invalid command option was detected.
a...a: Command option
S: Terminates processing.
P: Eliminate the cause of the error and then re-execute.

JXU7312E

DEFINITION FORMAT ERROR, FILE= a...a, line=b...b

The definition format is invalid in the conversion definition file.
a...a: Name of the conversion definition file
b...b: Row number
S: Terminates processing.
P: Correct the definition on the indicated line in the conversion definition file and then re-execute.

JXU7313E

INVALID CHARACTER CODE, FILE=a...a, LINE=b...b, KIND=c...c, REASON=d...d

An invalid character was detected.
a...a: Name of the conversion definition file
b...b: Line number
c...c: Type
before: Source character code
after: Target character code
d...d: Reason
S: Terminates processing.
P: Use the indicated reason to correct the character code defined on the indicated row in the conversion definition file, and then re-execute.

JXU7314E

OPTION VALUE IS INVALID, OPTION NAME a...a

The value specified in a command option is invalid.
a...a: Command option
S: Terminates processing.
P: Eliminate the cause of the error and then re-execute.

JXU7315E

FILE ACCESS ERROR HAS OCCURRED, OPERATION=a...a, FILE=b...b, ERRNO=c...c

A file manipulation error occurred.
a...a: Type of manipulation
b...b: File name
c...c: Error number
S: Terminates processing.
P: See errno.h or the applicable OS manual for the interpretation of the error number, eliminate the cause of the error, and then re-execute.

JXU7316E

INVALID COMMAND ARGUMENT

A specified command argument is invalid.
S: Terminates processing.
P: Eliminate the cause of the error and then re-execute.