Filter
Top Products
the original files on the AS/400. If the LRECL of the files is increased during the
edit process, they will be truncated when they are returned to the AS/400.
Note: If an ADSM recovery file exists with an LRECL that is different than what is
being used on the LRECLRECOVERYFILE option, the existing file must be
deleted and re-created with the appropriate BACKUP command. For
example, the device configuration file is re-created with the BACKUP
DEVCONFIG command.
ANR8556W (AS/400)
LRECLRECOVERYFILE statement in file filespec results in ADSM recovery
files that cannot be edited on the AS/400.
Explanation: While processing the specified server options file, the server has
encountered an LRECLRECOVERYFILE statement with a value greater than 240.
An AS/400 file with an LRECL greater than 240 cannot be edited on the AS/400.
The ADSM recovery files affected by this option are the volume history file, the
device configuration file and the DRM recovery plan file.
System Action: Server initialization continues.
User Response: Ignore the warning or change the LRECLRECOVERYFILE
statement to a value less than 241 and restart the server. If the warning is ignored
and it becomes necessary to edit the ADSM recovery files, the files will have to be
edited on a platform other than the AS/400 and returned to the AS/400. For
example, it may be necessary to FTP the files to a PC Workstation, edit them there
and FTP the changed files back to the AS/400. While editing the files, ensure that
the new LRECL does not exceed that of the original files on the AS/400. If the
LRECL of the files is increased during the edit process, they will be truncated when
they are returned to the AS/400.
Note: If an ADSM recovery file exists with an LRECL that is different than what is
being used on the LRECLRECOVERYFILE option, the existing file must be
deleted and re-created with the appropriate BACKUP command. For
example, the device configuration file is re-created with the BACKUP
DEVCONFIG command.
ANR8557E (AS/400)
Truncation occurred during a write operation.
Explanation: ADSM has detected a truncation while attempting a write operation.
System Action: The server activity which encountered this error will end, but
server processing continues.
User Response: Refer to the other displayed messages to determine which file was
involved when the write operation failed. As a group, the volume history file, the
960
Version 3 Release 7