Tag Archives: Configure

COBOL targets failed to compile or link

Problem:

After deploying files from MP5, the COBOL programs must be compiled. However, some files do not compile:

E:tempcompile>set PS_HOME=E:PSOFTFS900
E:tempcompile>set COBROOT=E:cobolBase
E:tempcompile>cd /d E:PSOFTFS900setup
E:PSOFTFS900setup>cblbld E: tempcompile

ASCII Cobol Compilations Proceeding
Logging progress to file E:tempcompileCBLBLD.LOG
COBOL compiler found in E:cobolBase
Target directory (E:PSOFTFS900CBLBINA) exists and is writable

Copying source files …

Building the COBOL targets …
File(s) that failed to compile or link:
.
Compile error for CPPIPRDN.obj
Compile error for INPFVALD.obj
Compile error for INPGPROC.obj
Compile error for INPGREPL.obj
Compile error for INPJIURV.obj
Compile error for INPPPROC.obj
Compile error for INPTVALD.obj
Compile error for INPVPROC.obj
Compile error for INPVVALD.obj
Compile error for INPZPWFB.obj
Compile error for SFPBPCFG.obj
Compile error for SFPDCDRV.obj
Compile error for SFPDCOMP.obj
Compile error for SFPDCVAL.obj
Compile error for SFPDISUE.obj
Compile error for SFPSGBRC.obj
Compile error for SFPSUPDT.obj
Compile error for SFPSVALD.obj
The error list is in E:tempcompileERROR.LIS
.
Aborting this process !!! EXEs/GNTs/INTs are not going to be copied/replaced…
.
Please fix the errors and rerun this batch file !!!!!!!
.

Symptoms:

The problem is with COBOL compiles, where if the customer doesn’t have all the products licensed when we compile the COBOLs from recent Maintenance Packs we get errors. This is due to the fact that CA is not looking at the licensed products or dbcodes to validate licensed products. Therefore errors are displayed during the compilation as copybooks are not supplied for the non licensed products.

Here’s an example list of the COBOLs that don’t compile:
CEPCSQL2, CPPICSTI, CPPIPRDN, INPADYN3, INPADYN4, INPAPROC, INPIVALD, INPOTEST, INPSDRCT, INPVIADJ, INPVPROC, INPVVALD, INPXPROC, SFPDISUE, SFPEPROC, SFPFPROC, SFPREVAL

Here’s a copy of what’s in the dbcodes.ep:
EP PeopleSoft FIN/SCM Database
EP PeopleSoft FIN/SCM Demo Database
AM PeopleSoft Asset Management
CM PeopleSoft Cash Management
CO PeopleSoft Common Objects
TR = PeopleSoft Deal Management
EO = PeopleSoft Enterprise Components
EPO = PeopleSoft eProcurement
GL = PeopleSoft General Ledger
AP = PeopleSoft Payables
PO = PeopleSoft Purchasing

Cause:
Not Applicable

Solution:

Tools incident 714685000 was created. The incident is considered to be an enhancement for change assistant in a tools versions greater than 8.45.

If the customer does not have licenses for the modules related to the cobol files that are failing, they can ignore the compile errors. If they do not want to ignore the error messages, they can remove the erroring files from the src directory (move them to another directory) and run compile again.

Reference:

E-CA Change assistant not checking the license before compiling the cobols (Doc ID 623178.1)

Compiling COBOL Programs Using cblmake

set PS_HOME=E:PSOFTFS900
set COBROOT=”C:Program FilesMicro FocusNet Express 5.0Base”
E:PSOFTFS900srccblwin32cblmake FSP*
E:PSOFTFS900srccblwin32cblmake GLP*

Note that the above commands assume that the current working directory is the directory with the COBOL programs. It may be a good idea to run the cblmake, after running cblbld and the current working directory is that with the output of the cblbld programs (e.g. E:tempcompile_20081223b).

Distribution Status stays at Posting

Problem:

When processes submitted, status remains at “Posting”.

Solution:

Navigate to PeopleTools > Process Scheduler > Report Nodes

Create a new Node Name e.g. FSDMO1.
Under Distribution Node Details, set the URL: http://GLWebApp:8000/psreports/fsdmo
Set Description: FSDMO Reporting Node
Set Operating System: NT/Win2000
Under Connection Information, set Network Path: \glwebappe$psreports

Navigate to PeopleTools > Process Scheduler > Servers

Click Search, and then click PSNT.
Click the Distribution tab.
Under Server Distribution Details, in Distribution Node Name, enter FSDMO1.

Insufficient privileges for cloning

Problem:

When trying to log on to the newly cloned TEST instance as sysadmin user, the following error appears:

You have insufficient privileges for the current operation. Please contact your System Administrator.

Solution:

Used URL:

http://ebusinesstest.support.com:8001/OA_HTML/jsp/fnd/aoljtest.jsp

