ISO8859-1 / / 4 84 m ) ( /  ; C 6  ) & ! ! ) K g4 # . - 9> @x 4 : E)6o;F&))PCz !50-G.uH_PM j N $X(}2 1&,KS  3[ 7 5 (T !$B(g6G & P6 & e .+C6o0=BEXR /D!Af9J|- hp ` B: d} =) )J+t.10 $ 2 ; W . * - #!C!?@!.!0!@"$"eH# E#f Q# M# )$L E$vM$S% <%^*%*% )%@&#&\#&@&+&7'-'I 7'w O'j'%(j'(T(D) 4)R1) e)G*C*g2*&*/+:+5&+p0+ O+ _, ;,x A, Y,j-P:---/.$,.T1./.1.,/D/B*/B//O0n0Y1T71U1M2<J2L2+3"-3N 3| 3 23 13 34" 4VG4t44F4J58X5"5*5X6*6"6'6G6848^:p: p;T r; V<8 r< K=3=N"=H===G>,<>ta>a?.?u????@(@2'@[ @ @ :@ -@ &A'&ANAu'AA7B_#B4B6BDC' ClKC[C>D5@DtHD;D,E:IEg7EMENF7HF NF XG 5Gw IG HGIH@HH,HrICIs*IXI5J;gJq;JK:KjK8L;ULtBL6M 8MD)M}2MYMVN4N ;O.AOjO4P,BPaSPPPHQI FQ UQFR/GRv&RUR:S;$Sv4S4S GT ;TM %T %T $T T4U!UP-UrCU(U2V /V@1Vp3V VFW]'WVW0X#GXTJXX Y~VZ(9Z4Z.Z[A\.w\p\$]])]C]ce]A]>^+E^j8^9^C_#_g1020-001 Couldn't create the file %s (%d). %s%s1020-002 Couldn't access the file %s (%d). %s%s1020-003 Couldn't create the directory %s (%d). %s%s1020-004 Couldn't access the directory %s (%d). %s%s1020-005 Not enough memory.%s1020-006 Out of memory: %u bytes needed%s1020-007 System call %s error (%d). %s%s1020-008 Couldn't execute %s command (%d). %s%s1020-009 Error in exec command starting the WPAR (%s): %s%s1020-010 Couldn't load the shared library %s : %d %s%s1020-011 Missing symbol %s in %s: %d %s%s1020-012 Can't free memory: %d bytes%s1020-013 File %s already exists%s1020-014 File %s does not exist%s1020-015 File %s is empty%s1020-016 %s is not a directory%s1020-017 Directory %s does not exist or is invalid%s1020-018 Unable to remove file %s%s1020-019 Unsupported char device on stdio %d%s1020-020 Unsupported file type for stdio %d%s1020-021 Unsupported file type %s for file '%s' (fd %d)%s1020-022 Can't checkpoint with a deleted directory opened (%s)%s1020-023 File '%s' may have been moved or unlinked%s1020-024 Unlinked FIFO not supported (it may be on GPFS)%s1020-025 Cannot change directory to the checkpointed value '%s': %d%s1020-301 Cannot get file information for fd:%d %d.%s%s1020-323 Unsupported file type (%d) for fd (%d) (pid: %d)%s1020-324 Unsupported file type (%d) for fd (%d) (pid: %d) (name: %s)%s1020-026 Can't send message (%d). %s%s1020-027 Can't receive message (%d). %s%s1020-028 Message received incomplete :%llu bytes received on %llu%s1020-029 Socket %d disconnected%s1020-030 Can't connect to the remote node %s: %d %s%s1020-031 Can't unlink socket node '%s' : %d %s%s1020-032 Can't read on connection %d: %d %s%s1020-033 Can't write on connection %d: %d %s%s1020-034 Internal error, communication with ipc-helper failed (%d). %s%s1020-035 WARNING: Reverse lookup to find my host name failed. Defaulting to numeric notation.%s1020-036 Can't establish enough connections with the remote node for migration%s1020-294 AF INET socket resource embedded in a AF UNIX socket is not supported for a no virtual ip WPAR.%s1020-037 Full statefile path is too long (%d characters, max is %d) : %s%s%s%s1020-038 Statefile is not complete%s1020-039 Unable to remove %s statefile%s1020-040 Can't get the real path for %s (%d). %s%s1020-041 Invalid statefile: %s%s1020-042 Couldn't erase incomplete statefile %s%s1020-043 Statefile corrupted (%u/%u)%s1020-044 Pathname of statefile must be visible inside and outside of WPAR%s1020-045 %s statefile path includes a mount point not defined at WPAR creation. When statefile path contains a mount point, this mount point should be visible through lswpar -M command %s1020-046 Couldn't write to the statefile (%d). %s%s1020-047 Error while accessing the statefile (%d). %s%s1020-048 Error while reading the statefile (%d). %s%s1020-295 Unable to overwrite %s. A statefile can only be overwritten by the same WPAR and the same user which created the statefile.%s1020-049 WPAR already frozen%s1020-050 WPAR isn't frozen (state: %s)%s1020-051 This operation can only be done with a statefile from an application WPAR%s1020-052 WPAR %s is not active%s1020-053 WPAR %s is already active%s1020-054 WPAR %s is not checkpointable%s1020-055 Can't dump administrative data for the WPAR%s1020-056 Can't find out if WPAR %s is an application or a system WPAR%s1020-057 Will retry in %d second(s).%s1020-058 Invalid WPAR name %s. It should match WPAR name on departure node: %s%s1020-059 Can't configure the WPAR %s%s1020-060 The state of the WPAR is currently non-checkpointable. Checkpoint should be retried later.%s1020-061 Process cannot enter WPAR %d: %d %s%s1020-062 Unable to run lswpar command, %s%s1020-063 Can't get or set WPAR state (0x%x 0x%x): %d%s1020-064 WPAR isn't restart-paused (state: %s)%s1020-065 Current user is not allowed to control the WPAR %d%s1020-066 Another operation is already in progress on the WPAR %d%s1020-067 The current state of the WPAR doesn't allow this operation%s1020-291 The checkpoint operation cannot be done because the WPAR is terminating%s1020-068 Unsupported configuration version %d%s1020-070 This version (%d) of the encrypted data is not supported.%s1020-071 This statefile format is not supported (version is %d)%s1020-072 Server cannot talk to an older client version.%s1020-073 Version of data provided by the kernel is not supported by MCR.%s1020-074 Kerberos support is not available with the mcrk kernel extension currently loaded. You should reboot your system.%s1020-075 The version of MCRP (%s) and MCRTL (%s) differs. Most of the time this is because the version of MCR installed inside a system WPAR with private /opt is not the same than the global one.%s1020-076 MCR version has been changed during operation, previous version was %d, current version is %d%s1020-292 Unable to manage data from departure node. You should upgrade MCR on the arrival node%s1020-293 The server version (%d) is not supported by this client%s1020-307 The filesets installed on departure and arrival nodes are not compatible with a migration%s1020-077 Signal %d received. Interrupting current operation%s1020-078 Can't set signal mask (%d). %s%s1020-079 %s child exited abnormally: %d%s1020-080 %s child exited due to signal %d%s1020-081 Can't set PATH environment variable%s1020-082 Can't suspend AIOs for the process: %d%s1020-083 Can't resume AIOs for the process: %d%s1020-084 Cannot start subsystem %s%s1020-085 Couldn't forward signal %d to forked process: %d%s1020-086 Can't load nfs kernel extension: %d%s1020-087 Couldn't save the nfs state: %d%s1020-088 Couldn't restore the nfs state: %d%s1020-089 Internal error detected.%s1020-090 Configuration is about WPAR %d while working on WPAR %d.%s1020-091 The abort of the previous action is still in progress%s1020-092 Currently in action %s. Can't kill.%s1020-093 Currently in action %s. Can't resume.%s1020-094 Unexpected death of WPAR during the restart operation%s1020-095 The stdio %d is missing at restart time but was inherited at execute time. The restartwpar command should be run in the same context as the wparexec one (telnet, rsh, etc).%s1020-096 Internal error detected while calling rc.boot inside the WPAR%s1020-097 Internal error detected while cleaning up the loader state%s1020-098 Internal error detected while saving the list of internal mount points%s1020-099 Internal error detected while recreating the internal mount points%s1020-306 Unexpected '%s' output from %s%s1020-100 Protocol error: received message of type %d instead of %d.%s1020-101 Protocol error: unexpected data count received (%d instead of %d).%s1020-102 Disconnection error occurred while the WPAR is in zombie state. Exiting.%s1020-103 Protocol error: cannot sync up with server: %d %s%s1020-104 Server interrupted by signal %d%s1020-105 Server exited abnormally (0x%x)%s1020-106 Invalid crypt script '%s': %s.%s1020-107 Encrypted statefile probably corrupted or invalid key%s1020-108 Failed to decrypt buffer%s1020-109 Failed to encrypt buffer%s1020-110 Internal error detected in the crypt process error %d%s1020-111 Unable to load the CLiC library.%s1020-112 Can't find the symbol %s in the CLiC library%s1020-113 Unable to get AES key, error : %x.%s1020-114 Internal error: Call %s to mcrk failed %d %s%s1020-115 Invalid '%s' crypt script owner. The script should be owned by root.%s1020-116 Invalid '%s' crypt script permission. The script should only be writable or executable by root.%s1020-117 Unable to change %s: %d %s%s1020-118 %s file is not owned by root%s1020-119 The command should be executed as root, or with the appropriate RBAC role%s1020-120 A non-root user is not allowed to manipulate system WPARs%s1020-121 Can't get WPAR owner for WPAR %s (%d). %s%s1020-122 Can't get WPAR id for WPAR %s (%d). %s%s1020-123 Non-root user support is not possible with the version of MCR in use on the departure node%s1020-124 Couldn't read the list of internal mount points of WPAR: %d.%s1020-125 Unsupported file system (type %d) for mount point '%s' .%s1020-126 Can't mount internal filesystem %s: %d.%s1020-127 Can't vmount(%s, %s): %d %s%s1020-128 Can't unmount wpar scratch fs: %d %s%s1020-129 SAN disks need recovery. Delaying interruption.%s1020-130 Local SAN recovery failure.%s1020-131 Arrival node failed its SAN recovery.%s1020-132 Cannot synchronize SAN recovery between arrival and departure nodes.%s1020-133 Could not get SAN disks reservation(s). The wpar cannot run and needs to be stopped.%s1020-134 Could not recover SAN disks. Reported status %d.%s1020-135 SAN: a process is editing the ODM. Cannot migrate now.%s1020-136 Default location for pmemfs mount point (%s) exists, but it is not a directory%s1020-137 Default location for pmemfs mount point (%s) is already in use for a different file system type%s1020-138 Can't create translation table for the WPAR: %d%s1020-139 Can't export the swap directory %s%s1020-140 Can't unexport the swap directory %s%s1020-141 Can't remove swap file %s: %d. %s%s1020-142 Can't remove swap directory %s: %d. %s%s1020-143 Can't activate the swap '%s': %d. %s%s1020-144 Can't delete obsolete swap device '%s'%s1020-145 Can't delete the swap device '%s'%s1020-146 Conflicting swap device exists even after cleanup attempt%s1020-147 Can't swapoff device %s: %d. %s%s1020-148 Can't read the swap device name created by mkps: %d. %s%s1020-149 Found 2 conflicting paging devices : '%s' and '%s'. Check that these paging devices are no more used and remove them manualy using the rmps command.%s1020-298 Unsupported locally modified file '%s' (fd %d) on STNFS file system.%s1020-299 Unsupported memory mapping of a file (%s) opened with the O_*SHARE flags on local JFS2 file system.%s1020-300 Unsupported in use file (%s) stored on a file system owned by an another WPAR.%s1020-150 Invalid IP address "%s" to connect to server%s1020-151 No TTY is inherited. A TTY was set at checkpoint time, but not at restart.%s1020-152 Can't restart without stdio %d wich was in use at checkpoint time.%s1020-153 stdio %d is a dup of %d but it was separate at checkpoint time.%s1020-154 Resource %s is not checkpointable (pid: %d). Query returned %d %s%s1020-155 Deleted POSIX shms not supported%s1020-156 Deleted mmaped file not supported.%s1020-157 Unsupported map type.%s1020-158 Unknown map type %d.%s1020-159 Too many arguments passed to %s command%s1020-160 Error processing argument list for MCR%s1020-161 Unknown WPAR %s. Please check WPAR list.%s1020-162 No server running.%s1020-163 User command returned bogus status %d. Will be changed to %d%s1020-164 A SAN file (fd %d) may have been moved %d%s1020-165 Failed to initialize log service, check your log parameters%s1020-296 Checkpointable workload partitions require additional software.%s1020-303 A cross level migration is only allowed on a rootvg (SAN) workload partition.%s1020-304 Invalid key value "%s".%s1020-310 Unsupported tunable value %s=%d%s1020-154 Resource %s is not checkpointable (pid: %d) (pname: %s). Query returned %d %s%s1020-166 Usage: %s wparName 1020-167 Usage: %s [-b] wparName 1020-168 Usage: %s wparName signalNum 1020-169 Usage: To checkpoint an active WPAR: chkptwpar [-k | -p] [-F] -d /path/to/statefile [-o /path/to/logfile [-l ]] wparName To freeze an active WPAR: chkptwpar -f [-F] -d /path/to/statefile [-o /path/to/logfile [-l ]] wparName To checkpoint a frozen WPAR: chkptwpar [-k | -p] [-F] wparName 1020-170 Usage: To restart a WPAR: restartwpar [-p [-u userCommand]] -d /path/to/statefile [-o /path/to/logfile [-l ]] [-C /path/to/cpumappingfile | -R /path/to/cpusetfile] [-a] wparName 1020-171 Usage: To start a migration server on the source node: movewpar -s [-w] [-o /path/to/logfile [-l ]] [-c connectport] wparName [IP_address] to stop a migration server: movewpar -x wparName to migrate an active WPAR: movewpar [-b] [-a] -k key [-o /path/to/logfile [-l ]] [-u callback] [-K] [-B] [-C /path/to/cpumappingfile] wparName departureNode 1020-172 Usage: To generate keys needed to encrypt/decrypt a WPAR statefile: genwparstatekey 1020-173 Usage: To encrypt a WPAR statefile: encryptwparstate -d /path/to/statefile -x /path/to/encrypted_file 1020-174 Usage: To decrypt a WPAR statefile: decryptwparstate -d /path/to/statefile -x /path/to/encrypted_file 1020-175 Usage: To remove a WPAR statefile: removewparstate (-d /path/to/statefile | -D /path/to/directory) [-F] 1020-176 Usage: To convert a virtual PID to the real PID: wparvpid2pid wparname vpid 1020-177 Usage: To extract CPU resource set from statefile: extractcpu -d /path/to/statefile -x /path/to/newfile 1020-178 %s: '-d' option is required when the WPAR is not already frozen.%s1020-179 %s: '-o' or '-l' options aren't allowed.%s1020-180 Invalid log level value%s1020-181 One (and only one) operation must be specified: -s, -x and -k%s1020-182 The -c option is only available with the -s option%s1020-183 The -k key and an IP address are required for wpar migration%s1020-184 This command is not permitted from inside a WPAR.%s1020-297 Moving the workload partition back to its previous host requires use of the -B option.%s1020-302 The -B option is only valid for moving a workload partition back to its previous host.%s1020-185 Please wait for the key generation...1020-186 %s command succeeded1020-187 %s command failed.1020-188 WPAR is paused.1020-189 WPAR %s was started.1020-190 WPAR %s was frozen.1020-191 WPAR %s was checkpointed in %s.1020-192 WPAR %s was restarted from %s.1020-193 WPAR %s was resumed.1020-194 WPAR %s was killed.1020-195 Migration server started successfully for WPAR %s1020-196 Migration server for WPAR %s stopped1020-197 WPAR %s migrated successfully1020-198 User call back command failed1020-199 Connection key:1020-200 MCR kernel driver %s is loaded1020-290 The statefile couldn't be opened and the WPAR name does not match a defined system WPAR. Please check that both the statefile path and the WPAR name are valid.1020-312 Migration server started successfully for LPAR1020-313 LPAR migrated successfully1020-320 %s must be terminated prior to Live Update.1020-201 Failed to remove statefile lock '%s' %d. %s%s1020-202 There's already an operation in progress on statefile: %s%s1020-203 Invalid WPAR name: %s%s1020-204 WPAR %s is locked, another operation may already be in progress.%s1020-205 Lock error: the state of the WPAR %s does not allow checkpoint/restart operation%s1020-206 Unexpected error when locking WPAR %s (lockstat=%d)%s1020-207 Unexpected error when unlocking WPAR %s (lockstat=%d)%s1020-208 Kerberos: Can't find required symbol %s in the shared library%s1020-209 Kerberos: Failed to open gss library (%s): %d %s%s1020-210 Kerberos: gss error %s code 0x%x %s1020-211 Kerberos: Can't import server name. Please check configuration%s1020-212 Kerberos: Can't convert imported server name%s1020-213 Kerberos: Can't acquire kerberos credentials. Service name is '%s'%s1020-214 Kerberos: Can't accept security context. Please check configuration%s1020-215 Kerberos: Remote node couldn't initialize. Reported status %d%s1020-216 Kerberos: Can't initialize client security context with server '%s'%s1020-217 Kerberos: Departure node couldn't accept kerberos context. Reported status %d%s1020-218 Kerberos: Service name too long: %s max=%d%s1020-219 Kerberos: Couldn't encrypt buffer. Please check authorizations%s1020-220 Kerberos: Couldn't encrypt buffer. Please check configuration%s1020-221 Kerberos: Couldn't decrypt buffer. Please check authorizations%s1020-222 Kerberos: Couldn't decrypt buffer. Please check configuration%s1020-223 Kerberos: Configuration error: %d%s1020-224 Migration with Kerberos encryption is not possible with the version of mcr in use on the departure node%s1020-225 Kerberos: helper couldn't initialize. Reported status %d%s1020-226 Kerberos: Initialization failed%s1020-228 Check syslog output for potential Kerberos configuration error in NFSv4 setup%s1020-229 Unable to read the '%s' configuration file%s1020-230 Statefile %s is not in the list of authorized paths, please check your %s configuration file%s1020-231 -R option is only available for application WPAR%s1020-232 Missing capabilities. You need to have CAP_NUMA_ATTACH and CAP_PROPAGATE set to be able to use the -R or -C options.%s1020-233 BSR version not supported or BSR not configured%s1020-234 BSR support window configuration on arrival node (%d) is not the same as on departure node (%d)%s1020-235 chkptwpar is not allowed on rootvg (SAN) WPAR%s1020-305 WPAR architecture '%s' is not lower than or equal to system's architecture%s1020-236 Couldn't resume the WPAR. Please check the WPAR's state%s1020-237 Unable to restore shared memory %x (%d). %s%s1020-238 Unable to set shm %d page size to %d (%d). %s%s1020-239 Unable to lock shm %d (%d). %s%s1020-240 Unable to reattach to POSIX shm %s : %d%s1020-308 Process %d is running in the Native Runtime Environment and cannot be migrated%s1020-309 Binary for process %d (%s) is not compatible with migration across OS level%s1020-318 Shared Memory Transport Sockets are not supported by live update. Process %d (%s) cannot be checkpointed. Stop the X server and try live update again.%s1020-241 No CPU ressource set to extract, no file created%s1020-242 CPU %d is unavailable, it can't be set in resource set%s1020-243 Unable to restore resource set (%d). As the -R ou -C option has been set, check carefully CPUs data are well defined%s1020-244 Unexpected line %d in CPU mapping file %s%s1020-245 Error while reading VPID line %d in CPU mapping file %s%s1020-246 Error while reading number of CPU bitmap, line %d in CPU mapping file %s%s1020-247 Error while reading CPU bitmap number, line %d in CPU mapping file %s%s1020-248 Not enough CPU bitmap defined, line %d in CPU mapping file %s%s1020-249 Too much CPU bitmap defined, line %d in CPU mapping file %s%s1020-250 Departure CPU ID %d has not arrival CPU ID defined in the CPU mapping file%s1020-251 Cannot send the checkpoint signal to the process PID:%d: %d%s1020-252 Acting thread TID:%d of process PID:%d has died unexpectedly%s1020-253 Cannot release %s id %d: %d%s1020-254 The clogined process PID:%d owns the virtual PID %d needed for the restart%s1020-255 Can't get inode details for fd %d of process %d%s1020-256 Can't allocate new %s: %d%s1020-257 %s process (PID:%d) has died unexpectedly%s1020-258 Memory allocator error for process PID:%d%s1020-259 Can't manage the new thread TID:%d of the process PID:%d: %d%s1020-260 Can't remove thread TID:%d of process PID:%d: %d%s1020-261 Can't create %s id %d : %d%s1020-262 Can't delete %s id %d : %d%s1020-263 Can't find data for %s %d%s1020-264 Unknown %s command %d%s1020-265 Can't recreate thread RTID %d VTID %d: %d%s1020-266 Killing process PID:%d%s1020-267 Can't register the new WPAR %d: %d%s1020-268 DR path length %d is too long, maximum path length is %d%s1020-269 Unexpected error with DR (%d)%s1020-270 Can't trigger phase of DR event %s (%d)%s1020-271 Can't register event %s with DR (%d)%s1020-272 Can't unregister event %s with DR (%d)%s1020-273 Error during %s event with DR in WPAR %s%s1020-274 Departure node couldn't freeze the WPAR (status %d). Check the output of the movewpar command on the departure for details.%s1020-275 The cleanup of the previous operation is still in progress.%s1020-276 No process left in the WPAR.%s1020-277 Aborting recovery. WPAR suffered an unrecoverable error. Stopping the WPAR.%s1020-278 Connection lost with the remote node.%s1020-279 WPAR temporarily not checkpointable. Retrying in %d seconds.%s1020-280 The command on the remote node received an interrupting signal.%s1020-281 The migration operation has failed on the remote node (remote status %d). Please check the command's output on the remote node for details.%s1020-282 A non disruptive error occurred while cleaning up the departure node. Reported status %d. Please check the command's output on the departure node for details.%s1020-283 The shell (/usr/bin/sh) used to run the user command returned the error: %d%s1020-284 The user command got killed with the signal %d%s1020-285 The MCR kernel extension sucessfully loaded1020-286 The kernel extension %s is not loaded1020-287 Usage: Loading : %s -l -f -m [-q] Unloading : %s -u [-f | -i ] -f specify kernel extension pathname -m specify MCRK user mode module pathname -i specify kernel extension id -q quiet mode, do not complain if mcrk is already loaded 1020-288 Unconfiguration of the MCR kernel extension failed. %s%s1020-289 Configuration of the kernel extension mcrk failed. %s. Make sure the versions of MCR and AIX are compatible.%sSystem and Application WPARSystem and Application WPAR MobilityApplication WPAR MobilityOwned Application WPAR MobilityOther Application WPAR Mobility1020-311 The state of the LPAR is currently non-checkpointable. Checkpoint should be retried later.%s1020-314 Timeout while waiting for init to checkpoint its state%s1020-315 Timeout while waiting for init to restore its state%s1020-316 %s temporarily not checkpointable. Retrying in %d seconds.%s1020-317 Active WPAR found, live update cannot proceed%s1020-321 Failed to checkpoint %s %d times. Give up now.%s1020-319 %s temporarily not checkpointable. Retrying in %d seconds.1020-322 (pid: %d) (name: %s) The current working directory of this process appears to be in a file system that has been force-unmounted.