1

COBOL in PeopleSoft

By: Kunwar Singh
Date Created May 2009















PeopleSoft White Paper
2

Table of Contents
TABLE OF CONTENTS 3
CHAPTER 1 - PAPER INTRODUCTION 4
Structure of this Paper 4
Related Materials 4
CHAPTER 2 - OVERVIEW 5
CHAPTER 3 - PEOPLESOFT COBOL COMPILERS 7
How to check supported version of compiler 8
How can we get a Cobol Compiler 8
How to get Permanent SERIAL NUMBER and LICENSE KEY for ServerExpress 8
CHAPTER 4 - PEOPLESOFT COBOL: NAMING CONVENTION, TYPES OF FILES AND DIRECTORIES 9
CHAPTER 5 - INSTALLATION OF NETEXPRESS 13
Installation Steps 13
Permanent License Code Process 22
How to check if License of NetExpress has expired 27
How to check version of NetExpress 28
REVOKE KEY 29

CHAPTER 6 - HOW TO COMPILE COBOL WITH NETEXPRESS COBOL COMPILER 30
Compiling COBOL with CBLBLD.BAT 30
Environment Variable 30

CHAPTER 7 - HOW TO TEST COBOL CONFIGURATION 35
How to run Test COBOL 36
RemoteCall Test 37



3
CHAPTER 8 - HOW TO TRACE COBOL 38
Steps 38

CHAPTER 9 - SERVEREXPRESS COBOL COMPILER 45
How to Compile and Link COBOLs on UNIX 45
Setting Environment Variables 46

CHAPTER 10 - MISCELLANEOUS INFORMATION 48
How to Check which Modules you are Licensed and Using 48
How to Know version of ServerExpress Compiler Installed 50
How to find the License Manager Directory 51
Can we install two different version of ServerExpress on one machine 52

APPENDIX A TROUBLESHOOTING TIPS 53
General error Messages 53

APPENDIX B - GSC COBOL DOCUMENTS (SOLUTIONS) 55














4
Chapter 1 Introduction
This Paper is an introductory and practical guide for technical COBOL users, beginners. This Paper discusses the
COBOL in PeopleSoft applications, PeopleSoft COBOL Configuration & Troubleshooting Tips.


Much of the information contained in this document originated within the PeopleSoft Global Support Center and is
therefore based on "real-life" problems encountered in the field. The issues that appear in this document are the
problems that prove to be the most common or troublesome.
STRUCTURE OF THIS PAPER
This Paper provides guidance in properly understanding of COBOL and its use in PeopleSoft Applications. It covers
basic understanding of COBOL compilers and issues related to installation of compilers. It also covers FAQ of
COBOL in PeopleSoft. It is recommended that you also review the information related to COBOL in PeopleTools
installation guide for your PeopleTools release.

Keep in mind that PeopleSoft updates this document as needed so that it reflects the most current feedback we
receive from the field. Therefore, the structure, headings, content, and length of this document is likely to vary with
each posted version. To see if the document has been updated since you last downloaded it, compare the date of
your version to the date of the version posted on MetaLink.
RELATED MATERIALS
To take full advantage of the information covered in this document, we recommend that you have a basic
understanding of system administration and PeopleSoft Applications.

We recommend that you should also read the COBOL related information in the PeopleTools Installation Guide of
your PeopleTools version.

5

Chapter 2 - Overview
Common Business Oriented Language (COBOL) A programming language for simple computations on large
amount of data. It is portable to multiple platforms and support for complex program structures. As COBOL is
suited to batch processing, some PeopleSoft applications uses routines written in Micro Focus COBOL.

PeopleSoft applications use COBOL for the purpose of building and executing SQL with additional logic structures.


If PeopleSoft application uses COBOL routines then we require a COBOL compiler and if application does
not use COBOL routines then we do not require a COBOL compiler.

Some products within PeopleSoft Human Resources Management (HRMS), Financial Management Solutions, and
Supply Chain Management use Micro Focus COBOL routines. PeopleSoft Customer Relationship Management
(CRM), Enterprise Performance Management, and Portal solutions do not use Micro Focus COBOL routines.

If you are licensed and using any of such modules in peoplesoft products, which use Micro Focus COBOL routines,
then you must have to have Micro Focus COBOL compiler in order to initially compile the code, and to re-compile
the code if any fixes are necessary.

