Category Archives: TRAM - Page 6

Compiling COBOL Programs using cblbld

Posted by on December 23, 2008 No comments

In Command Prompt, run the following commands:

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

set PS_HOME=E:PSOFTFS900
set COBROOT=”C:Program FilesMicro FocusNet Express 5.0Base”
cd /d E:PSOFTFS900setup
cblbld E: tempcompile_20081223b

Problem:

After compiling, the following is displayed:

File(s) that failed to compile or link:
.
Compile error for FSPCTADJ.obj
Compile error for FSPYCLOG.obj
Compile error for GLPCEARN.obj
Compile error for GLPCIPNL.obj
Compile error for GLPCPROC.obj
Compile error for GLPOELIM.obj
Compile error for GLPPBKCD.obj
Compile error for GLPPINWK.obj
Compile error for GLPPRVRS.obj
Compile error for GLPPUNPS.obj
Compile error for PTPSQLGS.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 !!!!!!!

Solution:

Check the CBLBLD.LOG file for details:

The E:tempcompileERROR.LIS file showed:

Compile error for FSPCTADJ.obj
Compile error for FSPYCLOG.obj
Compile error for GLPCEARN.obj
Compile error for GLPCIPNL.obj
Compile error for GLPCPROC.obj
Compile error for GLPOELIM.obj
Compile error for GLPPBKCD.obj
Compile error for GLPPINWK.obj
Compile error for GLPPRVRS.obj
Compile error for GLPPUNPS.obj
Compile error for PTPSQLGS.obj

Check the list file for the above files:

FSPCTADJ.LIS
FSPYCLOG.LIS
GLPCEARN.LIS
GLPCIPNL.LIS
GLPCPROC.LIS
GLPOELIM.LIS
GLPPBKCD.LIS
GLPPINWK.LIS
GLPPRVRS.LIS
GLPPUNPS.LIS
PTPSQLGS.LIS

The above COBOL programs exceed the 2200-line limit for the free version of Micro Focus Cobol Net Express Edition, and so cannot be compiled.

Exception java.lang.NullPointerException caught in org.apache.xml.serialize.BaseMarkupSerializer.serializeNode()

Posted by on December 22, 2008 No comments

Exception java.lang.NullPointerException caught in org.apache.xml.serialize.BaseMarkupSerializer.serializeNode()

Dec 22, 2008 4:44:58 PM com.peoplesoft.pt.changeassistant WARNING: Exception java.lang.NullPointerException caught in org.apache.xml.serialize.BaseMarkupSerializer.serializeNode() java.lang.NullPointerException at org.apache.xml.serialize.BaseMarkupSerializer.serializeNode(Unknown Source) at org.apache.xml.serialize.BaseMarkupSerializer.serialize(Unknown Source) at com.peoplesoft.pt.changeassistant.XMLEncoding.fromXML(XMLEncoding.java:54) at com.peoplesoft.pt.changeassistant.XMLEncoding.fromXML(XMLEncoding.java:40) at com.peoplesoft.pt.changeassistant.Job.fromXML(Job.java:1373) at com.peoplesoft.pt.changeassistant.step.steps.DeployFile.onExecuteDeployFiles(DeployFile.java:98) at com.peoplesoft.pt.changeassistant.Job$StepRunner.run(Job.java:2041) at java.lang.Thread.run(Unknown Source)

Checking the Environment Hub (http://glwebapp:8000/PSEMHUB/hub), it returns:

Registered Hosts Summary – 8.49.15.

Hostname OS Type OS Version IP Address State Peer ID Peer Type Peer Version
GLDBASE Windows 2003 5.2 10.18.14.31 Running 4 Agent 8.49.15.
GLWEBAPP Windows 2003 5.2 10.18.14.30 Running 1 Agent 8.49.15.
GLWEBAPP Windows 2003 5.2 10.18.14.30 Not Running 2 Change Assistant 8.49.15.

Note that from the above table, the Change Assistant is not running.

Solution:

In Change Assistant, under Tools > Options, the Change Assistant Mode is set to Perform PeopleSoft Upgrade. It should be set to Apply Application Update.

Application Designer Crashes

Posted by on December 22, 2008 No comments

Problem:

When recreating database (on page 420-421 of Enterprise PeopleTools 8.49 Installation for Microsoft SQL Server), Application Designer crashes on record 2746/4009 while copying project PPLTL84CUR.

Solution:

1. Run Application Designer on glwebapp, not gldbase

2. Copy the PTPATCH project using Application Designer

Others suggestions:

FSCM MP5 partially applied to node. Inconsistent libraries for Application Designer. Reapply MP5.

Allocate more memory to the Java runtime.

Error running rel849n.sql

Posted by on December 21, 2008 No comments

The following errors appear when running rel849n in SQL Server:

Msg 1913, Level 16, State 1, Line 2
The operation failed because an index or statistics with name ‘PSAPSROLECLASS’ already exists on table ‘PSROLECLASS’.
Msg 1913, Level 16, State 1, Line 2
The operation failed because an index or statistics with name ‘PSCPSTREELEAF’ already exists on table ‘PSTREELEAF’.

Solution:

These objects already exist in the database, and the error can be ignored.

Starting PeopleSoft Services

Posted by on December 20, 2008 No comments

Starting Application Server
To start the application server, log on to the gl-web-app server (10.18.14.30) using Terminal Services Client. Open Command Prompt and enter the following commands (in bold red):

C:> E:
E:> cd PSOFTFS900appserv
E:PSOFTFS900appserv> psadmin.exe

Enter the following options:
1) Application Server
1) Administer a domain
1) FSDMO
1) Boot this domain
1) Boot (Serial Boot)

