Tuesday, 14 July 2020

Upgrade from Server Express to Micro Focus Visual COBOL Development Hub 4.0


Hardware Requirements


Software Requirements




Advantages of Upgrading
The products from the Visual COBOL suite help you bring existing applications up-to-date and extend them so they take advantage of the variety of new technologies that are emerging. In most cases, you can keep the existing COBOL logic intact and then extend your applications to enable support for the modern technologies.
Choosing to upgrade to Visual COBOL Development Hub offers the following advantages:
·         A basic upgrade - Visual COBOL Development Hub supercedes Server Express. There should be no changes required in your existing build scripts and not or minimal changes to your source code to ensure that the applications compile as before.
The development environment is very similar to Server Express so you can quickly get up-to-speed with developing and maintaining your applications.
·         Utilize modern technologies - Visual COBOL Development Hub enables you to compile your existing applications to Java byte code without any changes. Compiling to Java byte code helps expose your applications to any other languages and technologies that use Java byte code.




These are the steps to install this product using the Micro Focus installer:
1. Give execute permissions to the setup file: chmod +x setup_visualcobol_devhub_4.0_platform
2. Run the installer with superuser permissions: ./setup_visualcobol_devhub_4.0_platform If you don't run this as superuser you will be prompted to enter the superuser password during the installation.
The COBOL environment is installed by default into /opt/microfocus/VisualCOBOL, (COBDIR).
yum install glibc*i686*
yum install libgcc*i686*
 yum install libstdc++*i686*
yum install glibc-devel*i686*
yum install glibc-devel
yum install gcc
yum install libstdc++*i686*
It is don’t work try below one
yum install libstdc++*i686* --skip-broken
export JAVA_HOME=/oracle/jdk/default
export PATH=$JAVA_HOME/bin:$PATH
export COBDIR=/oracle/mfcobol


Run below command with root access:

./setup_visualcobol_devhub_4.0_patchupdate04_196243_redhat_x86_64 -installlocation="/oracle/mfcobol"

-=-==================================================================-=-
Micro Focus Product - Product Extractor
www.microfocus.com Please Wait.
Performing Product and Platform Checks... All Checks Passed. Extracting Payload... Creating work area...Installation requires root permissions.
Enter root password to continue.
Just press Enter to exit.Enter Root Password: -=-==================================================================-=-
Micro Focus Visual COBOL Development Hub 4.0 - Patch Update 04
www.microfocus.com Product will be installed to
[ /oracle/mfcobol ] Product : Micro Focus Visual COBOL Development Hub 4.0 - Patch Update 04
PRN : KXCRH/AAD:Ao.U4.13
ESadminID : Not given
Build ID : pkg_196243 Run installer with command line argument -ESadminID=[ User ID ] to
configure SOA support during installation. -=----------------------------------------------=- Before installing and using this software product you must
agree to be bound by the terms and conditions of the end user
license agreement ("End User License Agreement") which
accompanies this product. Please take this time to read the
License Agreement. If you are not in agreement with the terms
and conditions of the License Agreement, please contact your
Account Representative. If you require a copy of the License Agreement before installing the
product then answer no and run the installer with the command: ./setup_visualcobol_devhub_4.0_patchupdate04_196243_redhat_x86_64 -EULADo you agree to the terms of the License Agreement? (y/n): y End User License Agreement (EULA) can be found in the product directory
/oracle/mfcobol/etc/EULA_VCED_v4_0.htm The product installed at /oracle/mfcobol
has been backed up to /oracle/mfcobol.BKP.2020-01-21.12:56:09 Important Information
========================== All your files and settings are preserved at this location. Check the following files for any user configuration changes.
cob.cfg, cob64.cfg, coboops.cfg, coboops64.cfg,
coboops64_t.cfg, coboops_t.cfg, cobopt, cobopt64,
liblist, liblist64 You will need to import your Enterprise Server Regions from
/oracle/mfcobol.BKP.2020-01-21.12:56:09/etc/mfds
to /oracle/mfcobol/etc/mfds To configure SOA support in Micro Focus Visual COBOL Development Hub 4.0 - Patch Update 04 run
$COBDIR/bin/casperm.sh -=-==================================================================-=-
Micro Focus Visual COBOL Development Hub 4.0 - Patch Update 04
Installation Complete. End User License Agreement (EULA) can be found in the product directory
/oracle/mfcobol/etc/EULA_VCED_v4_0.htm -=-==================================================================-=- To use this version of :
Micro Focus Visual COBOL Development Hub 4.0 - Patch Update 04 Run "cobsetenv" to set your environment. . /oracle/mfcobol/bin/cobsetenv -=-==================================================================-=-