Hence, if you are using a module, which has COBOL routines, you will require a COBOL compiler.

There is a complete list of PeopleSoft products that contain routines written in COBOL available in our COBOL and
Module Chart available on Metalink. In the COBOL spreadsheet, you can find a listing of PeopleSoft Enterprise
products and an indication of whether COBOL is required for that product.


The criteria for determining whether COBOL is required for your product is based on the following:

1. COBOL code is in the product that is delivered on the CD; or,
2. There is a required dependency with another product that has COBOL delivered under their product on the CD. A
"required dependency" means that a customer has to have this other product along with their product.

Examples include:

General Ledger has COBOL that is delivered on the CD, so the COBOL requirement is "yes".
Resource Management has No COBOL they deliver (and no required dependency on a product that has COBOL)
so the requirement is "no".
Supply Planning has no COBOL they deliver, but they have a required dependency on Inventory (who does deliver
COBOL), so the requirement is "yes".


So if our application has COBOL routines, then we have to compile all the cobols with PeopleSoft certify Cobol
compiler after the installation of PeopleTools and Application. We can run COBOL processes only after successful
compilation of all the Cobol source files. We cannot use any other COBOL compiler from any vendor because
PeopleSoft routines in COBOL are specifically written for the Micro Focus Complier syntax. They will not work
correctly with other COBOL compliers.





6
So obviously your first question might be

What are peoplesoft certify Cobol compilers and how can we check it?
How can we get a COBOL compiler?





























7
Chapter 3 - PeopleSoft COBOL Compilers

This chapter will provide you understanding of COBOL Compilers for PeopleSoft.

In Peoplesoft COBOL compilers of Microfocus and IBM can only be used:

For UNIX MicroFocus Server Express COBOL compiler
For Windows -- MicroFocus Net Express COBOL compiler

Note: We cannot use any other COBOL compiler of any other vendor.


Below are IBM Cobol compilers which can be used in PeopleSoft.
IBM COBOL for AIX
IBM COBOL for Windows
IBM Enterprise COBOL for z/OS




8
HOW TO CHECK SUPPORTED VERSION OF COMPILER
Login to My Oracle Support ( MOS) and click Certification.
Please refer below knowledge Doc for details:
PeopleSoft PeopleTools Certifications (Doc ID 747587.1)

