1,126
edits
| Line 27: | Line 27: | ||
== Troubleshooting == | == Troubleshooting == | ||
There are two main causes for ARS1400E - either you are running multiple arsload processes that are interfering with each other, or arsload experienced an unrecoverable error and exited without cleaning up after itself, or 'crashed'. | |||
It's also possible that you tried to load a file with arsload, but didn't use the <code> -f </code> option, which 'forces unload' in the case of a failure during the load. | |||
=== Find multiple arsload processes === | |||
It may be possible that you're running more than one arsload daemon at a time: | |||
Find the Process ID numbers for the arsload processes with: | Find the Process ID numbers for the arsload processes with: | ||
On AIX: | |||
ps -ef |grep arsload | ps -ef |grep arsload | ||
On Linux: | |||
ps auxw |grep arsload | |||
Then issue a kill command for both of the processes: | Then issue a kill command for both of the processes: | ||
| Line 37: | Line 47: | ||
And restart only one instance of the IBM CMOD arsload command. | And restart only one instance of the IBM CMOD arsload command. | ||
=== Crashed load === | |||
If a load was running, and the arsload processes crashed, you will need to unload the failed file. (Normally, this would be done by adding the -f option to arsload to 'force unload of failed loads'. | |||
arsadmin unload -I ARCHIVE -u ADMIN -p PASSWORD -g APPGROUP -Q -L LOADID | |||
;Where... | |||
: ARCHIVE is the name of the CMOD instance that the file was being loaded into | |||
: ADMIN is a User ID with the the Delete privilege for the App Group | |||
: PASSWORD is the account password or name of the stash file containing the password for the account | |||
: APPGROUP is the name of the Application Group that the data was being loaded into | |||
: LOADID is the Load ID reported by arsload. | |||
== Articles Related to this message == | == Articles Related to this message == | ||
None available. | None available. | ||