Error Running 'proupdt' on OE 10.2B Linux

Posted by Jeff Ledbetter on 06-Mar-2017 09:18

Hi.

Trying to update 10.2B license information and receiving the following:

** Error in TERM definition in PROTERMCAP

Has anyone encountered this before? We've successfully used proupdt in the past so I'm not sure what we've broken..

Thx.

Posted by Scott Dulecki on 06-Mar-2017 09:26

Jeff,
 
Check your TERM type and look at that entry in PROTERMCAP.  Maybe there’s something funky there…
 
Scott
 
==============================================
Scott M. Dulecki                   MPUG 16 Feb
Progress                          WMPUG 16 Feb
616/481-4313                    MWUG 19-21 Mar
sdulecki@progress.com                 SEUG TBD
==============================================
 

All Replies

Posted by Tom Cattigan on 06-Mar-2017 09:22

Try setting your TERM to xterm before running the proupdt - 

export TERM=xterm 



Posted by Jeff Ledbetter on 06-Mar-2017 09:25

That is the current value of $TERM.

Posted by Scott Dulecki on 06-Mar-2017 09:26

Jeff,
 
Check your TERM type and look at that entry in PROTERMCAP.  Maybe there’s something funky there…
 
Scott
 
==============================================
Scott M. Dulecki                   MPUG 16 Feb
Progress                          WMPUG 16 Feb
616/481-4313                    MWUG 19-21 Mar
sdulecki@progress.com                 SEUG TBD
==============================================
 

Posted by Tom Cattigan on 06-Mar-2017 09:30

Make sure your environment is set up correctly (what is the OS?) on unix proupdt is just a shell script:


Posted by Tom Cattigan on 06-Mar-2017 09:32

Sorry accidentally sent that last email

Here is the main part of the script - check that the PROTERMCAP can be found
# set home location
home=`pwd`;export home

# setup PROTERMCAP to point at local protermcap
PROTERMCAP=$home/protermcap;export PROTERMCAP

# setup HHPATH for Help
HHPATH=$home;export HHPATH
HOHPATH=$home;export HOHPATH

# run installation executable
./_ovrly -u

Posted by Jeff Ledbetter on 06-Mar-2017 10:32

Couldn't find anything funky but just copied the PROTERMCAP from another installation to get past this.

Thanks for your input.

Posted by Jeff Ledbetter on 06-Mar-2017 13:40

Found the funky. There was a blank line in the PROTERMCAP.,

Posted by Tom Cattigan on 06-Mar-2017 13:48

ah that'll do it.  I modified the protermcap file once...once.. :-)  Glad you found it!

This thread is closed