It is always recommended to compile All the COBOL programs by supported version of COBOL compiler after:
1) PeopleTools Upgrade
2) Database Upgrade
3) Operating System Upgrade
4) Applying any patch and fixes
5) Applying Tax Updates
HOW CAN WE GET A COBOL COMPILER
You can download COBOL compiler from Oracle E-Delivery (http://edelivery.oracle.com).
OR
You may also contact our local customer care.
List of Customer Care contacts at:
URL:
http://www.oracle.com/support/contact.html
>>>
On Oracle E-Delivery (http://edelivery.oracle.com), we have a PDF document COBOL Quick Installation Guide,
refer it for more details.
A single user license is provided in this PDF document COBOL Quick Installation Guide for those customers
wishing to immediately install and use the software. The software should ultimately be installed using the permanent
license code.
HOW TO GET PERMANENT SERIAL NUMBER AND LICENSE KEY FOR
SERVEREXPRESS
A COBOL Serial Number and License Key for your 'licensed number of users' are required to install Server Express.
You can obtain these by emailing your company name, customer number, and CSI (Customer Support Identifier)
number to Oracle E-Delivery Customer Service at:
licensecodes_ww@oracle.com
If you do not know your CSI number, please contact your Oracle Sales Representative.
9
Chapter 4 - PeopleSoft COBOL: Naming Convention, Types of
Files and Directories
This chapter will provide you understanding of naming convention of COBOL, different types of files and directories.

COBOL programs have eight-character names.
The files that have a "P" in the 3rd position are COBOL source files. The file type is . cbl and resides in
\base directory
The files that have a "C" in the 3rd position are COBOL copybooks. The file type is .cbl and resides in
\base directory

The module name for a program is aaPnxxxx, where
aa identifies the application:
AP = Accounts Payable
AR = Accounts Receivable
GL = General Ledger
IN = Inventory
PS = Payroll
PT = PeopleTools

P stands for Program,
nxxxx identifies the specific module within application.
n identifies a sub-system within the application, e.g. A for Allocations, P for Posting.
(Payroll was not developed with this convention, and there are no plans to rename Payroll modules.)

Here is a quick sheet for the modules, by two letter prefix, and a short description what they are used for:

AD - Student Admin - Admissions
AV - Student Admin
BP - Benefits
CC - Student Admin - Contact Information
EG - Education and Government - Public Sector
FA - Student Admin - Financials
FE - Student Admin - ISIR
10
FG - Federal Government
FM - Student Admin - Federal Methodology
FU - Student Admin - INAS Functions
GL - Student Admin - Global Files
GP - Global Payroll
IM - Student Admin - IM Formulas
IN - Student Admin - Interim Need Analysis
PA - Pension Admin
PI - Payroll Interface
PL - Student Admin - Plus Work Area
PR - Student Admin - CSS Data
PS - North American Payroll
PT - PeopleTools
SF - Student Admin - Financials
SR - Student Admin - Student Records
TA - Student Admin - Tax Parameters

Similarly, COPY modules are named aaCnxxxx.
COBOL source file name must be unique because the extension is dropped on some target systems.
In COBOL Naming Convention, only initial three letters are important. Rest five depends upon the function of that
program used for.
For example,
Cobol program SFPREVAL,

SF -- indicated a manufacturing module Cobol (MFG includes CE, CM, CP, DP, EN, FI, FP, IN, PE, PO and SF)
P -- Program
REVAL -- short of its description 'Revalue Inventory and WIP'





11
Note: There is no such master index or list for each Cobol job available. However, you can get some information
related to COBOL program in below two ways:
1 - GO TO PS_HOME /SRC/CBL/BASE
Search for that particular COBOL cbl file
Open and read initial lines.
2 - LOGIN PIA -- PEOPLETOOLS-- PROCESS SCHEDULER -- PROCESS
Search with process name
Open and in Process Definition, read Description, and Long Description, which have some information, related to
that COBOL process.

Please refer screen shot below.



12



















13
Chapter 5 - Installation of NetExpress 4.0/5.0
In this chapter we will discusses how to install NetExpress COBOL compiler and how to get Full License.
Information which is referred for Netexpress 4.0 is also applicable for NetExpress 5.0

Net Express 4.0/5.0 has two major components, a COBOL Compiler and a COBOL Runtime.

Please install and license either the Net Express 4.0/5.0 COBOL compiler or the Net Express 4.0/5.0
Runtime, on a system, BUT NOT BOTH!!!

How to Decide What to Install, the Compiler or the Runtime?

A. For Compiling or Compiling and Running Cobol Programs Install the Compiler

If you need to compile or compile and run COBOL Programs, install and license the Net Express 4.0/5.0
Compiler.

The Net Express 4.0/5.0 Compiler installation includes the Runtime, so it is not necessary to install the
Runtime if you install the Compiler.

B. For Running Cobol Programs Install the Runtime

If you need to run COBOL Programs but DONT need to compile, just install and license the Net
Express 4.0/5.0 Runtime.

Note: For Netexpress Runtime, there is a patch known as runtime license patch for Netexpress (MFLicense.EXE ) .
You can get this runtime license patch only by emailing to
licensecodes_ww@oracle.com
with your company name, customer number, CSI (Customer Support Identifier) number.

INSTALLATION STEPS:

1. Run the Setup from F:\Microfocus1 then navigates to the install link.

2. Click the Click here to install or upgrade Net Express 4.0

14


3. Accepted Defaults.


If you are unable to start installation by above way and receive Invalid Initialization error, follow below:

1. Type "cd \setup" to make the Net Express \setup folder your current directory and press ENTER.
2. Type "setup.exe /ini=.\nxsetup.ini /no_subsystem" and press ENTER.

This will start the setup.exe program that is in the Setup subdirectory and tell it which initialization file to use during
setup. In this case it is using the nxsetup.ini file within the Setup subdirectory and specifies the /no_subsystem
option.


15





setup.exe /ini=.\nxsetup.ini /no_subsystem












16






17










18





No Serial Number and W.O Number required
19


















20







21


STEP 1 - CLICK RUN
Run
License Information
22



The software will work for up to 30 days. In order to get full license, you have to request Permanent License Code.
PERMANENT LICENSE CODE PROCESS
A Request Key is generated during the installation of MicroFocus NetExpress by encrypting unique hardware
identifiers. Access is granted when a Response Key is entered that matches the Request Key. You can obtain the
Response Key by emailing your company name, customer number, CSI (Customer Support Identifier) number, and
the Request Key ( check as in above screen shot) to Oracle E-Delivery Customer Service at:
licensecodes_ww@oracle.com

If you do not know your CSI number, please contact your Oracle Sales Representative. If you do not request
response key by following above process, your netexpress license will expire in 30 days.




23
Now, To determine what your Request Key is, and to enter your Response Key when you get it, click the Licensing
button in the Protection System dialog box when you start NetExpress, or go to Start --> Programs --> MicroFocus
NetExpressX.X -> Configuration -> License Management System. Click on the Generate Full License key to obtain
your request key as well as to enter the response key.




24



Send request key to licensecodes_ww@oracle.com by emailing your company name, customer number, CSI
(Customer Support Identifier) number.











Once you receive response key, put it and after putting response keys, we will see like below:
25





Click on licensing:
26
















27
HOW TO CHECK IF LICENSE OF NETEXPRESS HAS EXPIRED

Go to the directory where you have NetExpress installed.
e.g.,
C:\Program Files\MicroFocus\NetExpress\Base\BIN
and launch MFNETX.EXE



If you get message Your Net Express license has expired. as in above screen shot, means your license has
expired.







28
HOW TO CHECK VERSION OF NETEXPRESS


Start--> Program-->NetExpress-->




Click on help about NetExpress









29
REVOKE KEY
For Upgrade/Reinstallation, the revoke key needs to be generated after uninstalled from previous version. If you
need to move NetExpress to a different machine , then in order to install NetExpress you have to revoke license by
generating revoke key from the current machine.
It is recommended that once the response key is applied, click on the full license and generate a revoke key and
keep it safe because once the system crash, there is no way to generate the revoke key.
You need to generate the Revoke Key from Old COBOL compiler and generate the Request Key from new COBOL
compiler and send it licensecodes_ww@oracle.com to get the response key for the new COBOL compiler.
























30
Chapter 6 - How to Compile COBOL with NetExpress COBOL
compiler
This Chapter includes all information related to COBOL compilation of Windows with NetExpress COBOL compiler.

COMPILING COBOL WITH CBLBLD.BAT

To compile COBOL with CBLBLD.BAT:

1. Set up two environment variables, PS_HOME and COBROOT, on the machine from which you'll compile
COBOL. (This should be either your file server or a machine that has access to your file server.) You can do
this from a DOS command prompt window.
ENVIRONMENT VARIABLE

PS_HOME PeopleSoft home directorythat is, the drive letter and high-level PeopleSoft directory where you
installed PeopleTools and the application.
COBROOT Drive letter and root directory of the COBOL compiler.
For example, you could enter the following at the DOS command prompt:

set PS_HOME=C:\hr840
set COBROOT=c:\netexpress\base

2. Open a DOS command prompt window if you do not have one open already, and change directories to
<PS_HOME>\Setup.

3. Execute CBLBLD.BAT as follows
cblbld <compile drive> <compile directory>
where <compile drive> is the drive where the compile takes place, <compile directory> is the temp
directory where the compile takes place

31
The CBLBLD.BAT file will create the compile directory for you if it does not already exist.

Note. Make sure to include a space between the <compile drive> and <compile directory> parameters; they are
treated as two different parameters within the CBLBLD.BAT batch program. Also ensure that you have write
permission to <compile drive> and <compile directory> as the compile process will take place there.

For example, the following command will take the COBOL source from <PS_HOME>\src\cbl and do the compile
process under c:\temp\compile:
cblbld c: \temp\compile
Make note of the information that is displayed on the screen while the process is running; it provides the locations of
important files that you will need to examine.



32









33







When compiled, the resulting optimized COBOL executables are written to the \cblbin directory as .gnt or .int files
depends upon our choice.

.gnt = .gnt are binary code, thus they execute very quickly but take longer time to compile. Generally, we are more
concerned with modules executing quickly rather than compiling quickly, because we compile once, but we run
more.
.int = this is very quick to compile, but very slow to run.
34
These COBOL copybook files are not compiled themselves. (And since no .gnt executable modules are created for
them, we never see any of these file names in the cblbin directory.)
When we compile COBOL programs and if they fail, we check error.lis file and <COBOL program name>.lis file.
Error.lis file has name of all the COBOL programs those fail to compile while corresponding .lis file of COBOL
program has actual error message.

3 files of a COBOL process, for example:

SFPGRPCL.cbl - the COBOL program itself
SFPGRPCL.dms - Contains the script for loading the stored statements into a PeopleSoft table
SFPGRPCL.gnt or SFPGRPCL.int - This is the actual compiled COBOL program
.cbl gets compiled into .gnt
.dms is run via Data Mover to store SQL statements into table PS_SQLSTMT_TBL
. gnt is executed and call SQL statements from PS_SQLSTMT_TBL



















35
Chapter 7 - How to test COBOL configuration
In this chapter we will check our Cobol setup to run COBOL Processes.
After you have successfully compiled your source code, all executables should be in your <PS_HOME>\CBLBINX
directory (this directory will be named CBLBINA, CBLBINU, or CBLBINE, depending on whether you are using
ANSI, Unicode or EBCDIC).
Make sure that all of the .gnt or .int files are available correctly in this directory.

Now follow below steps to run COBOL test process to ensure that setup is fine.

1. Test COBOLs are running successfully by Process Scheduler
2. Remote call test is successful.





















36
HOW TO RUN TEST COBOL

Step 1 - Process Scheduler -- System Process Request














Step 2













37

RemoteCall Test
Step: PeopleTools 8.4x, =>Go, PeopleTools, Utilities,> Debug > People Tools Test Utilities


















If above both test are successful then your COBOL setup is fine to run COBOL processes.










38
Chapter 8 - How to Trace COBOL
This chapter will provide you all information and steps to get a COBOL process Trace.

STEPS

Step 1 - Sign in the PIA.

Step 2 - Navigate to the Process Types component and select the Process Type as COBOL SQL and the
Appropriate Operating System and Database Type.

Operating System: should be the Process Scheduler Server where the Process is being run (lets use NT as an
example).

Database Type: should be the type of database where the process is run (lets use Microsoft as an example).

People Tools>> Process Scheduler >> Process Types
39

40
Step 3 - Copy the data from the Parameter List field.



Here is an example:

%%DBTYPE%%/%%DBNAME%%/%%OPRID%%/%%OPRPSWD%%/%%RUNCNTLID%%/%%INSTANCE%%//
%%DBFLAG%%


Step 4 - Navigate to the Processes component and select the COBOL process that you would like to get a trace
on.

41


42
Step 5 - Go to the Override Options tab. Set the Parameter List option to Override and paste in the text field the
data you copied at step 3. Add then the sum of all the Trace Options you want to use in between INSTANCE and
DBFLAG as shown below and save.

%%/%%INSTANCE%%/3/%%DBFLAG%%



Here is the list of Trace Options and associated numbers for each option:

; 1 = SQL Statements
; 2 = SQL statement variables
; 4 = SQL connect, disconnect, commit and rollback
; 8 = Row Fetch (indicates that it occurred, not data)
; 16 = All other API calls except SSBs
; 32 = Set Select Buffers (identifies that attributes of columns to be selected.
; 64 = Database API specific calls
;128 = COBOL statement timings
;256 = Sybase Bind information
;512 = Sybase Fetch information

To turn traces on, sum all the options you want to use and enter the results in between INSTANCE and DBFLAG as
shown above. For example, to enable tracing SQL statements (1), SQL statement variables (2) SQL connect,
disconnect, commit and rollback (4), Row Fetch (8), and COBOL statement timings (128) you should use 255
(1+2+4+8+16+32+64+128).
43
Step 6 - Go ahead and run the COBOL process that you would like to get a trace on. Make sure to run the
process on the Operating System you chose at step 2 (NT in the example).






Note down the Process Instance (252 in our example).





44
Step 7 - Get the trace file.

Location:
%%PS_HOME%%\appserv\prcs\<database_name>\log_output\CBL_<process_name>_<process_instance>
Example:
\\Gsamas06\E\mss\e841g70n\appserv\prcs\e802f72a\log_output\CBL_INPSSTGE_544

File name: cobsql_<process_instance>.trc
Example: cobsql_252.trc






















45
Chapter 9 - ServerExpress COBOL Compiler
In this chapter we will cover useful information related to ServerExpress COBOL Compiler for UNIX.
There are 2 types License databases for ServerExpress COBOL Compiler

1. Development license database.
2. Runtime License Database.

Development license database: This license database is used when compiling the cobols. The license manager
should be running to compile any COBOL program. This is installed when we install the product ServerExpress
Development. The license database files are mflmfdb, mflmfdb.idx, mflmfdbX, and mflmfdbX.idx.

Runtime license database: While installing development license database, this get install under /var/mfaslmf
directory.


HOW TO COMPILE AND LINK COBOLS ON UNIX
First make sure the basic is set properly.
On Digital Unix and Sun Solaris, the variable to check is LD_LIBRARY_PATH.
On HPUX, the variable is SHLIB_PATH.
On AIX, the variable is LIBPATH.
A typical LD_LIBRARY_PATH, SHLIB_PATH, or LIBPATH might be:

LD_LIBRARY_PATH=/usr/lib/cobol/coblib:/usr/sybase/lib
This can be set in the .profile or the psconfig.sh file in the $PS_HOME directory.
1) COBDIR <== Should point to where the compiler is installed
2) PATH <== Should have your $COBDIR/bin (which cob will tell you which one it is executing)
3) LD_LIBRARY_PATH, LIBPATH, SHLIB_PATH <== Should have $COBDIR/lib (depending on flavour of unix)



Then at the prompt if you type ' cob , you should get a message to the effect saying I see no work.
46
Please follow the 'Compiling COBOL on UNIX' in PeopleTools installation guide to check the environment variables.

MicroFocus advises "unset COBPATH" when compiling, leaving
$COBPATH set when executing is okay!

To test a compile, set your env minus $COBPATH and create a temp directory:
# cp -p $ COBDIR/demo/debug/pi.cbl /tmp/location
Change to your /tmp/location:
# cob pi.cbl
This should compile if all is well...

In Unix all you need to do to compile all the COBOL is from the $PS_HOME/install directory type:
pscbl.mak
Linking cobol
psrun.mak

Setting Environment Variables
On your UNIX system, you need to log in and ensure the following environment variables are set appropriately.
Alternatively, make sure the following environment variables are set in the .profile file in the user's home directory:

$ORACLE_HOME must point to the correct Oracle installation; for example:
ORACLE_HOME=/products/oracle/8.1.7;export ORACLE_HOME
$ORACLE_HOME/bin must be added to PATH; for example:
PATH=$PATH:$ORACLE_HOME/bin;export PATH
$ORACLE_HOME/lib must be appended to LD_LIBRARY_PATH, LIBPATH, or SHLIB_PATH,
whichever is appropriate for your platform.
$ORACLE_SID must be set to the correct Oracle instance; for example:
ORACLE_SID=hdmo;export ORACLE_SID

$COBDIRmust be set to the Server Express installation; for example:
COBDIR=/cobol/prod/svrexp-2.2.SP1;export COBDIR
$COBDIR/lib must be appended to LD_LIBRARY_PATH, LIBPATH, or SHLIB_PATH, whichever is appropriate for
your platform.
47
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$COBDIR/lib;export LD_LIBRARY_PATH
LIBPATH=$LIBPATH:$COBDIR/lib;export LIBPATH
SHLIB_PATH=$SHLIB_PATH:$COBDIR/lib;export SHLIB_PATH
$COBDIR/bin must be appended to the PATH; for example:
PATH=$PATH:$COBDIR/bin;export PATH
To set the required PeopleSoft environment variables, run psconfig.sh. Enter the following command:
cd <PS_HOME>
. ./psconfig.sh
























48
Chapter 10 - Miscellaneous Information
In this Chapter we will cover Miscellaneous Information related to COBOL in PeopleSoft.
If you are compiling Cobol after applying any Maintenance Pack or Tax update and only few cobols are giving
compile error then there is a possibility that these few failing cobols may belong to modules for which you are not
licensed and using. In such scenario you can ignore these error.
HOW TO CHECK WHICH MODULES YOU ARE LICENSED AND USING

Steps: 1 Log in PIA SetUp HRMS Installation Table













Step 2: Check dbcodes file in PS_HOME/setup directory









49
Step 2
Check dbcodes.hc in PS_HOME/setup

















50
HOW TO KNOW VERSION OF SERVEREXPRESS COMPILER INSTALLED
Check the output of three commands (login as root):

$PS_HOME/bin> cobrun
$PS_HOME/bin> cob -v <---(small "v")
$PS_HOME/bin> cob -V <---(upper "V")









If Output of $ cob -V

version @(#)cob.c 1.310
PRN=RXCPR/AAM:9h.N3.40.03
PTI=SP1
PTI=Fixpack40.03_10
I see no work

Then compiler is Server Express 4.0 SP1 FixPack 10

Similarly below is the output of $ cob V for ServerExpress 4.0 SP2
version @(#)cob.c 1.313
PRN=RXCTO/AAD:9i.T4.40.03
PTI=SP2
I see no work

51
To check whether ServrExpress compiler is installed in 32 bit or 64 bit mode , check the output of

$ cob -v
and it should be like below for 32 bit mode.

cob32 -C nolist -v
I see no work

And for 64 bit , it will be like

Cob64 -C nolist -v
I see no work


HOW TO FIND THE LICENSE MANAGER DIRECTORY
1. Change to $COBDIR/lmf
2. Run the command ./lmfgetpv
License Manager version 121
Loaded from /products/mf/svrexp-1.1/mflmf

HOW TO START AND STOP THE LICENSE MANAGER

1) Must be logged in as root

2) Check status & stop
cd $COBDIR/lmf
lmfgetpv << Shows Status
lmfgetpv k << Stops LMF

