Troubleshooting
Problem
You get the following server connection error when you attempt to run the ARSLOAD program: arsload: Using /usr/lpp/ondem/ars/tmp for temporary files arsload: Could not connect to server to establish log id The job abends with the following error: USER COMPLETION CODE=4093 REASON CODE=00000034
Diagnosing The Problem
Here is a portion of the JCL:
//PS015 EXEC PGM=ARSLOAD,
// PARM=('-h ARSTST1 -u AAAAA -p XXXXXXXX -n -g VER2FOR7
// -s INPUT -v afp')
Here is the ars.ini in use:
HOST=IBMSYSF2
PROTOCOL=2
PORT=3011
DIRECTORY=
SRVR_INSTANCE=ARSTST1
SRVR_INSTANCE_OWNER=STCARST
SRVR_FLAGS_SECURITY_EXIT=1
SRVR_FLAGS_FOLDER_APPLGRP_EXIT=1
SRVR_OD_CFG=/usr/lpp/ars/config/ars.cfg
SRVR_SM_CFG=/usr/lpp/ars/config/ars.cache
.@srv@_V2MIGRATE.
HOST=V2MIGRATE
PROTOCOL=1
DIRECTORY=/SYSF/tmp/v2migrate
Resolving The Problem
This problem often results from a space issue with your temporary file system. The indexer abends when the hierarchical file system (HFS) fills up. This problem causes the U0040 error with reason 85 and then the ARSLOAD program does not terminate. When the ARSLOAD program tries to get a log ID for the next file to process, it fails with the error ABEND USER 4093 REASON CODE=00000034.
Check that you have enough space in the file system mounted for your temporary space by issuing the df -kP command at either the telnet or OMVS shell command line.
These errors can also be caused if the HFS was mounted as read only.
See also the referenced technote in the Related information section.
Related Information
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21292165