Starting Batch Server/Process Scheduler

To start the batch server, log on to the gl-web-app server (10.18.14.30) using Terminal Services Client. Open Command Prompt and enter the following commands:

E:
cd PSOFTFS900appserv
psadmin.exe

Enter the following options:
2) Process Scheduler
1) Start a Process Scheduler Server
1) FSDMO

Starting Web Server (BEA WebLogic)

To start the batch server, log on to the gl-web-app server (10.18.14.30) using Terminal Services Client. Open Command Prompt and enter the following commands:

E:
Cd PSOFTFS900webservfsdmobin
startWebLogicAdmin.cmd

The final line shows:

Open a second Command Prompt and enter the following commands:

E:
Cd PSOFTFS900webservfsdmobin
startManagedWebLogic.cmd PIA

The final line shows:

Starting Web Server (IBM WebSphere)

Single Node
cd /d E:PSOFTFS900webservfsdevbin
startserver.bat server1 -profileName fsdev

Multi Node
cd /d E:PSOFTFS900webservPIA_fsdmobin
startserver.bat server1 -profileName PIA_fsdmo

Distribution Status stays at Posting

Posted by on December 19, 2008 No comments

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.

Running PSAE Programs

Posted by on December 18, 2008 No comments

Task B-8-8: Running PeopleTools Conversions

In Task B-8-8: Running PeopleTools Conversions, on page 432 of the “Enterprise PeopleTools 8.49 Installation for Microsoft SQL Server”:

On glwebapp:

E:PSOFTFS900binclientwinx86psae -CD FSDMO -CT MICROSFT -CO VP1 -CP VP1 -R INSTALL -AI UPG844PORTAL

E:PSOFTFS900binclientwinx86psae -CD FSDMO -CT MICROSFT -CO VP1 -CP VP1 -R INSTALL -AI UPGQRYDUPHED

E:PSOFTFS900binclientwinx86psae -CD FSDMO -CT MICROSFT -CO VP1 -CP VP1 -R INSTALL -AI UPGPTSMDAT

E:PSOFTFS900binclientwinx86psae -CD FSDMO -CT MICROSFT -CO VP1 -CP VP1 -R INSTALL -AI UPGPT846PP

E:PSOFTFS900binclientwinx86psae -CD FSDMO -CT MICROSFT -CO VP1 -CP VP1 -R INSTALL -AI UPGPT848PP

Note: You may need to copy and paste the above lines into NotePad, and then copy these lines and paste into Command Line.

Task B-11: Running VERSION Application Engine Program

E:PSOFTFS900binclientwinx86psae -CD FSDMO -CT MICROSFT -CO VP1 -CP VP1 -R INSTALL -AI VERSION

Errors while running createvw.dms

Posted by on December 17, 2008 No comments

Errors while running createvw.dms:

Related language record RE_LANDLORD_LG used by record RE_LANDLORD not found. (20,52)
Related Language Record VCHR_SRCHLG1_VW used by VCHR_SRCHCRT_VW not found (20,52)
Related language record BI_SHP_LANG_VW used by record BI_SHP_ADDR_VW2 not found. (20,52)

Data Mover crashes out.

Solution:

