You did not say what version of HP-UX you are working on...
Till 11.23 ( after I dont know...) the default user shell was ksh , so you would use either .profile or .kshrc in your home directory, for root user its a little different...
I will add to previous post that you can in .kshrc and even in .profile now ( since 11.00 ? ) use also this syntax:
Thanks for the correcting me, was so obvious I zapped the magic line you need in .profile ...
There is a good reason to use a .kshrc if you use/have heavy customisation.:
To be sure no one has a corrupt environment when upgrading/patching OS if a new .profile is provided in the upgrade, it will be used as default for all users, thus avoiding extra most probable useless calls to internal support team... and as MadeInGermany flagged, the only thing we check here is that the magic line is present , if not will be added to the default...
Things get more complicated when using X server on PC with ssh and have an heterogenous environment with many flavours of UX/linux...
A correction: ksh does not take .kshrc. It takes an environment variable ENV.
You can of course put the following into .profile
#ksh takes this startup file:
ENV=$HOME/.kshrc; export ENV
If ENV is found in the environment when an interactive ksh is invoked, then parameter expansion, command substitution, and arithmetic substitution are performed on the value of $ENV to generate the pathname of a script that will be executed before the first prompt is issued. If ENV is not found in the environment when an interactive ksh is invoked and there is a file named .kshrc in your login directory, that file will be executed before the first prompt is issued.
Depending on how ksh is configured on your system, it may also look for /etc/ksh/.kshrc. On systems that are configured to use this file, you can skip executing it by setting ENV to a string starting with /./ or ././ (such as /.$HOME/.kshrc to execute only $HOME/.kshrc or /./dev/null to avoid executing either of those files).
Per our forum rules, all threads must have a descriptive subject text. For example, do not post questions with subjects like "Help Me!", "Urgent!!" or "Doubt". Post subjects like "Execution Problems with Cron" or "Help with Backup Shell Script".
The reason for this is that nearly 95% of all visitors to this site come here because they are referred by a search engine. In order for future searches on your post (with answers) to work well, the subject field must be something useful and related to the problem!
In addition, current forum users who are kind enough to answer questions should be able to understand the essence of your query at first glance.
So, as a benefit and courtesy to current and future knowledge seekers, please be careful with your subject text. You might receive a forum infraction if you don't pay attention to this.