USER@SERVER$ cob -V
version @(#)cob.c 4.0.0.86
PRN=KXCRH/AAD:Ao.U4.13.04
PTI=32/64 bit
PTI=Micro Focus Visual COBOL Development Hub 4.0 - Patch Update 04
PTI=Patch Update 04
PTI=pkg_196243
PTI=MFInstaller
PTI=ES
PTI=SOA Configured
I see no work (see `cob -?' for help)


export PATH=$PATH:/usr/bin/cc

For License Run below:
cd $COBDIR/bin


./cesadmintool.sh

        Micro Focus License Administration
        ==================================
        [Jan 21, 2020 2:25:23 PM] v10000.2.03110

        Welcome to the Micro Focus License Administration utility.
        Please select an option from the menu below.

         1. Online Authorization.
         2. Check License Status.
         3. Advanced Configuration Options.
         4. Manual License Installation.
         5. Uninstall Licenses.
         6. Get Machine Id.
         7. Commute/Return Licenses.
         8. Get License Details.

        99. Exit

select 4



PS-CS-UNIX-Linux_0.mflic ---RUNTIME
PS-VC-UNIX-Linux_1.mflic ---FULL 

Wednesday, 4 March 2020

Getting 'libpsora_ansi64.so, not found' Error or Other Library Errors When Running /psrun.mak

Issue:

libpsbtunicode64.so, needed by /psoft/pt85706/pt/ps_home8.57.06/bin/libpscompat_ansi64.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libpspal64.so, needed by /psoft/pt85706/pt/ps_home8.57.06/bin/libpscompat_ansi64.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libpscrypto.so, needed by /psoft/pt85706/pt/ps_home8.57.06/bin/libpssqlapi_ansi.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libpsssl.so, needed by /psoft/pt85706/pt/ps_home8.57.06/bin/libpssqlapi_ansi.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libpscmncipher_ansi64.so, needed by /psoft/pt85706/pt/ps_home8.57.06/bin/libpssqlapi_ansi.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libclntsh.so.11.1, needed by /psoft/pt85706/pt/ps_home8.57.06/bin/libpsora_ansi64.so, not found


Fix: 


Make sure Oracle_client is ok or not,,,fix that and it will run
export TNS_ADMIN=/uc01/app/oracle/product/12.1.0.2.0/fullclienthome1/network/admin
export ORACLE_HOME=/uc01/app/oracle/product/12.1.0.2.0/fullclienthome1

cob64: can not execute program "cc".

Issue : cob64: can not execute program "cc".

Fix:

1) Please work with your Linux admin to install GNU Compiler Collection
2) Once installed, execute the 'which cc' command to make sure 'cc' is found in the PATH
3) Test the linking of cobol via the $PS_HOME/setup/psrun.mak script

COBOL Program PTPNTEST aborted (2,-1) FUNCLIB_UTIL.RC_TEST_PB.FieldChange PCPC:2143 Statement:26

COBOL Program PTPNTEST aborted (2,-1) FUNCLIB_UTIL.RC_TEST_PB.FieldChange PCPC:2143 Statement:26


To fix this first check your licence manager is running or not

./mflmadm  then run F7 licence manager should be running and connecting.

Still if you get the error then
Go to root user export COBDIR and run below

export COBDIR=XXXXX

Run ./psauto64

./psauto64 - Updating the Application Server License Database - STARTING

License installed ok

./psauto64 - Updating the Application Server License Database - COMPLETED

It can be verfied on Prcs and appserver 

The purge process did not run because the Oprid configured to start the Process Scheduler did not have the required permissions to run the purge process.

  Purge process - Required permissions The PeopleSoft Oprid used to start the Process Scheduler, as defined in the Scheduler's psprcs.cf...