Did not perform step 10 of the PT 8.49.15 Product Patch User Documentation (https://psft-updates.oracle.com/ice/Resolutions/768890/PT84915UserDoc_rev2.htm). Using Application Designer, log on as user VP1 and copy project PATCH849. Then, in Data Mover, log on as VP1 and rerun CREATEVW.DMS.

10. Copy Patch Project – ONLY if PATCH849 exists –

Note: If no database changes have been made in PT 8.49 by the time this patch is released, the PATCH849 project will not exist in the projects folder and this step can be ignored.

a. Using PeopleTools 8.49.15, launch Application Designer, and sign on to the database as a PeopleSoft User. [VP1]
b. Select Tools > Copy Project > From File
c. Enter projects and select PATCH849 from the list of projects
d. Select Options and highlight the languages Common and English ONLY.
e. Select Copy to begin copying updated PeopleTools objects to your database.

After rerunning CREATEVW.DMS, the last four lines of the CREATEVW.LOG file shows:

SQL Views: 27267
Ended: Wed Dec 17 18:23:25 2008
Successful completion
Script Completed.

Other steps to try:

Stop SQL Server services and restart.
Log on as user VP1 when running createvw.dms

Reference:

http://www.pinpointps.com/?q=node/59

Restarting data mover after a crash
A data mover script can be restarted by coding in the DMS ‘set start after record name’ before the Import * command. If the record is name ps_tablename, then do not code the ‘ps_’, just code tablename.

Attempted to create views using Application Designer: In Application Designer, click Ctrl+F7 (Insert > Definitions from Project…), and search for all Records. Select All records and insert them into the current project (takes about 10 minutes to complete). Then click Build > Project and check only Create Views (modify other settings as necessary). Build the SQL script, and after creating,

COBOL batch programs not running

Posted by on December 11, 2008 No comments

Problem:

After installing PeopleSoft Financials, the COBOL batch programs not running.

Solution:

1. Download Micro Focus Cobol Net Express Edition from:

http://www.download.com/Net-Express-with-NET/3000-2069_4-10866201.html
http://microfocus.com/products/netexpress/
http://microfocus.com/products/netexpresswithnet/index.asp

2. Install Micro Focus Cobol Net Express With .Net on the batch server. Disable the option to install .Net, as it will require Microsoft Visual Studio 2008.

CopyUpdateProject fails

Posted by on December 8, 2008 No comments

Problem:

In Change Assistant, the CopyUpdateProject step fails:

Step Failed at: Copy Update Project

Contents of E:tempsoftwareupdateFSCM900_MP5{bb2f249c-b59c-11dd-aaa1-aa1d90f67f05}FSCM900_MP5.log:

PeopleSoft Project Command Line
Copy From File
Project Name: FSCM900_MP5
Tools Release: 8.49.15
2008-12-08 : 10.55.54

-CT Source Database Type = MICROSFT
-CS Source Database Server =
-CD Source Database Name = FSDMO
-CO Source Database Operator = VP1
-FP File Path = E:/staging/softwareupdateFSCM900_MP5{bb2f249c-b59c-11dd-aaa1-aa1d90f67f05}
-CL Commit Limit = 100
-AF Keep Target Audit Flags = 1
-DDL Keep Target DDL = 1
-CFD Keep Target Chartfield PageField Display Size = 1
-CFF Keep Target Chartfield DbField Format = 1
-PPL Keep Target Portal Structure Permission List = 1
-OBJ Object Types = All
-LNG Languages = ENG,COMMON

Project FSCM900_MP5 already exists, continuing processing, switch set to overwrite.
Transforming XML. Please be patient.
Processing Language : English
Processing Language : COMMON

Records Application Upgrade Copy started: 2008-12-08-10.58.38

Contents of E:tempsoftwareupdateFSCM900_MP5{bb2f249c-b59c-11dd-aaa1-aa1d90f67f05}FSCM900_MP5_CA.log

Command Line: E:PSOFTFS900binclientwinx86pside.exe -CT MICROSFT -CS -CD FSDMO -CO VP1 -CP * -PJFF FSCM900_MP5 -FP E:/staging/softwareupdateFSCM900_MP5{bb2f249c-b59c-11dd-aaa1-aa1d90f67f05} -LF E:tempsoftwareupdateFSCM900_MP5{bb2f249c-b59c-11dd-aaa1-aa1d90f67f05}FSCM900_MP5.log -CL 100 -AF 1 -DDL 1 -OBJ All -LNG ENG,COMMON -PPL 1 -CFD 1 -CFF 1 -HIDE -QUIET -SS NO -SN NO

Solution:

1. Batch server was running. Stopped batch server and restarted the CopyUpdateProject step.
2. Batch server started, and then restarted the CopyUpdateProject step.
3. Application server was running, stopped it and then restarted the CopyUpdateProject step.

(Advised by consultant) Skipped this step as it was previously deployed under IBM WebSphere.