element file aa...aa cannot be used as bbbb(xx...xx) journal file. file group: cc...cc, system A/B: d, reason code=eeee

This element file cannot be used as a journal file. Reason codes indicate the reason.

aa...aa: Name of journal element file in which an error occurred. (Up to eight alphanumerics)

bbbb: Type of journal file (up to four alphanumerics)

sys: System journal file

jar: Archive journal file

xx...xx: Resource group name

cc...cc: Journal file group name in which an error occurred. (Up to eight alphanumerics)

d: System in which an error occurred.

a: System A

eeee: Reason code (Up to four numerals)

The table below shows the reason codes and countermeasures.

S: Separates the file and continues processing.

O: Take a proper action according to the reason code.

Reason code	Meaning	Operator's action	OpenTP1 administrator's action
223	Insufficient capacity to store the maximum record data defined.	Ask the OpenTP1 administrator what the estimated file capacity should be and check the current file capacity. If it is incorrect, re-create the file with correct capacity.	Check that the maximum record data length in the definition is correct. If it is incorrect, re-estimate the file capacity and change the definition. If the maximum record data length is correct, ask the operator to re-create the file with the estimated file capacity.
601	Failed in opening the physical file	Follow the message KFCA01200-E or KFCA01203-E that was output immediately before this message.	--
602	Failed in reading the physical file management information
603	Management information on the physical file has been destroyed.	Initialize the file.
604	The system information on the physical file differs from the current system. File for another system may be destroyed.	Ask the OpenTP1 administrator whether the file is available to the current system. If it is available, initialize the file.	Check that the file is for another system. If it is used by another system, change the definition not to use the file.
605	The file configuration on the physical file differs from the current file configuration. The file configuration may have been changed.	Ask the OpenTP1 administrator whether the file configuration has been changed. If it has not been changed, initialize the file.	Check the definition to see whether the journal group using the file or the element file has been changed. If the file configuration has been changed, resume the file configuration in definition.
606	Physical file is a current file.	This file possibly caused error during the previous use. Do one of the following: Unload the journal information. Change the file status. Initialize the file.	--

Legend:

--: Not applicable

Note

Initialize the file in the following procedure.

1. Delete the file using the jnlrm command.
2. Re-create the file using the jnlinit command.

Use the jnlchgfg command to change the file status.

Use the jnlunlfg command to unload the journal information.