ftp error – expect load error

[Femina Jaffer]

We have just migrated into 5.5 and production.  However, we have just encountered a recent problem after a cron executes a script to ftp a file over to a server.  The error is as follows:

0509-036 Cannot load program /hci/quovadx/qdx5.5/integrator/tcl/bin/expe

ct because of the following errors:

       0509-150   Dependent module libtcl8.4.so could not be loaded.

       0509-022 Cannot load module libtcl8.4.so.

Any advise would be most helpful, as it seems that none of the enviromental variables are being set.

Thank you.

Femina

Topic

[Tom Rioux]

Did you look in the /hci/quovadx/qdx5.5/integrator/tcl/lib directory to make sure the libtcl8.4.so module is in there?

Tom Rioux

[Femina Jaffer]

Yes we did.  Thank you.

[Russ Ross]

Check your cron job because it probably needs to be modified to point to 5.5 instead of let’s say 5.2.

For example here is a typical cron entry for cloverleaf 5.2

Code:

30 03 * * 1-6 /bin/ksh -c ‘eval . ~/.profile.cron /quovadx/qdx5.2/integrator prod_batch_005; $HCISITEDIR/scripts/_005/iftp_005_cron_entry.ksh’

but if I upgrade to cloverleaf 5.5 then I would expect I would need to change the qdx5.2 part of the cron entry to be qdx5.5 as follows

Code:

30 03 * * 1-6 /bin/ksh -c ‘eval . ~/.profile.cron /quovadx/qdx5.5/integrator prod_batch_005; $HCISITEDIR/scripts/_005/iftp_005_cron_entry.ksh’

Russ Ross
RussRoss318@gmail.com

[Femina Jaffer]

Thank you Russ.  We eventually got this to work.  Our Unix Network Admin, forced a link at startup to point to the path that it was looking for;  because when the script ran from the CRON none of the environmental variables were being set.

Thank you for your tip.

Femina

[Russ Ross]

Femina Jaffer:

Here is a URL that contains posts I made describing in more detail about setting up the cron envirnment before running your script to do the work:

http://clovertech.infor.com/viewtopic.php?t=1867” class=”bbcode_url”>http://clovertech.infor.com/viewtopic.php?t=1867

Russ Ross
RussRoss318@gmail.com

[Femina Jaffer]

hi Russ,

Thanks again. Upon looking at that post / link you suggested, I have a couple of questions.  The .profile file we have in the /home/hci directory is the file in question, correct?  Do we modify this file or create a another file as stated in the comments section of the .profile file, which should be either .profile.local.start or .profile.local.end ?  OR now if I think more clearly, leave teh .profile alone and create a new file .profile.cron and then reference this in the crontab, is this correct?

Thank you, Russ.

[Russ Ross]

Femina Jaffer:

Sounds like your figured it out when you asked,

OR now if I think more clearly, leave the .profile alone and create a new file .profile.cron and then reference this in the crontab, is this correct?

Yes that is what I did because the /home/hci/.profile is good for an interactive login session, whereas my /home/hci/.profile.cron is taylor made for running scheduled jobs from cron.

Russ Ross
RussRoss318@gmail.com

[Russ Ross]

Femina Jaffer:

By the way I do use these files for normal hci interactive session which get called by /home/hci/.profile

/home/hci/.profile.local.start

/home/hci/.profile.local.end

here is what I have in my /home/hci/.profile.local.start to give you some ideas:

Code:

#———————————————–
# define the functions and environment variables
#———————————————–

   . /quovadx/qdx5.2/integrator/mda_global/scripts/do_function.ksh

   set_HCI_PROFILE_PATH
   set_IGNORE_VMFULL

here is what I have in my /home/hci/.profile.local.end to give you some ideas:

Code:

# Make sure the terminal is correct
#———————————-

  TERM=xterm
  if [ $DISPLAY = “”                        ]; then
     TERM=aixterm
  fi
  if [ $DISPLAY = “pcis114.mdacc.tmc.edu:0” ]; then
     TERM=aixterm
  fi
  if [ $DISPLAY = “mdahub3.mdacc.tmc.edu:0” ]; then
     TERM=aixterm
  fi