52
3) To start
cd /usr/lib/mflmf ( on AIX it would be /opt/lib/mflmf on other OS's )
sh ./mflmman

>>>>>>>
Verify the status that the License Manager is running
./lmfgetpv If it is running this command will return the version number of the running License Manager & the
path from where it was loaded.

Starting the License Manger
./mflmman [FORCE | WAIT] [TRACE]
Force = The License Manager does not by default start up if there are still licensed tasks running that were
started from a previous run. When this happens, you can use FORCE to force the License Manager to first
terminate the previously started tasks & then to start.
Wait = This suspends the License Manager until any outstanding licensed tasks from a previous License
Manager have finished. Use this when you do no want the existing licensed tasks to be terminated prematurely,
and want to wait until they have finished naturally.
Trace = Creates a log of the License Manager activity in MF-LMF.log
Stopping the License Manager
./lmfgetpv k This will stop the License Manager



CAN WE INSTALL TWO DIFFERENT VERSION OF SERVEREXPRESS ON ONE
MACHINE

Two versions of COBOL compilers can be installed on the same machine as long as they run under different
directories. You can install on same machine but under different directories. The license database for both of them
should be served by only one license manager. The license manager version should be the version that came with
the latest compiler.

You will just need to install the compiler on a different location & if the compiler is bought from peoplesoft, skip the
license management facility. They must be installed in separate $COBDIRs but one license daemon
(mflm_manager) will serve both products.

53
Appendix A Troubleshooting Tips

In this section we will go through some issues and approach to troubleshoot.

GENERAL ERROR MESSAGES

A : Issues of License Manager


1. Micro Focus LMF - 002: The license database is corrupt.


The License Manager detected corruption in the license database. The license database may have been tampered
with. Therefore, the License Management Facility terminated execution of the licensed product.
Follow the Instructions of Doc ID 611140.1


2. Micro Focus LMF - 005: You have exceeded the license limit for this product.

You will be getting this error message when multiple users are trying to compile the COBOL programs at the same
time. Make sure you have enough licenses to cater all the users to compile or contact customer care to buy extra
licenses.


3. Micro Focus LMF - 006: You are not licensed to use this product or version.

If you have got the COBOL compiler from peoplesoft.
a. You may have installed the COBOL compiler in 64-bit mode. To change the COBOL compiler mode use the
following command
cobmode s 32
b. Check license licenses through License Administration Services.



4. Micro Focus LMF - 008: Maximum license database size exceeded.

The license database has too many licenses to be loaded by the License Manager. Therefore, the License
Management Facility terminated execution of the licensed product. So uninstall the licenses that are not required
through License Administration Services



5. Micro Focus LMF - 010: Unable to contact License Manager.

This product has been unable to contact the License Manager.
Therefore, the License Management Facility terminated execution of the licensed product. Check the license
manager is running.



54
B : How to stop "The license database is corrupt" error.
Analysis:
When you try to start LMF the error message "The license database is corrupt" is issued. There may have been a
system crash and reboot. You may also see this error when you try to start License Administration Services.
Solution: The simplest solution to this problem is to rebuild the LMF database files.

1. Make sure that no LMF functions are running.
a. Signed on as root, cd to the correct mflmf directory. (Where LMF was installed. The default is /usr/lib/mflmf or
/opt/lib/mflmf.
b. Issue the command ./lmfgetpv. If license manager is running, issue ./lmfgetpv -k to kill it. Then issue ps -aef |
grep mflm and kill any other license processes that might not be registered.

2. Delete all four of the license data bases > rm mflmfdb*
3. Start License Administration services with >sh ../mflmadm and reinstall the serial number and license keys from
the License Key Folder as described in the Micro Focus License Management Administrator's Guide.
Note: DO NOT enter any spaces into the license key even if there are spaces shown on the folder.
Exit to the UNIX command prompt.

4. Start license manager with >sh ./mflmman.
Summary:
Once the license management databases become corrupt, the quickest and simplest way to recover is to rebuild the
database files.






















55
Appendix B GSC COBOL Documents (Solutions)
Below is a list of some important documents ( solutions) on Metalink.
This is not a complete list and this document will be updated periodically with corrected information.

Summary

Information Center: Overview of Peoplesoft PeopleTools COBOL [Document 1476983.2]

E-COB: Net Express Cobol compiler - How to resolve the "license is not setup correctly" error (Doc ID 753692.1)
E-COB: Files\Micro was unexpected at this time error when compiling cobol (Doc ID 618022.1)
E-COB: Unable to compile any COBOL Programs using the NetExpress compiler (Doc ID 610711.1)
E-COB: Net Express cobol compiler install fails with error "Error 1721. There is a problem with the Windows
Installer package. A program required for this install to complete could not be found." (Doc ID 780015.1)
E-COB: Net Express 4.0 install- Failed to set Integrated Development Environment (Doc ID 654788.1)
E-COB : Error installing NetExpress 4.0 runtime license patch (ULP) (Doc ID 655099.1)
E-COB: Net Express compiler error "Your Net Express license has been corrupted" (Doc ID 664394.1)
E-COB: The License database for the Net Express application server has been moved from its original location or
removed and recreated.Delete the database,which is mfasdb,and reinstall the license keys (Doc ID 778962.1)
E-COB: Net Express 3.1 SP1 Semaphore failure. ASLM : Errno 1000 and Errno 1002 (Doc ID 618345.1)

E-COB: Invalid Product Error when applying server express 4 SP2 cobol compiler fix pack 77 (SX40SP2-RedHat-
32bit-Fixpack40
E-COB: Cobol processes fail with error No Application Server License Available: 5 system and 0 user license
installed 5 in use (Doc ID 794766.1)
E-COB: Installing COBOL compiler license "This is a Development System license! (Doc ID 660056.1)
E-COB: COBOL Programs Error : No Application Server License available on Unix (Doc ID 611140.1)
E-COB: Linking cobol psrun.mak error -> cob64: can not execute as (Doc ID 662354.1)
E-COB: Linking cobol psrun.mak gives error "ld: cannot find -lgcc" (Doc ID 660798.1)
E-COB: Disaster Recovery and cobol Server Express compiler on UNIX (Doc ID 662980.1)
E-COB: How to copy Server Express COBOL compiler from an existing UNIX machine to another/new UNIX
machine ? (Doc ID 763968.1)
E-COB: Installing multiple Server Express cobol compiler releases on one machine (Doc ID 664113.1)
E-COB : How to Trace COBOL Process flow on UNIX (Doc ID 650869.1)
E-COB: Cobol license manager. Unable to open License Key database (Doc ID 660113.1)
E-COBOL: Micro Focus LMF - 006: You are not licensed to use this product ... (Doc ID 618428.1)
E-COB: Load error : file 'psauto64.int' unsupported format when applying ULP (Doc ID 661674.1)
E-COB: PSRUN: error while loading shared libraries: libcobrts.so: cannot open shared object file: No such file or
(Doc ID 786557.1)
Documents
E-COB: Tools 8.48 - error code: 211 Program not executable by Run-Time System (Doc ID 650863.1)
E-COB: Micro Focus LMF-004: You have exceeded the license limit for this product (Doc ID 624132.1)
E-COB: Tools 8.48 -COBOL error Code: 00404 SQLRT: Unable to connect to database (Doc ID 650883.1)
E-COB: Tools 8.49.14 All COBOL programs fail PTPSQLRT-ERROR IN BIND SETUP/DATA (Doc ID 664888.1)
E-COB: Compile warning message " Ignored - LINKCOUNT "1024" " (Doc ID 782851.1)
E-COB: What is the Purpose a Revoke Key? (Doc ID 1570641.1)