to compare differences between TEST and PROD. Noticed that JSP Ping not working on both.

In Metalink, searched for error:

java.lang.StringIndexOutOfBoundsException: String index out of range: -1

Checked document: Subject:  Troubleshooting Login (Doc ID:  Note:178437.1), “3. Login: java.lang.StringIndexOutOfBoundsException when log into jtflogin.jsp”

In SQL*Plus, executed the following code:

select SESSION_COOKIE_DOMAIN from icx_parameters;

update icx.icx_parameters set SESSION_COOKIE_DOMAIN = ‘.support.com’;

commit;

select SESSION_COOKIE_DOMAIN from icx_parameters;

Tested logon on ebusinesstest, working now.

Reference:

Subject:  Configuring and Troubleshooting the Self Service Framework 5.5.2 with 11i (Doc ID:  Note:177095.1)

Important 11i Files, Directories, Locations

This documentation lists important files, directories and locations.

Output for adadmin and adpatch:

$APPL_TOP/admin/<SID>/log

Output for concurrent requests:

$COMMON_TOP/admin/log/<CONTEXT_NAME>

$COMMON_TOP/admin/out/<CONTEXT_NAME>

Output files from installation:

Database logfile:

$ORACLE_HOME/appsutil/log/<CONTEXT_NAME>

e.g. C:oraclevisdb9.2.0appsutillogVIS_eam 11060210.log

Appltop logfile:

$APPL_TOP/admin/<CONTEXT_NAME>/log

e.g. C:oraclevisappladminVIS_eamlog11060210.log

Output files from running AutoConfig:

Database logfile:

<RDBMS ORACLE_HOME>/appsutil/log/<CONTEXT_NAME> /<MMDDhhmm>/adconfig.log

e.g. C:oraclevisdb9.2.0appsutillogVIS_eam 11160751adconfig.log

Appltop logfile:

<APPL_TOP>/admin/<CONTEXT_NAME>/log/<MMDDhhmm>

e.g. C:oraclevisappladminVIS_eamlog11060210.log

Output files from running TUMS:

$COMMON_TOP/temp

Database context file:

<RDBMS ORACLE_HOME>/appsutil/<CONTEXT_NAME>.xml

e.g. C:oraclevasudb9.2.0appsutilVASU_localhost.xml

Application context file:

$APPL_TOP/admin/<CONTEXT_NAME>.xml

e.g. C:oraclevasuappladminVASU_localhost.xml

Concurrent manager log file:

$APPLCSF/$APPLLOG/SID_MMDD.mgr

JInitiator files:

$APPL_TOP/admin/appltop.cer

$APPL_TOP/admin/adsign.txt

$APPL_TOP/admin/adcert.txt

$HOME/identitydb.obj (/home/applmgr)

Launch Forms Logon:

http://<server>:<port>/dev60cgi/f60cgi

Launch Self Service Personal Home Page Mode (“Personal Home Page”):

http://<server>:<port>/OA_HTML/US/ICXINDEX.htm

Launch Self Service Personal Home Page Mode (“Framework only”):

http://<server>:<port>/oa_servlets/AppsLogin

Test your Webserver setup for Self Service Framework Applications:

http://ebusinesstest.support.com:8001/OA_HTML/jsp/fnd/aoljtest.jsp

Unable to mount NFS share

Problem:

When mount -t nfs ebusinesstest:/u0/oracle/testdata /mnt/testdata/ executed, the following error is returned:

mount: mount to NFS server ‘ebusinesstest’ failed: RPC Error: Program not registered.

Solution:

Run:

service nfs restart

on source and target machines.

Configuring VNC to Use Gnome

Problem: On CentOS 4.8, logging into VNC session on server for first time does not show Gnome session.

Solution: Edit the VNC xstartup file.

Edit the ~/.vnc/startup and replace the line

# xterm -geometry 80×24+10+10 -ls -title “$VNCDESKTOP Desktop” &

twm &

with

gnome-session &

When vncserver is first run, the xstartup file should be similar to the following:

[oracle@localhost ~]$ cat .vnc/xstartup
#!/bin/sh

# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &

After replacing the last line, the xstartup file should now appear as follows:

[oracle@localhost ~]$ cat .vnc/xstartup
#!/bin/sh

# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
gnome-session &

After running vncserver, if the GNOME desktop GUI does not load when you connect with the VNC viewer, then try replacing the contents of xstartup with the following:

#!/bin/sh
# Add the following line to ensure you always have an xterm available.
( while true ; do xterm ; done ) &
# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc
[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
gnome-session &

Note that you need to kill the vncserver session and restart it for the changes to take effect. For example, to kill the vncserver session 1, issue the following command:

vncserver -kill :1

Then rerun ‘vncserver’ to restart the VNC server session and reconnect with the VNC viewer.

Reference:

http://wiki.centos.org/HowTos/VNC-Server