HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- upper working on one system but not in another
Operating System - HP-UX
1834070
Members
3131
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2003 01:52 PM
05-04-2003 01:52 PM
upper working on one system but not in another
I came up into a very irritating situation in which a portion of a script is working in one system but not working in another. Here is the segment in question:
============================================================
BRANCH=NONE
while echo "Enter branch #, or command, or help (Current branch = $BRANCH): \c"
read COMMAND
do
COMMAND=`upper \"$COMMAND\"`
case $COMMAND in
### change branch
[F,P,M,T,A,C,S,Z,R]*) FIELD=`echo $COMMAND | awk '{print $1}'`
VALUE=`echo $COMMAND | awk '{print $2}'`
if [ "$HAVEBRANCH" = "Y" ]
then PARMFILE=bmaint.$$
echo "$BRANCH|$COMMAND" > /tmp/$PARMFILE
echo "\n"
sqlplus -s $IMALOGIN @branch_upd.pl $PARMFILE
echo "\n" sqlplus -s $IMALOGIN @bchlist.pl $BRANCH
echo "\n"
else
echo "\nBranch must be specified!\n"
fi;;
HELP) cat branch_maint.hlp;;
============================================================
The code is the same in two machines, one is an RP5470 and the other is an HP9000, both have 64 bit HP-UX 11.00. However, the piece of code with "upper" only works on the RP5470 and it's not working on the HP9000. Why?
I have managed to resolve the problem by substituing the portion:
COMMAND=`upper \"$COMMAND\"`
With:
typeset -u COMMAND
This above the "read COMMAND". However, I am still puzzled why it works on one but not the other.
Please, any clues are appreciated.
============================================================
BRANCH=NONE
while echo "Enter branch #, or command, or help (Current branch = $BRANCH): \c"
read COMMAND
do
COMMAND=`upper \"$COMMAND\"`
case $COMMAND in
### change branch
[F,P,M,T,A,C,S,Z,R]*) FIELD=`echo $COMMAND | awk '{print $1}'`
VALUE=`echo $COMMAND | awk '{print $2}'`
if [ "$HAVEBRANCH" = "Y" ]
then PARMFILE=bmaint.$$
echo "$BRANCH|$COMMAND" > /tmp/$PARMFILE
echo "\n"
sqlplus -s $IMALOGIN @branch_upd.pl $PARMFILE
echo "\n" sqlplus -s $IMALOGIN @bchlist.pl $BRANCH
echo "\n"
else
echo "\nBranch must be specified!\n"
fi;;
HELP) cat branch_maint.hlp;;
============================================================
The code is the same in two machines, one is an RP5470 and the other is an HP9000, both have 64 bit HP-UX 11.00. However, the piece of code with "upper" only works on the RP5470 and it's not working on the HP9000. Why?
I have managed to resolve the problem by substituing the portion:
COMMAND=`upper \"$COMMAND\"`
With:
typeset -u COMMAND
This above the "read COMMAND". However, I am still puzzled why it works on one but not the other.
Please, any clues are appreciated.
Contrary to popular belief, Unix is user friendly. It's just very particular about who it makes friends with
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2003 01:57 PM
05-04-2003 01:57 PM
Re: upper working on one system but not in another
Oh, by the way, I forgot to mention that I kept testing this only with the "HELP" portion of the case control structure. I was typing lower case "help"+CR and the system would just hang, nothing would happen. It would not execute the cat of the help text file.
But this was working on the other system.
But this was working on the other system.
Contrary to popular belief, Unix is user friendly. It's just very particular about who it makes friends with
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2003 02:06 PM
05-04-2003 02:06 PM
Re: upper working on one system but not in another
Oh, no sweat. I found where the problem was happening.
This upper was an internal utility which converts lower to upper case by use of PL/SQL code and was not well documented. The login required for the PL/SLQ code to execute was not changed in the system in question and that is why it was failing.
Thanks!
This upper was an internal utility which converts lower to upper case by use of PL/SQL code and was not well documented. The login required for the PL/SLQ code to execute was not changed in the system in question and that is why it was failing.
Thanks!
Contrary to popular belief, Unix is user friendly. It's just very particular about who it makes friends with
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP