COBOL compilation on Unix


COBOL compilation on Unix

To compile COBOL on UNIX:

1. Take backup of existing COBOL files (cblbin)

Note. When you bring patches up from the file server, the files need to have a lowercase cbl extension and an uppercase program name, as in PATCH.cbl.

2. Run the below to set the respective environment variables

PATH=$PATH:/app/microfocus/cobol/bin; export PATH
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/app/microfocus/cobol/lib; export LD_LIBRARY_PATH
COBDIR=/app/microfocus/cobol; export COBDIR
PS_HOME=<Path_To_PS_HOME>; export PS_HOME

3. Change to the PS_HOME/setup directory:

cd $PS_HOME/setup

4. To compile all the COBOL source dynamically, issue the command:

./pscbl.mak

The dynamic compile creates INT, LST, and GNT files, which are copied to these locations:

*.INT -> PS_HOME/src/cbl/int
*.LST -> PS_HOME/src/cbl/lst
*.GNT -> PS_HOME/cblbin

Recompiling COBOL on UNIX:

COBOL recompilation is required in the following situations:

• Any COBOL programs change
• The supported COBOL compiler changes
• You change the version of your RDBMS
• You change your version of your operating system
• You apply a patch or a fix

Note. Remember, you must always use your file server as the source repository for your COBOL. You should download any patches and apply any customizations to the file server, and disseminate them from there.

You can compile a single COBOL program dynamically by using this command syntax:

./pscbl.mak <PROGRAM NAME WITHOUT "cbl" EXTENSION>

For example,

./pscbl.mak PTPDBTST compiles the lone file PTPDBTST.




Note. If you want to recompile all your COBOL, you can follow the procedure described earlier.
See “Compiling COBOL Programs.”

The compile should run without errors until it completes. After the script is complete, check the destination directories for the newly created files in PS_HOME/src/cbl/int, PS_HOME/src/cbl/lst, and PS_HOME/cblbin.

They should have a length greater than zero as well as a current date and time stamp.
Note. You can also use pscbl.mak PTP or pscbl.mak PTP* to compile all source files that start with PTP.

Steps to be followed for Password Split




Step1.Dev team needs to raise a TT to setup PWP for the particular Environment.

Step2.Setup PWP on the process schedulers and make sure it works.

Step3.Dev team provides the TT for Password split.

Setp4.Copy the all the .sh files from this foler(R:\Infosys_Offshore\Common Processes Docs\PasswordSplit) to the PSHOME.

Step5.Run c_pwchg_sysadm.sh to change the password.

Step6.Run c_pwchg_pwp.sh to get the passowrd updated in the PWP setup also.

Step6.Cross check if sysadm pwd is to be changed on BO and AI side also.

Step7.Dev team needs to raise a seperate TT to Stat team to make the changes on stat side as well.

Step8.We need to bounce the application after the sysadm password is changed and this is mandatory.

How to run Version AE program




cd $PS_HOME/bin

export PS_SERVER_CFG=$PS_HOME/appserv/prcs/PAPRDG/psprcs.cfg

psae -CD PAPRDG -CT ORACLE -CO JN84227 -CP 'Jibo Peoplsoft 2 tier Password' -R INSTALL  -AI VERSION

Procedure to run ae job

PROPER PROCEDURE
The proper steps to follow when running VERSION AE are:
1. Shutdown all Application Servers, Process Schedulers, and other PeopleTools clients.
2. *critical step* Ensure that all Application Designer session are logged out and shut down. If necessary, shutdown and restart the database and its communication software.
3. Establish the proper shell environment. Normally this includes logging in as your PeopleSoft id, and
changing to the PSFT bin directory (i.e. cd $PS_HOME/bin)
setting the PS_SERVER_CFG environment variable (export PS_SERVER_CFG=$PS_HOME/appserv/prcs/<dbname>/psprcs.cfg)

4. Execute the command from a command line:
psae -CD <dbname> -CT <dbtype> -CO <oprid> -CP <pswd> -R INSTALL [where INSTALL is a valid run control] -AI VERSION
(Note: INSTALL must be a valid run control for <oprid>)
5. Issue the following SQL and archive the output to ensure that the program ran (all the versions should be 1).
SELECT * FROM PSVERSION ORDER BY VERSION DESC;
6. Clear the cache files from the Application Server, Web Servers, Process Schedulers, and Client machines.
7. Restart the system per normal operational procedures. There will be expected performance impact as the system rebuilds its cache files.
8. Over the course of the following days, every 4 hours or so, rerun the SQL from Step #5. You should observe a gradual growth of the versions, typically in the order of dozens per day. The version associated with SYS should always be equal to or greater than all other values in the table.
Should you observe one of the following conditions contact the GSC immediately for further advice.
1. The version value associated with SYS is no longer greater to or equal all other value in the PSVERSION table.
2. Some of the values increase dramatically, on the order of several thousand, and then remain fairly constant. Normal behavior is for the values to increase by increments of 1. One exception would be during the migration of a project with many records. Some values will increase by the number of records migrated.
Workaround:
N/A
Running version may fix the problem, but the entire dbms will be slow for sometime because objects will need time to be recached.



PS installation


rpm -ivh j2sdk-1_4_2_08-linux-i586.rpm

Alternatively the following lines can be added to the /etc/sysctl.conf file:

kernel.shmmax = 2147483648
kernel.shmmni = 128
kernel.shmall = 2097152
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000

sysctl -p

In addition the following lines can be added to the /etc/security/limits.conf file:

oracle soft nofile 65536
oracle hard nofile 65536
oracle soft nproc 16384
oracle hard nproc 16384


Add following groups
groupadd oinstall
groupadd dba
groupadd oper
groupadd apache

Add a user oracle

useradd -g oinstall -G dba oracle !(-g primary group ,-G secondary group and oracle is user under this group)
passwd oracle

mkdir -p /u01/app/oracle/product/9.2.0.4.0
chown -R oracle.oinstall /u01   !(-R option is recursive rights..ownership to all the /u01 user)
chown -r

Add the folling entries .bash_profile

ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE
ORACLE_HOME=/u01/app/oracle/product/9.2.0.4.0; export ORACLE_HOME
ORACLE_TERM=xterm; export ORACLE_TERM
PATH=/usr/java/j2sdk1.4.2_08/bin:$ORACLE_HOME/bin:$PATH; export PATH
ORACLE_OWNER=oracle; export ORACLE_OWNER
ORACLE_SID=PROD; export ORACLE_SID
LD_LIBRARY_PATH=$ORACLE_HOME/lib; export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib
CLASSPATH=$CLASSPATH:$ORACLE_HOME/network/jlib; export CLASSPATH
LD_ASSUME_KERNEL=2.4.1; export LD_ASSUME_KERNEL
TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR


The following setup steps relate to Metalink Note:252217.1 and must be performed as the root user.

Install the following packages:

# From RedHat AS3 Disk 2
cd /mnt/cdrom/RedHat/RPMS
rpm -Uvh setarch-1.3-1.i386.rpm
rpm -Uvh tcl-8.3.5-92.i386.rpm

# From RedHat AS3 Disk 3
cd /mnt/cdrom/RedHat/RPMS
rpm -Uvh openmotif21-2.1.30-8.i386.rpm
rpm -Uvh compat-db-4.0.14-5.i386.rpm \
         compat-gcc-7.3-2.96.122.i386.rpm \
         compat-gcc-c++-7.3-2.96.122.i386.rpm \
         compat-libstdc++-7.3-2.96.122.i386.rpm \
         compat-libstdc++-devel-7.3-2.96.122.i386.rpm


Put gcc296 and g++296 first in $PATH variable by creating the following symbolic links:

mv /usr/bin/gcc /usr/bin/gcc323
mv /usr/bin/g++ /usr/bin/g++323
ln -s /usr/bin/gcc296 /usr/bin/gcc
ln -s /usr/bin/g++296 /usr/bin/g++

Make sure the hostname command returns a fully qualified host name by amending the /etc/hosts file if necessary:

hostname
Install the 3006854 patch:

unzip p3006854_9204_LINUX.zip
cd 3006854
sh rhel3_pre_install.sh


18.  Run the installer (ORACLE 940 CD)

       $ ./runInstaller

     This will start the installation wizard

1. Ensure that we have logged in as oracle user before running the installer. To check this issue the following
   command.

    $id

 2. If the wizard fails to start saying that you don’t have permission to connect to the Xwindows.

     Start a new terminal with  root user and execute
   
     #xhost +

     And restart the installer again

    Note : The xhost + command will permit any user on network or local system to open window of his
               application on this xwindows server.


3. Follow the instructions provided by the wizard

Choose the inventory location to /u03/oracle/oraInventory (/u01/app/oracle/orainventory)
Choose unix group name as oinstall
The wizard will ask to execute a shell script as root user at /tmp/orainstRoot.sh

     Open a new terminal, and login as user root

      # su - root
      # /tmp/orainstRoot.sh

5.   Wizard will ask to run root.sh as root user

      Open a new terminal, and login as user root

      # su - root
      # /u03/oracle/root.sh
-------------------------------------------------------------------------------------------------------------------------
Tuxedo Installation


1. Log in as root.

     # su - root


2. # vi /etc/sysctl.conf

    Add the following line

     kernel.msgmni = 100

     sysctl -p (to set the value)


2. Create a directory /u02/psoft
 mkdir -p /u02/psoft
2. Create the linux user who will be the owner of WebLogic, we use psoft

    # useradd  -d /u02/psoft psoft

   Note: -d flag will create the home directory at given location instead of creating it at default
             location i.e. /home/psoft

5. Create directory to hold the BEA Tuxedo software

   # mkdir /u02/bea

6. Change the ownership of the above created directories to psoft user

   # chown psoft.psoft /u02/bea
   # chown psoft.psoft /u02/psoft

5. Log in as the Tuxedo administrator user i.e psoft.

    # su - psoft

6. Change to the tuxedo installer software directory.

 Mount the Tuxedo software.

5. Execute the shell script, install.sh to install tuxedo

    $./install.sh

6. The tuxedo install program will prompt to choose the platform to install for. Choose
   
    linux/aes21
   
7. When asked to choose the where files are to be installed, choose /u02/bea

8.  Provide the password for tlisten when asked for.

9. Follow the subsequent onscreen instructions and complete the installation.

--------------------------------------------------------------------------------------------------------------------
PeopleTools Installation

6. Login as psoft user

    # su - psoft

7. Make a folder to Install PeopleSoft Software
   mkdir -p /u02/psoft/PROD
7. Start the PeopleTools installation

    # cd /mnt/cdrom/Disk1
    # ./setup.linux
./setup.linux -is:javahome /usr/java/j2sdk1.4.2_08/bin -console

8. This will launch the installer wizard. Click Next when you see the welcome screen.

9. Follow the onscreen instructions.

Enter your license code for PeopleTools.
Choose Non-Unicode database for non multilingual installation
Select all the servers to be installed (Database Server, Application Server, Web Server, Batch server).
Specify the PS_HOME directory when asked for. (/u02/psoft/PROD)
When it prompts for the tuxedo directory, enter /u02/bea/tuxedo81

10. After the files have been installed, click Finish to complete the setup.

***Environment Hub machine name: [PSEMHUB] sudhir


--------------------------------------------------------------------------------------------------------------------
Installation of Peoplesoft Application
# su - psoft

6. Start the peopletools installation


    # cd /mnt/cdrom/hcm89/HCM89
$ ./setup.linux
./setup.linux -is:javahome /usr/java/j2sdk1.4.2_08/bin -console
     This will launch the installer wizard. Click Next when you see the welcome screen.

7. Follow the onscreen instructions

Enter your license code for PeopleSoft HRMS 8.9 Application.
Choose Non-Unicode database for non multilingual installation
Select all the servers to be installed (Only Web Server will be listed).
Specify the PS_HOME directory when asked for. (/u02/psoft/PROD)
When it prompts for the tuxedo directory, enter /u02/bea/tuxedo81
8. After the files have been installed, click Finish to complete the setup.



--------------------------------------------------------------------------------------------------------------------
Installation of Weblogic software

# su - psoft

5. Create directory to hold the BEA WebLogic software

   # mkdir /u02/weblogic

6. Change the ownership of the above created directories to psoft user

   # chown psoft.psoft /u02/weblogic

8. Change to the weblogic installer software directory.

Mount the Weblogic Software

9. Execute the shell script, install.sh to install weblogic

    $ ./install.sh -silent

10. The weblogic install program will detect the OS version and will prompt for the install location
      choose
         /u02/weblogic
11. Follow the subsequent onscreen instructions and complete the installation.

.bash_profile for --> psoft

# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
        . ~/.bashrc
fi

# User specific environment and startup programs

PATH=$PATH:$HOME/bin

export PATH
unset USERNAME

# Oracle 9i

ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/product/9.2.0.4.0; export ORACLE_HOME
ORACLE_TERM=xterm; export ORACLE_TERM
PATH=/usr/java/j2sdk1.4.2_08/bin:$ORACLE_HOME/bin:$PATH; export PATH
ORACLE_OWNER=oracle; export ORACLE_OWNER
ORACLE_SID=PROD; export ORACLE_SID
PS_HOME=/u02/bea/PROD
LD_LIBRARY_PATH=$ORACLE_HOME/lib; export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib
CLASSPATH=$CLASSPATH:$ORACLE_HOME/network/jlib; export CLASSPATH

LD_ASSUME_KERNEL=2.4.1; export LD_ASSUME_KERNEL
TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/u02/psoft/PROD/bin/sqr/ORA/lib:/u01/app/oracle/product/9.2.0.4.0/lib
PATH=$PATH:$HOME/bin
. /u02/psoft/PROD/psconfig.sh
export NLSPATH=/u02/bea/tuxedo81/locale/C
export PATH LD_LIBRARY_PATH PS_HOME
cd /u02/psoft/PROD/appserv