

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
We have already implemented solution provided in HP blog like change prompt to $.
But it does not fix this error.
We have moved from Hp UNIX to Red hat Linux.
We have seen this error in HP UNIX but very rarely.
Found text 'KSC_EXIT_STATUS' without a '$?' and without an exit status.
thanks
Rahul
Accepted Solutions


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hello,
Well, this is a defect and RnD created a new defect accordingly:
I think we can track the status to check for the possible resolution of this fix.
Regards,
Alonso

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hello Rahul,
Could you please tell me what was the possible solution that HP provided you? I have found that This may happen when the command line prompt is a long prompt. Solution: Set the prompt to be a short prompt Change the command prompt to be a short string by setting the following in the .profile.
Please let me know if this helped you.
Best Regards,
Carolina.
“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
This is solution
Still i get error randomly.
----------------------
Checking our knownledge database I found out that this may happen when the command line prompt is a long prompt. Example: If the following is set in the .profile, you will receive the above error for sqlplus check or in execution logs: PS1=`hostname`:'abc/test/oracle/temp/dump/trump/dust/rust-> '
A solution could be "PS1" setting will avoid the possibly having an issue of exceeding command line length restrictions. Set the prompt to be a short prompt. Change the command prompt to be a short string by setting the following in the .profile: PS1="$"


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Could you please attach your .profile file here?


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
$: vi /home/kintana/.bash_profile
# set up stuff unique to the Korn Shell
if [ "$RANDOM" != "$RANDOM" ]
then
EDITOR="vi" ; export EDITOR
PS1="${HOSTNAME}:${LOGNAME}: "
fname=`date +%b%d:%H%M`
HISTFILE=$HOME/.sess_history/.${HOSTNAME}hist.$fname
HISTSIZE=1024; export HISTSIZE
# Set up useful aliases
alias ls="/bin/ls -F"
alias ls-l="/bin/ls -Fl"
fi
#export PS1='${LOGNAME}:'
#export PS1='$'
#added this to avoid SCP error
export TERM=vt100
export PS1='$: '
"~/.bash_profile" 56L, 1423C 49,1 Bot
export RCS_HOME=/eb_rdk0_p/software/archives
#added this to avoid SCP error
export TERM=vt100
export PS1='$: '
# check for existance of standard environment variables
# if they are null, assign values to them
LOGNAME=${LOGNAME:-`whoami`}
HOSTNAME=${HOSTNAME:-`hostname`}
export LOGNAME HOSTNAME
# set up stuff unique to the Korn Shell
if [ "$RANDOM" != "$RANDOM" ]
then
EDITOR="vi" ; export EDITOR
PS1="${HOSTNAME}:${LOGNAME}: "
fname=`date +%b%d:%H%M`
HISTFILE=$HOME/.sess_history/.${HOSTNAME}hist.$fname
HISTSIZE=1024; export HISTSIZE
# Set up useful aliases
alias ls="/bin/ls -F"
alias ls-l="/bin/ls -Fl"
fi
#export PS1='${LOGNAME}:'
#export PS1='$'
#added this to avoid SCP error
export TERM=vt100
export PS1='$: '


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Let's try to change
export TERM=vt100
export PS1='$: '
for
export TERM=Dumb
PS1='$' or "$"
Regards,
Alonso


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
last time i changed ter to DUMB but it has an issue. When i tried to edit file using vi, terminal get hung up.
So i changed back to vt100


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hello,
Well, this is a defect and RnD created a new defect accordingly:
I think we can track the status to check for the possible resolution of this fix.
Regards,
Alonso

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
We are also facing same issue frequently in our deployment managemnt migrations.
Found text 'KSC_EXIT_STATUS' without a '$?' and without an exit status
Is there any further update to this defect as I couldn't able to find any progress on defect rasied with RnD team.