# Make sure our root and site are set
# and check if any alerts are still turned off
#———————————————

  if [ -a /quovadx/qdx5.2/integrator/sbin/hcisetenv ]; then
     setroot -clear
     setroot $ROOT $SITE
     showroot

#      check_alert_off.ksh p_golive_maxsys
     check_alert_off.ksh p_global_adt_mock
     check_alert_off.ksh prod_sms_sched_mock

     check_alert_off.ksh prod_batch

     check_alert_off.ksh p_g_adt_out
     check_alert_off.ksh prod_cbord
     check_alert_off.ksh prod_doc_mgt
     check_alert_off.ksh prod_emr
     check_alert_off.ksh prod_flat_adt
     check_alert_off.ksh prod_genie
     check_alert_off.ksh prod_global_adt
     check_alert_off.ksh prod_hdx
     check_alert_off.ksh prod_lis
     check_alert_off.ksh prod_mymda
     check_alert_off.ksh prod_pharm
     check_alert_off.ksh prod_pulm_lab
     check_alert_off.ksh prod_ris
     check_alert_off.ksh prod_sms_21_adt
     check_alert_off.ksh prod_sms_22_adt
     check_alert_off.ksh prod_sms_23_adt
     check_alert_off.ksh prod_sms_order
     check_alert_off.ksh prod_sms_sched
     check_alert_off.ksh p_sched_out
     check_alert_off.ksh prod_super_adt

     check_ftp_kill.ksh
  fi

# set any extra paths that do not ordinarly get defined
#———————————————————-

  # export PATH=$PATH:$HCIROOT/scripts
  export MANPATH=$MANPATH:/usr/share/man:/usr/local/man:/usr/dt/man

# Specifiy the HCI GUI tools to use the vi editor in a xterm window
#——————————————————————

  export VISUAL=’xterm -fn 10×20 -fg yellow -bg black -e /usr/bin/vi’
  export EDITOR=’/usr/bin/vi’
  export XtermPath=’/usr/local/scripts/do_xterm’

# Make sure the aliases are set
#——————————

  . do_alias.ksh

# set MDA environment variables
#——————————

  set_MDA_ARCHIVE_ROOT
  set_MDA_BATCH_ENV
  set_MDA_HCIROOT_OFF_LIST
  set_MDA_UPDIR

# set cursor recall to vi edit mode
#———————————-

  set -o vi

# set prompt to the display the directory you are in
#—————————————————

  PS1=’(’`uname -n`’:$LOGNAME) $PWD > ‘

# make sure the window manager keyboard focus for hci user is set correctly
# sometimes people change it when they exit their sessions
#————————————————————————–

#  if [[ “`whoami`” = “hci” ]]; then
#    cp /home/hci/.dt/dt.resources_hci /home/hci/.dt/sessions/current/dt.resources
#  fi

Russ Ross
RussRoss318@gmail.com

[Richard Hart]

We use a profile and source this at the start of our cron scripts. Our FTP has a cron entry of

#  Central Waitlist Bureau – ftp TOPAS data to CWB server

#

0 0-23 * * *    /hci/InfoHEALTH/bin/CwbFtp.sh > /tmp/CwbFtp.log 2>&1

and the first line of the script is

. /hci/InfoHEALTH/bin/profile

This is also sourced in the user ‘.profiles’ as we peform almost all of our work on the AIX server.

The profile is a bit more complex as I have not updated since it was required for both Cloverleaf 3.5.5 and 5.2.1.

Note that we have our own ksh environment (FPATH) this lets us call the ‘normal’ scripts and also set the prompt/PATH so that our ‘main’ Cloverleaf path (LOCALBIN) is always available.

Profile

LOCALBIN=/hci/InfoHEALTH/bin

FPATH=/hci/InfoHEALTH/kshlib

export LOCALBIN

export FPATH

for myProfilePath in `ls -d /apps/qdxi*/qdx* 2>/dev/null` `ls -d /apps/aise*/qdx* 2>/dev/null`

do

       if -d $myProfilePath/integrator

       then

               QUOVADX_INSTALL_DIR=$myProfilePath

               break

       fi

done

export QUOVADX_INSTALL_DIR

PATH=$LOCALBIN:$PATH

[Author]

Replies